Complete reference guide to HTTP status codes and their meanings.
The request has succeeded. The response depends on the HTTP method used.
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 server successfully processed the request but is not returning any content.
The server is delivering only part of the resource due to a range header sent by the client.
The requested resource has been permanently moved to a new location.
The requested resource has been temporarily moved to a different location.
The resource has not been modified since the last request.
The requested resource has been temporarily moved to a different location.
The requested resource has been permanently moved to a new location.
The server cannot process the request due to invalid syntax or malformed request.
Reserved for future use. Originally intended for digital payment systems.
Authentication is required and has failed or has not been provided.
The server understood the request but refuses to authorize it.
The server can not find the requested resource.
The request method is not supported for the requested resource.
The server cannot produce a response matching the list of acceptable values.
Authentication is required to access the proxy server.
The request could not be completed due to a conflict with the current state of the resource.
The server refuses to accept the request without a defined Content-Length header.
One or more conditions given in the request header fields evaluated to false.
The server timed out waiting for the request.
The requested resource is no longer available and will not be available again.
The request entity is larger than limits defined by the server.
The URI provided was too long for the server to process.
The media format of the requested data is not supported by the server.
The range specified in the request's Range header field cannot be fulfilled.
The expectation given in the request's Expect header field could not be met by the server.
This is a joke status code from RFC 2324. It indicates that the server refuses to brew coffee because it is a teapot.
The request was directed at a server that is not able to produce a response.
The request was well-formed but contains semantic errors.
The resource that is being accessed is locked.
The request failed because it depended on another request that failed.
The server refuses to perform the request using the current protocol.
The origin server requires the request to be conditional.
The server is unwilling to process the request because its header fields are too large.
The user has sent too many requests in a given amount of time.
The server is denying access to the resource as a consequence of a legal demand.
The server has encountered a situation it does not know how to handle.
The server does not support the functionality required to fulfill the request.
The server, while acting as a gateway, received an invalid response from the upstream server.
The server is temporarily unable to handle the request due to maintenance or overload.
The server, while acting as a gateway, 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 that prevents it from completing the request.
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.