|request_initiator_site_lock| enforcement - attempt #2.
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. Therefore it is possible 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: If4fbdb6336703f53784c036ca5d9e408ff223d78 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2006113 Auto-Submit: Łukasz Anforowicz <lukasza@chromium.org> Commit-Queue: Yutaka Hirano <yhirano@chromium.org> Reviewed-by:Yutaka Hirano <yhirano@chromium.org> Cr-Commit-Position: refs/heads/master@{#739359}
Showing
Please register or sign in to comment