Re-Opening this bug. I can replicate it again on a Win32 Mozilla Build 3.5.5. GlobalSign NV-SA is in the cert store as a token, expiry 2028. If you need a shot of that, let me know.
Is this a misunderstanding on my part of the SSL Cert coverage? It seems sometimes the cert will cover all ports, sometimes not. Does it require a wildcard?
Re-Opening this bug. I can replicate it again on a Win32 Mozilla Build 3.5.5. GlobalSign NV-SA is in the cert store as a token, expiry 2028. If you need a shot of that, let me know.
I replicate this on https:/ /cosmos. constellationme dia.com: 2096. This cert ought to cover this, unless I'm missing something. Any ideas Steve? Port 80 works fine, as does https:/ /2028.globalsig n.com/
Is this a misunderstanding on my part of the SSL Cert coverage? It seems sometimes the cert will cover all ports, sometimes not. Does it require a wildcard?