A fast, searchable table of common RFC 9110–style codes (1xx–5xx) plus a few widely seen non-standard responses (nginx, Cloudflare). Filter by series, search by number or phrase, and click a row to copy — everything runs in your browser with no server round-trips.
| Code | Reason phrase | Meaning |
|---|
Every HTTP response includes a three-digit status code that classifies the outcome: informational (1xx), success (2xx), redirection (3xx), client error (4xx), or server error (5xx). APIs, browsers, CDNs, and proxies all rely on these codes — along with headers and bodies — to decide caching, retries, and error handling.
The table lists IANA-registered semantics as described in RFC 9110 (HTTP semantics), including WebDAV-related codes where they are commonly encountered. A small Extensions filter covers non-standard codes you may see in nginx or Cloudflare edge responses — they are labeled Non-standard in the table.
When you build REST or mobile backends, pairing the right status with a clear error body (problem+json, JSON errors, or protobuf) matters as much as the number itself. Use 4xx for caller-fixable issues (validation, auth, not found) and 5xx for failures after the request reached your app logic or upstream dependencies.
In HTTP/1.1 the textual reason phrase appears on the status line; in HTTP/2 and HTTP/3 the code is carried in binary frames without that phrase. Intermediaries may normalize or omit wording — clients should rely on the numeric code and response headers, not exact phrase text.
No. The reference is embedded in the page script. Search and filters run entirely in your browser; nothing is transmitted to DroidXP for this feature.
This page focuses on standard and commonly encountered codes. IANA may assign additional codes over time; vendor-specific codes exist beyond nginx/Cloudflare examples here. For authoritative registration data, consult the IANA HTTP Status Code Registry.
Frameworks and proxies sometimes substitute or localize text. The number is what clients and caches key on; treat phrases as informative, not contractual.
302 Found historically allowed changing POST to GET on redirect; behavior varied. 307 Temporary Redirect and 308 Permanent Redirect preserve the original method and body. Prefer 307/308 when method preservation matters.
It originated as an April Fools joke (RFC 2324). Some stacks return it for fun or as a placeholder. Do not rely on it for production API contracts.
401 Unauthorized means authentication is missing or invalid (often with WWW-Authenticate). 403 Forbidden means the server understood who you are but
refuses access. (Naming is confusing: “Unauthorized” really means “unauthenticated” in practice.)
They are non-standard extensions used by those products between the edge and the client. Browsers may display them when the edge cannot reach your origin. Your origin may never emit them directly.
Many APIs use 422 Unprocessable Content when JSON is syntactically fine but business rules fail; others use 400 Bad Request for everything invalid. Pick one convention per API and document it.