tools.http-status-ref.desc
The initial part of the request has been received and has not yet been rejected by the server.
The server understands and is willing to comply with the client's request to change the application protocol being used on this connection.
The server has received and is processing the request, but no response is available yet.
Used to return some response headers before the final HTTP message is ready.
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 metadata is not exactly the same as available from the origin server, but is collected from a local or third-party copy.
The server successfully processed the request and is not returning any content.
The server successfully processed the request and asks 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 response body contains status information for multiple independent operations.
The members of a DAV binding have already been enumerated in a preceding part of the response and are not being included again.
The server has fulfilled a GET request for the resource, and the response is a representation of the result of one or more instance-manipulations applied to the current instance.
The request has more than one possible response. The user-agent or user should choose one of them.
The URL of the requested resource has been changed permanently. The new URL is given in the response.
The URI of the requested resource has been changed temporarily. Further changes may be made to the URI in the future.
The server redirects the client to a different URI, typically to confirm the result of a POST or PUT operation.
The resource has not been modified since the version specified by the request headers.
The requested resource is only available through a proxy, whose address is provided in the response.
No longer used. Originally meant that subsequent requests should use the specified proxy.
The server sends a temporary redirect to the target resource. The client must not change the HTTP method used.
The resource has been permanently moved to another URI and the client must not change the HTTP method used.
The server cannot or will not process the request due to something perceived as a client error.
The client must authenticate itself to get the requested response.
Reserved for future use as a digital payment status code.
The client does not have access rights to the content. The server understood the request but refuses to authorize it.
The server cannot find the requested resource. This is probably the best-known HTTP status code.
The HTTP method is known by the server but is not supported by the target resource.
The server cannot produce a response matching the list of acceptable values defined in the request's proactive content negotiation headers.
Similar to 401 but authentication is needed to be done by a proxy.
The server would like to shut down this unused connection.
The request conflicts with the current state of the target resource.
The target resource is no longer available at the origin server and this condition is likely to be permanent.
The server refuses to accept the request without a defined Content-Length header.
One or more conditions given in the request headers evaluated to false on the server.
The request entity is larger than limits defined by the server.
The URI requested by the client is longer than the server is willing to interpret.
The media format of the requested data is not supported by the server.
The Range header field in the request cannot be fulfilled.
The expectation given in the Expect request header could not be met by the server.
The server refuses the attempt to brew coffee with a teapot.
The request was directed at a server that is not able to produce a response.
The server understands the content type and syntax of the request but was unable to process the contained instructions.
The resource that is being accessed is locked.
The request failed because it depended on another request that also failed.
The server is unwilling to risk processing a request that might be replayed.
The server refuses to perform the request using the current protocol but might do so after the client upgrades 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 (rate limiting).
The server is unwilling to process the request because its header fields are too large.
The server is denying access to the resource as a consequence of a legal demand.
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 not ready to handle the request.
The server, while acting as a gateway or proxy, did not receive a timely response from the upstream server.
The server does not support the HTTP protocol version used in the request.
The server has an internal configuration error: the chosen variant resource is configured to engage in transparent content negotiation itself.
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.