offshoreoffline.blogg.se

1. PROFILE FOR MACOS MAC OS X BLOCK INCOGNITO CHROME UPDATE
2. PROFILE FOR MACOS MAC OS X BLOCK INCOGNITO CHROME FULL

Per David Amey's answer, it is still necessary to specify -user-data-dir= for Chrome to respect the -disable-web-security option.

PROFILE FOR MACOS MAC OS X BLOCK INCOGNITO CHROME FULL

On MacOS, the full command becomes: open -na Google\ Chrome -args -user-data-dir= -disable-web-security -disable-site-isolation-trials In Chrome 67+, it is necessary to pass the -disable-site-isolation-trials flag alongside arguments -user-data-dir= and -disable-web-security to truly disable web security. 0, which properly disables web security with these flags. It is unclear when the Chromium codebase regressed, but downloading an older build of Chromium (following "Not-so-easy steps" on the Chromium download page) is the only workaround I found. Thanks to for the Chrome 81 tip in the comments.Īs of Chrome 80 (possibly even earlier), the combination of flags -user-data-dir=/tmp/some-path -disable-web-security -disable-site-isolation-trials no longer disables web security. See -user-data-dir= vs -user-data-dir=/some/path for more details below. (Speculation) It is likely that Chrome requires a non-empty profile path to mitigate the high security risk of launching the browser with web security disabled on the default profile.

# Windows (from "Run" dialog or start menu in Windows 8+)Ĭhrome.exe -user-data-dir=%TMP%\temporary-chrome-profile-dir -disable-web-security -disable-site-isolation-trials Open -na Google\ Chrome -args -user-data-dir=/tmp/temporary-chrome-profile-dir -disable-web-security -disable-site-isolation-trials

PROFILE FOR MACOS MAC OS X BLOCK INCOGNITO CHROME UPDATE

Update Īs of Chrome 81, it is mandatory to pass both -disable-site-isolation-trials and a non-empty profile path via -user-data-dir in order for -disable-web-security to take effect: # MacOS (in Terminal) To test whether you've successfully launched Chrome with web security disabled, run the snippet in Web Security Test at the bottom of this post. (Some of the arguments are not formally supported by Chrome, as it will warn you.) As of Chrome 95, on MacOS and Windows, -disable-site-isolation-trials remains a required flag in order to disable web security, so the command-line arguments to Chrome seen below are still valid.