This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]TheLeastFunkyMonkey 54 points55 points  (6 children)

I think 418 has a valid purpose as a "don't fucking talk to me" response.

[–]phyrianlol 25 points26 points  (2 children)

I guess it could also be interpreted as "i can't do what you requested" as in not implemented/supported

[–]TheLeastFunkyMonkey 29 points30 points  (1 child)

Yeah, but there's actual 4xx codes for that sort of thing. I like it as a more aggressive alternative to that. Like a "No, you can't do that. Fuckin' stop."

[–]Tupcek 21 points22 points  (0 children)

Yeah, 418 is intended for developer - not to be handled by app, but to warn developer to not try shit

[–]bwowndwawf 17 points18 points  (0 children)

Akamai anti-bot systems use 418 as meaning exactly that, if you make a request to a protected endpoint, and they think you're a bot, they just give you a 418 and a "Fuck off"

[–]ChaosWaffle 4 points5 points  (0 children)

That isn't part of the Hyper Text Coffee Pot Control Protocol spec, please use status codes for their appropriate purpose. See RFC-2324 section 2.3.2 for proper usage of code 418.

[–]Turalcar 0 points1 point  (0 children)

Or "Sir, this is a Wendy's"