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!

Avatar for Username

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

This thread was archived. Please ask a new question if you need help.

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

  • 2 majibu
  • 2 wana tatizo hili
  • 4 views
  • Last reply by Zakiia

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

Modified by Zakiia

Chosen solution

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.

Read this answer in context 👍 2

All Replies (2)

philipp
philipp
  • Moderator
more options

Suluhisho teule

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.

Zakiia
Zakiia Mwenye swali
more options

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

Thanks! :)