1138588 - Secure Connection Failed at optimum.net

Status: RESOLVED FIXED

(Web Compatibility :: Site Reports, defect)

Description

[Gary [:streetwolf52]]

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.

Comment 1

[Gary [:streetwolf52]]

https://www.ssllabs.com/ssltest/analyze.html?d=optimum.net

Comment 2

[Gary [:streetwolf52]]

FYI.... Site works fine using IE11.

Comment 3

[Gary [:streetwolf52]]

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.

Comment 4

[Masatoshi Kimura [:emk]]

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.

Comment 5

[Gary [:streetwolf52]]

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?

Comment 6

[Masatoshi Kimura [:emk]]

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.

Comment 7

[:Cykesiopka]

(Fixing URL field so that clicking it doesn't result in a Bugzilla error page)

Comment 8

[Masatoshi Kimura [:emk]]

Fixed.