On Sun, 27 Jul 2008, Yehoshua Hershberg (yhershbe) wrote:

> Here is the scenario. I am using the multi interface, I issue a request to a
> certain url and the request finishes with CURLE_PEER_FAILED_VERIFICATION due
> to the CN in the server cert not matching the URL. After that I place
> another request with a *different* CURL handle and the request succeeds
> since it seems to be using the connection from the first request which was
> apparently cached, even though the first request failed verificatoin.

Ouch, that sounds like a bug. Is this happening with libcurl 7.18.2?

Can you provide a smallish example that shows this happening (against a public
URL) ?

-- 
  / daniel.haxx.se