Avatar for Username

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

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

  • 2 antwurd
  • 2 hawwe dit probleem
  • 4 werjeftes
  • Lêste antwurd fan 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?

Bewurke troch Zakiia op

Keazen oplossing

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.

Dit antwurd yn kontekst lêze 👍 2

Alle antwurden (2)

philipp
philipp
  • Moderator
more options

Keazen oplossing

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 Fraacheigener
more options

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

Thanks! :)