Re: [whatwg/fetch] Block subresource requests whose URLs include credentials. (#465)

What about the case when receiving error/challenge 401 with (WWW-Authenticate: Basic realm=...) for a URL for which the browser already has the credentials cached.
May be I am wrong, but I think that Chrome is using the same erroneous approach when having the cached credentials - instead of putting the Authorisation header in the GET retry after 401 with the cached credentials (base64 encoded), it is composing a new URL with the credentials exposed in it.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/pull/465#issuecomment-296736518