The initial part of a request has been received and has not yet been rejected by the server. The client SHOULD continue by sending the remainder of the request or, if the request has already been completed, ignore this response.

The server understands and is willing to comply with the client's request, via the Upgrade header field, for a change in the application protocol being used on this connection.

An interim response used to inform the client that the server has accepted the complete request, but has not yet completed it.

Used to return some response headers before final HTTP message.

The request has succeeded. The payload sent in a 200 response depends on the request method.

The request has been fulfilled and has resulted in one or more new resources being created.

The request has been accepted for processing, but the processing has not been completed. The request might or might not eventually be acted upon.

The request was successful but the enclosed payload has been modified from that of the origin server's 200 (OK) response by a transforming proxy.

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

The server successfully processed the request, asks that the requester reset its document view, and is not returning any content.

The server is successfully fulfilling a range request for the target resource by transferring one or more parts of the selected representation.

A Multi-Status response conveys information about multiple resources in situations 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 target resource has more than one representation, each with its own more specific identifier, and information about the alternatives is being provided so that the user (or user agent) can select a preferred representation by redirecting its request.

The target resource has been assigned a new permanent URI and any future references to this resource ought to use one of the enclosed URIs.

The target resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the client ought to continue to use the effective request URI for future requests.

The server is redirecting the user agent to a different resource, as indicated by a URI in the Location header field, which is intended to provide an indirect response to the original request.

A conditional GET or HEAD request has been received and would have resulted in a 200 (OK) response if it were not for the fact that the condition evaluated to false.

Defined in a previous version of the HTTP specification, and is now deprecated.

The target resource resides temporarily under a different URI and the user agent MUST NOT change the request method if it performs an automatic redirection to that URI.

The target resource has been assigned a new permanent URI and any future references to this resource ought to use one of the enclosed URIs.

The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).

The request has not been applied because it lacks valid authentication credentials for the target resource.

Reserved for future use.

The server understood the request but refuses to authorize it.

The origin server did not find a current representation for the target resource or is not willing to disclose that one exists.

The method received in the request-line is known by the origin server but not supported by the target resource.

The target resource does not have a current representation that would be acceptable to the user agent, according to the proactive negotiation header fields received in the request.

Similar to 401 (Unauthorized), but it indicates that the client needs to authenticate itself in order to use a proxy.

The server did not receive a complete request message within the time that it was prepared to wait.

The request could not be completed due to a conflict with the current state of the target resource. This code is used in situations where the user might be able to resolve the conflict and resubmit the request.

The target resource is no longer available at the origin server and that this condition is likely to be permanent.

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

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 origin server is refusing to service the request because the payload is in a format not supported by this method on the target resource.

None of the ranges in the request's Range header field overlap the current extent of the selected resource or that the set of ranges requested has been rejected due to invalid ranges or an excessive request of small or overlapping ranges.

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

Any attempt to brew coffee with a teapot should result in the error code "418 I'm a teapot". The resulting entity body MAY be short and stout.

The request was directed at a server that is not able to produce a response. This can be sent by a server that is not configured to produce responses for the combination of scheme and authority that are included in the request URI.

The server understands the content type of the request entity, and the syntax of the request entity is correct, but it 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 and that action 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 but might be willing to do so after the client upgrades 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 ("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.

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 a temporary overload or scheduled maintenance, which will likely be alleviated after some delay.

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

The server does not support, or refuses to support, the major version of HTTP 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, and is therefore not a proper end point in the negotiation process.

The method could not be performed on the resource because the server is unable to store the representation needed to successfully complete the request.

The server terminated an operation because it encountered an infinite loop while processing a request with "Depth: infinity".

The policy for accessing the resource has not been met in the request. The server should send back all the information necessary for the client to issue an extended request.

The client needs to authenticate to gain network access.