HTTP Status Reference

Server has received the request headers; client should proceed to send the body.

Server is switching protocols as requested by the client.

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

Used to return some response headers before final HTTP message.

Standard successful response. The meaning depends on the HTTP method used.

Request fulfilled and a new resource has been created.

Request accepted for processing, but processing is not complete.

Returned meta-information is from a local or third-party copy.

Server successfully processed the request, but returns no content.

Server processed the request; tells the client to reset the document view.

Server delivers only part of the resource due to a Range header.

Body contains multiple status codes for multiple operations (WebDAV).

Members of a DAV binding have already been enumerated.

Server has fulfilled a GET request and the response is a representation of instance-manipulations.

Multiple options for the resource — the client can select one.

Resource has been permanently moved to a new URI.

Resource temporarily resides under a different URI.

Response can be found under a different URI using GET.

Resource has not been modified since the last request.

Request should be repeated with another URI, keeping the method.

Request and future requests should use another URI, keeping the method.

Server cannot process the request due to client error (malformed syntax).

Authentication is required and has failed or not been provided.

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

Server understood the request but refuses to authorize it.

The requested resource could not be found on the server.

HTTP method is not supported for the requested resource.

Server cannot produce a response matching the Accept headers.

Client must first authenticate with the proxy.

Server timed out waiting for the request.

Request conflicts with the current state of the target resource.

Resource is no longer available and no forwarding address is known.

Server requires Content-Length header to be specified.

One or more conditions in the request header fields were false.

Request entity is larger than the server is willing to process.

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

Request entity has a media type the server does not support.

Range specified in the Range header cannot be fulfilled.

Server cannot meet the requirements of the Expect header.

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

Request was well-formed but semantically incorrect (WebDAV).

The resource being accessed is locked (WebDAV).

Server is unwilling to process a request that might be replayed.

Server refuses to perform the request using the current protocol.

Origin server requires the request to be conditional.

User has sent too many requests in a given time (rate limiting).

Server refuses to process because headers are too large.

Resource is unavailable due to legal demands (censorship).

Generic server error when no more specific message is suitable.

Server does not support the functionality required to fulfill the request.

Server received an invalid response from an upstream server.

Server is currently unable to handle the request (overloaded/down).

Server did not receive a timely response from the upstream server.

Server does not support the HTTP version used in the request.

Transparent content negotiation resulted in a circular reference.

Server unable to store the representation needed (WebDAV).

Server detected an infinite loop while processing (WebDAV).

Further extensions to the request are required for fulfillment.

Client needs to authenticate to gain network access.