Pomoc pśepytaś

Glědajśo se wobšudy pomocy. Njenapominajomy was nigda, telefonowy numer zawołaś, SMS pósłaś abo wósobinske informacije pśeraźiś. Pšosym dajśo suspektnu aktiwitu z pomocu nastajenja „Znjewužywanje k wěsći daś“ k wěsći.

Dalšne informacije

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

  • 2 wótegronje
  • 1 ma toś ten problem
  • 4 naglědy
  • Slědne wótegrono wót 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?

Wubrane rozwězanje

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

Toś to wótegrono w konteksće cytaś 👍 0

Wšykne wótegrona (2)

more options

Wubrane rozwězanje

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".