Loading...
Complete reference guide for HTTP status codes. Quick lookup with descriptions and explanations.
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 and the server has agreed to do so.
The server has received and is processing the request, but no response is available yet.
The request has succeeded.
The request has been fulfilled and resulted in a new resource being created.
The request has been accepted for processing, but the processing has not been completed.
The server successfully processed the request and 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 URI of the requested resource has been changed temporarily.
The resource has not been modified since the version specified by the request headers.
The request should be repeated with another URI but future requests should still use the original URI.
The request and all future requests should be repeated using another URI.
The server cannot or will not process the request due to something perceived to be a 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 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 cannot handle the request (because it is 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.