JSON to Rust Struct
Generate serde-ready Rust structs from a sample JSON document.
Every HTTP status code, searchable, with what it actually means.
The complete HTTP status code list, searchable by number, name or intent, with a practical explanation of each rather than its specification wording — including which codes require a companion header to be implemented correctly.
The complete list of HTTP status codes, searchable by number, by name or by what you are trying to describe. Each entry says what the code means in practice rather than quoting the specification back at you.
The distinctions that actually matter are spelled out: why 401 means unauthenticated despite being named Unauthorized, why 403 means authentication will not help, when to send 422 rather than 400, and why 307 exists when 302 already did. Codes that require a companion header — 405 needs Allow, 401 needs WWW-Authenticate, 429 should carry Retry-After — are marked, because omitting them is the most common way a correct status code is still implemented wrongly.
Why 401 means unauthenticated, why 403 means authenticating will not help, and when 422 beats 400 — the distinctions that decide which code to send.
405 needs Allow, 401 needs WWW-Authenticate, 429 should carry Retry-After. Omitting those is the usual way a correct code is still implemented wrongly.
Type a number, part of a name, or a phrase such as "rate limit" and the matching codes surface.
Narrow to informational, success, redirection, client error or server error when you are choosing rather than looking up.
From 100 through 511, including the WebDAV codes and 418, which every framework implements anyway.
Type a number, a name, or a phrase such as "rate limit".
Narrow to informational, success, redirection, client error or server error.
Each code has a practical explanation, not just its official name.
Click a code or its name to copy it.
401 means the server does not know who you are — authenticate and try again. 403 means it knows exactly who you are and is refusing anyway, so authenticating will not help.
400 when the request cannot be parsed at all, such as malformed JSON. 422 when it parses fine but the values are wrong. Many APIs use 400 for both, which is acceptable but less informative.
301 only when the move is genuinely permanent — browsers and search engines cache it aggressively and it is very hard to undo. For anything temporary use 302, or 307 if the method must be preserved.
It began as an April Fools joke in 1998 and was never a serious part of HTTP. It is, however, implemented by most major frameworks and defended often enough that it is not going away.
What people who use the HTTP Status Codes think of it. Reviews come from visitors and are posted as written.
No ratings yet
Yours would be the first.
0 reviews
Newest first
No reviews yet
Be the first to rate the HTTP Status Codes. It takes half a minute and no account.
Write the first reviewGenerate serde-ready Rust structs from a sample JSON document.
Convert JSON into a PHP array literal or a typed class you can paste into a project.
Verify a download by computing its SHA-256 without uploading it anywhere.
Measure text in UTF-8 bytes, code points, UTF-16 units and graphemes.
Build a docker-compose.yml with databases, caches and health checks.
Strong random passwords and passphrases, generated locally.
Read a cron expression in plain English and see when it next runs.
Find the MIME type for any file extension, or the extensions for a type.