HTTP Status Codes

The server has received the request headers and the client should proceed to send the body.

The requester has asked to switch protocols and the server is complying.

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.

Primarily used with Link headers for preloading.

The request succeeded. The result depends on the HTTP method used.

The request succeeded and a new resource was created. Common response to POST.

The request has been received but not yet acted upon. Used for async operations.

The response is a modified version of the origin server's response.

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

The server tells the client to reset the document which sent this request.

Delivered when a Range header is sent from the client — used for resumable downloads.

Conveys information about multiple resources, in WebDAV scenarios.

Used inside a DAV: propstat element to avoid enumerating members of multiple bindings.

The server has fulfilled a GET request, using one or more instance-manipulations.

The request has multiple possible responses. The client should pick one.

The URL of the requested resource has changed permanently.

Use for SEO-friendly redirects. Search engines update their index.

The URL has changed temporarily. The original URL should continue to be used.

The server directs the client to get the resource at another URL using GET.

The response has not been modified. The client can use its cached version.

Used with conditional requests (ETag, Last-Modified).

The request should be repeated at another URL, preserving the HTTP method.

Unlike 302, the method must not change.

The resource is now at another URL permanently, and the method must not change.

Like 301 but method is preserved.

The server cannot process the request due to a client error — malformed syntax, invalid request, etc.

Authentication is required and has failed or not been provided.

Despite the name, this means unauthenticated. See 403 for unauthorized.

Reserved for future use. Sometimes used by APIs to indicate quota exceeded.

The client does not have access rights to the content — it is authenticated but not authorized.

The server cannot find the requested resource. The URL may be wrong or the resource deleted.

The HTTP method used is not supported for this resource.

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

Authentication must be done by a proxy.

The server timed out waiting for the request to complete.

The request conflicts with the current state of the resource.

The resource has been permanently deleted and will not be available again.

Unlike 404, this is intended to indicate permanent removal.

The server rejected the request because the Content-Length header is not defined.

The server does not meet one of the conditions in the request headers.

The request entity is larger than limits defined by the server.

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

The media format is not supported by the server for this endpoint.

The range specified in the Range request header cannot be fulfilled.

The server cannot meet the requirements of the Expect request-header field.

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

An April Fools' joke in RFC 2324. Kept in the spec.

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

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

Common in REST APIs for validation failures.

The resource being accessed is locked (WebDAV).

The request failed due to failure of a previous request (WebDAV).

The server is unwilling to risk processing 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 (rate limiting).

Often includes Retry-After header.

The server is unwilling to process the request because its header fields are too large.

The resource cannot be provided for legal reasons, such as a page censored by a government.

Named after the novel Fahrenheit 451.

The server encountered an unexpected condition that prevented it from fulfilling the request.

The request method is not supported by the server and cannot be handled.

The server, acting as a gateway, received an invalid response from the upstream server.

Common when a proxy or load balancer can't reach the origin.

The server is not ready to handle the request — overloaded or down for maintenance.

Temporary. Often includes Retry-After header.

The server, acting as a gateway, did not get a response from the upstream server in time.

The HTTP version used in the request is not supported by the server.

The server has an internal configuration error during content negotiation.

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

The server detected an infinite loop while processing the request (WebDAV).

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

The client needs to authenticate to gain network access — e.g. a captive portal.