Andre,
--header 'Content-type: foo/bar' doesn't work as intended because
'Content-type: application/x-www-form-urlencoded' is still added too. So
both headers are sent, which breaks my use case.
Yes, you are right and I described the behaviour in a comment. The
headers overriding doesn't work in
On 22/06/2022 12:26, Sergey Ponomarev wrote:
Hi Andre and Jo-Philipp,
Please add the calloc() error handler yourself because I'm not
experienced in C and I haven't time. But for you this may be just 5
minutes.
Sure, I had a look, and while adding that wrapper isn't a problem, the
patchset its
Hi Andre and Jo-Philipp,
Please add the calloc() error handler yourself because I'm not
experienced in C and I haven't time. But for you this may be just 5
minutes.
The feature is very important from my point of view. The first version
I sent a year(s?) ago but still no progress.
If there are any
Hi Sergey,
any update on this series? I'd be interested in the --header option.
Thanks,
Andre
On 10/05/2022 11:11, Jo-Philipp Wich wrote:
Hi Sergey,
a minor nitpick inline below.
On 5/9/22 11:59 PM, Sergey Ponomarev wrote:
You can add a custom HTTP header(s) to request:
wget --header=
Hi Sergey,
a minor nitpick inline below.
On 5/9/22 11:59 PM, Sergey Ponomarev wrote:
> You can add a custom HTTP header(s) to request:
>
> wget --header='Authorization: Bearer TOKEN' \
> --header='If-Modified-Since: Wed, 9 May 2021 12:16:00 GMT' \
> https://example.com/
>
>
You can add a custom HTTP header(s) to request:
wget --header='Authorization: Bearer TOKEN' \
--header='If-Modified-Since: Wed, 9 May 2021 12:16:00 GMT' \
https://example.com/
Some headers like Authorization or User-Agent may be already set by --password
or --user-agent.
We m
