418 I’m a teapot • Hacker News Board

Re: 418 I’m a teapot

#41

Post by cybrox » Mon, Oct 28, 2024, 8:46 AM UTC

mrmincent wrote: post #38

I hate to be that guy, but just a reminder that if you’re implementing a production system - even if it’s an internal tool - please don’t return 418 as a joke unless you really are a teapot. As an SRE I’ve been on the receiving end of a broken system returning teapots over the weekend, and it’s not as funny then.

Well, statistically, 9 out of 10 engineers find this very funny come Monday.

Re: 418 I’m a teapot

#42

Post by dark-star » Mon, Oct 28, 2024, 9:08 AM UTC

XeO3 wrote: post #20

enews01 wrote: post #3

https://http.cat/418

Google has it too. :) https://www.google.com/teapot

I didn't realize that this is actually interactive!

Re: 418 I’m a teapot

#43

Post by fastball » Mon, Oct 28, 2024, 9:14 AM UTC

mrmincent wrote: post #38

I hate to be that guy, but just a reminder that if you’re implementing a production system - even if it’s an internal tool - please don’t return 418 as a joke unless you really are a teapot. As an SRE I’ve been on the receiving end of a broken system returning teapots over the weekend, and it’s not as funny then.

We return 418s for captcha failures.

Re: 418 I’m a teapot

#44

Post by chrisbra80 » Mon, Oct 28, 2024, 9:21 AM UTC

Vim implemented this: `:call err_teapot()`.

Re: 418 I’m a teapot

#45

Post by falleng0d » Mon, Oct 28, 2024, 9:29 AM UTC

thih9 wrote: post #25

The linked source RFC is a pleasant read too: https://www.rfc-editor.org/rfc/rfc2324

Now. I didn't know about the RFC. This is so good. I hope we can continue to advance this field with good humor, and good coffee.

Re: 418 I’m a teapot

#46

Post by seanthemon » Mon, Oct 28, 2024, 9:33 AM UTC

mrmincent wrote: post #38

I hate to be that guy, but just a reminder that if you’re implementing a production system - even if it’s an internal tool - please don’t return 418 as a joke unless you really are a teapot. As an SRE I’ve been on the receiving end of a broken system returning teapots over the weekend, and it’s not as funny then.

I did this many years ago on the app I still work on, the product became much more enterprise and eventually customers started to see 418 errors.. it wasn't a good look and I felt great shame.

Re: 418 I’m a teapot

#47

Post by sureIy » Mon, Oct 28, 2024, 9:43 AM UTC

chrisbra80 wrote: post #44

Vim implemented this: `:call err_teapot()`.

Why would a text editor have a way to produce HTTP error codes? I don't get it

Re: 418 I’m a teapot

#48

Post by karol » Mon, Oct 28, 2024, 9:45 AM UTC

The older generation of software craftsmen have been reading about it for a while now and the joke got a bit tedious at this point.

Re: 418 I’m a teapot

#49

Post by ctm92 » Mon, Oct 28, 2024, 9:48 AM UTC

falleng0d wrote: post #45

thih9 wrote: post #25

The linked source RFC is a pleasant read too: https://www.rfc-editor.org/rfc/rfc2324

Now. I didn't know about the RFC. This is so good. I hope we can continue to advance this field with good humor, and good coffee.

There are quite some RFC with humor, most prominently probably RFC1149 and its extension RFC2549

Re: 418 I’m a teapot

#50

Post by sleepyhead » Mon, Oct 28, 2024, 9:50 AM UTC

mrmincent wrote: post #38

I hate to be that guy, but just a reminder that if you’re implementing a production system - even if it’s an internal tool - please don’t return 418 as a joke unless you really are a teapot. As an SRE I’ve been on the receiving end of a broken system returning teapots over the weekend, and it’s not as funny then.

I don't get it. If the system is so broken it is returning some random http code then I don't see how returning some other random http code is better?