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 request was successful.
The request has been fulfilled and a new resource has been created.
The request was successful but there is no content to return.
The server is delivering only part of the resource due to a range header.
The requested resource has been permanently moved to a new URL.
The requested resource temporarily resides under a different URL.
The resource has not been modified since the last request.
The request should be repeated with another URL but future requests should use the original.
The request and all future requests should be repeated using another URL.
The server cannot process the request due to something perceived to be a client error.
Authentication is required and has failed or has 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 the requested resource.
The server timed out waiting for the request.
The request could not be completed due to a conflict with the current state.
The resource requested is no longer available and will not be available again.
The request entity is larger than the server is willing to process.
The server refuses to brew coffee because it is, permanently, a teapot.
The request was well-formed but semantically erroneous.
The user has sent too many requests in a given amount of time.
The resource is unavailable due to legal demands.
The server encountered an unexpected condition.
The server received an invalid response from an upstream server.
The server is currently unable to handle the request.
The server did not receive a timely response from an upstream server.