Connections to ivwbox.de not blocked

[sugo]

I want to block connections to ivwbox.de

So i added the following filter rule: http://*.ivwbox.de/*

When i check with privoxy i see that connections to ivwbox.de are still made. Why isn't it working?

[Michael]

I suspect that connections are being made to http://ivwbox.de/, which is not filtered by your rule. I would therefore instead suggest that you instead use the filter ||ivwbox.de^ to block the domain entirely (see en/filters#anchors for more information about the syntax used).

[sugo]

I don't want to block ivwbox.de but heise.ivwbox.de, chip.ivwbox.de/ads...for example. These connections go through with filter http://*.ivwbox.de/*

[Michael]

What are the exact addresses that are reported by Privoxy?

[sugo]

Sep 07 03:09:36.414 b24f8b70 Request: heise.ivwbox.de/cgi-bin/ivw/CP/homepage;/?r=&d=
Sep 07 03:07:43.140 b6e1fb70 Request: heise.ivwbox.de/blank.gif

[Michael]

Which browser do you use and which version of Adblock Plus is installed?

[sugo]

Chrome 14 Beta with Version Adblock Plus Version 1.1.4

[Michael]

Adblock Plus for Chrome is currently unable to block items properly due to browser limitations; when the required Application Programming Interface (API) is implemented, the blocking rules should work according to the behaviour of Adblock Plus, which functions as expected.

[sugo]

Sorry, i posted in the wrong forum.

When do you think will the API be implemented?

[Michael]

Frankly, I haven't a clue. The Chrome developers control the API and, while it has been implemented, it is not yet considered stable enough to permit add-ons to use officially. I've heard that the feature won't be present in Chrome 16, which delays the API availability by at least a month or so, but know no further details about its release.