4 ms·
It also bypasses browser preloading settings and messes with people who have limited bandwidth or transfer quota. It should be optional.
by AstralStorm 6y ago
It also bypasses browser preloading settings and messes with people who have limited bandwidth or transfer quota. It should be optional.
- megous 6y agoYeah, I'm currently looking for a way to disable this and it seems like it may be controlled by: network.predictor.preconnect-min-confidence in Firefox.
- Deukhoofd 6y agoLooking at caniuse.com preconnect hasn't been supported by Firefox since v71. I assume for this very reason. https://caniuse.com/link-rel-preconnect https://caniuse.com/link-rel-preconnect
- Jestar342 6y ago"network.predictor.enabled" is there. Defaults is still "true".
- youngtaff 6y agoSuspect that's not for explicit `<link rel=preconnect` More likely it's for when FF is making a connection because it predicts that page is going to use a connection to another origin
- judge2020 6y agoIt just connects to the domain without making a request to it, so how does it use even a remotely noticeable amount of bandwidth?
- megous 6y agoTo answer that question: https://megous.com/dl/tmp/5a6729bcaa62d382.png https://megous.com/dl/tmp/5a6729bcaa62d382.png From wireshark capture of `openssl s_client localhost:443` 2kb can add up if done often enough. And this is a fairly ideal case. I just have two simple certs using secp384r1. If certificate chain is longer and when the certs use RSA, it will consume more bandwidth.