HTTP Status Code Lookup

The client should continue with its request; the initial part was received.

The server is switching protocols as requested by the client (e.g. to WebSocket).

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

Returns some response headers early so the client can start preloading resources.

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

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

The request was accepted for processing, but processing is not complete.

Returned metadata is from a local or third-party copy, not the origin server.

The request succeeded but there is no content to return.

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

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

Conveys information about multiple resources (WebDAV).

Members of a WebDAV binding were already enumerated and are not repeated.

The server fulfilled a GET request; the response is an instance manipulation result.

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

The resource has permanently moved to a new URL given in the Location header.

The resource is temporarily at a different URL; keep using the original URL.

The response is found at another URL and should be fetched with GET.

The cached version is still valid; no need to retransmit the resource.

Like 302, but the method and body must not change on the redirected request.

Like 301, but the method and body must not change on the redirected request.

The server cannot process the request due to a client error (malformed syntax).

Authentication is required and has failed or not been provided.

Reserved for future use; sometimes used by APIs for payment/quota limits.

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 this resource.

No content matching the request's Accept headers could be produced.

Authentication with a proxy is required before the request can proceed.

The server timed out waiting for the request.

The request conflicts with the current state of the resource.

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

The server requires a Content-Length header, which was missing.

A precondition in the request headers was not met.

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

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

The request's media type is not supported by the server.

The requested Range cannot be fulfilled.

The expectation in the Expect header could not be met.

An April Fools' joke code; the server refuses to brew coffee in a teapot.

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

The request was well-formed but has semantic errors (often validation).

The resource being accessed is locked (WebDAV).

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

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

The header fields are too large for the server to process.

The resource is unavailable due to legal demands (e.g. censorship).

A generic error; the server hit an unexpected condition.

The server does not support the functionality required to fulfil the request.

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

The server is not ready — often overloaded or down for maintenance.

The server, acting as a gateway, did not get a timely response upstream.

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

A content-negotiation configuration error on the server.

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 the server to fulfil it.

The client needs to authenticate to gain network access (e.g. captive portal).