61–70 of 146 posts
Earlier quoted context omitted.
We return 418s for captcha failures.
Surely that should be a 401 unauthorized?
The older generation of software craftsmen have been reading about it for a while now and the joke got a bit tedious at this point.
Its not like people are posting this daily
Discussions in: 2020 (153 points, 118 comments) https://news.ycombinator.com/item?id=24206899 2021 (193 points, 108 comments) https://news.ycombinator.com/item?id=28541327 2023 (206 points, 189 comments) https://news.ycombinator.com/item?id=36090344
I think we were due another
Earlier quoted context omitted.
Other than the humor in it, makes you wonder why they'd pick 418. It does sometimes feel like some errors are missing from the http codes, prompting developers to either create their own, or repurpose some, like 418, where they feel relatively safe that it won't conflict with something. It never ceases to amaze how http status codes can be misused. My favorite is still the customer who had built a service that would…
There are definitely missing codes, which is why sometimes the WebDAV status additions get used in purported RESTful APIs—which is semantically wrong, but often carries a lot of helpful meaning. For example, things like 422: Unprocessable Content or 423: Locked are really helpful to convey meaning, but not available in plain HTTP.
I honestly would have thought 400 Bad Request would cover that? Might be too generic though. Is "422" "ok, I admit it's formatted correctly, but I can't process it for some higher-level reason than syntax"?
(Just reading through 4xx codes, and I think I need to use 410 Gone a lot more often. Does anyone know if search engines treat 404 and 410 differently?)
you are not a tea pot.
If you are bored you can read the discussion when _mnot_ tried removing 418 status code from different languages and implementations because it wasn't technically correct. https://github.com/nodejs/node/issues/14644 https://github.com/golang/go/issues/21326 And someone even ended up making a website http://save418.com/
This 418 stuff reminds me of a previous job where we had some arguments about putting emojis in our applications. I was against it and a coworker was for it. Like putting rocket ship emoji when an operation succeeds. My main argument was that if you put things like that in your applications then people start having opinions about it and they want to discuss it and add more to certain places or remove from other place…
Discussions in: 2020 (153 points, 118 comments) https://news.ycombinator.com/item?id=24206899 2021 (193 points, 108 comments) https://news.ycombinator.com/item?id=28541327 2023 (206 points, 189 comments) https://news.ycombinator.com/item?id=36090344
I think we were due another