HTTP Status Code Reference

The server has 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 received and is processing the request, but no response is available yet.

Used to return some response headers before final HTTP message, allowing preloading of resources.

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

The request has been fulfilled and has resulted in one or more new resources being created.

The request has been accepted for processing, but the processing has not been completed.

The returned meta-information is not the definitive set from the origin server but from a local or third-party copy.

The server has successfully fulfilled the request and there is no additional content to send.

The server has fulfilled the request and the user agent should reset the document view.

The server is delivering only part of the resource due to a range header sent by the client.

Conveys information about multiple resources where multiple status codes might be appropriate.

Used inside a DAV: propstat response element to avoid enumerating internal members of multiple bindings to the same collection repeatedly.

The server has fulfilled a GET request for the resource, and the response is a representation of one or more instance-manipulations applied to the current instance.

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

The requested resource has been permanently moved to a new URL. Future requests should use the new URL.

The requested resource temporarily resides at a different URL. The client should continue to use the original URL for future requests.

The response to the request can be found at another URI using a GET method.

The resource has not been modified since the version specified by the request headers. No body is returned.

The requested resource must be accessed through the proxy given by the Location header.

The requested resource temporarily resides at a different URL. The method and body should not change.

The resource has permanently moved to a new URL and the method should not change on redirect.

The server cannot process the request due to something perceived to be a client error (malformed syntax, invalid framing, deceptive routing).

The request requires user authentication. The response must include a WWW-Authenticate header.

Reserved for future use. Originally intended for digital payment schemes.

The server understood the request but refuses to authorize it. Authentication will not help.

The server cannot find the requested resource. The URI is not recognized.

The HTTP method used is not supported for the requested resource.

The resource cannot generate content matching the Accept headers sent by the client.

The client must authenticate with the proxy before the request can be processed.

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

The request could not be completed due to a conflict with the current state of the resource.

The resource is no longer available and no forwarding address is known. This is permanent.

The server refuses the request because it requires a Content-Length header.

One or more conditions given in the request header fields evaluated to false when tested on the server.

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

The URI provided was 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.

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

The server refuses to brew coffee because it is, permanently, a teapot. Defined in Hyper Text Coffee Pot Control Protocol.

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

The server understands the request but was unable to process the contained instructions.

The resource that is being accessed is locked.

The request failed because it depended on another request that also failed.

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

The server refuses to perform the request using the current protocol. The client should upgrade to a different protocol.

The origin server requires the request to be conditional (include If-Match or similar headers).

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

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

The server is denying access to the resource as a consequence of a legal demand.

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

The server is currently unable to handle the request due to temporary overloading or maintenance.

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

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

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

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

The server detected an infinite loop while processing the request.

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

The client needs to authenticate to gain network access, typically via a captive portal.