On Thu, 20 Sep 2007, autrelandes-curl_at_yahoo.fr wrote:

> Sorry. "identifient le même fichier" means "identifies the same file".
> You are right, I installed curl in the same directory than I unpacked it.
> Obviously, it's a bad habit I should quit.

Yes, that's a rather unwise thing to do...

>> This kind of behaviour is in 99.7% of all cases because you do this
>> connection over a firewall/NAT/router/whatever that times out "idle"
>> connections after N minutes and idleness and in your case I would say that
>> N is greater than 13 and that your latter case doesn't use the same network
>> route as your first case did.

> For the test during 54 minutes, I indeed used an totally different network.
> The connection where the problem occurs indeed includes router, firewall and
> NAT equipment.

> Does this mean that, for this problem, there is no bug or any possible fix
> in curl and that it is only due to the network equipment ?

I would say it is a minor annoyance and it could of course be seen as a bug.
The real fix for that would be to add an option to libcurl to make it send a
NOOP command over the control connection every Z minutes to prevent it from
actually being idle during long transfers.

This has been mentioned numerous times in the past but so far nobody has
deemed this important enough to actually fix it. And the fix isn't really
trivial either.

> A workaround would then be to chunk a file in smaller pieces, which,
> hopefully, I can do.

That should work, yes.

-- 
  Commercial curl and libcurl Technical Support: http://haxx.se/curl.html