222545 - Error message -8075 comes up: Error establishing connection

Status: RESOLVED DUPLICATE of bug 220275

(Core Graveyard :: Security: UI, defect)

Description

[Thomas Hadig]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031007
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031007

A dialog with the error message -8075 comes up. This happened with Mozilla 1.4
and 1.5. It works fine with e.g. netscape 7.1.

Reproducible: Always

Steps to Reproduce:
1. ... just enter the URL.



Expected Results:  
load and show the page

Comment 1

[Thomas Hadig]

After testing netscape again, netscape didn't work anymore. Removing the
perferences (.mozilla directory), fixed the problem.

Therefore, I played with the preferences a bit and found that OCSP setting
was causing the problems. Somehow, the setting got screwed up while moving 
from netscape 7.1 to mozilla 1.4. I assume one of the OCSP defaults has incorrect
settings.

Maybe, a line in the FAQ would be helpful, such as:

Q: I get a dialog box with error -8075 when I try to connect to a secure web site.
A: Open the preferences, open the Privacy & Security category and select
Validation. Change the OCSP setting to "Do not use OCSP for certificate
validation" and try again.

Comment 2

[Maxious]

I can reproduce this on Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.7b)
Gecko/20040415 Firefox/0.8.0+ using the instructions on
http://www.openvalidation.org/browsersets.htm. Both the intended test page on
openvalidation.org and the main etrade.com page return an error.

I get error code -8040 instead of -8075.

Comment 3

[Frank Thynne]

This error is also manifest in Firefox 0.10.1 when OCSP verification is turned
on. All https URIs produce this error. 

Comment 4

[Josh Birnbaum]

See bug 220275 for an explanation of error -8075.  If you're seeing that error
for another reason, reopen this bug.  For those of you reporting potentially
different issues, you may need to open up a new bug.  But please search the
existing PSM/NSS bugs first, and open up the bug in an appropriate location
(read: PSM or NSS, not Browser).

*** This bug has been marked as a duplicate of 220275 ***