We have an Angular interceptor to obtain our access tokens. We might fire numerous http requests that need an access token.
I've noticed the library handles this in that it only issues one access token request and tells the others to wait which is great. But it still fires multiple requests for the OpenID configuration.
Is that expected? Seems wasteful...

@spottedmahn We are tracking this issue after our 1.0.0 release.
@spottedmahn Is this still an issue?
no clue, sorry, not doing B2C stuff these days
@spottedmahn @RobARichardson We reviewed this as a team and found that these request responses are being served from the browser cache, not making network calls. Can you please verify the Size column and see if this is the case? It should say (disk cache) in the Size field for the relevant requests.
Closing this as we did not get a response. As mentioned above the responses are being served from the browser cache and should not have a performance impact.
Most helpful comment
@spottedmahn We are tracking this issue after our 1.0.0 release.