HTTP Status Code 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.

Used to return headers before the final HTTP message to allow preloading critical assets.

The request has succeeded. The information returned with the response depends on the method used.

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 has successfully fulfilled the request and there is no additional content to send in the response payload.

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

The target resource has been assigned a new permanent URI and any future references should use one of the returned URIs.

The target resource resides temporarily under a different URI. Browsers often incorrectly change POST to GET.

Indicates that the resource has not been modified since the version specified by the request headers If-Modified-Since or If-None-Match.

The target resource resides temporarily under a different URI and the user agent MUST NOT change the request method.

The target resource has been assigned a new permanent URI and the request method MUST NOT change.

The server cannot or will not process the request due to something perceived to be a client error (e.g. malformed syntax, invalid framing).

The request has not been applied because it lacks valid authentication credentials for the target resource.

The server understood the request but refuses to authorize it. Unlike 401, re-authenticating will not help if permissions are lacking.

The origin server did not find a current representation for the target resource or is not willing to disclose that one exists.

The method received in the request-line is known by the server but 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 target resource is no longer available at the origin server and no forwarding address is known.

The server is refusing to process a request because the request payload is larger than the server is willing or able to process.

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

The server understands the content type of the request entity, and the syntax is correct, 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 does not support the functionality required to fulfill the request.

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

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

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