Buy commercial curl support from WolfSSL. 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
himself.
Re: --remote-header-name security?
- 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: Sun, 9 Jan 2022 11:16:59 +0100 (CET)
On Sat, 8 Jan 2022, Paul Gilmartin via curl-users wrote:
> or will curl download only to the current directory?
--remote-header-name will always trim off the remotely provided directory name
before it uses the file name.
It will save in current directory, or in the given --output-dir.
> Also, what's a good way of testing for --remote-header-name? I'm thinking:
> curl --remote-header-name --remote-name URL
> if $?==23 then curl --output tempname URL
That won't work. The --remote-name part will kick in if there's no
Content-Disposition header.
Date: Sun, 9 Jan 2022 11:16:59 +0100 (CET)
On Sat, 8 Jan 2022, Paul Gilmartin via curl-users wrote:
> or will curl download only to the current directory?
--remote-header-name will always trim off the remotely provided directory name
before it uses the file name.
It will save in current directory, or in the given --output-dir.
> Also, what's a good way of testing for --remote-header-name? I'm thinking:
> curl --remote-header-name --remote-name URL
> if $?==23 then curl --output tempname URL
That won't work. The --remote-name part will kick in if there's no
Content-Disposition header.
-- / daniel.haxx.se | Commercial curl support up to 24x7 is available! | Private help, bug fixes, support, ports, new features | https://curl.se/support.html -- Unsubscribe: https://lists.haxx.se/listinfo/curl-users Etiquette: https://curl.haxx.se/mail/etiquette.htmlReceived on 2022-01-09