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.

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 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 processing is not complete.

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

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

The server successfully processed the request and is asking 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.

A multi-status response conveys information about multiple resources.

The members of a DAV binding have already been enumerated.

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

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

The URI of the requested resource has been changed temporarily. Further changes may 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 response has not been modified. The client can continue to use the cached version.

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 client error (e.g., malformed request syntax).

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

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

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

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's headers.

Authentication is required by 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, with no forwarding address.

The server requires the Content-Length header field to be defined.

The server does not meet one of the preconditions set by the client in the request headers.

The request entity is larger than limits defined by the 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 of the request cannot be fulfilled.

The server refuses the attempt to brew coffee with a teapot. (RFC 2324)

The request was well-formed but was unable to be followed due to semantic errors.

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

The resource is unavailable due to legal demands.

The server has encountered a situation it doesn't know how to handle.

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

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

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

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

The server detected an infinite loop while processing the request.

The client needs to authenticate to gain network access (e.g., captive portal).