Export to GitHub

adblockforchrome - issue #6369

Error 20 (net::ERR_BLOCKED_BY_CLIENT): Requests to the server have been blocked by an extension


Posted on Jan 7, 2012 by Quick Rabbit

AdBlock version number: 2.5.9 Operating system: Windows 7 Browser version number: 18.0.1000.0 (Developer Build 116823 Windows) Paste the URL from your address bar where you see the problem: http://betanews.com

What steps will reproduce the problem? Please be very specific.

  1. Open http://betanews.com with AdBlock enabled
  2. Observe the ad block on the right replaced with http://dl.dropbox.com/u/2752840/screens/snap0704-1325966516.png

What do you expect to see? What do you see instead?

I expect to see the black space, instead I see chrome message:

This webpage was blocked by an extension A third-party extension has blocked access to this webpage. Here are some suggestions: Disable your extensions and then reload this webpage. Error 20 (net::ERR_BLOCKED_BY_CLIENT): Requests to the server have been blocked by an extension.

See the issue reported at http://code.google.com/p/chromium/issues/detail?id=107515. Looks like in the new Chromium versions extensions need to provide some return value when cancelling resource load so that the browser doesn't display this placeholder page.

Comment #1

Posted on Jan 7, 2012 by Helpful Bear

As said in the Chrome issue, this is most likely caused by issue chromium:105981. When betanews gets online (currently it shows an error page) I'll see if the blocked frame can also be hidden.

Comment #2

Posted on Jan 7, 2012 by Helpful Bear

It's back online. Are you by any means not subscribed to the (default) Easylist filters? (options page, second tab) Could you possibly try updating your filters (options page, second tab) Do you have any custom filters (options page, third tab) That part of the page should already been hidden by Easylist?

Comment #3

Posted on Jan 7, 2012 by Helpful Bear

Sorry... didn't look at the Chrome version number. They have some stupid bug that breaks all code of us that runs in the page itself, including the hiding rules...

Comment #4

Posted on Jan 7, 2012 by Quick Rabbit

I'm subscribed to the following filters and they are up to date: http://dl.dropbox.com/u/2752840/screens/snap0705-1325989456.png .

The issue can be also reproduced on http://www.youtube.com. It's specific to the recent Chromium nightly builds.

Comment #5

Posted on Jan 7, 2012 by Quick Rabbit

Thanks for the update, I'll watch that bug.

Comment #6

Posted on Jan 11, 2012 by Happy Elephant

this affects "Google Chrome 18.0.1003.1 dev" too (same message different logo).

Comment #7

Posted on Jan 11, 2012 by Helpful Bear

Hi, please update to the latest version of AdBlock (in chrome://extensions/), which fixes this issue for 99% of the sites.

Comment #8

Posted on Jan 12, 2012 by Happy Lion

using version 2.5.12 (as of January 12), but still experiencing this issue in sites such as tripit.com

Comment #9

Posted on Jan 12, 2012 by Helpful Bear

This issue was updated by revision r3453.

This is due to a different Chrome bug, which we currently just have to work around. Added it to the custom filters, when Michael releases it, it'll be fixed. (or you can add the filter tripit.com##iframe[id^="open_ad_stream_frame_"] yourself)

Comment #10

Posted on Jan 12, 2012 by Happy Lion

Thanks for the update, this custom filter did the trick.

Comment #11

Posted on Mar 27, 2012 by Happy Rhino

I am getting the same error message on facebook and youtube. How do I get filters for them?

Comment #12

Posted on Apr 10, 2012 by Happy Monkey

Comment deleted

Comment #13

Posted on Apr 10, 2012 by Happy Monkey

Comment deleted

Comment #14

Posted on Apr 10, 2012 by Happy Monkey

Comment deleted

Comment #15

Posted on Apr 10, 2012 by Happy Monkey

Comment deleted

Comment #16

Posted on Apr 10, 2012 by Happy Monkey

The merge into issue 6360 appears not to be correct, it refers to an unrelated problem not involving the 'This webpage was blocked by an extension' problem at all. Checkout issue 6489 in stead. . And regarding the custom filters workaround and the ubiquitous 'How do I get filters for ...' question, I wonder: if we're doing workarounds anyway(for the time being), is it not enough to just simply Right Click on the offensive 'This webpage was blocked ...' frame and use one of the helpers on the 'AdBlock' sub-menu?

Comment #17

Posted on Apr 10, 2012 by Helpful Bear

At that time, that was the correct merge. I just guess you starred the wrong issue :)

Comment #18

Posted on Jul 19, 2012 by Helpful Bear

Locking closed issues from comments to prevent spam

Status: Duplicate

Labels:
Priority-Medium Type-Defect MoreInfoNeeded Restrict-AddIssueComment-Commit