Appendix 2. List of HTTP errors
Some status codes (errors) are provided by the HTTP protocol. AntDM shows it as is HTTPxxx.
4xx Client errors
|
400
|
Bad Request
|
The server cannot or will not process the request due to an apparent client error (e.g., malformed request syntax, size too large, invalid request message framing, or deceptive request routing)
|
|
401
|
Unauthorized
|
Similar to 403 Forbidden, but specifically for use when authentication is required and has failed or has not yet been provided. The response must include a WWW-Authenticate header field containing a challenge applicable to the requested resource.
|
|
403
|
Forbidden
|
The request was valid, but the server is refusing action. The user might not have the necessary permissions for a resource, or may need an account of some sort.
|
|
404
|
Not Found
|
The requested resource could not be found but may be available in the future. Subsequent requests by the client are permissible.
|
|
406
|
Not Acceptable
|
The requested resource is capable of generating only content not acceptable according to the Accept headers sent in the request.
|
|
407
|
Proxy Authentication Required
|
The client must first authenticate itself with the proxy.
|
|
408
|
Request Timeout
|
The server timed out waiting for the request. According to HTTP specifications: "The client did not produce a request within the time that the server was prepared to wait. The client MAY repeat the request without modifications at any later time
|
|
410
|
Gone
|
Client error response code indicates that access to the target resource is no longer available at the origin server and that this condition is likely to be permanent.
|
|
|
|
|
|
|
|
|
5xx Server errors
|
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 fulfil the request.
|
|
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
|
|
504
|
Gateway Timeout
|
The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.
|
|
|
|
|
|
|
|
|
In details see here
The help manual was created with Dr.Explain
Unregistered version