http://www.ilovejackdaniels.com/article/block-prefetching/Latest comments on Block Prefetching on ILoveJackDaniels.comhttp://www.ilovejackdaniels.com/article/block-prefetching/comments/http://www.ilovejackdaniels.com/article/block-prefetching/comments/Comment by Nemesis#13 ( <a href=""></a> )<br /><br />nice tip. thx <br /> <br />ps: some css rules for these inputs would make this site also look good on systems using unsuitable themes. i think, black text on white bg would do it already :)http://www.ilovejackdaniels.com/article/block-prefetching/comments/http://www.ilovejackdaniels.com/article/block-prefetching/comments/Comment by Sven Krohlas ( <a href="http://krohlas.de">http://krohlas.de</a> )<br /><br />I just had a look at http://www.mozilla.org/projects/netlib/Link_Prefetching_FAQ.html <br />Prefetching should only take place in link-tags with rel="prefetch". So if you really can reproduce a situation where if simply fetches all links file a bug at http://bugzilla.mozilla.org, here the responsible developers won't read it. <br /> <br />PS: really great comment preview, I start loving "Web 2.0" applications. :-)http://www.ilovejackdaniels.com/article/block-prefetching/comments/http://www.ilovejackdaniels.com/article/block-prefetching/comments/Comment by Brett ( <a href=""></a> )<br /><br />Products like Basecamp that use GET requests with intermediary Javascript confirm() calls for potentially dangerous actions such as deleting an item are suffering the most from prefetching. <br /> <br />I have to wonder why Javascript is used in favor of an intermediary confirmation screen that requires a POST request to complete the delete action? <br /> <br />Off the top of my head I can think of one big one: intercepting a GET request with Javascript saves the user (and the server) an additional page load. <br /> <br />XMLHttpRequest is perhaps an option, but is it yet viable?