Timeline for How to fix HTTP method DELETE doesn't support output
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 13, 2015 at 0:36 | vote | accept | rpm07 | ||
| Feb 12, 2015 at 18:42 | comment | added | CloudConnect | As far as security is concerned, both POST and DELETE are almost same. If data is transferred over secure HTTP the chances of data breach are minimal. Few things that can effect in either case are: POST - size could affect, as the data packets are big DELETE - as id is passed through URL, it could be logged in client browser as cache etc. | |
| Feb 12, 2015 at 12:45 | comment | added | rpm07 | would it more vulnerable when it comes in security, setting it to the endpoint? | |
| Feb 12, 2015 at 11:38 | comment | added | Richard Durrant | Could also set the endpoint to testsite.com/api/User/29 ? More standard in REST APIs to do it this way. | |
| Feb 12, 2015 at 10:39 | history | edited | CloudConnect | CC BY-SA 3.0 |
added 69 characters in body
|
| Feb 12, 2015 at 10:03 | history | answered | CloudConnect | CC BY-SA 3.0 |