Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Bug 1658587 [wpt PR 24957] - |request_initiator_site_lock = <opaque>|…
… for the process-wide factory., a=testonly Automatic update from web-platform-tests |request_initiator_site_lock = <opaque>| for the process-wide factory. The CL modifies URLLoaderFactoryParamsHelper::CreateForRendererProcess so that it sets |request_initiator_site_lock| of the process-wide factory to an opaque origin. This change is based on https://crbug.com/1105794 which shows that there are indeed no cases in the wild where a process-wide factory is used with a non-opaque initiator origin. This intuitively makes sense - the process-wide factory should only be used in frames that have not yet committed any navigation and such frame should not (yet) have a non-opaque origin. Additionally, thanks to the change described above, there is no longer a need for site/eTLD+1 comparisons in VerifyRequestInitiatorLock nor for SiteInstanceImpl::GetRequestInitiatorSiteLock. Fixed: 1098938 Change-Id: I9e8b53139a2418636c84e783f86ea8d7be34eed9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2274591 Reviewed-by: Kinuko Yasuda <kinuko@chromium.org> Commit-Queue: Łukasz Anforowicz <lukasza@chromium.org> Cr-Commit-Position: refs/heads/master@{#797542} -- wpt-commits: e9e85e67994df01673a8eb55c47d1b6f5eb6c18a wpt-pr: 24957
- Loading branch information