HTTP Status Codes Reference

Server received request headers; client should proceed.

Server is switching to the protocol specified by the client.

Server has received and is processing the request.

Preload hints sent before the final response.

Request succeeded.

Request succeeded and a new resource was created.

Request accepted but processing not completed.

Metadata differs from the origin server.

Request succeeded with no response body.

Client should reset the document view.

Server is delivering part of a resource (range request).

Multiple status codes for multiple operations (WebDAV).

Members of a DAV binding have already been reported.

Server has applied delta-encoding to the response.

Multiple options available; client must choose.

Resource permanently moved to a new URL.

Resource temporarily located at a different URL.

Redirect to another URI using GET.

Cached version is still valid; no body returned.

Temporary redirect; client must use same method.

Permanent redirect; client must use same method.

Server cannot process the request due to client error.

Authentication required.

Client lacks permission to access the resource.

Resource could not be found.

HTTP method not allowed for this resource.

Server cannot produce a response matching Accept headers.

Authentication with a proxy is required.

Server timed out waiting for the request.

Request conflicts with the current state of the resource.

Resource permanently deleted and will not return.

Content-Length header is required.

Conditional request precondition not met.

Request body exceeds server limits.

The request URI is longer than the server can process.

Payload format not supported.

The Range header cannot be fulfilled.

Server cannot meet the Expect request-header field.

The server is a teapot (April Fools' joke, RFC 2324).

Request is well-formed but has semantic errors.

Resource is locked (WebDAV).

Request failed due to a failed dependent request (WebDAV).

Server unwilling to process a potentially replayed request.

Client must switch to a different protocol.

Conditional request required to prevent conflicts.

Rate limit exceeded; slow down requests.

Request headers are too large.

Access denied due to legal constraints.

Generic server-side error.

Server does not support the request method.

Upstream server returned an invalid response.

Server is temporarily unable to handle requests.

Upstream server did not respond in time.

HTTP protocol version not supported.

Circular reference in content negotiation.

Server cannot store the representation (WebDAV).

Infinite loop detected while processing (WebDAV).

Further extensions required to fulfil the request.

Client must authenticate to gain network access.