Firefox Prefetch

[Dan Zollman]

I don't think prefetch (in the way Firefox implements it) can open the door for malware.

From a security standpoint, the worst it can do is allow cookies to be sent by the prefetched domain. It could make things happen on the website's server, but that's would related to server vulnerabilities, not vulnerabilities on your computer. Prefetch does not even activate scripts from the prefetched page.

Prefetch will only download the page specified by the current page as the "next" page. For example, Google search result pages sometimes specify the most commonly clicked result as the "next" page.

[JackG]

I'm with Dan on this one. If there's a real security threat, please point me to the source of that information, someone reporting on it, anything. All I could find from Googling is some other people saying that this could be a security risk. None of them seemed to go any deeper than that. FWIW, it's apparently enough of a non-issue that a Google search for Firefox prefetch security turns this thread up on the first page. I realize that there may indeed be some risk by keeping leaving it enabled, but until I hear some reputable security firm echo this sentiment, I like my speed surfing enough to leave prefetch turned on.

[Dan Zollman]

One reason people may be concerned about the feature is that they make have confused prefetch with what Google Web Accelerator did. Google Web Accelerator would follow every non-https link on a page indicriminately, which caused problems, and it had a few other flaws. Prefetch doesn't do that.