e3e480e63a
This CL breaks-out two additional special-cases out of the old kIncorrectLock category: - kExcludedScheme will be used for chrome-extension, since non-allowlisted extensions will use an incompatible request_initiator until https://crbug.com/940068 is fixed. - kExcludedUniversalAccessPlugin will be used for requests from renderers which are embedding a universal-access plugin (like Flash) - the renderer is proxying requests on behalf of the (potentially cross-origin = request_initiator-incompatible) plugin. The CL adds or modifies tests, so that if we started to treat an incorrect lock as a bad message, then the tests would fail without the additional exceptions outlined above. Bug: 920634 Change-Id: I93f14a43d6569c010898a662c250d2bda0613fca Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1762677 Commit-Queue: Łukasz Anforowicz <lukasza@chromium.org> Reviewed-by: Nasko Oskov <nasko@chromium.org> Reviewed-by: Bill Budge <bbudge@chromium.org> Reviewed-by: Maks Orlovich <morlovich@chromium.org> Reviewed-by: Devlin <rdevlin.cronin@chromium.org> Reviewed-by: Yutaka Hirano <yhirano@chromium.org> Reviewed-by: Alex Moshchuk <alexmos@chromium.org> Cr-Commit-Position: refs/heads/master@{#691013}