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.
Same. I know and see several of the codes all the time. But occasionally I encounter a weird one and I always go to http.cat to find out what it is.
i still don't understand 409 errors. saw one for the first time a few weeks ago
Ahaha same.
I used to have a middleware that replaced generic http error responses with http.cat pics. One time a VIP somehow got into a URL that returned http 400 response on the website and got mad.
I ended up getting a call to explain why the website is showing middle finger to our VIP customer.
still, probably better than a 450 error, at least
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.
Is that available for every country root server?
As far as I can tell, there is no rule requiring this wiki to be kept up to date (it's not run by ICANN, though they sponsor it), but I've had good luck with it. The wiki is updated fairly frequently: https://icannwiki.org/Special:RecentChanges . I wasn't able to find a list that proves it covers every TLD but there are about 9x as many articles as TLDs, so I think it's likely. Someone with better MediaWiki chops could probably figure it out. I think that information is there I just don't know how to access it.
ETA: This category lists 314 ccTLDs.
https://icannwiki.org/Category:CcTLD
There are 316 ccTLDs. So; it's either missing 2, or they are documented but not in the right category.
If you're looking for an authoritative source I think you should check out the PSL, but it doesn't have the right metadata to answer your question. You'd need to supplement it somehow.
Does look to be the case.
nyan.cat has a language picker that includes Catalan, even though it just changes the page title.
Imho it's pretty messed up that their translation tool doesn't actually translate the page and only translates one element. For the most part the site is a lark and the text unimportant. But the banner disclaiming any affiliation with any meme coin really ought to be translated.
The funny thing is that upon registration of a .cat domain you are required to acknowledge that your website is not related to cats at all. So those domains are, in theory, not in compliance.
But what if it's a Catalan cat charity?
There is also https://http.dog/
Previous discussions:
https://news.ycombinator.com/item?id=37735614 (2023)
https://news.ycombinator.com/item?id=31438989 (2022)
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.
404 should have been the cat footprints in the concrete but without the cat.
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
There's an alternative[0] for the canine lovers.
Or the shorter https://http.dog
Illustrating "451 Unavailable For Legal Reasons" with Ray Bradbury made me laugh
Love it.
Only feedback I have is when I click into an image then hit back, it brings me to the top of the page which is kind of annoying. I wish it held my place.
I prefer https://HTTPStatusDogs.com
Is the picture for 303 meant to be the device from Heisenberg’s thought experiment?
I was wondering the same thing.
Love http and love cats
I'm partial to http.dog
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.)
599 is good for any error.
Not to be confused with Cat as a Service - https://cataas.com/
This is hilarious
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 fun because it’s pre-AI and most of the pics are real. Doing this nowadays would be a meh.
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.)
Nginx makin' up status codes...
450 gave me good chuckle
glad you got the teapot
this is exactly what I was looking for!
Wo makes this with babies?
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.
