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.

Used to return some response headers before the final HTTP message, allowing the client to preload 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 not exactly the same as available from the origin server, but collected from a local or third-party copy.

The server has successfully fulfilled the request and there is no additional content to send in the response body.

The server has fulfilled the request and the client should reset the document view.

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

A Multi-Status response conveys information about multiple resources where multiple status codes might be appropriate.

Used inside a DAV: propstat response element to avoid enumerating the internal members of multiple bindings to the same collection repeatedly.

The server has fulfilled a GET request for the resource, and the response is a representation of the result of one or more instance-manipulations applied to the current instance.

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

The requested resource has been assigned a new permanent URI and any future references should use one of the returned URIs.

The requested resource resides temporarily under a different URI. The client should continue to use the original URI for future requests.

The response to the request can be found under a different URI and should be retrieved using a GET method on that resource.

The resource has not been modified since the version specified by the request headers. The client can use its cached version.

The requested resource must be accessed through the proxy given by the Location header. Deprecated due to security concerns.

The requested resource resides temporarily under a different URI. The request method should not be changed when reissuing the original request.

The requested resource has been permanently moved to another URI. The request method should not be changed when reissuing the original request.

The server cannot process the request due to something perceived to be a client error such as malformed syntax or invalid framing.

The request requires user authentication. The client must authenticate itself to get the requested response.

Reserved for future use. Originally intended for digital payment schemes, but not widely used.

The server understood the request but refuses to authorize it. Authentication will not help.

The server cannot find the requested resource. The URI may be incorrect or the resource may have been removed.

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

The server cannot produce a response matching the list of acceptable values defined in the request headers.

The client must first authenticate itself with the proxy before the request can be fulfilled.

The server timed out waiting for the request. The client did not produce a request within the time the server was prepared to wait.

The request could not be completed due to a conflict with the current state of the target resource.

The target resource is no longer available at the server and no forwarding address is known. This condition is expected to be permanent.

The server refuses to accept the request without a defined Content-Length header.

One or more conditions given in the request header fields evaluated to false when tested on the server.

The server is refusing to process a request because the request payload is larger than the server is willing or able to process.

The server is refusing to service the request because the request-target is longer than the server is willing to interpret.

The server is refusing to service the request because the payload is in a format not supported by this method on the target resource.

The range specified in the Range header of the request cannot be fulfilled. The range may be outside the size of the target resource's data.

The expectation given in the request's Expect header could not be met by at least one of the inbound servers.

The server refuses to brew coffee because it is, permanently, a teapot. Defined by the Hyper Text Coffee Pot Control Protocol.

The request was directed at a server that is not able to produce a response for the combination of scheme and authority included in the request URI.

The server understands the content type of the request but was unable to process the contained instructions.

The source or destination resource of a method is locked.

The method could not be performed on the resource because the requested action depended on another action that failed.

The server is unwilling to risk processing a request that might be replayed, to avoid potential replay attacks.

The server refuses to perform the request using the current protocol but might be willing to do so after the client upgrades to a different protocol.

The origin server requires the request to be conditional to prevent lost update conflicts.

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 request may be resubmitted after reducing the size of the request header fields.

The server is denying access to the resource as a consequence of a legal demand. Named after the novel Fahrenheit 451.

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 an inbound server it accessed while attempting to fulfill the request.

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

The server, while acting as a gateway or proxy, did not receive a timely response from an upstream server it needed to access to complete the request.

The server does not support the HTTP protocol version that was used in the request message.

The server has an internal configuration error: the chosen variant resource is configured to engage in transparent content negotiation itself, creating 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, typically used by captive portals.