> Just try it out and report back if there is a problem.
It is hard to reproduce the problem.
--
Regards,
Peng
On 18.05.19 13:39, Peng Yu wrote:
> On 5/18/19, Tim Rühsen wrote:
>> On 17.05.19 23:09, Peng Yu wrote:
>>> Hi,
>>>
>>> curl has this problem "(18) transfer closed with outstanding read data
>>> remaining". Does wget have a similar problem like this? Thanks.
>>>
>>> https://curl.haxx.se/mail/archiv
On 18.05.19 16:22, Daniel Stenberg wrote:
> On Sat, 18 May 2019, Tim Rühsen wrote:
>
>> The connection is closed prematurely and you do not want to
>> re-download everything.
>>
>> Wget has -c / --continue for that.
>
> I could be noted that transfers with chunked encoding are rarely resumable.
>
On Sat, 18 May 2019, Tim Rühsen wrote:
The connection is closed prematurely and you do not want to re-download
everything.
Wget has -c / --continue for that.
I could be noted that transfers with chunked encoding are rarely resumable.
--
/ daniel.haxx.se
On 5/18/19, Tim Rühsen wrote:
> On 17.05.19 23:09, Peng Yu wrote:
>> Hi,
>>
>> curl has this problem "(18) transfer closed with outstanding read data
>> remaining". Does wget have a similar problem like this? Thanks.
>>
>> https://curl.haxx.se/mail/archive-2018-10/0015.html
>
> The connection is c
On 17.05.19 23:09, Peng Yu wrote:
> Hi,
>
> curl has this problem "(18) transfer closed with outstanding read data
> remaining". Does wget have a similar problem like this? Thanks.
>
> https://curl.haxx.se/mail/archive-2018-10/0015.html
The connection is closed prematurely and you do not want to
The question is whether wget can fix the problem by resuming from where it
failed. Curl can not do it as mentioned in the email.
On Fri, May 17, 2019 at 4:20 PM Daniel Stenberg wrote:
> On Fri, 17 May 2019, Peng Yu wrote:
>
> > curl has this problem "(18) transfer closed with outstanding read da
On Fri, 17 May 2019, Peng Yu wrote:
curl has this problem "(18) transfer closed with outstanding read data
remaining". Does wget have a similar problem like this? Thanks.
That's not a "problem" curl has. That's a feature. It detects prematurely cut
off transfers when receiving chunked encoded
