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 processing has not been completed.

The returned metadata is not exactly the same as available from the origin server.

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

The server successfully processed the request and is not returning any content, and requires the requester to reset the document view.

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

The message body contains multiple status codes for multiple independent operations.

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

The server has fulfilled a GET request for the resource with instance-manipulations applied.

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

The response can be found under a different URL using a GET method.

The resource has not been modified since the version specified by the request headers.

The requested resource must be accessed through the proxy given by the Location header.

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

The request and all future requests should be repeated using another URL.

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. Originally intended for digital payment schemes.

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 requested resource is capable of generating only content not 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 could not be processed because of conflict in the current state of the resource.

The resource requested 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 specified in the request headers.

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 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 request-header field.

The server refuses to brew coffee because it is, permanently, a teapot.

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

The request was well-formed but was unable to be followed due to semantic errors.

The resource that is being accessed is locked.

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

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

The client should switch to a different protocol.

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

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 the upstream server.

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

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

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

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.