HTTP Status Codes

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

The requester has asked the server to switch protocols (e.g. to WebSocket).

The server has received and is processing the request, but no response is available yet (WebDAV).

Used to send some headers before the final response, e.g. preloading hints.

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

The request succeeded and a new resource was created, usually after a POST/PUT.

The request has been accepted for processing, but it is not complete yet.

The response was modified by a transforming proxy.

The request succeeded but there is no content to send back.

Tells the client to reset the document view, e.g. to clear a form.

Returned for a Range request; only part of the resource is sent.

Conveys status for multiple independent operations (WebDAV).

The server fulfilled the request using instance manipulations.

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

The resource has been permanently moved to a new URL; update bookmarks and links.

The resource is temporarily at a different URL.

The response is elsewhere; use GET to fetch it (commonly after form submission).

The cached response is still valid; no body is sent.

Same as 302 but the method and body must not change.

Same as 301 but the method and body must not change.

The server cannot process the request due to client-side errors (bad syntax).

Authentication is required and has failed or not been provided.

Reserved for future use; originally intended for digital payment systems.

The server understood the request but refuses to authorize it.

The requested resource could not be found on the server.

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

The server cannot produce a response matching the Accept headers.

Authentication with the proxy is required before continuing.

The server timed out waiting for the request.

The request conflicts with the current state of the resource.

The resource is no longer available and will not return.

The request is missing the required Content-Length header.

One of the precondition headers evaluated to false.

The request body is larger than the server is willing to process.

The request URI is longer than the server can interpret.

The request body format is not supported by the server.

The Range header specifies a range the server cannot fulfill.

The server cannot meet the requirements of the Expect header.

An April Fools joke from 1998; the server refuses to brew coffee.

The request was well-formed but semantically invalid (validation errors).

The resource is locked and cannot be modified (WebDAV).

The request failed because a previous request it depends on failed (WebDAV).

The server refuses to process a request that might be replayed.

The client should switch to a different protocol, e.g. TLS 1.0.

The request should be conditional to avoid lost updates.

The user has sent too many requests in a given time (rate limited).

The request headers are too large for the server to process.

The resource is unavailable for legal reasons, e.g. censorship.

An unexpected condition prevented the server from fulfilling the request.

The server does not support the functionality required by the request.

A gateway or proxy received an invalid response from the upstream server.

The server is not ready to handle the request, often during maintenance.

A gateway did not receive a timely response from the upstream server.

The server does not support the HTTP protocol version used.

The server cannot 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 it to be fulfilled.

The client must authenticate to gain network access, e.g. captive portals.