Is your feature request related to a problem?
Add support for passing custom request headers from the CLI, including common cases like bearer tokens, cookies, referer, and user-agent. This would allow downloading from authenticated or anti-hotlink-protected endpoints.
Describe the Solution
In the CLI, we should be able to pass headers while downloading files using
--headers keyword argument. We can pass all headers as either JSON string or
comma separated key:value pair.
Describe Alternatives
A clear and concise description of any alternative solutions or features you've considered.
How should it look in the CLI?
With Headers
furl https://example.com -h "{\"Authorization\": \"Bearer XXXXXX\"}"With Username and password
furl https://example.com -u "username:password"
Additional Context
Add any other context or screenshots about the feature request here.
Is your feature request related to a problem?
Add support for passing custom request headers from the CLI, including common cases like bearer tokens, cookies, referer, and user-agent. This would allow downloading from authenticated or anti-hotlink-protected endpoints.
Describe the Solution
In the CLI, we should be able to pass headers while downloading files using
--headerskeyword argument. We can pass all headers as either JSON string orcomma separated key:value pair.
Describe Alternatives
A clear and concise description of any alternative solutions or features you've considered.
How should it look in the CLI?
With Headers
furl https://example.com -h "{\"Authorization\": \"Bearer XXXXXX\"}"With Username and password
furl https://example.com -u "username:password"Additional Context
Add any other context or screenshots about the feature request here.