Closed edmonds closed 2 years ago
Hi @edmonds,
something is off with my notifications. I did not get a message when you opened this issue (3 months ago 🤦🏾♀️). Just stumbled upon it by accident. So sorry for my late reply.
I was looking into your issue and it seems you are totally right. First I looked it up in the ietf rfc7616 where I read the Effective Request URI
(see here) differently. But then I googled some examples and looked into the implementation of the underlying crate digest_auth
and saw this. It clearly states that it is without domain and should start with a slash.
Took care here and already published to crates.io.
Thanks for reporting it! 👋🏾
Hi,
I was not able to get
diqwest
to successfully work against an embedded device with an HTTP server that requires digest authentication. I was able to get it to work withcurl --digest
, so I compared the requests generated by curl vs. those generated by reqwest+diqwest.It turns out curl generates an Authorization header that looks like:
while reqwest+diqwest generates an Authorization header that looks like:
I was able to get diqwest to generate an Authorization header closer to what curl generates with something like this:
Is this a bug in diqwest?
Thanks!