5

I want to debug a local dev environment issue potentially caused by CORB in Chrome 74. I want to see if - when I swith off CORB - the issue goes away.

The according Google developer docs say that

You can confirm if a problem is due to CORB by temporarily disabling it, by starting Chrome with the following command line flag: --disable-features=CrossSiteDocumentBlockingAlways,CrossSiteDocumentBlockingIfIsolating

However, if I run 

"C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --disable-features=CrossSiteDocumentBlockingAlways,CrossSiteDocumentBlockingIfIsolating --user-data-dir="C:/ChromeDevSession"

Chrome still shows CORB warnings and blocks according requests.

sideshowbarker
  • 81,827
  • 26
  • 193
  • 197
Robert
  • 1,710
  • 2
  • 18
  • 35

1 Answers1

3

If you take a look at mentioned in the docs feature tracking page you will find link to tracking bug. The last commit in that bug actually refers to revision where this feature is enabled by default and is no more controlled from outside through command line (at least using mentioned in the question flags).

But there is interesting piece of code added : 

  // --disable-web-security also disables Cross-Origin Read Blocking (CORB).
  if (base::CommandLine::ForCurrentProcess()->HasSwitch(
          switches::kDisableWebSecurity)) {
    params->is_corb_enabled = false;
    return;
  }

Hopefully in 74 version it still exist. So if you OK with all consequences just add --disable-web-security instead.

By the way in latest sources you will not find it anymore. So with never version of chromium you will not be able to disable it.

j2ko
  • 2,479
  • 1
  • 16
  • 29