I'm glad you got it working!
If you can send me more details of the problems you found, I can work on getting them fixed in future versions of CMS.
Just to be clear, there is no Directory Server 4.2, and Directory doesn't have an OCSP capability anyway. CMS 4.2sp2 has built-in OCSP responder functionality, so I assume this must be what you were referring to.
We are very anxious to fix any problems we find in our OCSP support.
--
Steve Parkinson
Engineering Manager, Certificate Management System
Netscape Communications Corp
Dave wrote:
Well I fixed it if anyone wants to know... there appears to be some weird
things with Netscape's implementation of OCSP.
dave.
"Dave" <[EMAIL PROTECTED]> wrote in message
jlMi7.21257$[EMAIL PROTECTED]">news:jlMi7.21257$[EMAIL PROTECTED]...I am trying to write an OCSP agent that talks with the Netscape OCSP
responder built into Netscape Directory Server 4.2. I have followed theRFCspecification for OCSP and cannot seem to get it to work. It talks withtheValiCert OCSP responder ok, but when it attempts to talk with Netscape it
appears to hang. So I captured what Netscape 6.1 sends to it (because it
says that it works), and played it back at the server using netcat, but it
also seems to fail.
When I send the Http Request in Win32 it fails on the HttpSendRequest(...)
it just sits there blocking forever. Does anyone have any ideas ? It
necessarily wasn't a Win32 thing, because it appears in Perl when I
attempted to write the same request to the server aswell.
thanks,
dave.
