Timeline for Why should someone block all methods other than GET and POST in a RESTful application?
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 6, 2020 at 11:13 | comment | added | domen | In context of this question - security aspect answers something, I'm not sure other parts do. | |
| Feb 6, 2020 at 10:42 | comment | added | Michael Quad | @domen Not only security. Browsers are made to be more restrictive to PUT/DELETE methods, so more lines of code will be involved into implementation of PUT/DELETE. More tests should be made. Besides GET/POST, OPTIONS should also be taken into account, if you like to create public accessible API. For example Telegram Bot API doesnt have PUT/DELETE. Check out other services! | |
| Feb 6, 2020 at 8:46 | comment | added | domen | So, I guess you're trying to say security risks can be the same, because same functionality will be implemented with GET and POST? | |
| Feb 5, 2020 at 18:35 | review | Late answers | |||
| Feb 5, 2020 at 20:06 | |||||
| Feb 5, 2020 at 18:20 | review | First posts | |||
| Feb 6, 2020 at 8:46 | |||||
| Feb 5, 2020 at 18:16 | history | answered | Michael Quad | CC BY-SA 4.0 |