undefined | Better HN

0 pointswyldfire3y ago0 comments

I've never worked on a webserver but doesn't 500 seem better suited for that condition?

0 comments

4 comments · 2 top-level

lucumo3y ago· 2 in thread

Yes. And write something to the logs, so you can find out there's a bug before users call your helpdesk. Arguably that's the most important part of any 5xx error.

It's a bit of a purist argument, but 4xx series means the client can fix something and get a better response.

prerok3y ago

Hmm, I don't think it's that purist. All my HTTP clients have the logic that 4xx is a non-retryable error, i.e. if I repeat the request I will always get the same response unless something is changed, whereas 5xx means that something is wrong on the backend and I should retry it later.

It is true I have often encountered inconsistencies in implementations but I do think that when that happens it really is a backend bug that should be fixed.

sholladay3y ago

There are some 4xx codes that should be retried. 408, 413, and 429 at the very least. There are also cases where it makes sense to retry 404, such as when polling for a resource that is being created and will soon be available.

1 more reply

duxup3y ago

500 is correct.

But nobody enjoys a 500 so I occasionally use 418 for extra unexpected situations.

j / k navigate · click thread line to collapse