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.
> 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.
Users expect that their ticket been successfully purchased when the gray "Buy" button turned "Green! Yay", this is "the system" or whatever they call it. Just because the request went to backend and returned 200 OK doesn't necessarily mean that everything after that successfully completed, maybe the payment webhook was badly configured, and so on.
It seems pretty clear to me that this is what the author means and are talking about. But I'm not entirely why they're talking about this, or if there is any further point beyond just the "technically correct but ultimately not important" part.
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.
> 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/...
Authors point is something like this:
Users expect that their ticket been successfully purchased when the gray "Buy" button turned "Green! Yay", this is "the system" or whatever they call it. Just because the request went to backend and returned 200 OK doesn't necessarily mean that everything after that successfully completed, maybe the payment webhook was badly configured, and so on.
It seems pretty clear to me that this is what the author means and are talking about. But I'm not entirely why they're talking about this, or if there is any further point beyond just the "technically correct but ultimately not important" part.
Then probably do not use 200. Instead, use 202 - accepted. Then return a state that says PENDING.
[dead]