Oni2/Validate%20External%20Links/http_codes.txt

==HTTP Response Status Code Reference==
For use with ValExtLinks script (http://wiki.oni2.net/ValExtLinks).
Only codes understood by ValExtLinks are listed here.
Source: https://en.wikipedia.org/wiki/List_of_HTTP_status_codes


--2xx: Success--
This class of status codes indicates the action requested by the client was received, understood, accepted, and processed successfully.

200 OK
    Standard response for successful HTTP requests.


--3xx: Redirection--
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.

301 Moved Permanently
    This and all future requests should be directed to the given URI.

302 Found
    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.

303 See Other
    The response to the request can be found under another URI using a GET method.

307 Temporary Redirect
    The request should be repeated with another URI; however, future requests should still use the original URI.

308 Permanent Redirect
    The request and all future requests should be repeated using another URI.


--4xx: Client Errors--
The 4xx class of status codes is intended for situations in which the client seems to have erred.

400 Bad Request
    The server cannot or will not process the request due to an apparent client error (e.g., malformed request syntax).

401 Unauthorized
    Similar to 403 Forbidden, but specifically for use when authentication is required and has failed or has not yet been provided.

403 Forbidden
    The request was valid, but the server is refusing action. The user might not have the necessary permissions for a resource.

404 Not Found
    The requested resource could not be found but may be available in the future. Subsequent requests by the client are permissible.

405 Method Not Allowed
    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.

406 Not Acceptable
    The requested resource is capable of generating only content not acceptable according to the Accept headers sent in the request.

410 Gone
    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.

418 I'm a teapot
    This is a joke response code used by some sites. Probably equivalent to a 200.


--5xx: Server Errors--
The server failed to fulfill an apparently valid request.

500 Internal Server Error
    A generic error message, given when an unexpected condition was encountered and no more specific message is suitable.

501 Not Implemented
    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).

502 Bad Gateway
    The server was acting as a gateway or proxy and received an invalid response from the upstream server.

503 Service Unavailable
    The server is currently unavailable (because it is overloaded or down for maintenance). Generally, this is a temporary state.

530 Site is frozen
    Some Internet companies use this to indicate that a site is down, but usage is non-standard, so the site will have to be tried again later to see if the outage is due to a frozen account or something else.
Revision:	1127
Committed:	Sat Mar 28 02:08:29 2020 UTC (5 years, 6 months ago) by iritscen
Content type:	text/plain
File size:	3962 byte(s)
Log Message:	Val now counts redirects from youtu.be to youtube.com as OK links. These links will be reported on if the argument --show-yt-redirects is used. Renamed --show-https-upgrade to --show-https-upgrades for consistency. Also sorted the file and page suffix arrays and added some more items to them. Now handling status codes 400, 418, 502 and 530. Fixed incorrect nbsps in HTML report. Val is no longer confused by URLs ending in '(' or ')', or which contain a '%' towards the end.
#	Content
1	==HTTP Response Status Code Reference==
2	For use with ValExtLinks script (http://wiki.oni2.net/ValExtLinks).
3	Only codes understood 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	303 See Other
24	The response to the request can be found under another URI using a GET method.
25
26	307 Temporary Redirect
27	The request should be repeated with another URI; however, future requests should still use the original URI.
28
29	308 Permanent Redirect
30	The request and all future requests should be repeated using another URI.
31
32
33	--4xx: Client Errors--
34	The 4xx class of status codes is intended for situations in which the client seems to have erred.
35
36	400 Bad Request
37	The server cannot or will not process the request due to an apparent client error (e.g., malformed request syntax).
38
39	401 Unauthorized
40	Similar to 403 Forbidden, but specifically for use when authentication is required and has failed or has not yet been provided.
41
42	403 Forbidden
43	The request was valid, but the server is refusing action. The user might not have the necessary permissions for a resource.
44
45	404 Not Found
46	The requested resource could not be found but may be available in the future. Subsequent requests by the client are permissible.
47
48	405 Method Not Allowed
49	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.
50
51	406 Not Acceptable
52	The requested resource is capable of generating only content not acceptable according to the Accept headers sent in the request.
53
54	410 Gone
55	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.
56
57	418 I'm a teapot
58	This is a joke response code used by some sites. Probably equivalent to a 200.
59
60
61	--5xx: Server Errors--
62	The server failed to fulfill an apparently valid request.
63
64	500 Internal Server Error
65	A generic error message, given when an unexpected condition was encountered and no more specific message is suitable.
66
67	501 Not Implemented
68	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).
69
70	502 Bad Gateway
71	The server was acting as a gateway or proxy and received an invalid response from the upstream server.
72
73	503 Service Unavailable
74	The server is currently unavailable (because it is overloaded or down for maintenance). Generally, this is a temporary state.
75
76	530 Site is frozen
77	Some Internet companies use this to indicate that a site is down, but usage is non-standard, so the site will have to be tried again later to see if the outage is due to a frozen account or something else.