Firefox 36 very slow connecting - Says "Connecting ...." - while other browsers work
since FF 36 users within our network have problems connecting to web sites. Time to load the entire page is in the range of Minutes. Same behavior for different users after upgrading to FF36. Creating a new profile - same behavior Using portable version - same behavior enabled / disabled: network.dns.disableIPv6 network.dns.disablePrefetch network.http.spdy.enabled.http2 network.http.spdy.enabled.http2draft - same behavior
Using managed F-Secure Client Security
No problems at all with Chrome and IE11. Very odd - any idea?
الحل المُختار
Try to toggle network.dns.get-ttl to false on the about:config page.
Read this answer in context 👍 1All Replies (8)
Try Firefox Portable ESR that is simple for end users to install and test with. Maybe even consider deploying and supporting ESR yourselves
- Portable ESR
http://portableapps.com/news/2014-12-03--firefox-portable-esr-31.3.0-released - Mozilla ESR info https://www.mozilla.org/en-US/firefox/organizations/faq/
- Are you only having problems within your own network ?
- I have noticed occasional reports on the forum of a more general issue e.g.
Work around for server not found problems on FF36 /questions/1049998
Blind guess but http/2 support is new in fx36. I suggest as a test you temporarily disable that. Toggle the two prefs to false using about:config
- network.http.spdy.enabled.http2
- network.http.spdy.enabled.http2draft
On re-reading your post, you have already tried those two prefs.
If you are certain the effect is real and seen in Fx36 but not Fx35.0.1 file a bug at bugzilla.
Note however some users may have suggested similar problems are seen in Fx36 but resolved if Windows SafeMode is used. If that is the case then such an issue may not be a Firefox bug.
Update. This may be the fix and should be out in a few days with Fx36.0.1
- Bug 1093983 - DNS resolver should not use 'ANY' to get cached records for TTL
- Details of actual change https://hg.mozilla.org/releases/mozilla-release/rev/c37f6a5a0c8a
الحل المُختار
Try to toggle network.dns.get-ttl to false on the about:config page.
> Try to toggle network.dns.get-ttl to false on the about:config page.
THANKS - that did the trick - great!
Is this a new setting in ff36? Or what has changed in relation to this? Cheers, Thomas
Modified by tgoecke
John99 said
Update. This may be the fix and should be out in a few days with Fx36.0.1
- Bug 1093983 - DNS resolver should not use 'ANY' to get cached records for TTL
- Details of actual change https://hg.mozilla.org/releases/mozilla-release/rev/c37f6a5a0c8a
Thanks John, appreciate your feedback.
Note that Firefox 36.0.1 has been released, so you can update and see if it works with the pref I mentioned above set to default.
cor-el said
Note that Firefox 36.0.1 has been released, so you can update and see if it works with the pref I mentioned above set to default.
Works! Thanks a lot. So bug seems to be fixed.