fix: disable CORS when webSecurity is disabled#25463
Conversation
|
Release Notes Persisted
|
|
I have automatically backported this PR to "10-x-y", please check out #25503 |
|
I have automatically backported this PR to "11-x-y", please check out #25504 |
|
I have automatically backported this PR to "9-x-y", please check out #25505 |
|
mark |
|
I saw this PR has been merged to Electron 11.x, but have not been existed on any of Electron 10 release notes. I tested the related issue on Electron 10.2.0, it still persists. Also tried Electron 11, it did fix the issue. |
|
I just found 10.1.3 has addressed this issue in its release note, but I can still reproduce it. Not clear why. |
|
I had issues with an older version where cors wasn't being disabled by setting websecurity to false. |
|
@vrunhofen please open a new issue with a standalone test case, preferably using Electron Fiddle. Thanks! |
issue was fixed in electron/electron#25463 it will now be disabled when with webSecurity: false
issue was fixed in electron/electron#25463 it will now be disabled when with webSecurity: false
Description of Change
Close #23664.
Chromium has moved some web security controls from blink to browser, this PR updates our code to also disable web security in browser.
Checklist
npm testpassesRelease Notes
Notes: Fix CORS not being disabled by
webSecurity: false.