On Mon, 22 Oct 2018, Peng Yu wrote:

> I frequently see "curl: (18) transfer closed with outstanding read data
> remaining". It seems that it is related to the use of a http_proxy. Is there
> an option to make curl more robust so that it will handle this problem
> correctly?

It's not really a matter of "robustness". When the TCP connection gets
disconnected, that's not something curl can change or "improve".

What curl *could* do however, is retry the transfer when such an error occurs
if such an option is used (which it currently doesn't), and then it *could*
ask for the transfer to get resumed from the last byte position it received.
The latter part was submitted as the incomplete PR #2450 that seems to have
been abandoned...

[#2450] = https://github.com/curl/curl/pull/2450

-- 
  / daniel.haxx.se
-----------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-users
Etiquette:   https://curl.haxx.se/mail/etiquette.html