On Thu, 26 Feb 2004, Richard Bramante wrote:

> Has anyone else ever experienced these? What was cause this return, when it
> happens it happens very fast (reported as almost immediately) in which case
> I would expect something like a CURLE_COULDNT_CONNECT error, or at least
> wait the timeout period and then error with a timeout. This doesn't seem to
> be the case. Does this imply the connection was established but then
> immediatel closed or something to that effect?

It is hardly impossible to guess without any network traces. Clearly at least
libcurl thought it was a legitimate connect, but then it got closed before any
response was read from it. But I can't see why a high latency connection would
cause that effect.

-- 
    Daniel Stenberg -- http://curl.haxx.se/ -- http://daniel.haxx.se/
   [[ Do not send mails to this email address. They won't reach me. ]]