HTTP Status Codes

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

The server is switching protocols as requested by the client, e.g. upgrading to WebSocket.

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, allowing preloading of resources.

The request succeeded. The response body contains the requested resource or result.

The request succeeded and a new resource was created. Typically returned after POST.

The request has been accepted for processing but has not been completed yet.

The returned metadata was collected from a local or third-party copy, not from the origin server.

The request succeeded but there is no content to return. Common for DELETE and some PUT requests.

The request succeeded. The client should reset the document view, e.g. clear a form.

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

A WebDAV response that conveys information about multiple resources and operations.

Used in WebDAV to avoid enumerating the same bindings multiple times in a response.

The server has fulfilled a GET request and the response is the result of one or more instance manipulations.

The request has more than one possible response. The user or user agent should choose one.

The URL has permanently changed. The new URL is given in the Location header. Search engines update their index.

The URL has temporarily changed. The client should continue using the original URL for future requests.

The response to the request can be found at another URL using GET, often used after a POST.

The cached version of the resource is still valid. The client can use the cached copy.

Deprecated. The requested resource must be accessed through a proxy.

The URL has temporarily changed. The client must use the same HTTP method for the redirect request.

The URL has permanently changed. The client must use the same HTTP method for all future requests.

The server cannot process the request due to malformed syntax, invalid request message, or deceptive routing.

Authentication is required and has failed or has not been provided. The client must authenticate to get the resource.

Reserved for future use. Some APIs use it to indicate a payment or quota limit has been reached.

The server understood the request but refuses to authorize it. Unlike 401, re-authenticating will not help.

The server cannot find the requested resource. The URL is not recognized or the resource does not exist.

The HTTP method used is not supported for this resource. The Allow header lists supported methods.

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

The client must first authenticate with the proxy server before this request can be served.

The server timed out waiting for the request. The client should send the request again.

The request conflicts with the current state of the server, e.g. a duplicate resource or edit conflict.

The resource has been permanently deleted and will not be available again. Clients should remove cached links.

The request did not specify the Content-Length, which is required by the server.

The server does not meet one of the preconditions specified in the request headers (If-Match, If-None-Match, etc.).

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

The URI provided in the request is too long for the server to process.

The media format of the requested data is not supported by the server.

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

The expectation indicated in the Expect request header cannot be met by the server.

An April Fools joke in RFC 2324. Some APIs use it humorously for intentionally unsupported operations.

The request was directed at a server that is not able to produce a response.

The request is well-formed but contains semantic errors, e.g. a validation error in a REST API body.

The resource that is being accessed is locked. Used in WebDAV.

The request failed because it depended on another request that also failed. Used in WebDAV.

The server is unwilling to risk processing a request that might be replayed (related to TLS early data).

The client should switch to a different protocol, such as TLS/1.0.

The origin server requires the request to be conditional to prevent the lost-update problem.

The client has sent too many requests in a given amount of time. Rate limiting is in effect.

The server refuses to process the request because the header fields are too large.

The resource is unavailable due to a legal demand, such as a government-issued takedown or geo-restriction.

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

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

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

The server is not ready to handle the request, typically due to maintenance or overloading.

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

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

Transparent content negotiation for the request results in a circular reference.

The server is unable to store the representation needed to complete the request. Used in WebDAV.

The server detected an infinite loop while processing the request. Used in 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. a captive portal on public Wi-Fi.