Microsoft REST API Guidelines

Re:Microsoft REST API Guidelines by matthewmacleod on Friday November 22, 2019 @06:56PM (#21611358)

You’d use forms with buttons in them, and style them to look however you like. I used to do this a lot when building pages using progressive enhancement; it’s less common now.

An “upvote” is probably an idempotent action. Calling an “upvote” endpoint moves an object into an “upvoted” state, regardless of what it’s previous state was. However, it’s probably semantically a PATCH, since it’s a partial update of a resource.

There is no real disconnect here.

[ Parent | on HN ]

Re:Microsoft REST API Guidelines by chrisseaton on Friday November 22, 2019 @07:00PM (#21611381)

I see things like <a> GET links for destructive operations all the time - are they in violation of the HTTP spec? Do browsers speculatively load these resources and delete things without the user interacting?

[ Parent | on HN ]

Re:Microsoft REST API Guidelines by OkGoDoIt on Friday November 22, 2019 @07:17PM (#21611473)

It’s definitely a problem. You should never have any destructive or modifying actions of any sort done from a GET request. In addition to browser prefetching, users might share a link without the receiving user realizing they are taking an action as soon as they click the link, which can be a source of security issues.

That being said, I too have seen things like this on the Internet. I would assume Google has some sort of heuristic to determine whether or not they can safely prefetch a link, but who really knows? You should absolutely avoid making this mistake in your own code.

[ Parent | on HN ]