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 is acknowledging that it will do so.
Indicates that the server has received and is processing the request, but no response is available yet.
The request was successful and the server returned the requested resource.
The request was successful, and as a result, a new resource has been created.
The request has been received but not yet acted upon. It’s a non-committal response.
The request was successful but the returned data may be from a third-party source (e.g., cached data).
The request was successful, but the server is not returning any content.
The request was successful, but the client should reset its view.
The server is delivering only part of the resource due to a range header sent by the client.
There are multiple options for the resource.
The resource has been permanently moved to a new URL.
The resource is temporarily located at a different URL.
The response to the request can be found under another URL, and should be retrieved using a GET method.
The resource has not been modified since the last request.
The requested resource is temporarily located at a different URL.
The resource has been permanently moved, and future requests should use the new URL.
The server cannot process the request due to client-side issues (e.g., malformed syntax).
Authentication is required and has failed or has not been provided.
The server understands the request but refuses to authorize it.
The server cannot find the requested resource.
The request method is known by the server but has been disabled and cannot be used.
The requested resource is not available in a format acceptable to the client.
The client must authenticate itself with the proxy.
The server timed out waiting for the request.
The request could not be processed due to a conflict in the current state of the resource.
The requested resource is no longer available and has been permanently removed.
The server refuses to accept the request without a defined Content-Length header.
The server does not meet one of the preconditions specified by the client.
The request is too large for the server to process.
The requested URI is too long for the server to process.
The media format of the requested data is not supported by the server.
The client has asked for a portion of the file (byte serving), but the server cannot supply that portion.
The server cannot meet the requirements of the Expect header in the request.
An Easter egg code from an April Fools' joke.
The server understands the content type of the request entity, but was unable to process the contained instructions.
The client should switch to a different protocol.
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, while acting as a gateway or proxy, received an invalid response from the upstream server.
The server is currently unable to handle the request due to temporary overload or scheduled maintenance.
The server, while acting as a gateway or proxy, did not get a timely response from the upstream server.
The server does not support the HTTP version used in the request.
The client needs to authenticate to gain network access.