CyberKit

HTTP Status Codes

Every IANA-assigned HTTP status code, grouped by class, with its exact reason phrase.

A status code is the three-digit number at the start of every HTTP response. The phrase next to it is a label for people. Software branches on the number.

The first digit sets the class: 1 informational, 2 success, 3 redirect, 4 client error, 5 server error. Codes come from RFC 9110 and each code's own RFC.

63 rows.

HTTP status codes
CodePhraseDescription
100ContinueAn interim response telling the client the server has received the request headers and hasn't rejected them yet, so the client should go ahead and send the request body (typically after the client sent an Expect: 100-continue header).
101Switching ProtocolsThe server agrees to the protocol change the client asked for in its Upgrade header, for example, upgrading a plain HTTP connection to WebSocket.
102ProcessingA WebDAV extension telling the client that a long-running request is still being worked on, so the connection isn't mistaken for having stalled. Originally defined by RFC 2518, which RFC 4918 later obsoleted.
103Early HintsSent before the final response so the client can start acting on header fields (most commonly preloading resources via a Link header) while the server is still assembling the real reply.
200OKThe request succeeded. Any body carries the requested resource or the result of the action.
201CreatedThe request succeeded and resulted in one or more new resources being created, usually with a Location header pointing at (one of) the new resource(s).
202AcceptedThe request has been accepted for processing, but the processing hasn't completed, and, unlike 200, isn't guaranteed to eventually succeed.
203Non-Authoritative InformationThe request succeeded, but the payload was modified in transit by an intermediary (a transforming proxy) rather than delivered exactly as the origin server sent it.
204No ContentThe request succeeded and there's deliberately no body to send back, common for a successful DELETE, or a form submission that shouldn't navigate the client anywhere.
205Reset ContentThe request succeeded and the server wants the user agent to reset the view that submitted it (e.g. clear a form) rather than navigate away.
206Partial ContentThe server is fulfilling a range request, returning only the requested byte range of the resource (as named in the client's Range header) rather than the whole thing.
207Multi-StatusA WebDAV response covering multiple resources from a single request, where the body itself lists a separate status for each resource instead of one status for the whole request.
208Already ReportedUsed inside a WebDAV multi-status response to avoid re-listing the members of a collection that a previous binding in that same response already enumerated.
226IM UsedThe server fulfilled a GET request by applying one or more "instance manipulations" (such as a delta/diff encoding) to the resource, and the response is the result of those manipulations rather than the full representation.
300Multiple ChoicesThe target resource has more than one representation, and the response lets the client (or user) choose a preferred one rather than the server picking automatically.
301Moved PermanentlyThe resource has permanently moved to a new URI, and future requests should go straight to the URI given in the response's Location header.
302FoundThe resource is temporarily available at a different URI, but the client should keep using the original request URI for future requests.
303See OtherDirects the client to fetch a different resource, normally with a GET, as the result of the request: the standard way to redirect after a POST so a page refresh doesn't resubmit the form.
304Not ModifiedA conditional GET request (one carrying an If-Modified-Since/If-None-Match header) found the resource unchanged, so the client's cached copy is still valid and doesn't need to be re-downloaded.
305Use ProxyDeprecated: told the client it had to access the requested resource only through the proxy given in the response's Location header.
306(Unused)Reserved: the current spec states it must not be used by implementations. An expired 1996 HTTP/1.1 draft had assigned it to a proxy-redirection scheme nicknamed "Switch Proxy," which was never standardized and was dropped over security concerns.
307Temporary RedirectLike 302, the resource is temporarily at a different URI, but unlike 302 the client must repeat the request with the exact same method and body it originally used.
308Permanent RedirectLike 301, the resource has permanently moved, but unlike 301 the client must repeat the request with the exact same method and body it originally used.
400Bad RequestThe server can't or won't process the request because of something it perceives as a client-side problem (malformed syntax, invalid request framing, or similar) without a more specific 4xx code fitting better.
401UnauthorizedNo valid credentials for the target resource. The WWW-Authenticate header tells the client how to authenticate.
402Payment RequiredReserved for future use, for a request that has not been applied because payment is required and the client hasn't made payment. The spec keeps the code number set aside, but no standardized payment scheme has ever been built on top of it.
403ForbiddenThe server understood the request and refuses to fulfill it, unlike 401, authenticating (again) won't help; the client simply lacks permission for this resource.
404Not FoundThe origin server has no current representation for the target resource, and deliberately isn't saying whether that's temporary or permanent.
405Method Not AllowedThe request's HTTP method is known to the server but isn't supported by this particular target resource; the response's Allow header lists which methods are.
406Not AcceptableThe target resource has no representation that would be acceptable given the Accept-family headers the client sent.
407Proxy Authentication RequiredThe same idea as 401, but the client needs to authenticate to a proxy in the request path before that proxy will forward the request onward.
408Request TimeoutThe client didn't finish sending its request in time, so the server closed the connection.
409ConflictThe request conflicts with the resource's current state, such as two concurrent edits colliding.
410GoneThe target resource used to exist here but is no longer available, and this condition is believed to be permanent: a deliberately stronger statement than a plain 404.
411Length RequiredThe request arrived with no Content-Length, and the server requires one.
412Precondition FailedOne or more conditional request headers (such as If-Match or If-Unmodified-Since) evaluated to false when tested against the resource's current state.
413Content Too LargeThe server refuses to process the request because its content is larger than the server is willing or able to handle. RFC 9110 renamed this from the older "Payload Too Large" phrase, which is still what many implementations display.
414URI Too LongThe request URI is longer than the server is willing to interpret.
415Unsupported Media TypeThe request content's format isn't supported by this method on this resource.
416Range Not SatisfiableThe Range header asks for bytes the resource doesn't have.
417Expectation FailedThe expectation stated in the request's Expect header field couldn't be met by the server (or by a proxy in the request chain).
418(Unused)Reserved and formally unassigned. It originated as an April Fools' joke in 1998's RFC 2324, "Hyper Text Coffee Pot Control Protocol," and RFC 9110 later reserved the number outright, in part because the joke had already been implemented so widely.
421Misdirected RequestThe request was directed at a server that can't produce an authoritative response for the target URI: the code most commonly surfaces when a client reuses an HTTP/2 connection across origins (connection coalescing) and the server isn't actually configured for the requested one.
422Unprocessable ContentThe server understands the request's content type and syntax but can't act on the instructions it contains, e.g. a well-formed JSON body that fails validation. Originally a WebDAV-only code named "Unprocessable Entity" (RFC 4918); RFC 9110 folded it into core HTTP semantics under this renamed phrase.
423LockedThe resource is locked, and the request needs the right lock token.
424Failed DependencyThe request failed because it depended on the outcome of another request within the same operation, and that other request failed first.
425Too EarlyThe server isn't willing to risk processing a request that arrived as TLS 1.3 "early data" before the full handshake completed, since early data can potentially be captured and replayed by an attacker.
426Upgrade RequiredThe server refuses to complete the request using the current protocol and requires the client to upgrade to a different one, typically paired with an Upgrade header naming the required protocol.
428Precondition RequiredThe origin server requires the request to be conditional (carry an If-Match-style header), to prevent the "lost update" problem where two clients unknowingly overwrite each other's changes.
429Too Many RequestsToo many requests in too little time. The standard rate-limiting code.
431Request Header Fields Too LargeThe request's header fields are too large, individually or in total.
451Unavailable For Legal ReasonsAccess is denied because of a legal demand, such as a government takedown order.
500Internal Server ErrorThe server hit an unexpected condition and couldn't fulfill the request. It's the catch-all when no more specific 5xx fits.
501Not ImplementedThe server doesn't support what the request needs, such as an unrecognized method.
502Bad GatewayThe server, while acting as a gateway or proxy, received an invalid response from an inbound server it was trying to fulfill the request through.
503Service UnavailableThe server can't handle the request right now, usually from temporary overload or maintenance. Often paired with a Retry-After header.
504Gateway TimeoutThe server, while acting as a gateway or proxy, didn't receive a timely response from an inbound server it needed to complete the request.
505HTTP Version Not SupportedThe server doesn't support the request's major HTTP version.
506Variant Also NegotiatesA server misconfiguration: the resource chosen by transparent content negotiation is itself configured to perform content negotiation, so it isn't a valid negotiation endpoint.
507Insufficient StorageThe server is out of storage space to complete the request.
508Loop DetectedThe server terminated the operation because it encountered an infinite loop while processing a WebDAV request with a Depth: infinity header.
510Not ExtendedThe policy for accessing the resource hadn't been met by the request, and the server wanted the client to resend it with a required extension the response would describe. Defined by RFC 2774's HTTP Extension Framework, which never saw meaningful adoption and is now Historic.
511Network Authentication RequiredSent by an intercepting proxy (the canonical example being a captive portal) to indicate the client needs to authenticate for network access before its request can go through.

Related

All references