HTTP Status Codes Reference
Searchable reference of standard HTTP response status codes, category definitions, and specifications.
The server has received the request headers and the client should proceed to send the request body.
The requester has asked the server to switch protocols.
Standard response for successful HTTP requests.
The request has been fulfilled and resulted in a new resource being created.
The request has been accepted for processing, but processing is not completed.
The server successfully processed the request, but is not returning any content.
The server is delivering only part of the resource due to a range header sent by the client.
This and all future requests should be directed to the given URI.
The resource resides temporarily under a different URI.
Indicates that the resource has not been modified since the version specified by the request headers.
The request should be repeated with another URI, preserving the method.
The request and all future requests should be repeated using another URI.
The server cannot or will not process the request due to an apparent client error.
Authentication is required and has failed or has not yet been provided.
The request was valid, but the server is refusing action. The user might not have necessary permissions.
The requested resource could not be found but may be available in the future.
A request method is not supported for the requested resource.
The server timed out waiting for the request.
The request could not be processed because of conflict in the current state of the resource.
The request is larger than the server is willing or able to process.
The request entity has a media type which the server or resource does not support.
The request was well-formed but was unable to be followed due to semantic errors.
The user has sent too many requests in a given amount of time (rate limiting).
A generic error message, given when an unexpected condition was encountered.
The server either does not recognize the request method, or it lacks the ability to fulfil the request.
The server was acting as a gateway or proxy and received an invalid response from the upstream server.
The server is currently unavailable (overloaded or down for maintenance).
The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.