HTTP Status Code Lookup

The server has received the request headers and the client should proceed to send the request body.

The server is switching protocols as requested by the client.

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

Used to return some response headers before final HTTP message.

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 is a transforming proxy that received a 200 OK from its origin.

The server has successfully fulfilled the request and there is no additional content to send.

Tells the user agent to reset the document which sent this request.

The server is delivering only part of the resource due to a range header sent by the client.

Conveys information about multiple resources in situations where multiple status codes might be appropriate.

The members of a DAV binding have already been enumerated in a preceding part of the response.

The server has fulfilled a request for the resource, and the response is a representation of the result of instance manipulations.

Indicates multiple options for the resource from which the client may choose.

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

Tells the client to look at another URL (temporarily).

The response to the request can be found under another URI using a GET method.

Indicates that the resource has not been modified since the version specified by the request headers.

The requested resource is available only through a proxy.

The request should be repeated with another URI with the same method.

The request and all future requests should be repeated using another URI with the same method.

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.

Reserved for future use; originally intended for digital cash systems.

The request was valid, but the server is refusing action.

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 requested resource is capable of generating only content not acceptable according to the Accept headers.

The client must first authenticate itself with the proxy.

The server timed out waiting for the request.

Indicates that the request could not be processed because of conflict in the current state of the resource.

Indicates that the resource requested is no longer available and will not be available again.

The request did not specify the length of its content, which is required by the requested resource.

The server does not meet one of the preconditions that the requester put on the request.

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 or resource does not support.

The client has asked for a portion of the file, but the server cannot supply that portion.

The server cannot meet the requirements of the Expect request-header field.

Any attempt to brew coffee with a teapot should result in the error code 418.

The request was directed at a server that is not able to produce a response.

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

The resource that is being accessed is locked.

The request failed because it depended on another request that failed.

Indicates that the server is unwilling to risk processing a request that might be replayed.

The client should switch to a different protocol.

The origin server requires the request to be conditional.

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

The server is unwilling to process the request because its 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 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.

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

Transparent content negotiation for the request results in a circular reference.

The server is unable to store the representation needed to complete the request.

The server detected an infinite loop while processing the request.

Further extensions to the request are required for the server to fulfil it.

The client needs to authenticate to gain network access.