[SOLVED] Blocking an image with partial url

Posting here is no longer possible, please use the forum of a filter list project, such as EasyList
Locked
User avatar
rick752
Posts: 2709
Joined: Fri Jun 09, 2006 7:59 pm
Location: New York USA
Contact:

Post by rick752 »

If it is an image, you don't need to use element-hiding rules.

You should be able to block it simply with the regular rule:

Code: Select all

/pagead/imgad
(edit)... even though your should have worked too.
User avatar
rick752
Posts: 2709
Joined: Fri Jun 09, 2006 7:59 pm
Location: New York USA
Contact:

Post by rick752 »

Oh, now that's interesting :shock:

It seems that it doesn't like it if you start the "hide" description with a "/".

Try this instead:

Code: Select all

#img(src*=pagead/imgad)
.... learn something new everyday. :roll:
User avatar
rick752
Posts: 2709
Joined: Fri Jun 09, 2006 7:59 pm
Location: New York USA
Contact:

Post by rick752 »

Nicely done except for one thing.

Having many rules starting with:

Code: Select all

http://*
... is totally unnecessary because ALL rules normally start with "http://" (unless you are trying NOT to block an "https" version of the same thing)

In other words:

Code: Select all

http://*.bluestreak.com/*
could simply be:

Code: Select all

*.bluestreak.com/*
...there will ALWAYS be an "http://" before it somewhere.

It doesn't hurt mind you ... it just makes the code bigger without purpose.

:wink:
Last edited by rick752 on Sun Mar 04, 2007 3:55 pm, edited 1 time in total.
User avatar
rick752
Posts: 2709
Joined: Fri Jun 09, 2006 7:59 pm
Location: New York USA
Contact:

Post by rick752 »

You're welcome.

ps: The only time that "http://*" is important is when you need to make a @@whitelisting rule. Using "http://*" tells the ENTIRE page to become whitelisted .... not using it only whitelists specific strings WITHIN the page and not the page itself.

Have fun! :)
User avatar
rick752
Posts: 2709
Joined: Fri Jun 09, 2006 7:59 pm
Location: New York USA
Contact:

Post by rick752 »

From my experience, you have already created a bunch of false-positives. At a quick glance, just your 2 strings:

http://*/RealMedia/ads/*
and
http://*/ads/*.swf?*

..... will cause you much grief when trying to view major video sites. Try watching video at Foxnews or MSNBC for a couple of examples ... there will be many more.
Locked