Changeset 1127 for Validate External Links/http_codes.txt
- Timestamp:
- Mar 28, 2020, 3:08:29 AM (5 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
Validate External Links/http_codes.txt
r1069 r1127 34 34 The 4xx class of status codes is intended for situations in which the client seems to have erred. 35 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 36 39 401 Unauthorized 37 40 Similar to 403 Forbidden, but specifically for use when authentication is required and has failed or has not yet been provided. … … 52 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. 53 56 57 418 I'm a teapot 58 This is a joke response code used by some sites. Probably equivalent to a 200. 59 54 60 55 61 --5xx: Server Errors-- … … 62 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). 63 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 64 73 503 Service Unavailable 65 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.
Note:
See TracChangeset
for help on using the changeset viewer.