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

Reply via email to