In reqwest, when username/password is provided in url, it seems to use basic authentication. Something like this:
http://user:pass@host:port/path
My idea was to use .send_with_digest_authentication() using such an url, that way the authentication method would be "automatic":
If endpoint was basic, then first response would be OK
If endpoint was digest, then second request should do it
Problem is, reqwest seems to fallback to basic auth because of the user/pass in the url. I tried to patch diqwest in a fork to make sure username/pass are removed for the second request, but it seems that there is no way to access the url from RequestBuilder.
I don't know if solving this issue is in the scope of this crate, but an automatic authentication process would be a nice to have. Maybe there is another approach?
In reqwest, when username/password is provided in url, it seems to use basic authentication. Something like this:
My idea was to use
.send_with_digest_authentication()
using such an url, that way the authentication method would be "automatic":Problem is, reqwest seems to fallback to basic auth because of the user/pass in the url. I tried to patch diqwest in a fork to make sure username/pass are removed for the second request, but it seems that there is no way to access the url from RequestBuilder.The only way that I can think of this working, is thatresponse
from RequestBuilder::build is used. But that needs access to Client::execute.I don't know if solving this issue is in the scope of this crate, but an automatic authentication process would be a nice to have. Maybe there is another approach?