We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

搜尋 Mozilla 技術支援網站

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

了解更多

Loading the HTTPS version of Google causes Firefox to make 3 background request every 45 seconds even after closing the page.

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

more options

Loading the HTTPS version of Google causes Firefox to make 3 background request every 45 seconds even after closing the page. With other HTTPS sites that support HTTP Strict Transport Security (HSTS) I noticed only 1 background connection. How can I disable these background connections?

Loading the HTTPS version of Google causes Firefox to make 3 background request every 45 seconds even after closing the page. With other HTTPS sites that support HTTP Strict Transport Security (HSTS) I noticed only 1 background connection. How can I disable these background connections?

由 Zakiia 於 修改

被選擇的解決方法

hello, i'm no expert regarding the issue, but it may well be, that the spdy-protocol, that is used by google on its secure sites (and twitter atm), is causing the behaviour that you've observed.

"SPDY connections are persistent connections. For best performance, it is expected that clients will not close open connections until the user navigates away from all web pages referencing a connection, or until the server closes the connection. Servers are encouraged to leave connections open for as long as possible, but can terminate idle connections if necessary." http://mbelshe.github.com/SPDY-Specification/draft-mbelshe-spdy-00.xml#rfc.section.2.1

you may want to try to disable the support for the spdy protocol in firefox (in about:config) and see if this changes the number and length of connections to the server.

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

所有回覆 (2)

more options

選擇的解決方法

hello, i'm no expert regarding the issue, but it may well be, that the spdy-protocol, that is used by google on its secure sites (and twitter atm), is causing the behaviour that you've observed.

"SPDY connections are persistent connections. For best performance, it is expected that clients will not close open connections until the user navigates away from all web pages referencing a connection, or until the server closes the connection. Servers are encouraged to leave connections open for as long as possible, but can terminate idle connections if necessary." http://mbelshe.github.com/SPDY-Specification/draft-mbelshe-spdy-00.xml#rfc.section.2.1

you may want to try to disable the support for the spdy protocol in firefox (in about:config) and see if this changes the number and length of connections to the server.

more options

You have found the solution, the culprit is SPDY protocol.

Thanks! :)