HTTP Status Code Lookup

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.

The server has received and is processing the request, but no response is available yet.

The request has succeeded.

The request has succeeded and a new resource has been created.

The request has been accepted for processing, but processing is not complete.

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.

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

The resource resides temporarily under a different URI.

The response can be found under a different URI using a GET method.

Indicates the resource has not been modified since the version specified.

The request should be repeated with another URI, but future requests can still use the original.

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

The server cannot process the request due to a client error.

Authentication is required and has failed or not been provided.

Reserved for future use.

The request was valid, but the server is refusing to respond to it.

The requested resource could not be found.

A request method is not supported for the requested resource.

The requested resource is capable of generating only content not acceptable per the Accept headers.

The server timed out waiting for the request.

The request could not be completed due to a conflict with the current state of the resource.

The resource requested is no longer available and will not be available again.

The request did not specify the length of its content.

The request is larger than the server is willing or able to process.

The URI provided was too long for the server to process.

The request entity has a media type which the server does not support.

This code was defined as an April Fools joke and is not expected to be implemented.

The request was well-formed but could not be followed due to semantic errors.

The server is unwilling to process a request that might be replayed.

The user has sent too many requests in a given amount of time.

The server is unwilling to process the request because header fields are too large.

A server operator has received a legal demand to deny access to a resource.

A generic error message given when an unexpected condition was encountered.

The server either does not recognize the request method, or lacks the ability to fulfil it.

The server was acting as a gateway 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 and did not receive a timely response from the upstream server.

The server does not support the HTTP protocol version used in the request.

The client needs to authenticate to gain network access.