HTTP Status Codes that should never have been created

preview_player
Показать описание
Some of these probably shouldn't have ever been created.

#web #http #weird

Join this channel to support what I do:

My Equipment:

My Discord:
Рекомендации по теме
Комментарии
Автор

Status code 451 is also a reference to the book/movie Fahrenheit 451, and it’s honestly a pretty good match

Raoul.
Автор

So 418 is basically the webserver equivalent of "Sir this is a Wendy's" 💀💀💀

RenderingUser
Автор

451 refers to Fahrenheit 451 by Ray Bradbury. It means access is restricted due to censorship.
The implementation is kinda rebellious, since usually you would not be allowed to tell that information exists but you won't show it.
451 is the status code for digital book burning.

DasIllu
Автор

Error status codes are not about placing blame, they're more about explaining why this error is returned and what you can do to fix it. 4xx is generally "something on the client side", 5xx is "something on the server side"

With 451, you can move to another country, change your country's laws, use a VPN - all of that does not concern the server very much.

Meanwhile 5xx errors are caused by stuff that the client has no control over: some sort of bug in the server code, availability issues with other servers it talks to, etc.

em_the_bee
Автор

Just wanted to point out that 429 was the exact code we were getting during the rate limiting nonsense at Twitter recently. Super funny timing.

mattforgione
Автор

101 is an interesting code. It means “switching protocols” and wasn’t generally used before Websockets. A HTTP/S request to a WS server returns 101 and then awaits a Websocket packet. The connection then carries WS traffic (which is basically TCP)

sarahclark
Автор

Learning about 418 was the highlight of my software engineering class. I never got to implement it but I still think 418 is hilarious. Let us software devs keep our dumb jokes

anname
Автор

Nothing beats status code 418: I'm a Teapot

michaelsanchez
Автор

I actually used 418 the other day. My backup web servers are Raspberry Pi's and don't have much storage attached to them. When one of the backups is the main server (because the main server is getting maintenance) when one of the services that uses a lot of data / drive space, I returned a 418 code to say that this server can't really do that. I later decided that 503 was more acceptable as that part of the service is not available.

Dygear
Автор

200: I got what you wanted
300: I got what you wanted, it's over here
500: My bad
400: Your bad
401: Log in you dingus
403: You're not allowed here you dingus
404: It's not here

These are the most used ones. If you consume an API, ignore HTTP 300 and then contact support, we're legally required to slash your tires. If you run an API and ask for "all the things that are like this", like say "all my posts for the last 5 days on reddit" and send me an 404 instead of a 200 OK and an empty list, I am legally required to waterboard you until you learn the error of your ways. (Which btw, is a 500 error, because YOU did the wrong thing)

HrHaakon
Автор

It should be noted that Emacs does have an implementation of that april fool's joke thing that allows it to talk to compatible coffee makers (the list of which is currently 'nil, but that might change some day), so it's in "actual" use...

HrHaakon
Автор

451 is also pretty common here in the EU for US websites that don't want to deal with EU privacy law and just block all EU ip addresses. Edit: should have continued watching for 3 seconds lol...

snipsnap
Автор

4xx doesn't necessarily mean that it's the user's fault. For example 404 (Not Found) does not mean it's your fault that the resource wasn't found. It's more of a message _for_ the client, rather than the server administrator (5xx errors).

dealloc
Автор

I wasn't expecting it that you didn't shill some VPN right after briefly mentioning how it can be used for protection :D My brain was processing it for a few seconds

supernovaw
Автор

I used 418 once as I blocked an IP because I suspected it trying to DDOS my server.
I received a call from the client behind that IP minute later. Its computer got a trojan and was trying to access all the servers this person used. The joke lasted five minutes, but it was usefull.

warny
Автор

I now want a networked teapot that implements that protocol.

Linuxdirk
Автор

In case anyone wonders: HTTP status codes are defined in many different standards, so it's not like there is a single official standard that decides what is an official status code and what not. Instead the IANA has a list of official status codes and if a code is listed there, it is considered official, otherwise it isn't. This list also gives every status code a name and links to the standard that defines it. I cannot put a link here (YouTube doesn't like links in comments unless those are YT links) but if you search for "Hypertext Transfer Protocol (HTTP) Status Code Registry" you should find that list.

xcoder
Автор

418: Sir, this is a wendy's
Also 418 goes with the hyper text coffee pot control protocol. When your trying to talk to a coffee pot, but find a teapot instead.

MobCat_
Автор

I love this video. The light sprinkling of jokes and memes does not detract from the clarity of the video. You have great audio, great enunciation, and very good writing. 👍

bthrkay
Автор

418 seems like a really good status code to reply to malformed requests trying to misuse things.

TeraunceFoaloke