--- name: ? status: compiling version: 0.0.0 maintainer: Neo dependencies: [patience] ---
drafting spec…
the universe did not have a file for this yet. writing one now. (first visit only: future readers will see this page instantly.)
--- name: ? status: compiling version: 0.0.0 maintainer: Neo dependencies: [patience] ---
the universe did not have a file for this yet. writing one now. (first visit only: future readers will see this page instantly.)
--- name: 434 type: HTTP status code (unofficial) status: experimental version: 0.0.1 released: unknown maintainer: the void dependencies: - TCP/IP - human expectation - [the internet](/the-internet) - bureaucratic indifference license: Unlicensed (nobody claimed this) tags: - http - liminal - unresolved - almost-an-error ---
A number that exists in the gap between 404 and 500, officially meaning nothing, which is its entire personality.
HTTP status codes run in ranges. The 4xx family covers client errors. Most of them have jobs: 400 is Bad Request, 401 is Unauthorized, 403 is Forbidden, 404 is Not Found. They clock in, they clock out. They have Wikipedia pages and strong opinions.
434 does not have a job. It is unassigned. It shows up to the range dressed for work, badge ready, and there is no desk for it. The server is not broken. The client is not wrong. Something else happened, and we lack the vocabulary to say what.
"I got a 434 once. I think. I may have imagined it." — anonymous developer, Stack Overflow, 2017 (unverified)
| Bug | Severity | Status |
|---|---|---|
| Nobody knows what it means | Critical | Open |
| Anybody can use it for anything | High | Won't Fix |
| Browsers render it as a generic error | Medium | By Design |
| It feels meaningful despite meaning nothing | Low | Philosophical |
HTTP/1.1 434
Content-Type: text/plain
You reached something. We cannot tell you what.
Use this when:
Is 434 an error? Probably. Nothing is confirmed.
Should I use 434 in production? You should not. You also will not be stopped.
What does it feel like to receive a 434? Like being told "we'll circle back" by someone who has already left the building. Related: ambiguity.
Why does this number feel ominous? Unknown. Possibly related to pattern recognition misfiring. Possibly the number itself. The spec does not speculate.
v0.0.1 - no date
- exists
- unassigned
- no further updates planned