Explore the complete list of HTTP status codes and their meanings
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.
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 request has been fulfilled and resulted in a new resource being created.
The request has been accepted for processing, but the processing has not been completed.
The server is a transforming proxy and received non-authoritative response.
The server successfully processed the request and is not returning any content.
The server successfully processed the request, and is asking the client to reset the document view.
The server is delivering only part of the resource due to a range header sent by the client.
The message body contains multiple status codes.
The members of a DAV binding have already been enumerated.
The server has fulfilled a GET request for the resource with instance manipulations applied.
The request has more than one possible response.
The URL of the requested resource has been changed permanently.
The URI of requested resource has been changed temporarily.
The response to the request can be found under another URI using a GET method.
The resource has not been modified since the last request.
The requested resource is only available through a proxy.
No longer used.
The request should be repeated with another URI; future requests should still use the original URI.
The resource is now permanently located at another URI.
The server could not understand the request due to invalid syntax.
The client must authenticate itself to get the requested response.
This response code is reserved for future use.
The client does not have access rights to the content.
The server can not find the requested resource.
The request method is known by the server but is not supported by the target resource.
The requested resource is capable of generating only content not acceptable according to the Accept headers.
The client must first authenticate itself with the proxy.
The server timed out waiting for the request.
The request could not be processed because of conflict in the request.
The resource requested is no longer available and will not be available again.
The request did not specify the length of its content, which is required by the resource.
The server does not meet one of the preconditions that the requester put on the request.
The request is larger than the server is willing or able to process.
The URI provided was too long for the server to process.
The request entity has a media type which the server or resource does not support.
The range specified by the Range header field in the request can't be fulfilled.
The server cannot meet the requirements of the Expect request-header field.
The server refuses the attempt to brew coffee with a teapot.
The request was well-formed but was unable to be followed due to semantic errors.
Indicates that the server is unwilling to risk processing a request that might be replayed.
The client should switch to a different protocol.
The origin server requires the request to be conditional.
The user has sent too many requests in a given amount of time.
The server is unwilling to process the request because its header fields are too large.
The user requests an illegal resource, such as a web page censored by a government.
The server has encountered a situation it doesn't know how to handle.
The request method is not supported by the server and cannot be handled.
The server, while acting as a gateway or proxy, received an invalid response from the upstream server.
The server is not ready to handle the request.
The server is acting as a gateway and cannot get a response in time.
The HTTP version used in the request is not supported by the server.
Transparent content negotiation for the request results in a circular reference.
The server is unable to store the representation needed to complete the request.
The server detected an infinite loop while processing a request.
Further extensions to the request are required for the server to fulfill it.
The client needs to authenticate to gain network access.