HTTP Status Code Reference

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.

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 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.

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

The server requires the client to reset the document view.

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

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

The URL of the requested resource has been changed permanently. Use the new URL for future requests.

The URL of the requested resource has been changed temporarily. Keep using the original URL.

The response can be found under a different URI and should be retrieved using GET.

The resource has not been modified since the version specified in If-Modified-Since or If-None-Match.

The resource is temporarily available at a different URI. The method must not change.

The resource has been permanently moved to a different URI. The method must not change.

The server cannot process the request due to a client error (e.g., malformed syntax).

Authentication is required and has failed or not been provided.

Reserved for future use. Originally created for digital payment systems.

The client does not have permission to access the resource.

The server cannot find the requested resource.

The request method is not supported for the requested resource.

The server cannot produce a response matching the Accept headers.

The client must first authenticate itself with 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.

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

One or more conditions in the request headers evaluated to false.

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 media format of the requested data is not supported by the server.

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

The resource is unavailable due to legal reasons (e.g., censorship).

A generic error message when the server encounters an unexpected condition.

The server does not support the functionality required to fulfill the request.

The server received an invalid response from the upstream server.

The server is temporarily unable to handle the request (e.g., overloaded or down for maintenance).

The server did not receive a timely response from the upstream server.

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

The server cannot store the representation needed to complete the request.

The server detected an infinite loop while processing the request.