HTTP status codes

Waiting for the client to emit the body of the request.

The server has agreed to change protocol.

The server is processing the request, but no response is available yet. For WebDAV.

The server returns some response headers before final HTTP message.

Standard response for successful HTTP requests.

The request has been fulfilled, resulting in the creation of a new resource.

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

The server is a transforming proxy that received a 200 response from its origin, but is returning a modified version.

The server successfully processed the request, but is not returning any content.

The server successfully processed the request, but is not returning any content. The requester should reset the form.

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

The message body contains an XML message and can contain multiple response codes.

Used inside a DAV: propstat response element to avoid enumerating the internal members of multiple bindings to the same collection repeatedly.

The server has fulfilled a GET request for the resource, and the response is a representation of the result of one or more instance-manipulations applied to the current instance.

The request has more than one possible response. The user should select one of them.

The URL of the requested resource has been changed permanently. The new URL is given in the response.

The URI of requested resource has been changed temporarily. The new URI is given in the response.

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

The resource has not been modified since the last request.

The requested resource is available only through a proxy, the address for which is provided in the response.

No longer used. Originally meant "Subsequent requests should use the specified proxy."

The requested resource is temporarily located at another URI.

The requested resource is permanently located at another URI.

The server cannot or will not process the request due to a client error (e.g., malformed request syntax).

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

Reserved for future use. The original intention was that this code might be used as part of some form of digital cash or micropayment scheme.

The client does not have access rights to the content.

The server can not find the requested resource.

The request method is known by the server but is not supported by the target resource.

The server cannot produce a response matching the list of acceptable values defined in the request's headers.

The client must first authenticate itself with the proxy.

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 requested resource 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.

The server refuses to brew coffee because it is a teapot. (April Fools' joke from 1998)

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

The server understands the content type of the request entity, but was unable to process the contained instructions.

The resource that is being accessed is locked.

The request failed due to failure of a previous request.

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

The client should switch to a different protocol such as TLS/1.0, given in the Upgrade header field.

The origin server requires the request to be conditional.

The user has sent too many requests in a given amount of time ("rate limiting").

The server is unwilling to process the request because either an individual header field, or all the header fields collectively, are too large.

The user requests an illegal resource, such as a web page censored by a government.

The server has encountered a situation it doesn't know how to handle.

The request method is not supported by the server and cannot be handled.

The server, while acting as a gateway or proxy, received an invalid response from the upstream server.

The server is not ready to handle the request, often due to maintenance or overloading.

The server, while acting as a gateway or proxy, did not get a response in time from the upstream server.

The HTTP version used in the request is not supported by the server.

The server has an internal configuration error: 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 fulfill it.

The client needs to authenticate to gain network access.