HTTP Status Codes
Complete reference for HTTP response status codes
The client should continue with the request. Used to tell the client that the initial part of the request has been received.
Server is switching to a different protocol as requested by the client.
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 was successful. The meaning depends on the HTTP method used.
The request succeeded and a new resource was created as a result.
Request received but not yet acted upon. Processing happens asynchronously.
Returned metadata is not from the origin server but from a local or third-party copy.
Request succeeded but there is no content to send in the response.
The server is delivering only part of the resource due to a range header sent by the client.
Multiple status codes for multiple sub-requests in WebDAV.
Members of a DAV binding already enumerated in a previous reply.
Server fulfilled a GET request and the response is a result of instance manipulations.
The URL of the requested resource has changed permanently. The new URL is given in the response.
The URL of the requested resource has changed temporarily. Further changes may occur.
Server sends this response to direct the client to get the requested resource at another URI with a GET request.
Used for caching. Tells the client that the response has not changed, so it can use its cached version.
Server sends this response to direct the client to get the requested resource at another URI with the same method.
Permanent redirect that preserves the HTTP method used in the original request.
Server cannot process the request due to malformed syntax or invalid request message framing.
Authentication is required and has not been provided or is invalid.
Reserved for future use; sometimes used for digital payment requirements.
Client does not have access rights to the content. Unlike 401, the identity is known.
The server cannot find the requested resource. The URL is not recognized.
The request method is known but is not supported for the target resource.
Server cannot produce a response matching the list of acceptable values defined in the request headers.
Server did not receive a complete request message within the time it was prepared to wait.
The request conflicts with the current state of the server.
The target resource is no longer available and will not be available again.
Server refused the request because the Content-Length header field is missing.
Server refuses the request because the payload is larger than the server is willing to process.
The URI requested by the client is longer than the server is willing to interpret.
Server refuses to accept the request because the payload format is in an unsupported format.
Server understands the content type but is unable to process the instructions.
The resource being accessed is locked.
Indicates the server is unwilling to risk processing a request that might be replayed.
User has sent too many requests in a given amount of time (rate limiting).
Server refuses to process the request because the header fields are too large.
Server is denying access to a resource due to legal demands.
Server has encountered a situation it does not know how to handle.
Request method is not supported by the server and cannot be handled.
Server, acting as a gateway, got an invalid response from upstream server.
Server is not ready to handle the request. Common causes are down for maintenance or overloaded.
Server acting as a gateway did not get a timely response from the upstream server.
HTTP version used in the request is not supported by the server.
Server has an internal configuration error in transparent content negotiation.
Server is unable to store the representation needed to complete the request.
Server detected an infinite loop while processing the request.
Further extensions to the request are required for the server to fulfil it.
Client needs to authenticate to gain network access.