Reference
HTTP Status Codes
61 codes across 5 classes — RFC 9110 & extensions
The client should continue with its request; initial part has been received.
Server agrees to switch protocols per the Upgrade header.
Server received and is processing the request, no response yet.
Used to return headers before the final response, for preloading assets.
Request succeeded. The response body contains the requested resource.
Request succeeded and a new resource was created. Location header points to it.
Request accepted for processing but not yet completed (async operations).
Request succeeded but response comes from a transforming proxy, not the origin.
Request succeeded, no body to return. Common for DELETE and PUT.
Request succeeded; client should reset the document/form that sent the request.
Partial content delivered per a Range request header. Used for resumable downloads.
Multiple status codes for different operations in a single response body.
DAV binding members already enumerated in a prior part of the same multistatus.
The server has fulfilled a GET request for a resource with instance-manipulations.
Multiple possible responses; the user or user agent should choose one.
Resource permanently moved to a new URL. Browsers re-send to new URL.
Resource temporarily moved to a different URL. Client should use original URL next time.
Response to POST: the resource can be found at a different URL using GET.
Cache is up to date; no need to retransmit the requested resource.
Temporary redirect; method and body MUST NOT change on redirect (unlike 302).
Permanent redirect; method and body MUST NOT change on redirect (unlike 301).
Server cannot process the request due to malformed syntax or invalid parameters.
Authentication is required and has failed or not been provided.
Reserved for future use; some APIs use it for rate limit or quota exceeded.
Server understood the request but refuses to authorize it — valid credentials won't help.
Requested resource could not be found on the server.
HTTP method is not supported for the requested resource.
No content matching the Accept headers of the request.
Client must first authenticate with the proxy.
Server timed out waiting for the request from the client.
Request conflicts with the current state of the resource (e.g., edit conflict).
Resource is permanently gone; no forwarding address. Different from 404 — intentional removal.
Server requires Content-Length header but it was not sent.
One or more conditions in the request headers evaluated to false on the server.
Request body exceeds the limits defined by the server.
The URI requested by the client is longer than the server is willing to process.
Media format of the request body is not supported by the server.
Range header value cannot be fulfilled; outside the resource's bounds.
Expectation indicated by the Expect request header cannot be met by the server.
Server refuses to brew coffee in a teapot. An April Fools' joke in RFC 2324.
Request was directed to a server unable to produce a response for that combination.
Request is well-formed but contains semantic errors (e.g., validation failures).
Resource is locked.
Request failed due to failure of a previous request.
Server is unwilling to risk processing a request that might be replayed.
Client should switch to a different protocol specified in the Upgrade header.
Origin server requires the request to be conditional to prevent lost-update problems.
Client has sent too many requests in a given amount of time (rate limiting).
Server unwilling to process the request because header fields are too large.
Resource cannot be provided due to legal demands (e.g., government censorship).
Generic server error — an unexpected condition was encountered.
Server does not support the functionality required to fulfill the request.
Server acting as a gateway got an invalid response from an upstream server.
Server is not ready to handle the request — overloaded or down for maintenance.
Server acting as a gateway did not get a response in time from the upstream server.
HTTP version used in the request is not supported by the server.
Server has an internal configuration error in content negotiation.
Server cannot 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 must authenticate to gain network access (e.g., captive portals).
Showing 61 of 61 codes