From 777198600b2a0875855c00a14f5386de51f6e5cb Mon Sep 17 00:00:00 2001 From: hal9 Date: Sun, 31 Mar 2002 23:18:47 +0000 Subject: [PATCH] More on dealing with BLOCKED. --- doc/source/faq.sgml | 65 ++++++++++++++++++++++++++++++++------------- 1 file changed, 47 insertions(+), 18 deletions(-) diff --git a/doc/source/faq.sgml b/doc/source/faq.sgml index 5a95bfb7..ee6d3618 100644 --- a/doc/source/faq.sgml +++ b/doc/source/faq.sgml @@ -6,7 +6,7 @@ This file belongs into ijbswa.sourceforge.net:/home/groups/i/ij/ijbswa/htdocs/ - $Id: faq.sgml,v 1.34 2002/03/29 04:35:56 hal9 Exp $ + $Id: faq.sgml,v 1.35 2002/03/30 04:14:19 hal9 Exp $ Written by and Copyright (C) 2001 the SourceForge Privoxy team. http://www.privoxy.org/ @@ -20,7 +20,7 @@ Privoxy Frequently Asked Questions -$Id: faq.sgml,v 1.34 2002/03/29 04:35:56 hal9 Exp $ +$Id: faq.sgml,v 1.35 2002/03/30 04:14:19 hal9 Exp $ @@ -33,7 +33,7 @@ This FAQ gives users and developers alike answers to frequently asked - questions about Privoxy. + questions about Privoxy. Privoxy is a web proxy with advanced filtering @@ -531,12 +531,13 @@ All the ads are there. What's wrong? Can I use my old config files? - There are major changes to Junkbuster - configuration from version 2.0.x to 2.9.x and later. The older files will - not work at all. If this is the case, you will need to re-enter your old - data into the new configuration structure. This is probably also a good - recommendation even if upgrading from 2.9.x to 3.x since there were - many minor changes along the way. + There are major changes to Junkbuster, + Privoxy, configuration from version 2.0.x to + 2.9.x and later. Most of the older files will not work at all. This is + especially true of blocklist. If this is the case, you + will need to re-enter your old data into the new configuration structure. + This is probably also a good recommendation even if upgrading from 2.9.x to + 3.x since there were many minor changes along the way. @@ -898,20 +899,45 @@ Note that normally only local users can connect to Privoxyimages (e.g. ad banners). Depending on the URL itself, it is sometimes hard for Privoxy to - really know whether it is indeed an ad image or not. + really know whether it is indeed an ad image or not. And there are + limitations as to what Privoxy can do to + fool the browser. - If you want them to be treated as if they were images, so that they can be - made invisible, then move the offending URL from the +block - section to the +imageblock section of your actions file. Just - be forewarned, if make any URL is made invisible, you may not - have any inkling that something has been removed from that page. + For instance, if the ad is in a frame, then it is embedded in the separate + HTML page used for the frame. In this case, you cannot just substitute an + aribitray image (like we would for a blank image), for an HTML + page. The browser is expecting an HTML page, and that is what it must have + for frames. So this situation can be a little trickier to deal with, and + Privoxy will use the Blocked page. + + + + If you want these to be treated as if they were images, so that they can be + made invisible, you can try moving the offending URL from the + +block section to the +imageblock section of + your actions file. Just be forewarned, if any URL is made + invisible, you may not have any inkling that something has + been removed from that page. If this approach does not work, then you are + probably dealing with a frame (or ilayer), and the only thing + that can go there is an HTML page of some sort. - Alternately, you could modify the block - HTML template that is used by Privoxy to display - this, and make it something more to your liking. + To deal with this situation, you could modify the + block HTML template that is used by + Privoxy to display this, and make it something + more to your liking. Currently, there is no configuration option for this. + You will have to modify, or create your own page, and use this to replace + templates/blocked, which is what + Privoxy uses to display the Blocked + page. + + + Another way to deal with this is find why and where + Privoxy is blocking the frame, and + diable this. Then let the +image-blocker action + handle the ad that is embedded in the frame's HTML page. @@ -1436,6 +1462,9 @@ This is referenced in the doc header already. HB 03/25/02 Temple Place - Suite 330, Boston, MA 02111-1307, USA. $Log: faq.sgml,v $ +Revision 1.35 2002/03/30 04:14:19 hal9 +Fix privoxy.org/config links. + Revision 1.34 2002/03/29 04:35:56 hal9 Touch ups. -- 2.39.2