As it turns out the connection *is* cached even though the error has
occured and that is the problem. If I set the force reuse flag, the
second connection uses a fresh connection. This still does not solve my
problem, though, as I am working in a highly paralel environment and I
need to for bad connections to be cleaned up. Can anyone help me with
this?
 
-J

________________________________

From: curl-library-bounces_at_cool.haxx.se
[mailto:curl-library-bounces_at_cool.haxx.se] On Behalf Of Yehoshua
Hershberg (yhershbe)
Sent: Sunday, July 27, 2008 7:33 PM
To: curl-library_at_cool.haxx.se
Subject: issue with cached connection after
CURLE_PEER_FAILED_VERIFICATION

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.
 
Any ideas?
 
-Josh
 
         
Josh Hershberg
Technical Leader
Cisco Secure ACS

yhershbe_at_cisco.com
Phone :+972-9-892-7168
Mobile :+972-54-442-9684
Fax :+972-9-885-7804

32 Hamelacha Street
P.O.Box 8735 I.Z. Sapir
S. Natanya, 42504
Israel
www.cisco.com <http://www.cisco.com/>