On Sat, 13 Nov 2010, Steve M. Robbins wrote:
Does curl really treat the default value as 0 seconds timeout on the connection? Or does it treat 0 as unlimited (i.e. no timeout)? The manpage for curl_easy_setopt is unclear on this.
curl treats a TIMEOUT explicitly set to 0 as a way to disable any previous set timeouts and it goes back to the internal defaults - it is the same as not usig CURLOPT_TIMEOUT at all.
Internal default is pretty much no timeout at all (the situation is a bit more complicated than so, but in general you can consider it to be without timeout).
I have no idea where this bug belongs, but I'm not aware of any bug like this in curl.
-- / daniel.haxx.se -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
