Can no longer disable localhost restrictions for AJAX requests to a server using CORS

730 views
Skip to first unread message

glenn....@avaxa.com

unread,
May 11, 2018, 5:29:22 AM5/11/18
to Chromium-discuss
Chrome Version       : 66.0.3359.170 (Official Build) (64-bit)

Prior to version 66, I have been running Chrome in my development environment with the '--disable-web-security' switch to allow me to successfully connect my web application, running on http://localhost:8100 with a web service server running on the same PC using HTTPS and the hostname of the server. 

Since version 66 this no longer works. I believe the new Site Isolation feature is now getting in the way.

The connections are successful if I opt out of the site isolation trial with the following switch: chrome://flags/#site-isolation-trial-opt-out

However, I need a command line equivalent of this in my development environment (Visual Studio Code using the Debugger for Chrome add-in) and I can't find one so that I don't have to opt-out manually every time I start the web app.

Any help is much appreciated. This is a critical development workflow that is now making debugging of our web apps and PWA apps very difficult.






PhistucK

unread,
May 11, 2018, 5:32:55 AM5/11/18
to glenn....@avaxa.com, Chromium-discuss
If you go to about:version, it has a "Command Line" field that shows what about:flags adds ("--flag-switches-begin --enable-devtools-experiments --enable-experimental-web-platform-features --flag-switches-end").

Also, site isolation should not prevent network access. Is this a JavaScript access? If not -
You can search crbug.com for an existing issue and star it. If you cannot find one, file a new issue using the "New issue" link on the same page.
Please, do not add a "+1" or "Me too" or "Confirmed" (or similar) comment. It just wastes the time of Chrome engineers and sends unnecessary e-mails to all of the people who starred the issue.

You can reply with a link to the found or created issue and might get triaged (and fixed) faster.

Thank you.


PhistucK


--
--
Chromium Discussion mailing list: chromium...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-discuss

---
You received this message because you are subscribed to the Google Groups "Chromium-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-discu...@chromium.org.

John Vilk

unread,
Jun 10, 2018, 2:57:21 AM6/10/18
to Chromium-discuss, glenn....@avaxa.com
I had this same exact problem, and thankfully found this mailing list email! I found a workaround; add the following command line arguments to Chrome:

--disable-features=CrossSiteDocumentBlockingAlways,CrossSiteDocumentBlockingIfIsolating

I found this command line argument documented on the wiki page for site isolation: https://www.chromium.org/Home/chromium-security/site-isolation

I've documented this workaround at the following bug report that someone else has filed, so please star if you want it fixed: https://bugs.chromium.org/p/chromium/issues/detail?id=849708

John

Jingxue Tang

unread,
May 15, 2019, 4:51:47 AM5/15/19
to Chromium-discuss, glenn....@avaxa.com
Can I ask where can I add this command line arguments: --disable-features=CrossSiteDocumentBlockingAlways,CrossSiteDocumentBlockingIfIsolating
Reply all
Reply to author
Forward
0 new messages