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 <dan...@haxx.se> wrote: > 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 data. > > I would presume wget does the same, as so should all HTTP clients. > > But of course, a retry might repair the damage as the transfer can be > tried > again. > > -- > > / daniel.haxx.se > -- Regards, Peng