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 final HTTP message.

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

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 not exactly the same as available from the origin server.

The server successfully processed the request and 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 message body is an XML message containing multiple independent response codes.

The members of a DAV binding have already been enumerated in a preceding part of the response.

The server has fulfilled a GET request for the resource, and the response is a representation of the result of instance manipulations.

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

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

The requested resource resides temporarily under a different URI.

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

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

The requested resource is available only through a proxy. (Deprecated)

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

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

The server cannot or will not process the request due to something that is perceived to be a client error.

The request requires user authentication. The response must include a WWW-Authenticate header field.

Reserved for future use. Originally intended for digital payment systems.

The server understood the request but refuses to authorize it.

The server cannot find the requested resource. This is the most common HTTP error.

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

The target resource does not have a current representation acceptable to the user agent.

The client must first authenticate itself with the proxy.

The server timed out waiting for the request.

The request could not be completed due to a conflict with 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 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 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, permanently, a teapot. (RFC 2324 April Fools' joke)

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 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 server is denying access to the resource as a consequence of a legal demand.

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, while acting as a gateway or proxy, 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, while acting as a gateway or proxy, 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.