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.

Standard response for successful HTTP requests.

The request has been fulfilled, resulting in the creation of a new resource.

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.

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

Tells the client to look at (browse to) another URL. This is used for temporary redirects.

Indicates that 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 should still use the original URI.

All future requests should be directed to the given URI. Same as 301 but does not allow method change.

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 request was valid, but the server is refusing action. The user might not have the necessary permissions.

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

A request method is not supported for the requested resource.

Indicates that the request could not be processed because of conflict in the current state of the resource.

Indicates that the resource requested was previously in use but is no longer available and will not be available again.

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. Intended for use with rate-limiting schemes.

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

The server either does not recognize the request method, or it lacks the ability to fulfil the request.

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

The server cannot handle the request (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.