-
Notifications
You must be signed in to change notification settings - Fork 6.9k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Don't serve in-memory cached responses when NIK is transient
The following two NIKs, one is non-transient and the other is transient, will generate the same cache key: * NetworkIsolationKey("foo", "foo", <no nonce>) * NetworkIsolationKey("foo", "foo", <some nonce>) The in-memory cache should distinguish them. Don't serve responses from the in-memory cache when the request's NIK is transient. Bug: 1339708 Change-Id: Idd24ae6d30a9c11692f0ecab99ff2d095ee853c1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3758298 Commit-Queue: Kenichi Ishibashi <bashi@chromium.org> Reviewed-by: Matt Menke <mmenke@chromium.org> Cr-Commit-Position: refs/heads/main@{#1024125}
- Loading branch information
Showing
3 changed files
with
28 additions
and
4 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters