|request_initiator_site_lock| enforcement - attempt #1.
This CL starts treating |request_initiator| that doesn't match |request_initiator_site_lock| as a bad IPC message and ignoring such malformed resource requests. NetworkService.URLLoader.RequestInitiatorOriginLockCompatibility UMA is non-zero in recent Canary releases. We expect that this CL will get reverted after gathering sufficient number of DumpWithoutCrashing reports to understand why the lock doesn't match the initiator in some real world scenarios. Bug: 920634 Change-Id: I509ebade1d64e5c5243150df8c3f5184273cf8ac Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1661114 Commit-Queue: Łukasz Anforowicz <lukasza@chromium.org> Reviewed-by:Yutaka Hirano <yhirano@chromium.org> Cr-Commit-Position: refs/heads/master@{#717031}
Showing
Please register or sign in to comment