All users were logged out of Bugzilla on October 13th, 2018

Error with directory (OCSP) lookup for cert on https



14 years ago
2 years ago


(Reporter: vimages, Assigned: dveditz)


1.0 Branch
Windows XP

Firefox Tracking Flags

(Not tracked)





14 years ago
To reproduce:

1) Open:
2) Click the Website tonight or Website Complete links in the right hand column

results: A modal error dialog is displayed which reads:

"Error trying to resolve certificate from using  OCSP -
directory lookup error."

expected results: The requested page is opened.

Comment 1

14 years ago
wfm using FF trunk 20040802 on Win2k.

Comment 2

14 years ago
Forgot to mention. Browser this failed with was:
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040803
*** Bug 269510 has been marked as a duplicate of this bug. ***

Comment 4

14 years ago
The certificate lists an OCSP server of, which doesn't exist.

As long as you have OCSP enabled in your preferences, you won't be able to get
to sites using starfieldtech/godaddy certs.

Marking invalid, the crypto code is working as expected.
Last Resolved: 14 years ago
Component: Security: General → Client Library
Product: Browser → PSM
Resolution: --- → INVALID
Version: Trunk → 2.4

Comment 5

14 years ago
Thanks for the info.  Resolved the issue for me.

Comment 6

14 years ago
I asked Starfield support if they had anything to say on the matter.  They
responded: "We currently do not support OCSP but the server is listed in the
certificate so that every certificate we issue will work when we start
supporting it."

Comment 7

14 years ago
Josh,  did you ask them what the hell that means?  It sounds like "no, but when
we do it will be great!"  Are the taking lessons from M$?

Comment 8

14 years ago
Their support address is, if you want to discuss it
further.  Your interpretation of the email does match mine, though.


14 years ago
Component: Security: UI → Security: UI
Product: PSM → Core


10 years ago
Version: psm2.4 → 1.0 Branch
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.