> Does your cert.pem contain the chain of CA certs that signed your client > certificate?
Thank you very much for your reply. No, they are self signed. cert.pem was generated from a .p12 file, in turn generated from a self signed my.key and my.crt. (viewing it as text reveals an public and private key) > You have a working command-line already, so you can use the --libcurl option > to get the equivalent source file (with the exception of formpost stuff as > mentioned in the man page): > > curl --libcurl myCurlSsl.c -w -E cert.pem https://some.site.com Looks like a handy option. However I havn't been able to get it to produce anything meaningful from it. Beyond the default http opts, the only relavent option (in the commented out section) is CURLOPT_SSLCERT. By the way -vv was a typo on my part i meant -v(--VERBOSE) just so I can debug this issue. I've had a fairly long go at this before bothering this list again. But I must be missing something fundamental in the api. As this works just fine as a curl command line. ------------------------------------------------------------------- List admin: http://cool.haxx.se/list/listinfo/curl-library Etiquette: http://curl.haxx.se/mail/etiquette.html
