commit | 5df53e057eec8f9dd6ae8e9feb05d7c9b259b527 | [log] [tgz] |
---|---|---|
author | kenoss <kenoss@chromium.org> | Mon Jun 17 06:59:52 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Jun 17 06:59:52 2024 |
tree | a2d5cd8466b8d05490053556f1ca12e9d7f3ba7e | |
parent | 865aca6c93b13c4387841eddb9af834afa7b6b95 [diff] |
PrerenderFallback: Use Sec-Purpose header value "prefetch;prerender" This CL makes that prefetch uses a HTTP request header "Sec-Purpose: prefetch;prerender" for prefetch ahead of prerender. Note that "Purpose" header is unchanged. For more details, see https://github.com/WICG/nav-speculation/issues/133#issuecomment-1035315997 In addition, this CL makes prefetch not eligible if it's ahead of prerender and cross-origin, so that we ensure that Chrome doesn't send a request with "Sec-Purpose: prefetch;anonymous-client-ip;prerender" as it is not in the spec yet. No behavioral change if kPrerender2Fallback is disabled. NO_IFTTT=Wrote //tools/metrics/histograms/enums.xml entry and I will do https://docs.google.com/document/d/1PnrfowsZMt62PX1EvvTp2Nqs3ji1zrklrAEe1JYbkTk Fexed: 342539088 Change-Id: I6ea9461a0a6fc20d990e65e746431dc5287fdfb5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5580112 Reviewed-by: Alex Moshchuk <alexmos@chromium.org> Reviewed-by: Lingqi Chi <lingqi@chromium.org> Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org> Reviewed-by: Ryan Sturm <ryansturm@chromium.org> Commit-Queue: Ken Okada <kenoss@chromium.org> Cr-Commit-Position: refs/heads/main@{#1315672}
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.