| 1 |
==HTTP Response Status Code Reference== |
| 2 |
For use with ValExtLinks script (http://wiki.oni2.net/ValExtLinks). |
| 3 |
Only codes encountered so far by ValExtLinks are listed here. |
| 4 |
Source: https://en.wikipedia.org/wiki/List_of_HTTP_status_codes |
| 5 |
|
| 6 |
|
| 7 |
--2xx: Success-- |
| 8 |
This class of status codes indicates the action requested by the client was received, understood, accepted, and processed successfully. |
| 9 |
|
| 10 |
200 OK |
| 11 |
Standard response for successful HTTP requests. |
| 12 |
|
| 13 |
|
| 14 |
--3xx: Redirection-- |
| 15 |
This class of status code indicates the client must take additional action to complete the request. Many of these status codes are used in URL redirection. |
| 16 |
|
| 17 |
301 Moved Permanently |
| 18 |
This and all future requests should be directed to the given URI. |
| 19 |
|
| 20 |
302 Found |
| 21 |
This is an example of industry practice contradicting the standard. The HTTP/1.0 specification required the client to perform a temporary redirect (the original describing phrase was "Moved Temporarily"), but popular browsers implemented 302 with the functionality of a 303 See Other. Therefore, HTTP/1.1 added status codes 303 and 307 to distinguish between the two behaviors. However, some Web applications and frameworks use the 302 status code as if it were the 303. |
| 22 |
|
| 23 |
307 Temporary Redirect |
| 24 |
The request should be repeated with another URI; however, future requests should still use the original URI. |
| 25 |
|
| 26 |
|
| 27 |
--4xx: Client Errors-- |
| 28 |
The 4xx class of status codes is intended for situations in which the client seems to have erred. |
| 29 |
|
| 30 |
401 Unauthorized |
| 31 |
Similar to 403 Forbidden, but specifically for use when authentication is required and has failed or has not yet been provided. |
| 32 |
|
| 33 |
403 Forbidden |
| 34 |
The request was valid, but the server is refusing action. The user might not have the necessary permissions for a resource. |
| 35 |
|
| 36 |
404 Not Found |
| 37 |
The requested resource could not be found but may be available in the future. Subsequent requests by the client are permissible. |
| 38 |
|
| 39 |
405 Method Not Allowed |
| 40 |
A request method is not supported for the requested resource; for example, a GET request on a form that requires data to be presented via POST, or a PUT request on a read-only resource. |
| 41 |
|
| 42 |
406 Not Acceptable |
| 43 |
The requested resource is capable of generating only content not acceptable according to the Accept headers sent in the request. |
| 44 |
|
| 45 |
410 Gone |
| 46 |
Indicates that the resource requested is no longer available and will not be available again. This should be used when a resource has been intentionally removed and the resource should be purged. Upon receiving a 410 status code, the client should not request the resource in the future. |
| 47 |
|
| 48 |
|
| 49 |
--5xx: Server Errors-- |
| 50 |
The server failed to fulfil an apparently valid request. |
| 51 |
|
| 52 |
500 Internal Server Error |
| 53 |
A generic error message, given when an unexpected condition was encountered and no more specific message is suitable. |
| 54 |
|
| 55 |
501 Not Implemented |
| 56 |
The server either does not recognize the request method, or it lacks the ability to fulfill the request. Usually this implies future availability (e.g., a new feature of a web-service API). |
| 57 |
|
| 58 |
503 Service Unavailable |
| 59 |
The server is currently unavailable (because it is overloaded or down for maintenance). Generally, this is a temporary state. |
