commit cfcea24df99ff6ecfc7a6477ecaf013475bb6bf3
author Xiaochen Zhou <xiaochenzh@chromium.org> Tue Jul 30 20:46:55 2024
committer Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> Tue Jul 30 20:46:55 2024
tree 21f0745ac47d1f74ee3e5f94106a7b9d78fa7908
parent 0cc2f20c21606899ebb2af331d1f3988994745eb

Fenced frames: Disable preload when network is revoked

Fenced frames(FF) can disable network access by invoking FF API:
window.fence.disableUntrustedNetwork().

After the network access is revoked, no preload requests are
allowed from FF.

There are two triggers for preload requests:

1. Via a response header, for example:
Link: </main.js>; rel="preload"; as="script"

2. From a link element, for example:
<link rel="preload" href="/main.js" as="script"/>

The first case has already been disabled for FF, regardless of FF's
network status. See crrev.com/c/3468236.

The second case is taken care of by the existing network status checks
in CorsURLLoaderFactory. This CL adds tests to verify this.

See: https://github.com/WICG/fenced-frame/blob/master/explainer/fenced_frames_with_local_unpartitioned_data_access.md#revoking-network-access

Bug: 1515599
Change-Id: I19f0d74e682a28bae56d2a5bf12e96b9c5e796e4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5749322
Commit-Queue: Xiaochen Zhou <xiaochenzh@chromium.org>
Reviewed-by: Garrett Tanzer <gtanzer@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1335078}