Skip to content

Support --remote-header-name to make automatic filename smarter #93

@injust

Description

@injust

wcurl's automatic filename functionality is nice, but it doesn't work well with some URLs like /foo.php?download=... that send a Content-Disposition header in the response. This results in a file named foo.php.

Currently, passing --curl-options=--remote-header-name is a no-op, presumably because --remote-header/--remote-header-all wasn't passed to curl.

But if you pass --curl-options=--remote-header-name --curl-options=--remote-name-all, the Content-Disposition header isn't used and you get this warning:

Warning: Got more output options than URLs

This is (kind of?) a sub-issue of #59.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions