The server has received the request headers and the client should proceed to send the body.
The requester has asked the server to switch protocols.
The request succeeded.
The request succeeded and a new resource was created.
The request has been accepted for processing, but processing isn't complete.
The server successfully processed the request but is not returning content.
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 resource hasn't changed since the last request — use the cached version.
Like 302, but the request method must not change.
Like 301, but the request method must not change.
The server cannot process the request due to a client error.
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.
The request method is not supported for this resource.
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 limits the server is willing to process.
The media format of the requested data is not supported.
The request was well-formed but contains semantic errors.
The user has sent too many requests in a given amount of time.
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, often due to overload or maintenance.
The upstream server failed to send a request in time.