I unironically use this website everytime I forget a status code at work. The name is instantly memorable, it loads immediately, and I can ctrl-f it. It's basically muscle memory at this point.
I’ve used this site every time I’m doing http networking stuff for the past few years. It’s so easy to just go to http.cat/303 to check a status code you don’t know, or to scroll down the homepage to find the number you need for a specific response.
The cats make it much more fun than a regular docs page, whilst still being a useful quick reference. I wonder if other bits of reference information could be made more interesting in this way.
I love how there is a Catalan version too! I guess it’s probably a requirement for getting the .cat domain.
> Administered by the non-profit Fundació puntCAT under the oversight of ICANN, registrations are available only to individuals and organizations demonstrating use or promotion of the Catalan language and culture.
Does look to be the case.
nyan.cat has a language picker that includes Catalan, even though it just changes the page title.
Previous discussions:
https://news.ycombinator.com/item?id=37735614 (2023)
https://news.ycombinator.com/item?id=31438989 (2022)
I used similar idea in an app a while back:
https://github.com/tantalor/emend/blob/master/app/static/ima...
Still gives me a chuckle
404 should have been the cat footprints in the concrete but without the cat.
I'm partial to http.dog
There's an alternative[0] for the canine lovers.
Or the shorter https://http.dog
Why is the quality of the pictures so low?
Because this website has been around for a long time and pictures didn't used to be so big
This is hilarious
Came for 418. Left happy for Caturday.
(Every web site I've built in the last ten years has a series of conditions that combined will trigger a 418.)
Love http and love cats
Is the picture for 303 meant to be the device from Heisenberg’s thought experiment?
Do any browsers recognize a 420 response code?
Your browser (if you're using one of the "usual ones") doesn't really do much with the response's status code if it doesn't match a few specific ones for redirecting/caching/protocol shenanigans.
Anything in the 4XX range is going to be treated as just a regular ol' response, just like 404. (You could serve an entire site with all responses set to status=404, and be fine... other than probably never getting any cache hits) If you don't include a body in the response, the browser might sub in it's own error page, but it will just communicate that the user agent made a bad request.
I've seen sites that use unexpected HTTP response codes, I think to try to defeat bots. The front page would return a 503 Service Unavailable, but the body was just normal content that would load a bot detection script and then redirect you to the actual content.
I successfully wrote a bot that would bypass it all, but it was weird, and became a slight challenge since I couldn't rely on response codes to determine if I succeeded. When I solved the challenge, it would return a 400 Bad Request while serving me the content I was looking for.
Once upon a time, Internet Explorer used to substitute its own error pages if the body of the error response was too short for its liking. Those depended on whcih error code it got. (I expect nobody has used an old enough IE to see those pages for at least a decade.)
Not to be confused with Cat as a Service - https://cataas.com/
Nginx makin' up status codes...
This is fun because it’s pre-AI and most of the pics are real. Doing this nowadays would be a meh.
450 gave me good chuckle
Wo makes this with babies?
this is exactly what I was looking for!
HTTP 000: HTTP not found. HTTPS CA TLS only.
That said, at least they have a broad cipher set support and their HTTPS-only implemetation does work in older browsers and systems. That's nice. But HTTP+HTTPS would be better.
