Re: nonblocking sockets [PATCH]
Date: Mon, 7 Jan 2002 16:47:22 +0100 (MET)
On Mon, 7 Jan 2002, Georg Horn wrote:
> Yes, it seems to work:
> $ src/curl -v --connect-timeout 1 https://meine.db24.de
> * Connected to meine.db24.de (22.214.171.124)
> > GET / HTTP/1.1
> User-Agent: curl/7.9.2 (i686-pc-linux-gnu) libcurl 7.9.2 (OpenSSL 0.9.6)
> Host: meine.db24.de
> Pragma: no-cache
> Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, */*
> curl: (23) SSL connection timeout
> * Closing connection #0
> I'm just wondering why the "SSL connection timeout" appears after the
> request that is going to be sent...? Or, why the request is printed at all
> if the connection couldn't be established?
Hm, that doesn't look right. Another odd thing is why it returned 23
(CURLE_WRITE_ERROR) and not 28 (CURLE_OPERATION_TIMEOUTED)... The error text
clearly shows that the SSL connection timeout logic worked.
Could you set a break-point and single-step a little while from that point
and on to see where/why it does this?
-- Daniel Stenberg -- curl groks URLs -- http://curl.haxx.se/Received on 2002-01-07