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

The request has succeeded. The meaning of success depends on the HTTP method.

The request has succeeded and a new resource has been created as a result.

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

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

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

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

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

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

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

The client has made a conditional request and the resource has not been modified.

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 or will not process the request due to an apparent client error.

The client must authenticate itself to get the requested response.

The client does not have access rights to the content; the server is refusing to give the requested resource.

The server cannot find the requested resource. This is the most common error.

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.

The server timed out waiting for the request.

The request could not be completed due to a conflict with the current state of the resource.

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

The server refuses to accept the request without a defined Content-Length header.

The server does not meet one of the preconditions that the requester put on the request.

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

The URI provided was too long for the server to process.

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

The range specified by the Range header field cannot be fulfilled.

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

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

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

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

The server is denying access to the resource as a consequence of a legal demand.

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

The server is not ready to handle the request. Common causes are maintenance or overload.

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 method could not be performed on the resource because the server is unable to store the representation needed.

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.