HTTP Status Dogs (2011)
httpstatusdogs.com
HTTP Status Dogs (2011)
1–10 of 44 posts
Re: HTTP Status Dogs (2011)
#2Fabulous, inspired by https://http.cat/ of course
Re: HTTP Status Dogs (2011)
#3I hadn’t heard of code 418 before - seems like it started as a joke but is now “real” because people use it!
Re: HTTP Status Dogs (2011)
#4Fabulous, inspired by https://http.cat/ of course
amazing! thanks
Re: HTTP Status Dogs (2011)
#5The http 206 is disturbing.
Re: HTTP Status Dogs (2011)
#6501 and 206 are really disturbing.
Re: HTTP Status Dogs (2011)
#7I hadn’t heard of code 418 before - seems like it started as a joke but is now “real” because people use it!
I had a really painful experience with NPM where it was responding 418 and almost no extra info. I had not asked it for a NuGet package.
Re: HTTP Status Dogs (2011)
#8Fabulous, inspired by https://http.cat/ of course
http.cat is surprisingly useful because of the short url. Typing in e.g. http.cat/422 beats any other method I know for quickly looking up status codes by number.
Re: HTTP Status Dogs (2011)
#9How do I install them on my nginx or Apache?
Re: HTTP Status Dogs (2011)
#10One surprisingly practical use I found for things like this; when internal tools throw up a 404 or a 503 with the usual default status page, people assume "oh it's not working, I'll try again later".
When they get an unexpected cat (or dog, in this case) they tend to go and ask their tech team, "what's with the cat?" It's not a substitute for good logging and alerting in any way, and is totally unsuitable for environments where internal tools need to appear professional and sensible, but as a way to get people to pay attention when something goes wrong then a cute animal can work a lot better than a "normal" notification.