You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to move `Sec-Fetch-Mode` into the network service to ensure
that it's consistently set every time `Sec-Fetch-Site` is set, this
patch does a few things:
1. Based on the conversation in [1] and [2], this patch extends
`network::mojom::RequestMode` to include two new values to
represent nested navigations and object/embed navigations as
distinct from main-frame navigations.
2. It introduces a new `network::IsNavigationRequestMode()` function
to replace direct comparisons to `kNavigate` in various parts of
the codebase.
3. It refactors `network::SetSecFetchSiteHeader()` into
`network::SetFetchMetadataHeaders()`. This creates a single entry
point from `URLLoader` to set all Fetch Metadata headers, and
fleshes out the `Sec-Fetch-Mode` header.
[1]: w3c/webappsec-fetch-metadata#37
[2]: whatwg/fetch#755
Bug: 972263, 990864
Change-Id: Icd20c7640d3d08ecb34a739f0203140fdcc195d5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1780725
Reviewed-by: Kinuko Yasuda <[email protected]>
Reviewed-by: Łukasz Anforowicz <[email protected]>
Commit-Queue: Mike West <[email protected]>
Cr-Commit-Position: refs/heads/master@{#693517}
0 commit comments