RFC for 700 HTTP Status Codes (2012)(github.com)
github.com
RFC for 700 HTTP Status Codes (2012)
https://github.com/joho/7XX-rfc
64 comments
Needs something like 708 - Single dev that knew how this house of cards worked is dead.
«Relied On A Cloud Provider For Redundance» is missing. Typically misclassified as 503, but really belongs in 77x
That's not my (the developer's) fault. 787. Talk to the bean counters.
You could have hosted it on your work laptop and you know it.
They gave me an abacus. 787.
Really enjoyed "718 - I am not a teapot", a clever nod to "418 - I'm a teapot":
https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/418
https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/418
You realize that 418 really means, "I am not a coffee maker", right?
This is wasteful trash and has no place in a standard.
Good thing it's not in the HTTP standard but in a joke standard then.
79x needs something akin to "Global nuclear fallout; internet failed to live up to design requirements"
Also needs a reference to the AI Singularity ~ i.e. Skynet and the Robot Apocalypse.
Isn't that just a special case of 794?
001
Big fan of “786 - Try it now”
Bug report: "733 - Fucking Deadlocks" shouldn't be there? What kind of fake BS deadlock would let the server send back a status code?
read it as a verb instead
And that’s how you get a bat virus folks.
Sounds like "911 - Immediate Medical Attention Required"
would still be too busy
747: Server in Airplane Mode.
Missing an entry about "Missed the Balmer peak by that much"
Past threads:
RFC for 7xx HTTP status - https://news.ycombinator.com/item?id=17577434 - July 2018 (11 comments)
RFC for the 7XX Range of HTTP Status Codes – Developer Errors - https://news.ycombinator.com/item?id=10467470 - Oct 2015 (2 comments)
RFC for the 7XX Range of HTTP Status codes - Developer Errors - https://news.ycombinator.com/item?id=5442957 - March 2013 (2 comments)
HTTP 7xx: developer errors - https://news.ycombinator.com/item?id=3497866 - Jan 2012 (7 comments)
RFC for 7xx HTTP status - https://news.ycombinator.com/item?id=17577434 - July 2018 (11 comments)
RFC for the 7XX Range of HTTP Status Codes – Developer Errors - https://news.ycombinator.com/item?id=10467470 - Oct 2015 (2 comments)
RFC for the 7XX Range of HTTP Status codes - Developer Errors - https://news.ycombinator.com/item?id=5442957 - March 2013 (2 comments)
HTTP 7xx: developer errors - https://news.ycombinator.com/item?id=3497866 - Jan 2012 (7 comments)
787 should be Plane Crash
It could also be "IT didn't turn it off and on again" in reference to https://www.theregister.com/2020/04/02/boeing_787_power_cycl...
Unfortunately these have not (as yet) been added to http.cat
777 - "Idiot dev that wrote this thought that pure belief would keep the steam shovel rolling"
This might actually be useful!
[deleted]
737 - FuckThreadsing
Pretty clever :-)
Pretty clever :-)
Propose "769: Burning Man"
777 - Jackpot
762 - Stoned.
Should be HTTP 420. Except that'd be a client error.
Twitter used to return that for rate limiting (with a status message of "Enhance Your Calm") before 429 became standard.
I mean... that makes more sense
This is super cringe.
778 - not everyone approves
Hey, it's HN, if you're not up for super cringe perhaps you shouldn't be here? Or maybe you mean there should be a 7xx code for "This is super cringe"?