Server Header Status Code: Eating Status Codes in between!
April 16th, 2008 | 2,613 Views RSS Feed
Members at Webmaster World discusses about the problem of server header status codes. It is one of those topics that aren't touched often!
According to the Webmasters World thread, almost every server can return an incorrect HTTP status in the server header. But, Microsoft IIS (Internet Information Service) has a particularly long history of such errors been shown. For example:
Tried to set up a "custom 404" page, so your users get a friendly human like message.
When a bad URL is requested, the server responds with a 302 redirect to the custom error page (often called 404.html for example). Then the custom message is returned with a 200 OK http status.
The user agent is never informed by the server that the status of the requested URL should be 404. As a result a '302 temporary redirect' is issued. Unless the server informs the crawler about the correct status of requested URL, it won't matter what error code is written in the web page. Crawlers (including Googlebot) communicate with servers and not individual web pages.
Some of the interesting threads at Webmasters World:
"Any bad URL can be indexed according to the standard handling of an internal 302 redirect:
a) The content of the redirect's target URL is indexed.
b) With the original URL as the location.
So the bad URLs can start piling up as duplicate URLs for the same exact content."
Microsoft's .NET platform and IIS are particularly susceptible to this kind of errors. Inspite of the fact that the default error handling returns a correct 404 status code, still it is the way by which custom error messages are set up that pose the problem.
"For the IIS user, there is one other caution I should mention about 404 handling. If you are using .NET, then there are two levels of error handling: at the IIS level and at the .NET level. It is also common to find that only one of these two levels is set up correctly. So when you're stress testing your URLs, try a bad URL with an .asp (.aspx) extension, and also try a bad url with a .htm extension.
I felt it was important to focus on this issue in a dedicated thread – it's coming up much too often, both in threads here and in the sites of new clients that I evaluate.
The problem is by no means confined to IIS, either. For example, I see it on Apache servers running Tomcat for .jsp pages."
Click here to subscribe to our RSS feed to get a daily digest of news around search engine industry. PageTraffic SEO Blog is updated four times a day and is ranked as one of the best search engine resources blog by Pandia!
- del.icio.us
- Digg
- Furl
- Rojo
- StumbleUpon
- Technorati
- Yahoo!
Did you like this article?
Related Posts
Comments
2 Responses to “Server Header Status Code: Eating Status Codes in between!”
Leave a Reply
SEO Tools
FEATURED CATEGORIES
- adCenter (75)
- AdSense (108)
- AdWords (271)
- Analytics (45)
- AOL (5)
- Ask (98)
- Bing (8)
- Blogging (19)
- Copywriting (1)
- Directory (6)
- Google (1754)
- Industry News (763)
- Keyword Research & Targeting (18)
- Link Popularity (59)
- Live (78)
- Local SEO (7)
- Microsoft (126)
- Mobile Search (13)
- MSN (169)
- PageTraffic Happenings (5)
- Panama (21)
- Pay Per Click (33)
- Search Engine Conferences (153)
- Search Engines (92)
- SEO (214)
- SEO Tools (40)
- Social Media (18)
- Tips & Tricks (12)
- Web Marketing (4)
- Yahoo! (543)
- Yahoo! Search Marketing (64)






October 9th, 2008 at 2:47 pm
The comment is late, but I just stubbled upon this post
In IIS (assuming a custom 404 .html file), one can set a direct *directory* path to the 404-file, then IIS will give a valid "404 Not Found" status code.
Ofcourse, you cannot set directory paths to server side scripts like .asp and .php. But, you CAN set the "404 Not Found" code yourself:
404.php:
404.asp:
Set them up in IIS like: "/404.asp" or "/404.php" (Custom Errors tab of the virtual web site).
So it's not always a web server fault. My point of view: An admin should know how his system(s) work and it's also his job to inform his fellow colleagues of the support department. They are the onces who can inform customers about setting correct status codes in their server side scripts.
January 25th, 2009 at 9:47 am
ha – my comment is really late – but you should check out google new webmaster 404 code. Its javascript that you put on your 404 pages – it then displays automaticly other pages on your site that the user may have wanted to go though that are in the google index. You can also make sure your server status codes are setup good with a service like http://www.httpviewer.net/