HTTP Status Codes Lookup

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 and the server has agreed to do so.

Standard response for successful HTTP requests.

The request has been fulfilled, resulting in the creation of a new resource.

The request has been accepted for processing, but 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.

This and all future requests should be directed to the given URI.

Tells the client to look at another URL temporarily.

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

Temporary redirect guaranteeing that the HTTP method (e.g. POST) is NOT changed to GET.

Permanent redirect guaranteeing that the HTTP method is NOT changed to GET.

The server cannot or will not process the request due to something perceived to be a client error.

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

The server understood the request, but refuses to authorize it.

The origin server did not find a current representation for the target resource.

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

The server did not receive a complete request message within the time that it was prepared to wait.

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

The server is refusing to process a request because the request payload is larger than server limits.

The origin server refuses to service the request because the payload format is in an unsupported format.

The server understands the content type and syntax, but was unable to process the contained instructions.

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

The server encountered an unexpected condition that prevented it from fulfilling the request.

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

The server is currently unable to handle the request due to temporary overloading or maintenance.

The server, while acting as a gateway or proxy, did not receive a timely response from upstream.