HTTP Status Codes

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.

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 succeeded. The meaning depends on the HTTP method used.

The request succeeded and a new resource was created.

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

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

The server successfully processed the request but returns no content.

The server successfully processed the request and asks the client to 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 in situations where multiple status codes might be appropriate.

Used in a DAV binding to avoid enumerating the same collection members repeatedly.

The server has fulfilled a GET request and the response is a representation of the result of instance-manipulations.

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

The URL of the requested resource has been permanently changed.

The URI of the requested resource has been temporarily changed.

The server sent this response to direct the client to get the requested resource at another URI with a GET request.

The resource has not been modified since the last request.

The server sends this response to direct the client to a different URI, preserving the HTTP method.

The resource has permanently moved to another URI, specified in the Location header, preserving the HTTP method.

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

The client must authenticate itself to get the requested response.

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

The client does not have access rights to the content.

The server cannot find the requested resource.

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

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

The client must authenticate with the proxy.

The server timed out waiting for the request.

The request conflicts with the current state of the server.

The requested content has been permanently deleted from the server.

The server rejects the request because the Content-Length header is not defined.

The server does not meet one of the preconditions specified in the request headers.

The request body is larger than limits defined by the server.

The URI requested by the client is too long for the server to handle.

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

The range specified in the Range header cannot be fulfilled.

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

The server refuses the attempt to brew coffee with a teapot.

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

The request was well-formed but could not be processed due to semantic errors.

The resource that is being accessed is locked.

The request failed because it depended on another request 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.

The origin server requires the request to be conditional.

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

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

The user requested a resource that is not available due to legal reasons.

The server has encountered a situation it does not know how to handle.

The request method is not supported by the server.

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 get a response in time from the upstream server.

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

The server has an internal configuration error: transparent content negotiation 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 (captive portal).