Unable to distinguish a request blocking plugin from the browser itself
Reported by
adam.ko...@gmail.com,
Mar 23 2017
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.110 Safari/537.36 Steps to reproduce the problem: I'm developing a website. It has an URL which contains the phrase "tracker". It got blocked by the ad blocking software I'm using (uBlock Origin), but Chrome showed me raw net::ERR_BLOCKED_BY_CLIENT error not telling me about the ad-block's intervention. What is the expected behavior? Something like net::ERR_BLOCKED_BY_THIRD_PARTY or even the same net::ERR_BLOCKED_BY_CLIENT_ERROR but with an additional message pointing to the app which blocked the request. What went wrong? I spent more than an hour trying to figure out what's wrong, before I found the info about ad-blocks being one of possible reasons. I believe that the error is (mostly) correct, but more information on it would be really helpful. Besides the chrome network console is not helpful either, it showed me just "failed" information, with misleading information about the referrer-policy header. Did this work before? N/A Does this work in other browsers? N/A Chrome version: 57.0.2987.110 Channel: stable OS Version: OS X 10.12.3 Flash Version:
,
Mar 27 2017
,
Mar 27 2017
Marking component as Extensions as per the bug description.
,
Jan 22 2018
Mac triage: archiving old issue with no activity. |
||||
►
Sign in to add a comment |
||||
Comment 1 by kkaluri@chromium.org
, Mar 24 2017Labels: Needs-Feedback