Does BasicAuthenticator.proxy cause a concurrency bug?

Question

Does BasicAuthenticator.proxy cause a concurrency bug?

Closed this issue 4 years ago · 5 comments

Seems like two concurrent requests could get confused

Answer 1 · 2018-09-01T09:05:14.000Z

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?

Answer 2 · 2018-09-02T10:27:46.000Z

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?

Answer 3 · 2018-09-02T16:41:44.000Z

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.

Answer 4 · 2020-03-12T19:57:30.000Z

any updates? Otherwise I would like to close this.

Answer 5 · 2020-03-12T21:12:56.000Z

Close away. No updates. Sorry