Server has received request headers, client should send the body.
http status.
every http status code with a plain-english description and common causes. search by number, name, or a phrase in the description.
61 of 61
Server is switching protocols as requested by the client.
common causes: WebSocket upgrade.
Server has received and is processing the request.
Preliminary response for resource hints before the final response.
Request succeeded. The meaning depends on the HTTP method.
Request succeeded and a new resource was created.
common causes: Typical for POST requests.
Request accepted but processing is not complete.
Response from a transforming proxy, not the origin.
Success; no body to return.
common causes: DELETE, PUT often return this.
Tell the client to reset the document view.
Response body contains only part of the resource.
common causes: Range requests, resumable downloads.
WebDAV: body contains multiple status codes.
WebDAV: already enumerated in a prior part of this response.
Server applied instance-manipulations to the request.
Multiple options for the resource.
Resource has a new URL, use it from now on.
common causes: SEO-friendly redirect.
Resource is temporarily at another URL.
common causes: Default redirect in many frameworks.
Client should GET a different URL (changes method to GET).
common causes: POST-redirect-GET pattern.
Cached version is still fresh; no body.
common causes: Conditional GET with If-None-Match / If-Modified-Since.
Like 302 but preserves the HTTP method.
Like 301 but preserves the HTTP method.
Request was malformed and could not be understood.
Authentication required or failed.
common causes: Missing / invalid auth header.
Reserved for future use (rare in the wild).
Server understands but refuses to authorize.
common causes: Insufficient permissions, rate-limit (sometimes), geo-block.
Resource does not exist at that URL.
The method is known but not supported by this resource.
common causes: Trying POST on a read-only endpoint.
Server cannot produce a response matching the Accept headers.
Client must authenticate with the proxy.
Server timed out waiting for the client.
Request conflicts with the current state of the resource.
common causes: Edit conflicts, unique constraint violations.
Resource intentionally no longer exists.
Server requires a Content-Length header.
A precondition in the request headers was not met.
Request body is too big.
common causes: Upload limits.
URL is too long for the server to handle.
Server cannot accept the request body format.
Range header asks for a portion outside the resource.
Server cannot meet the Expect header requirements.
RFC 2324 joke — short and stout.
common causes: Easter eggs, sometimes used for bot deterrence.
Request sent to a server that cannot produce a response.
Semantic errors in a well-formed request.
common causes: Validation failures.
WebDAV: resource is locked.
WebDAV: request failed due to a prior request failing.
Server is unwilling to risk processing a replayable request.
Client should switch to a different protocol.
Origin requires the request to be conditional.
Rate-limited.
common causes: Check Retry-After header.
Headers exceed server limits.
Resource removed due to legal demand.
common causes: Court order, government takedown.
Generic error — something went wrong on the server.
Server does not support the request method.
Gateway or proxy got an invalid response from upstream.
common causes: Upstream crashed or unreachable.
Server is overloaded or down for maintenance.
Gateway did not receive a timely response from upstream.
Server does not support the requested HTTP version.
Content negotiation cycle / misconfigured.
WebDAV: server cannot store the representation.
WebDAV: infinite loop detected while processing.
Further extensions to the request are required.
Client must authenticate to gain network access.
common causes: Captive portals.