Re: libCurl 7.16.3: Are there any problems known for timeouts set with CURLOPT_TIMEOUT ?
Date: Sun, 13 Apr 2008 14:25:14 +0200
>> Debugging revealed the following. In file ssluse.c, at a certain
>> point during the SSL handshake, the function ossl_connect_common() is
>> called. In line 1790 it checks for sockets ready. Sockets are
>> nonblocking, so the timeout is 0. Curl_socket_ready() returns then 0
>> every time. That leads to the return of CURLE_OK. Without any action
>> on the sockets, that repeats endlessly and longer than the configured
> Ouch. How about the attached patch, does this fix the problem for you?
Yes, I retried my test with your patch and it works fine now. Thank you
very much for your support!
Will that patch be included in the next official release ?
Received on 2008-04-13