HTTP Status Code Reference

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 the final HTTP message.

The request has succeeded.

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

The request has been accepted for processing, but the processing has not been completed.

The returned metadata is from a local or third-party copy, not the origin server.

The server has fulfilled the request but there is no content to return.

The server has fulfilled the request and the client should reset the document view.

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

A WebDAV response that conveys information about multiple resources.

The members of a DAV binding have already been enumerated in a previous reply.

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

There are multiple options for the resource that the client may follow.

The resource has been permanently moved to a new URL.

The resource resides temporarily under a different URI.

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

The resource has not been modified since the last request.

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

The request and future requests should be sent to the provided URI.

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

Authentication is required and has failed or has not been provided.

Reserved for future use. Sometimes used for digital payment systems.

The server understood the request but refuses to authorize it.

The requested resource could not be found on the server.

The request method is not supported for the requested resource.

The resource cannot generate content acceptable according to the Accept headers.

Authentication with the proxy is required before the request can be served.

The server timed out waiting for the request.

The request conflicts with the current state of the target resource.

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

The request did not specify the length of its content as required by the server.

One or more preconditions in the request header fields evaluated to false.

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

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

The media format of the request data is not supported by the server.

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

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

The server refuses the attempt to brew coffee with a teapot.

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

The request was well-formed but the server was unable to process the contained instructions.

The resource that is being accessed is locked.

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

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

The client should switch to a different protocol.

The 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.

The resource is unavailable due to legal demands (censorship, court order).

The server encountered an unexpected condition that prevented it from fulfilling the request.

The server does not support the functionality required to fulfill the request.

The server received an invalid response from an upstream server.

The server is currently unable to handle the request.

The server did not receive a timely response from an upstream server.

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

The server has an internal configuration error during content negotiation.

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 fulfill it.

The client needs to authenticate to gain network access.