|
|
Posted by Paul Ding on 12/20/05 21:38
On Tue, 20 Dec 2005 07:45:46 +0000, Craig Cockburn
<craig@siliconglen.com> posted something that included:
>Does anyone know if there is a definitive list of 6xx http return codes
>anywhere?
To answer your question, yes. I know, and many others know as well.
Although you didn't ask for it, I might mention that the definitive
list of HTTP return codes is, as you might expect, in the RFC for the
HTTP protocol. The latest version of HTTP is 1.1 and the document is
RFC 2616.
And although you *really* didn't ask it, here's a list of the 6xx
return codes in HTTP:
And just in case you didn't catch on, here is a definitive list of all
http error codes in all ranges:
1xx return codes are informational
100 Continue
101 Switching Protocols
2xx return codes indicate success
200 OK
201 Created
202 Accepted
203 Non-Authoritative Information
204 No Content
205 Reset Content
206 Partial Content
3xx return codes require redirection
300 Multiple Choices
301 Moved Permanently
302 Found
303 See Other
304 Not Modified
305 Use Proxy
306 (Unused)
307 Temporary Redirect
4xx return codes indicate client error
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
5xx error codes indicate server error
500 Internal Server Error
501 Not Implemented
502 Bad Gateway
503 Service Unavailable
504 Gateway Timeout
505 HTTP Version Not Supported
--
If we're losing 40-130 species a day,
How come nobody can itemize them?
And why can't fruitflies be one of them?
Navigation:
[Reply to this message]
|