Buy commercial curl support from WolfSSL. We help you work
out your issues, debug your libcurl applications, use the API, port to new
platforms, add new features and more. With a team lead by the curl founder
himself.
Re: Recover from: (18) transfer closed ...?
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Daniel Stenberg via curl-users <curl-users_at_lists.haxx.se>
Date: Mon, 3 Jul 2023 20:09:45 +0200 (CEST)
On Mon, 26 Jun 2023, Paul Gilmartin via curl-users wrote:
> Lately, in a script with with
> curl --etag-save ... --time-cond ...
> I got:
> curl: (18) transfer closed with outstanding read data remaining
>
> Simply retrying shouldn't work because both the ETag and the timestamp of
> the target file were updated with the failure.
This error is a problem with the server or the network. Data is missing when
the transfer ended.
Date: Mon, 3 Jul 2023 20:09:45 +0200 (CEST)
On Mon, 26 Jun 2023, Paul Gilmartin via curl-users wrote:
> Lately, in a script with with
> curl --etag-save ... --time-cond ...
> I got:
> curl: (18) transfer closed with outstanding read data remaining
>
> Simply retrying shouldn't work because both the ETag and the timestamp of
> the target file were updated with the failure.
This error is a problem with the server or the network. Data is missing when
the transfer ended.
-- / daniel.haxx.se | Commercial curl support up to 24x7 is available! | Private help, bug fixes, support, ports, new features | https://curl.se/support.html -- Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-users Etiquette: https://curl.se/mail/etiquette.htmlReceived on 2023-07-03