6 comments

[ 3.4 ms ] story [ 22.3 ms ] thread
> A 200 OK response tells you the request was accepted. It tells you nothing about what actually happened after.

???

From [0]:

> The HTTP 200 OK successful response status code indicates that a request has succeeded.

From [1]:

> The HTTP 202 Accepted successful response status code indicates that a request has been accepted for processing, but processing has not been completed or may not have started.

[0]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/... [1]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/...

Then probably do not use 200. Instead, use 202 - accepted. Then return a state that says PENDING.
Not a great read. Its a very generic article that doesn't actually give you any information. Its too high level for anyone that actually works in this field and for anyone not in this field they are better off with an introduction to the topics of status codes and http layer works.
yeah fair

200 is correct at the protocol level, no argument there.

I think where it gets confusing is that people treat it as “done”, while in a lot of real systems it just means the request got accepted and handed off.

after that it’s queues, providers, retries, all kinds of stuff you don’t really see.

so you end up with “success” at the API layer but still inconsistent outcomes.

that’s mostly what I’ve been running into in production.

curious how others think about that.

I'm going to call.

This format of writing.

Partial sentences.

LinkedIn haiku.