Timeline for HTTP Status Code for "Still Processing"
Current License: CC BY-SA 3.0
16 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 10, 2022 at 22:54 | answer | added | gnasher729 | timeline score: 1 | |
| Nov 10, 2022 at 21:30 | answer | added | Alexis Wilke | timeline score: 0 | |
| Jan 18, 2022 at 9:11 | comment | added | AnorZaken | The response you should give depends on the headers used by the client making the request - at least if you feel that this draft is good Reporting Progress of Long-Running Operations in HTTP | |
| Jun 11, 2020 at 5:42 | vote | accept | Matthew Haugen | ||
| Nov 16, 2018 at 21:40 | history | protected | gnat | ||
| Nov 16, 2018 at 17:58 | answer | added | Xiangming Hu | timeline score: 20 | |
| Apr 21, 2016 at 15:48 | answer | added | Cormac Mulhall | timeline score: 9 | |
| Apr 20, 2016 at 16:55 | answer | added | Brian | timeline score: 3 | |
| Apr 20, 2016 at 5:47 | history | tweeted | twitter.com/StackProgrammer/status/722662913333456897 | ||
| Apr 19, 2016 at 20:05 | comment | added | Matthew Haugen | @GrandmasterB It's hours, potentially. I'm not responsible for the job processing itself, so I don't have a really good estimate, but it'll be a while. Otherwise, I'd just leave the first POST request open. The main issue with long polling or web sockets is that the user might close the browser and come back. I could open them again at that time (and that's what I do), but it seems cleaner to have a single API to call before I open those sockets, since it's an edge-case to have that problem arise. | |
| Apr 19, 2016 at 19:37 | comment | added | GrandmasterB | What kind of delay are you talking? 10 seconds? Or 6 hours? If the delays are short and generally within the same browser visit, you might do long polling or web sockets rather than periodic polling. | |
| Apr 19, 2016 at 19:20 | history | edited | user22815 | CC BY-SA 3.0 | grammar/spelling. |
| Apr 19, 2016 at 18:16 | comment | added | Matthew Haugen | @Andy I was looking at 102, but that's for WebDAV stuff. Beyond that, no... They're mostly for in-transit communications. Useful in switching to Web Sockets and such. | |
| Apr 19, 2016 at 18:07 | answer | added | Arseni Mourzenko | timeline score: 90 | |
| Apr 19, 2016 at 18:04 | comment | added | Andy | Isn't 1xx codes made exactly for that purpose? | |
| Apr 19, 2016 at 17:46 | history | asked | Matthew Haugen | CC BY-SA 3.0 |