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 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 processing is not complete.

The returned meta-information is from a local or third-party copy.

The server has fulfilled the request but there is no content to return.

The server has fulfilled the request and the client should reset the document view.

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

The resource has been permanently moved to a new URL.

The resource resides temporarily under a different URL.

The response can be found under a different URL using GET method.

The resource has not been modified since the last request.

The resource resides temporarily under a different URL; method must not change.

The resource has permanently moved; method must not change.

The server cannot process the request due to invalid syntax.

Authentication is required and has failed or not been provided.

The server understands the request but refuses to authorize it.

The server cannot find the requested resource.

The HTTP method is not allowed for the requested resource.

The server cannot produce a response matching the Accept headers.

The server timed out waiting for the request.

The request conflicts with the current state of the resource.

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

The request entity is larger than the server is willing to process.

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

The media format of the request is not supported by the server.

The server refuses to brew coffee because it is a teapot.

The request was well-formed but semantic errors prevent processing.

The user has sent too many requests in a given amount of time.

Resource cannot be provided for legal reasons.

The server encountered an unexpected condition.

The server does not support the functionality required.

The server received an invalid response from an upstream server.

The server is not ready to handle the request.

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