Here are the minimum rules that let the videos through:
{ -block }
.doubleclick.net/[0-9]+/DartShell.*\.swf
.doubleclick.net/pfadx/DARTSHELLCONFIGXML
.doubleclick.net/crossdomain.xml
.doubleclick.net/pfadx/3news.co.nz
.doubleclick.net/pfadx/www.tv3.co.nz
- set debug 1 in /etc/privoxy/config
- restart privoxy (sudo /etc/init.d/privoxy restart on Debian)
- watch the logfile for any blocked contents:
tail -f /var/log/privoxy/logfile | grep Blocked
4 comments:
Nice,
I don't know much about privoxy, but I do use a proxy on my desktop/laptop.
The main reason I do this is so that I can route HTTP traffic based on URL, is that something privoxy does well?, perhaps I should look at switching :-)
I don't think that Privoxy can route HTTP traffic to different places based on URLs.
The main uses for it are to:
- enhance privacy through the modification of cookies, rewriting referrers, etc.
- block undesirable contents entirely
- run Perl filters to clean up the "mostly desirable" content
You usually run it by chaining it to a different proxy (either before or after that other one).
@martyn i just use squid and a access helper perl script for that...
It gets all the details of the request on STDIN and can then do stuff with it.
I found that just adding "doubleclick.net/pfadx" to my whitelist was enough to allow tvnz, tv3 and others.
So far, I've yet to encounter a pfadx-type link outside of sites that force you to watch an ad before playing the content that you actually came to see, so it doesn't seem to be opening the floodgates to doubleclick to flood you with unrequested video spam (at this time).
Post a Comment