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

Used to return some response headers before the final HTTP message.

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

The request has been fulfilled and a new resource has been created.

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

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

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

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

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

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

The requested resource is temporarily located at a different URL.

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

The resource has not been modified since the last request.

The request should be repeated with the same HTTP method at another URL.

The resource has permanently moved and the same HTTP method should be used for the new request.

The server cannot process the request due to malformed syntax or invalid parameters.

Authentication is required and has failed or has not been provided.

The server understood the request but refuses to authorize it.

The server cannot find the requested resource at the specified URL.

The request method is known by the server but is not supported for the target resource.

The server cannot produce a response matching the acceptable values defined in the request headers.

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

The request conflicts with the current state of the target resource.

The target resource is no longer available and this condition is likely permanent.

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

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

The server refuses the attempt to brew coffee with a teapot, as defined in the Hyper Text Coffee Pot Control Protocol.

The request was well-formed but contains semantic errors that prevent processing.

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

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

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

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

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

The server detected an infinite loop while processing the request.