On Thu, 28 May 2009, junk_at_igrspace.com wrote:

> I found that when a connection is re-used over easies that had
> CURLOPT_CONNECT_ONLY set, a curl_easy_getinfo() for CURLINFO_LASTSOCKET
> fails (returning -1) for the subsequent easy.

You're out on deep water with that sort of trickery. Known bug #63 details it
somewhat and it links to more discussions.

Doing CURLOPT_CONNECT_ONLY sort of lets you take control over the socket and
after that moment libcurl really cannot depend on anything on that socket.

Can you elaborate a little on what exactly you're trying to accomplish with
this?

-- 
  / daniel.haxx.se