easy5 pts · first answer countshttprest-api-design

A GET that deletes data

An endpoint GET /users/5/delete removes user 5. What is the main problem with this design?

A.GET requests cannot include an id in the pathB.GET is slower than DELETE on most serversC.GET responses are cached by browsers and proxies, so the delete would run only once per user and then silently stop workingD.GET should be safe; crawlers, link previews and prefetching can trigger it, and it is easy to abuse with CSRF

Discussion 0

Join free to post in the discussion.

A GET that deletes data

Discussion 0

Related questions