Status class · Client error
4xx Client Error
Client-side request issues such as invalid syntax, missing resources, or permission failures.
- 400Bad RequestThe server cannot parse or accept the malformed request.
- 401UnauthorizedValid credentials are missing or wrong; authenticate.
- 402Payment RequiredReserved for payment flows; rarely used consistently.
- 403ForbiddenIdentity is known, but this action is not allowed.
- 404Not FoundNo resource found at this URL.
- 405Method Not AllowedThe method is not allowed for this resource.
- 406Not AcceptableCannot produce a representation matching the Accept headers.
- 407Proxy Authentication RequiredThe proxy in between needs credentials before forwarding.
- 408Request TimeoutServer gave up waiting for the complete request.
- 409ConflictThe request conflicts with the resource current state.
- 410GoneThe resource is gone and will not come back.
- 411Length RequiredThe server refuses requests without a Content-Length.
- 412Precondition FailedA conditional header (If-Match, etc.) evaluated to false.
- 413Content Too LargeRequest body is larger than the server accepts.
- 414URI Too LongThe request URL is longer than the server accepts.
- 415Unsupported Media TypeThe request body media type is not supported.
- 416Range Not SatisfiableThe requested byte range is outside the resource’s size.
- 417Expectation FailedThe server can’t meet the request’s Expect header.
- 418I'm a teapotRFC 2324 (joke)RFC 2324’s joke teapot; sometimes used to reject bots.
- 419Page ExpiredLaravelLaravel: the CSRF token did not match the session (often an expired form).
- 421Misdirected RequestThe request reached a server that can’t answer for this host.
- 422Unprocessable ContentSyntax is valid but the content fails validation.
- 423LockedWebDAVWebDAV: the resource is locked.
- 424Failed DependencyWebDAVWebDAV: failed because an action it depended on failed.
- 425Too EarlyThe server won’t risk processing a replayable TLS early-data request.
- 426Upgrade RequiredThe client must upgrade to a different protocol.
- 428Precondition RequiredThe server requires a conditional request.
- 429Too Many RequestsRate limit hit; slow down and check Retry-After.
- 431Request Header Fields Too LargeRequest headers are too large.
- 444No Responsenginxnginx closed the connection without sending any response.
- 451Unavailable For Legal ReasonsBlocked for legal reasons.
- 460Client Closed ConnectionAWS ALBAWS ALB: the client closed the connection before the idle timeout.
- 463Too Many Forwarded IP AddressesAWS ALBAWS ALB: X-Forwarded-For contains more than 30 IP addresses.
- 464Incompatible Request ProtocolAWS ALBAWS ALB: request protocol conflicts with the target group protocol version.
- 497HTTP Request Sent to HTTPS Portnginxnginx: a plain HTTP request hit an HTTPS port (clients see a 400).
- 499Client Closed Requestnginxnginx log code: the client hung up before the response.
Explore Other Status Classes
- 4 codes
1xx Informational
Interim responses that indicate request progress before a final response is sent.
- 9 codes
2xx Success
Responses indicating the request was accepted and processed successfully.
- 7 codes
3xx Redirection
Responses that tell clients to perform additional actions, usually by following a new URL.
- 22 codes
5xx Server Error
Server-side failures where the request was valid but the server could not complete it.