HTTP Status Codes

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

The server is switching to a different protocol 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 the processing has not been completed.

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

The server has fulfilled the request but does not need to return a body.

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 request has more than one possible response. The user should choose one.

The resource has been permanently moved to a new URL.

The resource resides temporarily at a different URL.

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

The resource has not been modified since the last request.

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

The resource has been permanently moved. The method must not change.

The server cannot process the request due to malformed syntax.

Authentication is required and has failed or not been provided.

The server understood the request but refuses to authorize it.

The requested resource could not be found on the server.

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

The resource has been permanently deleted 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 request media type is not supported by the server.

The request was well-formed but contained semantic errors.

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

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

The server does not recognize the request method or lacks the ability to complete it.

The server received an invalid response from an upstream server.

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

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

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