I’ve been a fan of HTTP status codes, and in particular 4xx client errors, since I discovered this April Fool joke one year when I was directed to a “418 I’m a teapot” page. See quote below from Wikipedia …
418 I’m a teapot (RFC 2324, RFC 7168) This code was defined in 1998 as one of the traditional IETFApril Fools’ jokes, in RFC 2324, Hyper Text Coffee Pot Control Protocol, and is not expected to be implemented by actual HTTP servers. The RFC specifies this code should be returned by teapots requested to brew coffee.[18] This HTTP status is used as an Easter egg in some websites, such as Google.com’s “I’m a teapot” easter egg.[19][20][21] Sometimes, this status code is also used as a response to a blocked request, instead of the more appropriate 403 Forbidden.[22][23]
From there it was only a short distance to HTTP 404 pages, some of which are great advertisements for their parent sites, some have games you can play, and others are just plain fun. A few for you to try … (Don’t be surprised if some don’t work) … LOL, so far, I’ve only ‘experienced’ a few 404s and the one 418, but my ambition is to see examples of all of them over time …
http://wildlifeqld.com.au/bird-conflicts/plover.html
https://www.netflix.com/NotFound?prev=https%3A%2F%2Fwww.netflix.com%2F404
https://www.cloudsigma.com/404-error
https://thisjungianlife.com/404
One of the best I’ve seen was on Ecosia but cannot find it again to show you. They get cagey when you try to catch them just for fun …
Rita de Heer 