Closed yschimke closed 4 years ago
Awkwardly it seems to be also how BasicAuthenticator knows which type to authenticate (proxy/WWW). Could this be avoided by using builder.proxyAuthenticator as well as builder.authenticator?
you are correct and it could but it would require a more complex setup. Need to think about it. Do you have a specific case where this causes a problem?
Yep - I'll link to it when it's landed. I'm getting it working without Caching, implementing my own BasicAuthenticator for now. Probably Kerberos next.
Essentially this hit whenever you want to use your nice library as part of another one. Unless you are the end user, it's hard to know whether it will need basic auth for both proxy and WWW together.
any updates? Otherwise I would like to close this.
Close away. No updates. Sorry
Seems like two concurrent requests could get confused