404 Error Page Return Status 200
Contents |
content and a result code. The result code is not shown to the user but processed by the program accessing the server 404 error page template ("client"). The result code is a code for the client telling it the
Google 404 Error Page
status of the content that it just sent There are several result codes, but the ones we'll look at now
404 Error Page Not Found
are "404" and "200". The result code 200 means that the page the client wanted is available and shown in the content. The result code 404 means that the page the client
Funny 404 Error Page
wanted is not available, but it can also return content (eg. a page saying "sorry, couldn't find your page"). Usually a normal web page returns 200, saying all is ok. Background - custom error pages Anyone who has ever looked for something special on the web will be able to tell stories of the "URL that got away" -- the link to the page with 404 error page design exactly the content you were looking for, that just doesn't work anymore. More and more, as people update their sites, URLs aren't valid for that long of a time - people moving from "Frontpage" to a content-management-system (CMS), or from one CMS to another. When they move, the old links usually become invalid, inside of the new site it shows the correct links, but coming from the outside it'll more than likely have old, obsolete links. So you find the page you were looking for -- and then just get a boring "404 - not found.". The people making these sites know that this is always going to happen sooner or later. So what can you do? Many sites now have custom error pages, so instead of landing on a plain "nothing found" page, you'll land on a page with lots of information about the sites, other links that might be interesting or similar to the link you were looking for. These custom error pages are a good thing - they help get people back on track, possibly helping them find the page they were originally looking for (or at least something similar). Sometime
from GoogleSign inHidden fieldsSearch for groups or messages
Contact Support About SISTRIX About us Careers Press Contact Support SISTRIX Toolbox Blog Resources Support Login Ask SISTRIX Webinar Seminar Tutorials Free Tools Videos HomeAsk SISTRIXHow to correctly return the HTTP status code 404 for an error https://www.sistrix.com/ask-sistrix/onpage-optimisation/http-status-code/4xx-client-error-404-error-page/how-to-correctly-return-the-http-status-code-404-for-an-error-page/ page How to correctly return the HTTP status code 404 for an error page http://serverfault.com/questions/401415/iis-7-returns-http-200-on-custom-404-error-page A 404 error page, also called an ErrorDocument 404, is, first and foremost, a page that informs the user that the requested resource does not exist. For example, if a user follows a link and the target page does not exist anymore, the webserver should show a 404 error page. This is not the only job 404 error of a 404 error page, though. When configured correctly, it informs the Google-Bot if a document actually exists. To ensure this happens the way it should, it is important that a 404 error page returns the correct HTTP status code 404 - otherwise the 404 page is defective. Why should a 404-error page return the correct HTTP status code and not be redirected, for example? ContentsHow do I return the 404 error page correct HTTP status code for a 404 error page?.htaccess and Apache webserver – correctly configuring the error pageWordPress CMS – correctly configuring the error pageWhy is it important for error pages to return the correct HTTP status code?Video Explanation by Matt Cutts / Google on this topicHow does Google handle "not found" pages that don't return a 404?Additional information about this topic:Do you like this post? How do I return the correct HTTP status code for a 404 error page? Webservers or the Content-Management-System (CMS) in use are often not set up correctly. This leads to the error page either returning the HTTP status code 200 (OK) or to a 301-redirect which sends the user as well as Google-Bot to another page. In both cases you would consider this to be a defective 404 page or a so-called soft 404 error. In this article, we will discuss the correct configuration of a 404 error page with the appropriate HTTP status code 404. We will actually differentiate between two use-cases: static 404 error page through the use of the Apache webserver and the .htaccess file using the WordPress CMS and the 404.php file in the theme-directory .htaccess and Apache webserver – correctly configuring the error page Regardless of whether y
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top IIS 7 returns HTTP 200 on custom 404 error page up vote 4 down vote favorite I have successfully set up custom static error pages for IIS7. IIS7 is currently working as a gateway to a Java tomcat application. The issue is that when the 404 error page is served it is served with a HTTP 200 status code header. I would like a way to configure IIS to continue to send a HTTP 404. The error page exists as a static page in the webroot. This is the main part of my web.config: