You were right, Nelson. The problem had nothing to do with the Mozilla/Netscape latest versions. It was a server side problem that was throwing an error before it had a chance to complete the SSL handshake between the browser and server. Once the server problem was corrected, the certificate/SSL connection came right up in the latest versions of Mozilla/Netscape.Greg wrote:
Nelson B wrote:
Greg wrote:
Any reasons why a certificate would work fine in Netscape 6.0 and not work in Netscape 7.2? It doesn't happen on all sites, just certain ones .. The browser loads the certificate fine (I can view it and see the proper chain) but when I press Ok (to continue), I get a "The connection to the host has been terminated unexpectedly. Some data may have been transfered." The certificate loads fine in Netscape 6.0.
Any thoughts?
The host terminated the connection. You should be asking the host admin why it did that.
True. However, there must be some change to the way the certificate is negotiated in the latest version because it works fine in previous versions. And, no issues in any "other" browsers.
Lots of servers look at the "User Agent" string that the browser sends in with the request, and only accept requests from browsers with known agent strings. Every time mozilla brings out a new browser, we get a raft of complaints about web sites that like the old and dislike the new. Banks are typically the worst offenders.
IIRC, there's a plugin for mozilla (and NS 7.x) that causes the browser to lie about what product it is, and claim to be another. It would be interesting to try that with your 7.2, having it claim to be (say) IE or NS 6.0, and see if your web site suddenly is happy with it.
Thanks for your follow up - it prompted me to look a little deeper on the server side where I found the problem. I'll post the solution in the appropriate server side forum.
Greg _______________________________________________ mozilla-crypto mailing list [email protected] http://mail.mozilla.org/listinfo/mozilla-crypto
