Timeline for Should HTTP status codes be used to represent business logic errors on a server?
Current License: CC BY-SA 4.0
17 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 14 at 14:01 | history | edited | VoiceOfUnreason | CC BY-SA 4.0 | Fix spelling error |
| Nov 25, 2022 at 14:51 | history | edited | VoiceOfUnreason | CC BY-SA 4.0 | Update HTTP Semantics URI |
| Oct 17, 2022 at 11:16 | history | edited | VoiceOfUnreason | CC BY-SA 4.0 | Fix typo |
| Jun 30, 2022 at 12:35 | comment | added | VoiceOfUnreason | I would expect to use 412 Precondition Failed when a request condition (like If-Match: ETag) evaluates to false. | |
| May 27, 2022 at 16:49 | history | edited | VoiceOfUnreason | CC BY-SA 4.0 | added 166 characters in body |
| Oct 7, 2021 at 7:34 | history | edited | CommunityBot | replaced https://tools.ietf.org/html/rfc with https://www.rfc-editor.org/rfc/rfc | |
| Mar 15, 2020 at 20:49 | comment | added | gavenkoa | 409 is for HTTP protocol, like if you PUT but ETag is outdated. 422 is a better choice as it doesn't mess with HTTP semantic. HTTP spec is messy, quotation doesn't show real intention by RFC designers. | |
| Jul 16, 2019 at 10:46 | history | edited | VoiceOfUnreason | CC BY-SA 4.0 | edited body |
| Apr 29, 2019 at 14:55 | history | edited | VoiceOfUnreason | CC BY-SA 4.0 | added 1298 characters in body |
| Apr 29, 2019 at 9:14 | comment | added | Konrad | I would use 422. Input is valid so 400 is not the right error code to use | |
| Jul 7, 2018 at 11:40 | history | edited | VoiceOfUnreason | CC BY-SA 4.0 | added 1 character in body |
| Sep 25, 2017 at 22:28 | comment | added | jpmc26 | "Business logic errors" sounds like "invalid input," to me, which is usually generally a straight 400, as there isn't a more specific error code for it. If it's not the input that's invalid, then the server has a bug and 500 is appropriate. Your answer seems to assume too much about the nature of a "business logic error." | |
| Apr 13, 2017 at 12:45 | history | edited | CommunityBot | replaced http://softwareengineering.stackexchange.com/ with https://softwareengineering.stackexchange.com/ | |
| Feb 9, 2017 at 9:19 | vote | accept | Joe Shanahan | ||
| Feb 8, 2017 at 17:37 | comment | added | JensG | "you are adapting your domain to look like a document store" -- I'd love to see people read this, and fully understand all the conseqences and implications before they decide for (or against) REST. Really. | |
| Feb 8, 2017 at 17:11 | history | edited | VoiceOfUnreason | CC BY-SA 3.0 | added 258 characters in body |
| Feb 8, 2017 at 17:04 | history | answered | VoiceOfUnreason | CC BY-SA 3.0 |