The server has received the request headers and the client should proceed to send the request body.
The server is switching protocols 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 succeeded and a new resource has been created.
The request has been accepted for processing, but the processing has not been completed.
The server successfully processed the request but is not returning any content.
The server is delivering only part of the resource due to a range header sent by the client.
The resource has been permanently moved to a new URL. Future requests should use the new URL.
The resource temporarily resides at a different URL. The client should continue using the original URL.
The response to the request can be found under a different URI using GET method.
The resource has not been modified since the last request. Use cached version.
The request should be repeated with another URI, but future requests should still use the original.
The resource has permanently moved. The request method should not change.
The server cannot process the request due to client error (malformed syntax, invalid request).
Authentication is required. The client must authenticate itself to get the response.
The client does not have access rights to the content. Unlike 401, identity is known.
The server cannot find the requested resource. The URL is not recognized.
The request method is not supported for the requested resource.
The server timed out waiting for the request from the client.
The request conflicts with the current state of the server.
The resource is no longer available and will not be available again.
The request was well-formed but semantic errors prevent it from being processed.
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 acting as a gateway received an invalid response from the upstream server.
The server is not ready to handle the request. Common causes: maintenance or overload.
The server acting as a gateway did not receive a timely response from the upstream server.
The server does not support the HTTP protocol version used in the request.