Our HTTP reference library maps each status code to standards-based semantics and real remediation paths for API and web teams. Every page clarifies when a response is expected, when it signals a defect, and how to verify the fix in production traffic.
These are the highest-signal HTTP pages for common production failures and the best first routes for internal linking and early user navigation.
Priority guide
Internal Server Error
Fix HTTP 500 by correlating stack traces, release changes, and dependency health to isolate deterministic code bugs, config drift, or late-translated...
->Priority guide
Too Many Requests
Fix HTTP 429 by tracing limiter dimensions, Retry-After behavior, and client backoff design to stop retry storms and quota spikes.
->Priority guide
Unauthorized
Fix HTTP 401 by tracing WWW-Authenticate challenges, bearer token claims, session cookies, and proxy header forwarding on the exact failing route.
->Priority guide
Forbidden
Fix HTTP 403 by tracing authenticated identity, denied action, resource scope, and explicit policy or WAF blocks for the exact route.
->Priority guide
Not Found
Fix HTTP 404 by validating route version, resource ID, tenant scope, and stale links before changing application logic.
->When you need broader context, move from provider-specific pages into the matching error category or incident playbook before changing production behavior.
Showing 46-60 of 62.
HTTP 425 Too Early means the server is unwilling to process a request that could be replayed.
HTTP 426 Upgrade Required means the server refuses current protocol and requires the client to switch protocols.
HTTP 428 Precondition Required means the origin requires conditional requests to prevent lost updates.
HTTP 429 Too Many Requests means a limiter rejected this request because the caller exceeded a rate, quota, or burst policy for the active window.
HTTP 431 Request Header Fields Too Large means one header field or the overall header section is larger than a server or intermediary is willing to process.
HTTP 451 Unavailable For Legal Reasons means access is denied due to legal demands or legal policy constraints.
HTTP 500 Internal Server Error means the application or a dependency hit an unexpected failure path and the server could not return a valid response.
HTTP 501 Not Implemented means the server does not support the functionality required to fulfill this request.
HTTP 502 Bad Gateway means a gateway or proxy received an invalid response from an upstream server.
HTTP 503 Service Unavailable means the server is temporarily unable to handle the request due to overload or maintenance.
HTTP 504 Gateway Timeout means a gateway or proxy did not receive a timely response from an upstream server.
HTTP 505 HTTP Version Not Supported means the server does not support the major HTTP version used in the request.
HTTP 506 Variant Also Negotiates means transparent content negotiation is misconfigured and selected variants are themselves negotiable.
HTTP 507 Insufficient Storage means the server cannot store the representation needed to complete this request.
HTTP 508 Loop Detected means the server found an infinite loop while processing recursive or depth-based operations.