russian MoD sites started returning this for foreign IPs shortly after the invasion began last february
418 I'm a teapot
41–50 of 195 posts
Re: 418 I'm a teapot
#42I'm more amused by "A combined coffee/tea pot that is temporarily out of coffee should instead return 503 [Service Unavailable]".
Kinda thought this should respond 404
Re: 418 I'm a teapot
#43I've seen a 418 response on a production system once... on a simple request that took 5 seconds to be fullfiled. Building integrations for duct-taped legacy systems in finance is fun.
it was steeping!
Re: 418 I'm a teapot
#44I honestly use this a lot when I'm testing, because it's basically the only response that can show up where I know god damned well that it's only happening because I programmed it to happen under certain conditions. edit: a common one for me is that if any test passes a post request without a csrf token... sorry, I'm a teapot, because I forgot to add a csrf token to that form.
It’s still in my production code, usually in places where i don’t expect code to ever lead to. It’s just my general “something particularly odd has happened” response.
I do this too for the same reason, but also for the next person that looks at my code to give the joy of laughter.
Re: 418 I'm a teapot
#45Had to think of https://yourmom.zip
Is anyone ever going to use that tld for anything non malicious, non prank, and instead something actually actually serious?
Re: 418 I'm a teapot
#46Earlier quoted context omitted.
It was added as a joke, and kept because (according to https://save418.com ) > “It's a reminder that the underlying processes of computers are still made by humans”
Stupid reason imo. Adding childish humor to a protocol seems like harmless fun until you remember how much of a mess network protocols, and their specs, and their implementation is. Maybe you think a 418 error page is funny, but I think you’ll appreciate it a lot less when your application gets a rather confounding error because some service provider wanted to remind you that the underlying processes of computers are…
...
Nope, it's still funny, we're keeping it.
Re: 418 I'm a teapot
#47Every time this pops up, I'm reminded of the day that the NPM registry started returning 418 responses for users accessing it via corporate HTTP proxies.
I remember being at a training course that day and my manager asking me what we could do to fix it because our CI was failing to pull dependencies from NPM.
Trying to explain that NPM was returning a status code intended as an April Fools joke and which was never meant to see the light of production was quite difficult
Perhaps I can fix a lot of things but debugging a response code that isn't meant to exist is not one of them.
Re: 418 I'm a teapot
#48Earlier quoted context omitted.
Stupid reason imo. Adding childish humor to a protocol seems like harmless fun until you remember how much of a mess network protocols, and their specs, and their implementation is. Maybe you think a 418 error page is funny, but I think you’ll appreciate it a lot less when your application gets a rather confounding error because some service provider wanted to remind you that the underlying processes of computers are…
/me slaps AmericanChopper around a bit with a large trout https://en.wiktionary.org/wiki/trout_slap
That’s trout abuse.
Re: 418 I'm a teapot
#49I honestly use this a lot when I'm testing, because it's basically the only response that can show up where I know god damned well that it's only happening because I programmed it to happen under certain conditions. edit: a common one for me is that if any test passes a post request without a csrf token... sorry, I'm a teapot, because I forgot to add a csrf token to that form.
It’s still in my production code, usually in places where i don’t expect code to ever lead to. It’s just my general “something particularly odd has happened” response.
I've never worked on a webserver but doesn't 500 seem better suited for that condition?
Re: 418 I'm a teapot
#50The weirdest HTTP code I've heard of is LinkedIn giving 999 for when it doesn't like your IP address.