Closed
Description
I did this
$ echo plop > robots.txt
$ curl --no-clobber -C 1 -O https://curl.se/robots.txt
The downloaded content is appended torobots.txt
file.
and
echo plop > important
curl --remove-on-error -C 1 -o important https://nonexisting.curl.se/
The file important
is removed.
I expected the following
Curl should likely report and error instead of behaving inconsistently, or the documentation should be improved to mention the behaviour in these scenarios.
curl/libcurl version
8.11.0
operating system
Any
Metadata
Metadata
Assignees
Type
Projects
Milestone
Relationships
Development
No branches or pull requests
Activity
bagder commentedon Dec 2, 2024
In the first case with
--no-clobber
and--continue-at
, what could the user possibly want to happen? Is there a legit use case there? Should we make it simple and just deny that option combination?icing commentedon Dec 2, 2024
Since these options are fairly new, I think denying it makes sense.
piru commentedon Dec 2, 2024
I think erroring out is the correct thing to do.
curl: --continue-at is mutually exclusive with --remove-on-error
curl: --continue-at is mutually exclusive with --no-clobber
curl: --continue-at is mutually exclusive with --no-clobber
curl: --continue-at is mutually exclusive with --remove-on-error