Timeline for Is it okay to use POST for REST API updates?
Current License: CC BY-SA 4.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 5, 2023 at 23:40 | answer | added | Greg Bowne | timeline score: 0 | |
| Jul 5, 2023 at 20:58 | answer | added | Aiden Cullo | timeline score: 0 | |
| Oct 31, 2019 at 19:03 | answer | added | Roman Vottner | timeline score: 2 | |
| Oct 31, 2019 at 16:27 | answer | added | Laiv | timeline score: 1 | |
| S Oct 31, 2019 at 15:02 | history | suggested | jnns | CC BY-SA 4.0 | indent JSON |
| Oct 31, 2019 at 9:25 | review | Suggested edits | |||
| S Oct 31, 2019 at 15:02 | |||||
| Apr 26, 2017 at 20:50 | vote | accept | John | ||
| Apr 26, 2017 at 0:58 | comment | added | zaza | In addition to the other answers i would point out that you can really do the opposite of what you are suggesting too (i.e. use a PUT/PATCH request to the base recourse to create a entry), it all depends on the back end of the web server. But good practice suggests that you don't do this, following good practice can save you a lot of trouble later on. see restapitutorial.com/lessons/httpmethods.html to get a better understanding of how a web server should react to cretin types. | |
| Apr 25, 2017 at 20:09 | history | edited | Tulains Córdova | CC BY-SA 3.0 | added 1 character in body; edited title |
| Apr 25, 2017 at 9:44 | answer | added | Batavia | timeline score: 1 | |
| Apr 25, 2017 at 9:35 | answer | added | imel96 | timeline score: 5 | |
| Apr 25, 2017 at 8:18 | history | asked | John | CC BY-SA 3.0 |