HTTP Status Codes 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 the final HTTP message.

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

The request succeeded and a new resource was created as a result.

The request has been accepted for processing, but the 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 is not returning any content.

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

Members of a DAV binding have already been enumerated in a previous reply and are not included again.

The server has fulfilled a GET request with instance-manipulations applied to the current instance.

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

The resource has been permanently moved to a new URL. Update bookmarks.

The resource is temporarily located at a different URI. Continue using the original URI.

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.

The resource is temporarily at another URI. The request method must not change.

The resource has permanently moved. The request method must not change.

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

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

Reserved for future use. Sometimes used for digital payment systems.

The server understood the request but refuses to authorize it.

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

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

The server cannot produce a response matching the client's Accept headers.

The client must first authenticate itself with the proxy.

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

The request conflicts with the current state of the server.

The resource is no longer available and will not be available again.

The server requires a Content-Length header in the request.

One or more conditions in the request headers evaluated to false.

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

The URI provided in the request is too long for the server to process.

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

The range specified in the Range header cannot be fulfilled by the server.

The server cannot meet the requirements of the Expect request-header field.

The server refuses to brew coffee because it is, permanently, a teapot.

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

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

The resource that is being accessed is locked.

The request failed because it depended on another request which 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 server requires the request to be conditional (e.g., include If-Match).

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 resource is unavailable due to legal demands (e.g., censorship or court order).

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 received an invalid response from an upstream server.

The server is not ready to handle the request, usually due to maintenance or overload.

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

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

The server has an internal configuration error during content negotiation.

The server cannot 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 (e.g., captive portal).