summaryrefslogtreecommitdiff
path: root/docs/cmdline-opts/remote-header-name.md
blob: 88c2808a3fecd6b4cce05b590e3ff4ea3fbb5764 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
---
c: Copyright (C) Daniel Stenberg, <daniel@haxx.se>, et al.
SPDX-License-Identifier: curl
Long: remote-header-name
Short: J
Protocols: HTTP
Help: Use the header-provided filename
Category: output
Added: 7.20.0
Multi: boolean
See-also:
  - remote-name
Example:
  - -OJ https://example.com/file
---

# `--remote-header-name`

Tell the --remote-name option to use the server-specified Content-Disposition
filename instead of extracting a filename from the URL. If the server-provided
filename contains a path, that is stripped off before the filename is used.

The file is saved in the current directory, or in the directory specified with
--output-dir.

If the server specifies a filename and a file with that name already exists in
the destination directory, it is not overwritten and an error occurs - unless
you allow it by using the --clobber option. If the server does not specify a
filename then this option has no effect.

There is no attempt to decode %-sequences (yet) in the provided filename, so
this option may provide you with rather unexpected filenames.

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.