Buy commercial curl support. 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 Daniel himself.
Re: cURL problems (by design?) (fwd)
- 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: Wed, 2 Sep 2026 09:42:46 +0200 (CEST)
On Wed, 2 Sep 2026, Daniel Stenberg via curl-users wrote:
> cURL -s --no-clobber -O "<path>"
>
> - the option is limited to 100 files.
I propose we extend this and try all the way up to 9999:
https://github.com/curl/curl/pull/22784
> - the 100 output files are (in this particular case): " default.jpg " to "
> default.jpg .99 ".
> Which is nice, as it avoids the above mentioned overriding, but... why
> doesn't cURL do so in a more practical way?
I propose that we inject the number into the target file name for --no-clobber
before the extension:
https://github.com/curl/curl/pull/22787
Date: Wed, 2 Sep 2026 09:42:46 +0200 (CEST)
On Wed, 2 Sep 2026, Daniel Stenberg via curl-users wrote:
> cURL -s --no-clobber -O "<path>"
>
> - the option is limited to 100 files.
I propose we extend this and try all the way up to 9999:
https://github.com/curl/curl/pull/22784
> - the 100 output files are (in this particular case): " default.jpg " to "
> default.jpg .99 ".
> Which is nice, as it avoids the above mentioned overriding, but... why
> doesn't cURL do so in a more practical way?
I propose that we inject the number into the target file name for --no-clobber
before the extension:
https://github.com/curl/curl/pull/22787
-- / daniel.haxx.se || https://rock-solid.curl.dev -- Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-users Etiquette: https://curl.se/mail/etiquette.htmlReceived on 2026-09-02