Skip to content

--retry ignores --continue-at for the latest file #18035

Closed

Description

@tkzv

I did this

I tried
curl -y 30 -Y 30 --connect-timeout 10 --retry 10 -C - -x socks5h://localhost:9050 -e https://somesite.com/ -LORf https://somesite.com/[1-10].webp

Downloading from this site is unstable. It often downloads 10-20k out of ~100k and gets stuck, thus it needs too be interrupted and resumed.

But when --retry command is used, when the transfer speed is too slow, the size of partially downloaded file is reset to 0 and downloading restarts from the start, ignoring -C -.

Same for adding --no-remove-on-error:
curl --no-remove-on-error -y 30 -Y 30 --connect-timeout 10 --retry 10 -C - -x socks5h://localhost:9050 -e https://somesite.com/ -LORf https://somesite.com/images/[1-10].webp --no-remove-on-error

I expected the following

If connection times out, curl --retry -O -C - --speed-limit 10 ... should retain the partially downloaded file, the same way curl -O -C - --speed-limit 10 ... does

curl/libcurl version

curl 8.14.1 (x86_64-pc-linux-gnu) libcurl/8.14.1 OpenSSL/3.3.3 zlib/1.3.1 brotli/1.1.0 zstd/1.5.7 c-ares/1.34.4 libidn2/2.3.8 libpsl/0.21.5 libssh2/1.11.1 nghttp2/1.65.0 nghttp3/1.8.0 librtmp/2.3 OpenLDAP/2.6.8
Release-Date: 2025-06-04
Protocols: dict file ftp ftps gopher gophers http https imap imaps ipfs ipns ldap ldaps mqtt pop3 pop3s rtmp rtsp scp sftp smb smbs smtp smtps telnet tftp ws wss
Features: alt-svc AsynchDNS brotli GSS-API HSTS HTTP2 HTTP3 HTTPS-proxy HTTPSRR IDN IPv6 Kerberos Largefile libz NTLM PSL SPNEGO SSL threadsafe TLS-SRP UnixSockets zstd

operating system

Gentoo Linux
Linux jet 5.15.32-gentoo-r1 #14 SMP PREEMPT Sun Apr 20 22:35:48 MSK 2025 x86_64 AMD FX(tm)-8300 Eight-Core Processor AuthenticAMD GNU/Linux

Activity

  1. bagder commented on Jul 27, 2025

    @bagder
    Member

    I believe you found the TODO ltem --retry should resume

  2. bagder commented on Jul 28, 2025

    @bagder
    Member

    Hm, not exactly like the old TODO item...

  3. jay commented on Aug 6, 2025

    @jay
    Member

    Does #15333 work for you

  4. tkzv commented on Aug 11, 2025

    @tkzv
    Author

    Does #15333 work for you

    Sorry, @jay, I don't quite understand what you want me to do. Should I download a patched version of source code, compile it and try to reproduce this problem? Which commit do I need?

  5. jay commented on Aug 18, 2025

    @jay
    Member

    Sorry, @jay, I don't quite understand what you want me to do. Should I download a patched version of source code, compile it and try to reproduce this problem? Which commit do I need?

    Yes, my question is can you reproduce with that branch https://github.com/jay/curl/tree/better_auto_resume

  6. bagder commented on Sep 15, 2025

    @bagder
    Member

    I don't think we will get an answer.

    @jay, are you going to make another attempt at landing that fix?

  7. jay commented on Sep 17, 2025

    @jay
    Member

    @jay, are you going to make another attempt at landing that fix?

    Ok I will look at it again. I think it was done and I'm not sure why I never did anything with it.

  8. tkzv commented on Sep 19, 2025

    @tkzv
    Author

    Yes, my question is can you reproduce with that branch https://github.com/jay/curl/tree/better_auto_resume

    @jay , -C - --retry works correctly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions