Timeline for How to handle exception in REST API
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 25, 2014 at 13:22 | comment | added | Wyatt Barnett | Actually you would be much better off letting bad request fail quickly -- hanging them creates a nasty ddos vector, web servers don't like stuck processes whereas clients can easily choose to fire and forget allowing them to create many, many hung processes. If you are looking at flood control or to prevent brute force attacks on secrets there are much better options. | |
| Apr 29, 2014 at 16:25 | vote | accept | ebb | ||
| Apr 29, 2014 at 2:17 | comment | added | TomG | It's usually better to allow clients to fail quickly, unless you have reason to think the failure is the result of some sort of malicious request. Allowing clients to hang until they time out can consume resources, frustrate users, etc., etc. | |
| Apr 29, 2014 at 1:05 | history | edited | Arseni Mourzenko | CC BY-SA 3.0 |
added 393 characters in body
|
| Apr 28, 2014 at 10:12 | history | edited | Arseni Mourzenko | CC BY-SA 3.0 |
added 850 characters in body
|
| Apr 28, 2014 at 10:02 | history | answered | Arseni Mourzenko | CC BY-SA 3.0 |