On Mon, 7 Jan 2002, Daniel Stenberg wrote:

> No, because the connect is made non-blocking and it probably returned
> something saying that it isn't quite connected yet. We need to add code in
> a manner similar to the regular connect for the SSL connection too, when
> using non-blocking sockets.

I've made an attempt to fix this. Could you please try the attached patch and
see if this improves your situation?

If this works out for you, it'll be interesting to see if Paul Harrington's
SSL-timeout problems disappear as well...

I've run all the tests with this fix applied, it doesn't seem to ruin
anything in my end (with Solaris, IPv4-only).

-- 
    Daniel Stenberg -- curl groks URLs -- http://curl.haxx.se/