HTTP Status Codes

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.

The server has received and is processing the request, but no response is available yet.

The request has succeeded. The meaning of success varies depending on the HTTP method.

The request has been fulfilled and resulted in a new resource being created.

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

The requested resource has been assigned a new permanent URI and future references should use that URI.

The requested resource resides temporarily under a different URI.

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

The request should be repeated with another URI, but future requests can still use the original URI.

The request and all future requests should be repeated using another URI permanently.

The server cannot or will not process the request due to an apparent 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 requested resource could not be found on the server.

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

The server timed out waiting for the request from the client.

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

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

The request is larger than the server is willing or able to process.

The request entity has a media type which the server or resource does not support.

The request was well-formed but was unable to be followed due to semantic errors.

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

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