remote-header-name.d: mention that filename* is not supported

and that you can use --clobber to allow overwriting.

Ref: #10533
Closes #10555

Co-authored-by: Jay Satiro <raysatiro@yahoo.com>
This commit is contained in:
Daniel Stenberg 2023-02-18 10:18:57 +01:00
parent cffe301299
commit bf54c9382f
No known key found for this signature in database
GPG key ID: 5CC908FDB71E12C2

View file

@ -20,12 +20,15 @@ The file is saved in the current directory, or in the directory specified with
If the server specifies a file name and a file with that name already exists
in the destination directory, it will not be overwritten and an error will
occur. If the server does not specify a file name then this option has no
effect.
occur - unless you allow it by using the --clobber option. If the server does
not specify a file name then this option has no effect.
There's no attempt to decode %-sequences (yet) in the provided file name, so
this option may provide you with rather unexpected file names.
This feature uses the name from the "filename" field, it does not yet support
the "filename*" field (filenames with explicit character sets).
**WARNING**: Exercise judicious use of this option, especially on Windows. A
rogue server could send you the name of a DLL or other file that could be
loaded automatically by Windows or some third party software.