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.

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.

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 the processing has not been completed.

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

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

The server processed the request and wants 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 inside a DAV: propstat response element to avoid enumerating internal members multiple times.

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

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

The URL of the requested resource has been changed permanently. The new URL is given in the response.

The URI of requested resource has been changed temporarily. Further changes might be made in the future.

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 version specified by the request headers.

The requested resource is only available through a proxy, the address for which is provided in the response.

The server sends this response to direct the client to get the requested resource at another URI with the same method.

The resource is now permanently located at another URI, specified by the Location header.

The server cannot process the request due to a client error (malformed syntax, invalid request).

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

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

The client does not have access rights to the content. Unlike 401, identity is known but access is denied.

The server cannot find the requested resource. The endpoint is valid but the resource does not exist.

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

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

The client must first authenticate itself with the proxy.

The server timed out waiting for the request.

The request conflicts with the current state of the server.

The content has been permanently deleted from the server with no forwarding address.

Server rejected the request because the Content-Length header is not defined.

The server does not meet one of the preconditions that the client put in the request headers.

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 by the Range header cannot be fulfilled.

The expectation indicated by 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 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 client should switch to a different protocol as indicated in the Upgrade header.

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 is unwilling to process the request because the request headers are too large.

The resource is unavailable due to legal demands.

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

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

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

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

The server, while acting as a gateway or proxy, 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: the chosen variant resource is configured to engage in transparent content negotiation.

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.