|
|
|
|
 |
|
HTTP Status Codes
|
|
Very brief descriptions of HTTP Status Codes / Return Codes (RFC 2616)
|
100 | Continue |
101 | Switching Protocols |
200 | OK |
201 | Created |
202 | Accepted |
203 | Non-Authoritative Information |
204 | No Content |
205 | Reset Content |
206 | Partial Content |
300 | Multiple Choices |
301 | Moved Permanently |
302 | Found |
303 | See Other |
304 | Not Modified |
305 | Use Proxy |
306 | (Unused) |
307 | Temporary Redirect |
400 | Bad Request |
401 | Unauthorized |
402 | Payment Required |
403 | Forbidden |
404 | Not Found |
405 | Method Not Allowed |
406 | Not Acceptable |
407 | Proxy Authentication Required |
408 | Request Timeout |
409 | Conflict |
410 | Gone |
411 | Length Required |
412 | Precondition Failed |
413 | Request Entity Too Large |
414 | Request-URI Too Long |
415 | Unsupported Media Type |
416 | Requested Range Not Satisfiable |
417 | Expectation Failed |
500 | Internal Server Error |
501 | Not Implemented |
502 | Bad Gateway |
503 | Service Unavailable |
504 | Gateway Timeout |
505 | HTTP Version Not Supported |
|
|
|
|
|
|
|
|
Many of these you will never see in your web logs (for a number of unimportant reasons).
Perhaps of greater interest (and annoyance) is that search engine robot behaviour
differs when they encounter these
codes. One would expect a robot to never return when it finds a 301 (and eventually give up on a 404).
Sadly, some robots come back, day in, day out, continuing to look for pages you've been telling
it for months have 'Moved Permanently'.
After a time it's best to remove the 301 redirect and
let the robot get a 404, but again, sadly they keep on looking.
|
| |
|
[Content of this page last reviewed: 12-Jun-2004] |
|
|
|
|