HTTP Status Codes

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 via the Upgrade header.

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

Used to return some response headers before the final HTTP message, allowing preloading of resources.

The request has succeeded. The meaning depends on the HTTP method used.

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 successfully processed the request but is not returning any content.

The server successfully processed the request and asks the client to reset the document view.

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

The response body contains multiple status codes for multiple independent operations (WebDAV).

The members of a DAV binding have already been enumerated and are not being included again (WebDAV).

The server has fulfilled a GET request and the response represents one or more instance-manipulations.

The request has more than one possible response. The user or user agent should choose one.

The resource has been permanently moved to a new URI. Future requests should use the new URI.

The resource resides temporarily under a different URI. The client should continue using the original URI.

The response can be found under another URI and should be retrieved using a GET method.

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. Method must not change.

The resource has been permanently moved. Future requests should use the new URI. Method must not change.

The server cannot process the request due to a client error (malformed syntax, invalid framing, etc.).

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

Reserved for future use. Some APIs use this to indicate a payment is required.

The server understood the request but refuses to authorize it.

The server cannot find the requested resource. The URI may be invalid.

The HTTP method is not allowed for the requested resource.

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

The client must first authenticate itself with the proxy.

The server timed out waiting for the request.

The request conflicts with the current state of the resource.

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

A precondition in the request headers was evaluated as false by the server.

The request entity is larger than limits defined by the server.

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

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

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

The server cannot meet the requirements of the Expect header.

The server refuses to brew coffee because it is, permanently, a teapot (RFC 2324).

The request was well-formed but contains semantic errors.

The resource is locked (WebDAV).

The request failed because it depended on another request that failed (WebDAV).

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

The server refuses to perform the request using the current protocol.

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 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, acting as a gateway, received an invalid response from the upstream server.

The server is currently unable to handle the request due to temporary overloading or maintenance.

The server, acting as a gateway, did not receive a timely response from the upstream server.

The server does not support the HTTP 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 (WebDAV).

The server detected an infinite loop while processing the request (WebDAV).

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

The client needs to authenticate to gain network access (captive portals).