OK, this is getting weird!
WFetch 1.3 works! (Win2003)
WFetch 1.2 works! (Win2000)
IE 6sp1 doesn't work (Win2000, WinXP)
IE 5.5sp1 doesn't work (WinNT4)
Netscape 4.7 doesn't work (Win2000)
On further investigation....
If I supply an incorrect certificate to WFetch:
0x8009030d [slib]: Could not AcquireCredentialsHandle
0x8009030d Failed to AcquireCredentials()
It would appear that WFetch works, because regardless of what CA issued
certs IIS asks for, it forcibly supplies the correct one (no authentication
handshake appears to take place, though that may be hidden in the SSL
handshake)
If I use any of the other certs built into WFetch, I get an HTTP 403.7
(since I don't have the root CA info for "jaroslad's test certificate
server". The "valid" test cert from VeriSign doesn't work (WFetch 1.2 gets
HTTP 403.7) as it has expired.
Help!
Soon'ish
Craig
"Wei-Dong Xu [MSFT]" <v-wdxu@online.microsoft.com> wrote in message
news:8RJZsWN2DHA.3564@cpmsftngxa07.phx.gbl...
> Hi Craig,
>
> Thank you for replying!
>
> I'd suggest you can use the WFetch utility to test the client request. You
> can run this utility in the client side and then specify the client
> certificate and send one request to the server. The WFetch log will help
> some.
>
> You can download this utility from the link:
> 284285 HOW TO: Use Wfetch.exe to Troubleshoot HTTP Connections
> http://support.microsoft.com/default...microsoft.com:
> 80/support/kb/articles/Q284/2/85.ASP&NoWebContent=1
>
> Please feel free to let me know if you have any further questions.
>
> Does this answer your question? Thank you for using Microsoft NewsGroup!
>
> Wei-Dong Xu
> Microsoft Product Support Services
> Get Secure! - www.microsoft.com/security
> This posting is provided "AS IS" with no warranties, and confers no rights.
>