Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

HTTP Status Dogs (2011)

httpstatusdogs.com

Post reply on HN
Print view View original

11–20 of 44 posts

Re: HTTP Status Dogs (2011)

#11

Post by wongarsu »

thenoblesunfish wrote: post #3

I hadn’t heard of code 418 before - seems like it started as a joke but is now “real” because people use it!

It has a proper RFC and everything [1].

All the April Fools RFCs are worth a read imho [2]. RFC2100 (The Naming of Hosts) and RFC8135 (Complex Addressing in IPv6) are real gems.

1: https://datatracker.ietf.org/doc/html/rfc2324

2: https://en.wikipedia.org/wiki/April_Fools%27_Day_Request_for...

Re: HTTP Status Dogs (2011)

#13

Post by maxehmookau »

wongarsu wrote: post #8
jjgreen wrote: post #2

Fabulous, 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.

httpstatus.es/404 works too, but it's less fun.

Re: HTTP Status Dogs (2011)

#15

Post by thanatos519 »

MattKimber wrote: post #10

One 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 environ…

If internal tools need to appear professional and sensible, then there's a serious culture problem and I don't wanna work there.

Re: HTTP Status Dogs (2011)

#17

Post by palsecam »

thenoblesunfish wrote: post #3

I hadn’t heard of code 418 before - seems like it started as a joke but is now “real” because people use it!

Related thread: https://news.ycombinator.com/item?id=24206899

I myself use 418 as a reply to mean bots. Fun + makes filtering logs easier.

Nginx config snippet:

  # Nothing to hack around here, I’m just a teapot:
  location ~* \.(?:php|aspx?|jsp|dll|sql|bak)$ { 
      return 418; 
  }
  error_page 418 /418.html;
Example: https://FreeSolitaire.win/wp-login.php

Re: HTTP Status Dogs (2011)

#18

Post by kypro »

Might be okay on a humour site, or perhaps in an internal tool, but some of these are a bit tasteless IMO. It could be far more useful if you were able to pick from a selection of individual images or image sets depending on the usecase. Although even then these kinds of http error images scream early-2000s web humour to me.

Re: HTTP Status Dogs (2011)

#19

Post by unknown_error »

wongarsu wrote: post #8
jjgreen wrote: post #2

Fabulous, 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.

Just type in "error 422" and a Google snippet tells you what it is. Saves 3 characters, doesn't depend on a single website, and returns a more descriptive paragraph instead of some silly image with no relevance...
Post reply on HN