You know how HTTP GET requests are meant to be idempotent?

Re:You know how HTTP GET requests are meant to be idempotent? by fenwick67 on Tuesday May 01, 2018 @01:29PM (#16969205)

GET is meant to get, not set. Since 1.0.

https://www.w3.org/Protocols/HTTP/1.0/spec.html#GET

> The GET method means retrieve whatever information (in the form of an entity) is identified by the Request-URI

[ Parent | on HN ]

Re:You know how HTTP GET requests are meant to be idempotent? by downer68 on Tuesday May 01, 2018 @02:25PM (#16969840)

So what?

If I never intended for the GET to be GOT, then the browser is just as much at fault for such unintended consequences.

[ Parent | on HN ]

Re:You know how HTTP GET requests are meant to be idempotent? by scottmf on Tuesday May 01, 2018 @07:06PM (#16972571)

That’s the whole point of HTTP request methods: it isn’t. GET should never cause such side effects. The entire web is built with these principles in mind precisely so that problems like this don’t happen.

If you want a slower browsing experience feel free to disable prefetching in your browser, but this isn’t a hill worth dying on.

[ Parent | on HN ]