On Wed, Sep 17, 2008 at 07:16:35PM +0200, Aurélien wrote:
> I waited some days (really), so I don't think it's entirely a TCP-related
> issue. But, the options you mentioned seems to be effective in my test
> environment, so I will bench them over the next few days in production. Anyway,
> I imagine that after some reasonable amount of time, the apache server at the
> other end closes the connection, and at this time, curl should stop waiting...
> which it doesn't do in my application.

This does sound suspicious. It's possible that there's some kind of problem
in curl that CURLOPT_LOW_SPEED_LIMIT will just mask. It would be good if
you could characterise the problem some more.

> The problem is quite hard and long (12-24hrs) to reproduce in production, so i
> can only test it in a VM. I'm not exactly sure of the exact conditions in which
> it occurs.
>
> What period of time is "a long time" for you ? Hours ? days ? longer ?

The Linux documentation says its default is 13-30 minutes.

>>> Dan

-- 
http://www.MoveAnnouncer.com              The web change of address service
          Let webmasters know that your web site has moved