Closed Bug 1138588 Opened 8 years ago Closed 8 years ago
Secure Connection Failed at optimum
User Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:39.0) Gecko/20100101 Firefox/39.0 Build ID: 20150302073044 Steps to reproduce: Go to www.optimum.net Actual results: Secure Connection Failed message. I believe the server is RC4 only. Expected results: Page should have been accessed.
FYI.... Site works fine using IE11.
Just wondering if there is a way to allow access to my site via a pref? I notified my sites technical support, who happens to be my ISP, about RC4 servers and they are looking into it. I doubt they will come up with a fix any time soon.
Please go to about:config and add the server name (www.optimum.net) to "security.tls.insecure_fallback_hosts". This pref is a comma-separated list so that you can add multiple host names. I'll update the built-in whitelist at least once before the next merge.
Please also add signin.optimum.net to the whitelist. This begs the question, can you make the whitelist accept something like optimum.net to cover all the optimum.net pages?
The built-in whitelist supports the wildcard, but I will use it only if I will have to add dozens of subdomains because the wildcard is very inefficient. The "security.tls.insecure_fallback_hosts" pref does not support the wildcard, sorry.
(Fixing URL field so that clicking it doesn't result in a Bugzilla error page)
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Product: Tech Evangelism → Web Compatibility
You need to log in before you can comment on or make changes to this bug.