HTTP Status Codes

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

The server agrees to switch 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 the final HTTP message.

The request has succeeded. The meaning of the success 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 request was successful but the payload has been modified by a transforming proxy.

The server successfully processed the request and is not returning any content.

The server successfully processed the request and asks the client to reset its document view.

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

Provides status for multiple independent operations in a single response.

Used in a 207 Multi-Status response to avoid repeatedly enumerating internal members of multiple bindings to the same collection.

The server has fulfilled a GET request with instance manipulations applied.

The request has multiple possible responses. The user-agent or user should choose one.

The requested resource has been permanently moved to a new URL.

The resource temporarily resides under a different URI.

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

The resource has not been modified since the version specified in request headers.

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

The resource temporarily resides under a different URI. The method must not change.

The resource has been permanently moved to a new URI. The method must not change.

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

The request requires user authentication. The client must authenticate itself to get the requested response.

Reserved for future use. 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 request method is known but not supported by the target resource.

The target resource does not have a current representation that would be acceptable to the user agent.

The client must first authenticate itself with the proxy.

The server did not receive a complete request message within the time it was prepared to wait.

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

The target resource is no longer available at the server and no forwarding address is known.

The server refuses to accept the request without a defined Content-Length.

One or more conditions given in the request header fields evaluated to false.

The request entity is larger than limits defined by server.

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

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

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

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

Any attempt to brew coffee with a teapot should result in the error code 418.

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

The server understands the content type and syntax but cannot process the contained instructions.

The source or destination resource of a method is locked.

The method could not be performed on the resource because the requested action depended on another action that 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 but might be willing to do so after the client upgrades.

The origin server requires the request to be conditional.

The user has sent too many requests in a given amount of time.

The server is unwilling 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.

Returned by the Twitter Search and Trends API when the client is being rate limited.

A non-standard status code used by nginx to indicate that the client closed the connection while the server was processing the request.

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 overload or maintenance.

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

The server does not support, or refuses to support, the HTTP protocol version used in the request.

The server has an internal configuration error: the chosen variant resource is configured to engage in transparent content negotiation.

The method could not be performed because the server cannot store the representation needed to complete the request.

The server detected an infinite loop while processing a request with Depth: infinity.

The policy for accessing the resource has not been met in the request.

The client needs to authenticate to gain network access.

A non-standard status code used by nginx to indicate that the server has returned no information and closed the connection.

The server is currently overloaded and cannot process the request.

The site has been frozen due to inactivity or non-payment.

Network read timeout behind the proxy.

Network connect timeout behind the proxy.