I felt compelled to verify httpcats has it covered and it does:
418 I'm a teapot
11–20 of 195 posts
Re: 418 I'm a teapot
#12I felt compelled to verify httpcats has it covered and it does: https://httpcats.com/
That url is way too long. I prefer https://http.cat/.
Re: 418 I'm a teapot
#13I felt compelled to verify httpcats has it covered and it does: https://httpcats.com/
also dogs
Re: 418 I'm a teapot
#14Over 20,000 teapots out there:
https://search.censys.io/search?resource=hosts&q=services.ht...
Re: 418 I'm a teapot
#15There is no shortage of numbers. I wonder if it would make sense for every web-server ot have its own status-code if up and running? Of course they would have to be registered somewhere.
Re: 418 I'm a teapot
#16[deleted]
Re: 418 I'm a teapot
#17I 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.
Re: 418 I'm a teapot
#18Found this while scouring this list of HTTP status codes, because I wanted to make sure I was giving appropriate responses in this web API I'm developing.
Re: 418 I'm a teapot
#19There is no shortage of numbers. I wonder if it would make sense for every web-server ot have its own status-code if up and running? Of course they would have to be registered somewhere.
This has nothing to do with servers though. It's in context to the requested resource. If you want to check if a server is alive it's happening several layers below an HTTP request.
Re: 418 I'm a teapot
#20On a related note, my favorite easter egg header: