Issue metadata
Sign in to add a comment
|
CORB blocked cross-origin error in Website with Google Adsense Ads
Reported by
erwinban...@gmail.com,
Jun 30 2018
|
||||||||||||||||||||||||
Issue descriptionChrome Version : 67.0.3396.99 (Official Build) (64-bit) URLs (if applicable) : https://www.yugatech.com/ Other browsers tested: Add OK or FAIL, along with the version, after other browsers where you have tested this issue: Safari: OK Firefox: OK Edge: OK What steps will reproduce the problem? (1) Going to any website with Google Adsense, example: https://www.yugatech.com/ (2) When going to Developer Console tab, the CORB blocked cross-origin error shows. (3) This is the error: Cross-Origin Read Blocking (CORB) blocked cross-origin response https://www.google.com/ads/measurement/l?ebcid=ALh7CaQrFx0ApdRwIHCe5IfRBZ2bioYyL_97IhJz6vlavazDovYNoUGuHKIeeB0SaKDL8GLfJNrXNSGHcJ2h7Rpd7Ee0wChkrA with MIME type text/html. See https://www.chromestatus.com/feature/5629709824032768 for more details. What is the expected result? There should be no error, and contents from adsense should not be blocked. What happens instead? It shows CORB blocked cross-origin error every-time when going to a website.. The error is: Cross-Origin Read Blocking (CORB) blocked cross-origin response https://www.google.com/ads/measurement/l?ebcid=ALh7CaQrFx0ApdRwIHCe5IfRBZ2bioYyL_97IhJz6vlavazDovYNoUGuHKIeeB0SaKDL8GLfJNrXNSGHcJ2h7Rpd7Ee0wChkrA with MIME type text/html. See https://www.chromestatus.com/feature/5629709824032768 for more details. Please provide any additional information below. Attach a screenshot if possible.
,
Jul 1
Looking at the response headers from https://www.google.com/ads/measurement/l?ebcid=ALh7CaQrFx0ApdRwIHCe5IfRBZ2bioYyL_97IhJz6vlavazDovYNoUGuHKIeeB0SaKDL8GLfJNrXNSGHcJ2h7Rpd7Ee0wChkrA : - content-length: 0 - content-type: text/html; charset=UTF-8 - status: 204 - x-content-type-options: nosniff This means that CORB blocking is effectively a no-op (replacing an already empty/204 body with a blocked [=empty] body). Therefore, there should be no need to be alarmed here. See also: - https://www.chromium.org/Home/chromium-security/corb-for-developers which among other things explains: In most cases, the blocked response should not affect the web page's behavior and the CORB error message can be safely ignored. For example, the warning may occur in cases when the body of the blocked response was empty already, or when the response was going to be delivered to a context that can't handle it (e.g., a HTML document such as a 404 error page being delivered to an <img> tag). - Issue 844178 which asks to limit CORB error message to only the responses where CORB blocking might actually impact the webpage. The fixes for this issue will most likely ship in M69. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by viswa.karala@chromium.org
, Jul 1