25 ms·
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.
by downer68 8y ago
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.
- 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.