HTTP Status Codes - Reason Phrases

From the W3C - World Wide Web Consortium

The individual values of the numeric status codes defined for HTTP/1.1, and an example set of corresponding Reason-Phrase's, are presented below. The reason phrases listed here are only recommendations - they MAY be replaced by local equivalents without affecting the protocol.

Reason Phrases

10.1 - 1xx Informational
Status Code           Reason Phrase
100  Section 10.1.1:  Continue
101  Section 10.1.2:  Switching Protocols
10.2 - 2xx Successful
Status Code           Reason Phrase
200  Section 10.2.1:  OK
201  Section 10.2.2:  Created
202  Section 10.2.3:  Accepted
203  Section 10.2.4:  Non-Authoritative Information
204  Section 10.2.5:  No Content
205  Section 10.2.6:  Reset Content
206  Section 10.2.7:  Partial Content
10.3 - 3xx Redirection
Status Code           Reason Phrase
300  Section 10.3.1:  Multiple Choices
301  Section 10.3.2:  Moved Permanently
302  Section 10.3.3:  Found
303  Section 10.3.4:  See Other
304  Section 10.3.5:  Not Modified
305  Section 10.3.6:  Use Proxy
307  Section 10.3.8:  Temporary Redirect
10.4 - 4xx Client Error
Status Code           Reason Phrase
400  Section 10.4.1:  Bad Request
401  Section 10.4.2:  Unauthorized
402  Section 10.4.3:  Payment Required
403  Section 10.4.4:  Forbidden
404  Section 10.4.5:  Not Found
405  Section 10.4.6:  Method Not Allowed
406  Section 10.4.7:  Not Acceptable
407  Section 10.4.8:  Proxy Authentication Required
408  Section 10.4.9:  Request Time-out
409  Section 10.4.10: Conflict
410  Section 10.4.11: Gone
411  Section 10.4.12: Length Required
412  Section 10.4.13: Precondition Failed
413  Section 10.4.14: Request Entity Too Large
414  Section 10.4.15: Request-URI Too Large
415  Section 10.4.16: Unsupported Media Type
416  Section 10.4.17: Requested range not satisfiable
417  Section 10.4.18: Expectation Failed
10.5 - 5xx Server Error
Status Code           Reason Phrase
500  Section 10.5.1:  Internal Server Error
501  Section 10.5.2:  Not Implemented
502  Section 10.5.3:  Bad Gateway
503  Section 10.5.4:  Service Unavailable
504  Section 10.5.5:  Gateway Time-out
505  Section 10.5.6:  HTTP Version not supported

HTTP status codes are extensible. HTTP applications are not required to understand the meaning of all registered status codes, though such understanding is obviously desirable. However, applications MUST understand the class of any status code, as indicated by the first digit, and treat any unrecognized response as being equivalent to the x00 status code of that class, with the exception that an unrecognized response MUST NOT be cached. For example, if an unrecognized status code of 431 is received by the client, it can safely assume that there was something wrong with its request and treat the response as if it had received a 400 status code. In such cases, user agents SHOULD present to the user the entity returned with the response, since that entity is likely to include human readable information which will explain the unusual status.


 


SEO Consultants Directory