Loading HTTP status reference...
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 has agreed to do so.
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 a new resource has been created.
The request has been accepted for processing, but the processing has not been completed.
The returned information may be from a local or third-party copy.
The server successfully processed the request but is not returning any content.
The server successfully processed the request, asks the requester to reset its document view.
The server is delivering only part of the resource due to a range header.
The message body contains multiple status codes for multiple sub-requests.
The members of a DAV binding have already been enumerated.
The server has fulfilled a request for the resource with instance-manipulations.
Multiple options for the resource from which the client may choose.
This and all future requests should be directed to the given URI.
The resource resides temporarily under a different URI.
The response to the request can be found under another URI using GET.
The resource has not been modified since the last request.
The request should be repeated with another URI but future requests should still use the original URI.
The request and all future requests should be repeated using another URI.
The server cannot process the request due to something perceived as a client error.
Authentication is required and has failed or has not been provided.
Reserved for future use. Originally intended for digital payment schemes.
The request was valid, but the server is refusing action. Authentication will not help.
The requested resource could not be found but may be available in the future.
A request method is not supported for the requested resource.
The requested resource can only generate content not acceptable per 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 current state of the resource.
The resource requested is no longer available and will not be available again.
The request did not specify the length of its content.
The server does not meet one of the preconditions in the request headers.
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 does not support.
The client has asked for a portion of the file the server cannot supply.
The server cannot meet the requirements of the Expect request-header field.
The server refuses to brew coffee because it is, permanently, a teapot.
The request was well-formed but was unable to be followed due to semantic errors.
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 the header fields are too large.
The resource is unavailable due to a legal demand.
A generic error message when the server encounters an unexpected condition.
The server either does not recognize the request method or lacks the ability to fulfill it.
The server was acting as a gateway and received an invalid response from the upstream server.
The server cannot handle the request (overloaded or down for maintenance).
The server was acting as a gateway and did not receive a timely response from the upstream server.
The server does not support the HTTP version used in the request.
Transparent content negotiation 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 the request.
Further extensions to the request are required for the server to fulfill it.
The client needs to authenticate to gain network access.