2 ms·
GET is meant to get, not set. Since 1.0. https://www.w3.org/Protocols/HTTP/1.0/spec.html#GET https://www.w3.org/Protocols/HTTP/1.0/spec.html#GET > The GET me
by fenwick67 8y ago
GET is meant to get, not set. Since 1.0.
https://www.w3.org/Protocols/HTTP/1.0/spec.html#GET 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
- downer68 8y agoSo what? If I never intended for the GET to be GOT, then the browser is just as much at fault for such unintended consequences.
- scottmf 8y agoThat’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.