Timeline for HTTP Status Code for "Still Processing"
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 10, 2022 at 22:45 | comment | added | gnasher729 | If I try to convert a video and it’s not ready after five minutes, I can’t see any conflict that justifies a 409. | |
| Jun 23, 2021 at 23:16 | comment | added | Géry Ogam | Sorry but what you are describing here is Asynchronous processing (done wrong). | |
| May 23, 2017 at 12:40 | history | edited | CommunityBot |
replaced http://stackoverflow.com/ with https://stackoverflow.com/
|
|
| Apr 21, 2016 at 22:21 | comment | added | Andy | No, especially the last few paragraphs of MainMa's answer. Separate end points to check the status of the request and to get the video itself. The status is not the same resource as the video and should be addressable on its own. | |
| Apr 21, 2016 at 14:39 | comment | added | Brian | @Andy: True, but so is every other alternative. E.g., 202 is really meant to be a response to the request which initiated processing, not the the request that requested the results of the processing. Really, the most spec-compliant response is 404, since the resource was not found (because it didn't exist yet). There's nothing stopping the API from providing the relevant api data within the 404 response. Mind you, 4xx/5xx responses tend to be annoying to consume; some languages will fire an exception rather than just providing a different status code. | |
| Apr 21, 2016 at 0:07 | comment | added | Andy | Seems like a stretch f what 409 is really meant for, which is in response to a put. | |
| Apr 20, 2016 at 16:55 | history | answered | Brian | CC BY-SA 3.0 |