Re: libCurl 7.16.3: Are there any problems known for timeouts set with CURLOPT_TIMEOUT ?
Date: Sun, 6 Apr 2008 16:51:30 -0700
On Sun, Apr 06, 2008 at 08:22:22PM +0200, Stefan Krause wrote:
> OK. What should happen, when I do _not_ configure any timeout? I observed
> the following: Without an explicit timeout, the operation (e.g.) POST
> expired after 10 minutes (on another QNX release, 6.3.0 instead of 6.3.2)
> when the physical network layer was removed. Is that a default timeout
> (maybe in the socket domain), which depends on the actual OS ? Or does
> libCurl is intended to wait for ever without time-outing ?
That sounds like a TCP-level timeout. It's probably not under control by
the application except perhaps on a global basis.
-- http://www.MoveAnnouncer.com The web change of address service Let webmasters know that your web site has movedReceived on 2008-04-07