Use a scoped handle instead of UnguessageToken in NetworkContext::SaveHttpAuthCache |
|
Issue descriptionNetworkContext::Save/LoadHttpAuthCache currently use an UnguessableToken to identify the saved HttpAuthCache contents. If a client calls SaveHttpAuthCache without a corresponding LoadHttpAuthCache, the cache contents will leak. We should figure out a way to return a scoped handle that will notify the network service when it goes out of scope to prevent possible leaks. See the comments on crrev.com/c/1366877. |
|
►
Sign in to add a comment |
|