New issue
Advanced search Search tips

Issue 870225 link

Starred by 1 user
Status: Duplicate
Merged: issue 844178
Owner: ----
Closed: Aug 2
Cc:
wfh@chromium.org
creis@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Cross-Origin Read Blocking (CORB) blocked cross-origin response

Reported by jai...@arcsncurves.com, Aug 2 
<b>Chrome Version       : <Copy from: 'about:version'></b>
URLs (if applicable) : https://www.businessxb.com
Other browsers tested: Version 68.0.3440.84 (Official Build) (64-bit)
  Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
     Safari:
    Firefox:
       Edge:

What steps will reproduce the problem?

(1)  Cross-Origin Read Blocking (CORB) blocked cross-origin response https://www.google.com/ads/measurement/l?ebcid=ALh7CaRU9hF_pAmM357BOR3bnzwQbP37RSWJxtJlGA5yOp_gCfuIy3cJlmNA-9fHzTITcHVl_xCAhSjwSmECoJehvu7WYapHfA with MIME type text/html. See https://www.chromestatus.com/feature/5629709824032768 for more details.

(2)Cross-Origin Read Blocking (CORB) blocked cross-origin response https://securepubads.g.doubleclick.net/pcs/view?xai=AKAOjst22xNhvDIOFQslWWM8GvYPF8aJc6sMKQ81X2-ufiSEHOpO_M-m4XKmyBpVkz2qLYHuX51V88-k0iaBPEXZnmWnLVIX7NFHGTghdWNik7FdU8GC9ULOkQ41fqRu9gdT5v5qR38AAzIWWegQ27dr2tFbEtZJgmwz767O5v3LC7D8mKhJF4NfHyAUNeNs1MJxbi9TQB2QH3spVq87RIeX4glLbny9HygIkweRxuyqGmvFnsS88clZ8WyAdUCLDYK1KCHVot2xi-PY&sai=AMfl-YQLM3AloI4gLOqy33rbocC3ptKggzuIsAIxps5s81XjMDwY3BkwpWC2Y8T5RJin61ojwH9Ky9bpFvMy1ScxQojGdhkbGrTdP64mxVsJunSejiHoJBonZk4Hie0&sig=Cg0ArKJSzEWDQBdVYxPxEAE&adurl= with MIME type text/html. See https://www.chromestatus.com/feature/5629709824032768 for more details.

(3) if refresh the page increase the warings.

What is the expected result?

How avoid these warnings?. How important these warnings?


What happens instead?


Please provide any additional information below. Attach a screenshot if
possible.
warnings.gif
71.0 KB View Download

Comment 1 by lukasza@chromium.org, Aug 2

Mergedinto: 844178
Status: Duplicate (was: Unconfirmed)
RE: How to avoid these warnings?

Wait for Chrome 69 (which is tentatively scheduled to reach the Stable channel around September the 4th) or upgrade to Chrome 69 (e.g. which is available on the Beta channel - see https://www.google.com/chrome/beta/).


RE: How important are these warnings?

The 2 warnings in this bug can be ignored - see the explanation below.

I've looked at the 2 reported URLs.  The first URL (https://www.google.com/ads/measurement/...) returns an empty  204 http response.  The second one ( https://securepubads.g.doubleclick.net/pcs/...) returns a http response with no body (and with "content-length: 0").

In both cases blocking of the response by CORB is a no-op (well, almost - some response headers are still stripped by CORB).  Chrome 69 won't emit the CORB message to the DevTools console in this situation - see  issue 844178 .


Given above, let me resolve the bug as a duplicate of  issue 844178
►

Sign in to add a comment