Revert "|request_initiator_site_lock| enforcement - attempt #2."
This reverts commit 0724e945. Reason for revert: https://crbug.com/1056949 (RBS) and https://crbug.com/1059218 Original change's description: > |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} TBR=yhirano@chromium.org,lukasza@chromium.org # Not skipping CQ checks because original CL landed > 1 day ago. Bug: 920634 Change-Id: Ief1019a74abf8e70364ad2f6aadc2d2216488910 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2108783Reviewed-by:Łukasz Anforowicz <lukasza@chromium.org> Commit-Queue: Łukasz Anforowicz <lukasza@chromium.org> Cr-Commit-Position: refs/heads/master@{#751470}
Showing
Please register or sign in to comment