Is firefox 2.0.0.8 suppose to try different OCSP responders?

Now that I have the OCSP responder stuff working, I started playing around with how firefox uses the AIA records. In the end entity certificates, I have setup AIA that lists three OCSP responders, namely: Not Critical OCSP: URI: http://server1:9000 OCSP: URI: http://server2:9000 OCSP: URI: http://

Re: Problems with getting OCSP to work with firefox 2.0.0.8 (Fedora Core 7)

Thanks for all the help. It turns out the CA cert had to be reinstalled. I had loaded a PKCS12 cert that included the certificate chain. When I checked the "Authorities", the CA was there, so it was loaded when I loaded the PKCS12 user cert. I deleted the CA then inported it again. When I imp

Re: Problems with getting OCSP to work with firefox 2.0.0.8 (Fedora Core 7)

Now I don't know much more, except as Nelson already mentioned that the CA root might not be installed in the browser. If the problem persist, an actual certificate and domain responder location etc is needed in order to get a better picture. Bruce Keats wrote: > OK. > > There is nothing specia

Re: Problems with getting OCSP to work with firefox 2.0.0.8 (Fedora Core 7)

Thanks for the hint. I didn't pay much attention to the cert warning as everything appears to work (other than the OCSP checks). I will give it another go once I resolve the warnings. Bruce On 11/2/07, Nelson B <[EMAIL PROTECTED]> wrote: > > Bruce Keats wrote: > > > I have an HTTPS server tha