Timeline for RESTful API represent the absence of a thing
Current License: CC BY-SA 3.0
21 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 26, 2017 at 13:08 | history | edited | Paul D'Ambra | CC BY-SA 3.0 | added explanation of why I chose the answer |
| Sep 26, 2017 at 12:59 | answer | added | Qwerky | timeline score: 24 | |
| Sep 26, 2017 at 12:44 | vote | accept | Paul D'Ambra | ||
| Sep 26, 2017 at 8:04 | history | edited | Paul D'Ambra | CC BY-SA 3.0 | added explanation of why I believe proposed duplicate is not a duplicate |
| Sep 26, 2017 at 7:47 | comment | added | Paul D'Ambra | @gnat that feels like a really different question to me... This is very specifically a question about where a resource is present as an indication of the absence of a choice | |
| Sep 26, 2017 at 5:38 | comment | added | el.pescado - нет войне | In this case there's not much difference. Do whatever feels more convenient for you, document it, and be consistent throughout your application. | |
| Sep 26, 2017 at 2:01 | answer | added | 9000 | timeline score: 1 | |
| Sep 25, 2017 at 22:12 | answer | added | Paul Draper | timeline score: 0 | |
| Sep 25, 2017 at 22:00 | review | Close votes | |||
| Sep 30, 2017 at 3:05 | |||||
| Sep 25, 2017 at 21:41 | comment | added | gnat | Possible duplicate of Should HTTP status codes be used to represent business logic errors on a server? | |
| Sep 25, 2017 at 19:55 | history | tweeted | twitter.com/StackSoftEng/status/912405337961041920 | ||
| Sep 25, 2017 at 19:50 | comment | added | Brandon Arnold | @PaulD'Ambra For what it's worth, I would not use a no-content. I haven't seen HTTP codes handled on the front-end that way in Javascript since the XmlHttpRequest days. But it is certainly valid. | |
| Sep 25, 2017 at 16:32 | answer | added | Brandon Arnold | timeline score: 25 | |
| Sep 25, 2017 at 16:31 | answer | added | TheCatWhisperer | timeline score: 1 | |
| Sep 25, 2017 at 16:24 | comment | added | Paul D'Ambra | I suppose my worry with 404 is disambiguating a config change that introduces a bad URL template from a person with no spirit animal | |
| Sep 25, 2017 at 16:18 | comment | added | Paul D'Ambra | or maybe it's better to return 204 no-content? | |
| Sep 25, 2017 at 16:14 | history | edited | Paul D'Ambra | CC BY-SA 3.0 | added 198 characters in body |
| Sep 25, 2017 at 16:13 | comment | added | Paul D'Ambra | Yep, we're actually just talking about that internally... Trying to decide if it's better to represent an explicit domain absence as a 200 response rather than a 404. Can't make our minds up | |
| Sep 25, 2017 at 16:04 | comment | added | Vincent Savard | You haven't explained why you believe it is an issue to return a 404. From a domain point of view, you don't know whether you received a 404 or a 200, that's abstracted by the client layer. | |
| Sep 25, 2017 at 16:03 | review | First posts | |||
| Sep 25, 2017 at 19:51 | |||||
| Sep 25, 2017 at 16:01 | history | asked | Paul D'Ambra | CC BY-SA 3.0 |