commit | c7f62ad3eb82ab8c11bb333600cd3feac9eb11a9 | [log] [tgz] |
---|---|---|
author | Adam Rice <ricea@chromium.org> | Thu Jan 16 08:22:50 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Jan 16 08:22:50 2025 |
tree | 62a2724de5317ecda6c33a94c6251752a3bdd039 | |
parent | 74674436b6862a0877c9997fee6d3889bb7d5154 [diff] |
Implement No-Vary-Search in-memory store Implement net::NoVarySearchCache, an in-memory mapping from URLs that will be looked up in the cache to previously-fetched URLs that are equivalent under the rules of No-Vary-Search (see https://httpwg.org/http-extensions/draft-ietf-httpbis-no-vary-search.html). This will be used to add No-Vary-Search support to net::HttpCache::Transaction in a future CL. This version does not yet support persistence of the cache to disk. That will be implemented in a future version. NoVarySearchCache will be owned by HttpCache, so there will be one instance per URLRequestContext. The object will be created when a Profile is created, and exist until it is destroyed (usually browser shutdown). See the design doc at https://docs.google.com/document/d/1RS3q6qZ7-k9CvZsDYseGOXzcdQ9fGZ6YYnaW7fTPu7A/edit. BUG=382394774 BYPASS_LARGE_CHANGE_WARNING=It is what it is NO_IFTTT=I did change enums.xml but it complains anyway. Change-Id: Ief53f1b4fd1f94366b3d719635d8b4fc553da5fd Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6088312 Commit-Queue: Adam Rice <ricea@chromium.org> Reviewed-by: Takashi Toyoshima <toyoshim@chromium.org> Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org> Auto-Submit: Adam Rice <ricea@chromium.org> Reviewed-by: Kenichi Ishibashi <bashi@chromium.org> Cr-Commit-Position: refs/heads/main@{#1407159}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.