You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
User gives authenticated url. Something like this: http://user:pass@host:port/path
If request is submitted with such an Url with reqwest, it will automatically form the "Authorization" header, assuming it's basic authentication.
The idea is to be able to "automatically detect" if it is basic auth or digest auth.
In order to implement this, send_with_digest_auth() could remove any previous "Authorization" headers set. But I'm not sure if this is possible. Maybe reqwest adds the header after send_with_digest_auth() acts.
Is this even something that diqwest should handle?
Maybe this issue can be brought to reqwest itself?
The text was updated successfully, but these errors were encountered:
I have the following use-case:
User gives authenticated url. Something like this:
http://user:pass@host:port/path
If request is submitted with such an Url with reqwest, it will automatically form the "Authorization" header, assuming it's basic authentication.
The idea is to be able to "automatically detect" if it is basic auth or digest auth.
In order to implement this,
send_with_digest_auth()
could remove any previous "Authorization" headers set. But I'm not sure if this is possible. Maybe reqwest adds the header aftersend_with_digest_auth()
acts.Is this even something that diqwest should handle?
Maybe this issue can be brought to reqwest itself?
The text was updated successfully, but these errors were encountered: