Avatar for Username

搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊，或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

此討論串已被封存。 如果您有需要幫助，請新增一個新問題

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

  • 2 回覆
  • 1 有這個問題
  • 4 次檢視
  • 最近回覆由 user1027088

user1027088
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?

被選擇的解決方法

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

從原來的回覆中察看解決方案 👍 0

所有回覆 (2)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

選擇的解決方法

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

user1027088
user1027088 提出問題者
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".