[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-wget] Connection closed vs read error

From: ptrk mj
Subject: Re: [Bug-wget] Connection closed vs read error
Date: Thu, 9 Aug 2012 20:21:56 +0200

Thanks for sheding light on it. It's important to understand what's going on.


On 8/9/12, Micah Cowan <address@hidden> wrote:
> On 08/09/2012 12:42 AM, ptrk mj wrote:
>> Greetings everyone,
>> I'd like to know what is the technical difference between
>> "Connection closed at byte x."
>> and
>> "Read error at byte x/y (Connection timed out)."
> "Connection closed at byte x" means that the remote end closed the
> connection while wget was still expecting to receive more data (as
> judged by Content-Length or the like). Note that in cases where the
> server doesn't tell us how much data to expect, you would never see this
> message, since in that case there's no way to know whether the server
> closed "early", or if it closed because it was properly finished sending
> content.
> "Read error at byte x/y (Connection timed out)." means that we simply
> stopped receiving packets from the remote server (not even a
> connection-closing packet), and the connection eventually timed out.
> HTH,
> -mjc

reply via email to

[Prev in Thread] Current Thread [Next in Thread]