HTTP Status Codes

The server has received the request headers and the client should proceed to send the request body.

The requester has asked the server to switch protocols.

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 request has been fulfilled, resulting in the creation of a new resource.

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

The server is a transforming proxy that received a 200 OK from its origin, but is returning a modified version of the origin's response.

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

The server successfully processed the request, but is not returning any content. The client should reset the document view.

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

Indicates multiple options for the resource from which the client may choose.

The requested page has moved to a new URL.

The requested page has moved temporarily to a new URL.

The response to the request can be found under another URI using the GET method.

Indicates that the resource has not been modified since the version specified by the request headers.

The requested resource resides temporarily under a different URI. The request method must not be changed.

The requested resource resides permanently under a different URI. The request method must not be changed.

The server cannot or will not process the request due to an apparent client error.

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

Reserved for future use.

The request was valid, but the server is refusing action. The user might not have the necessary permissions.

The requested resource could not be found but may be available in the future.

A request method is not supported for the requested resource.

The requested resource is capable of generating only content not acceptable according to the Accept headers sent in the request.

The client must first authenticate itself with the proxy.

The server timed out waiting for the request.

Indicates that the request could not be processed because of conflict in the current state of the resource.

Indicates that the resource requested is no longer available and will not be available again.

The request did not specify the length of its content, which is required by the requested resource.

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

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

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

The request entity has a media type which the server or resource does not support.

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 user has sent too many requests in a given amount of time ("rate limiting").

A generic error message, given when an unexpected condition was encountered.

The server either does not recognize the request method, or it lacks the ability to fulfil the request.

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

The server cannot handle the request (because it is overloaded or down for maintenance).

The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.

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