Yep, I’ve got one of these at work now. Technically, 200 can make sense here if you’re using HTTP as RPC transport, as the server relayed the request to its handler and returned the outcome, but damn if it’s not annoying to actually process the response.

I’ve also seen a lot of devs tie themselves into knots trying to map various execution types to the “semantically correct” HTTP code, but the thing is the abstraction of HTTP is not based around RPC and it’s ultimately a pretty weird fit that we’ve somehow come to view as normal.

[–] TomasEkeli@programming.dev 35 points 2 days ago (7 children)

Then just return a 500 - Server error. Nice and obscure.

The ability to separate "something wrong with what you sent" (4XX) and "something wrong on the server" (5XX) is very valuable in itself.

[–] MyNameIsIgglePiggle@sh.itjust.works 44 points 2 days ago* (last edited 2 days ago) (3 children)

Yep

2xx - it's good
3xx - not here cunt
4xx - you don fucked up
5xx - we fucked up, whatever you do aint changing shit.

[–] Ziglin@lemmy.world 6 points 1 day ago (1 children)

The number of times I've gotten 5xx codes for bad requests is annoyingly high.

[–] MyNameIsIgglePiggle@sh.itjust.works 2 points 1 day ago

Fair. But they still fucked up so at least that's on them

I guess it's like a retail worker apologising excessively because of trauma.

[–] mercano@lemmy.world 15 points 2 days ago* (last edited 2 days ago)

1xx - We’re still working on it

[–] Hawk@lemmy.dbzer0.com 9 points 2 days ago (1 children)

And then there's 418

[–] TomasEkeli@programming.dev 2 points 1 day ago

good old 418, always appears when you really want a cup of coffee

load more comments (3 replies)