source: Validate External Links/http_codes.txt@ 1119

Last change on this file since 1119 was 1069, checked in by iritscen, 7 years ago

ValExtLinks: IW links now reported as separate category from OK links. RD links that are just redirecting from http:// to https:// are now regarded as OK.

File size: 3.3 KB
RevLine 
[1064]1==HTTP Response Status Code Reference==
2For use with ValExtLinks script (http://wiki.oni2.net/ValExtLinks).
[1068]3Only codes understood by ValExtLinks are listed here.
[1064]4Source: https://en.wikipedia.org/wiki/List_of_HTTP_status_codes
5
6
7--2xx: Success--
8This class of status codes indicates the action requested by the client was received, understood, accepted, and processed successfully.
9
10200 OK
11 Standard response for successful HTTP requests.
12
13
14--3xx: Redirection--
15This 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
17301 Moved Permanently
18 This and all future requests should be directed to the given URI.
19
20302 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
[1068]23303 See Other
24 The response to the request can be found under another URI using a GET method.
25
[1064]26307 Temporary Redirect
27 The request should be repeated with another URI; however, future requests should still use the original URI.
28
[1068]29308 Permanent Redirect
30 The request and all future requests should be repeated using another URI.
[1064]31
[1068]32
[1064]33--4xx: Client Errors--
34The 4xx class of status codes is intended for situations in which the client seems to have erred.
35
36401 Unauthorized
37 Similar to 403 Forbidden, but specifically for use when authentication is required and has failed or has not yet been provided.
38
39403 Forbidden
40 The request was valid, but the server is refusing action. The user might not have the necessary permissions for a resource.
41
42404 Not Found
43 The requested resource could not be found but may be available in the future. Subsequent requests by the client are permissible.
44
45405 Method Not Allowed
46 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.
47
48406 Not Acceptable
49 The requested resource is capable of generating only content not acceptable according to the Accept headers sent in the request.
50
51410 Gone
52 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.
53
54
55--5xx: Server Errors--
[1069]56The server failed to fulfill an apparently valid request.
[1064]57
58500 Internal Server Error
59 A generic error message, given when an unexpected condition was encountered and no more specific message is suitable.
60
61501 Not Implemented
62 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).
63
64503 Service Unavailable
65 The server is currently unavailable (because it is overloaded or down for maintenance). Generally, this is a temporary state.
Note: See TracBrowser for help on using the repository browser.