Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Mulongo oyo etiyamaki na archive. Tuna motuna mosusu soki osengeli na lisalisi

Does Firefox now "read a page ahead" for WordPress sites?

  • 2 biyano
  • 1 eza na nkokoso oyo
  • 4 views
  • Eyano yasuka ya user1027088

more options

Hi there,

I've just noticed something odd in Firefox 26.0. Using Fiddler, I see that when I am browsing WordPress sites, the browser is requesting an additional page (only the source page, not the links on the page) to the one I am actually looking at. In effect it appears to be browsing "ahead" one page along the Wordpress menu, storing this page in case that happens to be the one I will look at next. This activity also happens in Safe Mode and does not happen with the latest version of Chrome.

Is this a new feature and, if so, how do I switch it off?

Hi there, I've just noticed something odd in Firefox 26.0. Using Fiddler, I see that when I am browsing WordPress sites, the browser is requesting an additional page (only the source page, not the links on the page) to the one I am actually looking at. In effect it appears to be browsing "ahead" one page along the Wordpress menu, storing this page in case that happens to be the one I will look at next. This activity also happens in Safe Mode and does not happen with the latest version of Chrome. Is this a new feature and, if so, how do I switch it off?

Solution eye eponami

Try to set the network.prefetch-next pref to false on the about:config page (search prefetch).

Tanga eyano oyo ndenge esengeli 👍 0

All Replies (2)

more options

Solution eye oponami

Try to set the network.prefetch-next pref to false on the about:config page (search prefetch).

more options

That did the trick cor-el, many thanks!

For anyone else reading this thread, the following article might prove useful: http://www.ghacks.net/2013/04/27/firefox-prefetching-what-you-need-to-know/

It appears that the WordPress page isn't using rel="prefetch" as described in the above article, but instead FF is prefetching the page indicated by rel="next".