HTTP error codesHere is a list of the common 'error codes'. Some are not errors are all, they are confirmations of one kind or another, such as the often-seen 304. The correct name is status codes, for this reason - but we still often call them error codes, wrongly of course. Here are the groups and broad meanings:
0 = No Connection
1xx - Informational
2xx - Success
3xx - Redirection
4xx - Client Error
5xx - Server Error
------------------------
- 0 - Network Connection Error
- 100 - Continue [request received, send the request body]
- 101 - Switching Protocols
- 102 - Processing [WebDAV]
- 122 - Requested URL too long
- 200 - OK / no error
- 201 - Created [new resource created]
- 202 - Accepted [processing started but not yet completed - depends on other factors]
- 203 - Non-Authoritative Information
- 204 - No Content
- 205 - Reset Content
- 206 - Partial Content [this is a message that a file has been partially downloaded. Used by tools like wget to enable resuming of interrupted downloads]
- 207 - Multi-Status [WebDAV - an XML message with additional codes]
- 300 - Multiple Choices [more info needed]
- 301 - Redirect - permanent [the 301 is always used for ANY redirect now]
- 302 - Found elsewhere [this code is often used incorrectly for a temporary redirect. A 302 DOES NOT mean "temporary redirect". The 302 is NEVER intentionally used FOR ANY PURPOSE now. Be careful: Apache may default to this]
- 303 - See Other [elsewhere - with various parameters - can be used for language redirects]
- 304 - Not Modified [ie 'unchanged ' - this is an 'OK' code telling the browser the page is unchanged and there is no need to download it again. You should see this code frequently - it is a 'good' code]
- 305 - Use Proxy [some browsers handle this wrongly]
- 306 - Switch Proxy [not used now]
- 307 - Temporary Redirect [elsewhere - another version with different parameters]
Both 303 and 307 are probably more accurate for use as a temporary redirect, which is one of the reasons why we never use a 302 now, and its use may attract unwanted results - 302 does not mean temp redirect and should not be used for that - Apache's use of it is incorrect. In addition a 302 is an attackers' tool and IT IS NEVER USED DELIBERATELY NOW FOR ANY PURPOSE.
- 400 - Bad request
- 401 - Unauthorized [login+password required]
- 402 - Payment Required
- 403 - Forbidden
- 404 - Page Not Found
- 405 - Method Not Allowed
- 406 - Not Acceptable [normally returned for an attack]
- 407 - Proxy Authentication Required
- 408 - Request Timeout
- 409 - Conflict
- 410 - Gone [page has moved]
- 411 - Length Required
- 412 - Precondition Failed
- 413 - Request Entity Too Large
- 414 - Request-URL Too Long
- 415 - Unsupported Media Type
- 416 - Requested Range Not Satisfiable
- 417 - Expectation Failed
- 422 - Unprocessable entity
- 423 - Locked
- 424 - Failed dependency
- 500 - Internal Server Error [you will often see this fail when adjusting an htaccess script - go back to the last known good version of the htaccess file, then try again]
- 501 - Not Implemented
- 502 - Bad Gateway
- 503 - Service Unavailable [this code IS acceptable for maintenance offlines but a 302 IS NOT, even if the resource has temporarily moved - use a 301]
- 504 - Gateway Timeout
- 505 - HTTP Version Not Supported
- 506 - Variant also negotiates
- 507 - Insufficient storage
- 510 - Not extended [on a Windows server you can get this with a database connectivity issue. A reported fix is to limit sessions per user to a max of 10, this fixes it by fixing the memory leakage which occurs with unlimited sessions, which uses up all the server memory, crashing it]
- 512 - Not Supported [might be seen on a server communicating with another server, for example when updating, but fails due to going through a proxy]
- 990 - Blocked by robots.txt file
- 999 - Undefined Error
Additional error codesThere are some error codes in the 000s that are not universally recognised.
Browser error messagesYou will also see browser error messages, when a page load fails, that can have similar meanings to some of the above. For example the 'Cannot Complete' message, which will say something like, "Firefox has detected that the URL request cannot be satisfied because the server is delivering the request in a form that will never complete".
This normally results from a faulty script within the htaccess file. Revert the last one that you changed.
===========================================================
Spurious HTTP error codes - codes that are unlikely to ever be officially recognised :)
0a - This is not the operator or room service, try google
8 - Wait while the server consults the I-Ching for what page to serve
66 - Consult google maps, we don't know which road you want
69 - Turn your webcam off before visiting this site, you are embarrassing us
83 - The server requires your social security number and a credit card number in order to process your request
99 - No chocolate Flake available at present
101a - Everything possible went wrong with your request
101b - No Dalmations currently available
108 - You are very lucky, no one else has got through today
401a - How many times are you going to try that dud password
403a - We are so tired of your weak, loser bot attacks - try something new
404a - Hey hero, forget trying to type the address after a liquid lunch, just let google do it
411a - Ooh, that long?
512 - Server has forgotten your request due to insufficient RAM - please resend
666 - This is a Windows server, your request for a Linux resource cannot be processed
666a - You are connected to the new Windows / GoogleApps central CloudServer - let us help you update your profile ;-)
1984 - Bandwidth exceeded due to multiple wiretaps. Please get a faster broadband connection or reduce the number of commercial and government agencies monitoring your line
2000 - The server may pack up when the date changes - or not
9999 - We issued so many errors today, this is the last - goodnight
|
|
HTTP Error Codes
