http.status

The server 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 accepted the request but has not yet completed it (WebDAV).

Returns some response headers before the final response, letting the client preload resources.

The request succeeded. The meaning of success depends on the HTTP method.

The request succeeded and a new resource was created as a result.

The request was received but not yet acted upon; processing happens later.

The returned metadata is from a local or third-party copy rather than the origin server.

The request succeeded but there is no content to send in the response body.

The request succeeded; the client should reset the document view that sent the request.

The server is delivering only part of the resource in response to a Range header.

Conveys information about multiple resources where several status codes apply (WebDAV).

The request has more than one possible response; the client should choose one.

The resource has a new permanent URL, given in the Location header.

The resource resides temporarily under a different URL given by the Location header.

The client should fetch the resource at another URL using a GET request.

The cached copy is still valid; the resource has not changed since the last request.

The resource is temporarily at another URL; the request method must not change.

The resource is permanently at another URL; the request method must not change.

The server cannot process the request due to a client error such as malformed syntax.

Authentication is required and has failed or has not been provided.

Reserved for future use; sometimes used by APIs to signal a payment or quota issue.

The server understood the request but refuses to authorize it.

The server cannot find the requested resource.

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

The resource cannot produce a response matching the request Accept headers.

The client must first authenticate itself with the proxy.

The server timed out waiting for the request from the client.

The request conflicts with the current state of the target resource.

The resource is permanently gone and no forwarding address is known.

The server requires a Content-Length header, which the request did not include.

A precondition given in the request headers evaluated to false on the server.

The request body is larger than the server is willing or able to process (formerly "Payload Too Large").

The requested URI is longer than the server is willing to interpret.

The request payload is in a format the server does not support.

The Range header requests a portion the server cannot supply.

The expectation given in the Expect request header could not be met.

The server refuses to brew coffee because it is, permanently, a teapot (RFC 2324). Reserved/unused in RFC 9110.

The request was directed at a server unable to produce a response for it.

The request was well-formed but had semantic errors (formerly "Unprocessable Entity").

The resource being accessed is locked (WebDAV).

The request failed because it depended on another request that failed (WebDAV).

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

The client should switch to a different protocol given in the Upgrade header.

The origin server requires the request to be conditional.

The client has sent too many requests in a given amount of time (rate limiting).

The request was refused because its header fields are too large.

The resource is unavailable for legal reasons, such as censorship or a takedown.

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, acting as a gateway, received an invalid response from the upstream server.

The server is not ready to handle the request, often due to overload or maintenance.

The server, acting as a gateway, did not receive a timely response from the upstream server.

The server does not support the HTTP version used in the request.

A content-negotiation configuration error: the chosen variant is itself a negotiation endpoint.

The server cannot store the representation needed to complete the request (WebDAV).

The server terminated the request because it encountered an infinite loop (WebDAV).

Further extensions to the request are required for the server to fulfill it.

The client must authenticate to gain network access, typically at a captive portal.