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.

Standard response for successful HTTP requests.

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 successfully processed the request and is not returning any content.

This and all future requests should be directed to the given URI.

The resource was found, but at a different URI.

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

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

The server cannot or will not process the request due to an apparent client error.

Similar to 403 Forbidden, but specifically for use when authentication is required and has failed or has not yet been provided.

The request was valid, but the server is refusing action.

The requested resource could not be found but may be available in the future.

A request method is not supported for the requested resource.

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

A generic error message, given when an unexpected condition was encountered and no more specific message is suitable.

The server was acting as a gateway or proxy and received an invalid response from the upstream server.

The server is currently unavailable (because it is overloaded or down for maintenance).

The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.