200: “I gotchu, bro. Here you go. Have a good day.”
401: “You’re not on the list. Get lost.”
402: “Pay me or get lost.”
403: “Everyone get lost.”
404: “You are lost.”
500: “Ooopsss.”
501: “Knew I forgot something…”
504: “I can’t do this shit all day.”
Serving multiple data streams
Thread safe pouring
I love the whimsy of developers.
429: “Please stop trying”
401 is “I don’t know who you are. Get fucked”
403 is “I know who you are and you’re not allowed here. Get fucked”
451: “The law says get lost.”
401 is more like “Tell me who tf you are or get lost”, while 403 means “You’re not on the list, get lost”
Surprised no one’s mentioned HTTP Cats yet:
Personally, HTTP 405 (Method not allowed) is my favorite:
Why do these feel like the 5 stages of grief 🤔
As a software developer / network admin, all of these are almost always “I fucked up configuring the web server”.
200: Here you go (secretly still an error)
These are pretty good as an overview tbh. I like it when teachers have a sense of humour at least.
🤣
200 OK
{ “error”: 404 }
Everyone give it up for the fella who ran a webserver on a teapot
I like returning 418 instead of 404 or 403 on the files the script kiddies are hunting for on my web servers. I’m sure it does nothing but I’d like to think I’ve wasted some of their time at least once.
I’m glad that error exists.
I’m pretty sure it exists because of RFC2324 hyper text coffee pot control protocol