The Save 418 Movement We are the teapots.
Any attempt to brew coffee with a teapot should result in the error code "418 I'm a teapot". The resulting entity body MAY be short and stout. See RFC2324 Section 2.3.2
The application of such an status code is boundless.
Its utility, quite simply, is astonishingly unparalleled.
It’s a reminder that the underlying processes of computers are still made by humans. It'd be a real shame to see 418 go.
Luckily, you went out there and expressed your concerns regarding the ramifications of removing such a wonderful error code from the internet! We saved 418.
The Internet Engineering Task Force is officially working on reserving 418 . Consider its place in HTTP cemented for a very, very long time. Thanks for everything Mark Nottingham, you put up a good fight! =)
Endorsement from the author of HTCPCP-TEA: “I’m the author of RFC 7168, which extends HTCPCP to allow for the brewing of various teas in supporting Internet-connected teapots. I think you’re doing a great thing, trying to save something of the old whimsical Internet from the ravages of the Overly Professional.”
d4rch0n on August 12nd, 2017 at 01:34 UTC »
Seeing as a lot of people write APIs that only use GET/POST with response statuses 200 or 500, I don't care either way.
One huge pet peeve of mine is getting back a 200 {"success": false}
copyrightisbroke on August 12nd, 2017 at 00:48 UTC »
that tea party is pretty powerful
sgtfrankieboy on August 11st, 2017 at 22:37 UTC »
Mark Nottingham both made the GitHub Issues and wrote the draft.
Reading the draft he added in that the status code can still be replaced if all other 4xx status codes have been exhausted.