From: hal9 Date: Thu, 11 Apr 2002 00:53:57 +0000 (+0000) Subject: Sync. X-Git-Tag: v_2_9_14~79 X-Git-Url: http://www.privoxy.org/gitweb/?a=commitdiff_plain;h=c01b30f9af53ef020661196131349e2c33ebfb9e;p=privoxy.git Sync. --- diff --git a/doc/text/user-manual.txt b/doc/text/user-manual.txt index ebc0bba0..399fa66d 100644 --- a/doc/text/user-manual.txt +++ b/doc/text/user-manual.txt @@ -2,7 +2,7 @@ Privoxy User Manual By: Privoxy Developers -$Id: user-manual.sgml,v 1.72 2002/04/10 04:06:19 hal9 Exp $ +$Id: user-manual.sgml,v 1.73 2002/04/10 18:45:15 swa Exp $ The user manual gives users information on how to install, configure and use Privoxy. @@ -69,6 +69,9 @@ Table of Contents 5.6. Templates 6. Contacting the Developers, Bug Reporting and Feature Requests + + 6.1. Submitting Ads and "Action" Problems + 7. Copyright and History 7.1. Copyright @@ -89,7 +92,7 @@ Table of Contents 1. Introduction This documentation is included with the current beta version of Privoxy, -v.2.9.13, and is mostly complete at this point. The most up to date reference +v.2.9.14, and is mostly complete at this point. The most up to date reference for the time being is still the comments in the source files and in the individual configuration files. Development of version 3.0 is currently nearing completion, and includes many significant changes and enhancements over earlier @@ -166,8 +169,8 @@ There are several ways to install Privoxy. To build Privoxy from source, autoconf and GNU make (gmake) are required. Source is available as gzipped tar archives. For this, first unpack the source: - tar xzvf privoxy-2.9.13-beta-src* [.tgz or .tar.gz] - cd privoxy-2.9.13-beta + tar xzvf privoxy-2.9.14-beta-src* [.tgz or .tar.gz] + cd privoxy-2.9.14-beta For retrieving the current CVS sources, you'll need the CVS package installed @@ -214,13 +217,13 @@ To build Redhat RPM packages from source, install source as above. Then: This will create both binary and src RPMs in the usual places. Example: - /usr/src/redhat/RPMS/i686/privoxy-2.9.13-1.i686.rpm + /usr/src/redhat/RPMS/i686/privoxy-2.9.14-1.i686.rpm - /usr/src/redhat/SRPMS/privoxy-2.9.13-1.src.rpm + /usr/src/redhat/SRPMS/privoxy-2.9.14-1.src.rpm To install, of course: - rpm -Uvv /usr/src/redhat/RPMS/i686/privoxy-2.9.13-1.i686.rpm + rpm -Uvv /usr/src/redhat/RPMS/i686/privoxy-2.9.14-1.i686.rpm This will place the Privoxy configuration files in /etc/privoxy/, and log files @@ -241,13 +244,13 @@ To build SuSE RPM packages, install source as above. Then: This will create both binary and src RPMs in the usual places. Example: - /usr/src/packages/RPMS/i686/privoxy-2.9.13-1.i686.rpm + /usr/src/packages/RPMS/i686/privoxy-2.9.14-1.i686.rpm - /usr/src/packages/SRPMS/privoxy-2.9.13-1.src.rpm + /usr/src/packages/SRPMS/privoxy-2.9.14-1.src.rpm To install, of course: - rpm -Uvv /usr/src/packages/RPMS/i686/privoxy-2.9.13-1.i686.rpm + rpm -Uvv /usr/src/packages/RPMS/i686/privoxy-2.9.14-1.i686.rpm This will place the Privoxy configuration files in /etc/privoxy/, and log files @@ -259,7 +262,7 @@ in /var/log/privoxy/. Privoxy is packaged in a WarpIN self- installing archive. The self-installing program will be named depending on the release version, something like: -privoxyos2_setup_2.9.13.exe. In order to install it, simply run this executable +privoxyos2_setup_2.9.14.exe. In order to install it, simply run this executable or double-click on its icon and follow the WarpIN installation panels. A shadow of the Privoxy executable will be placed in your startup folder so it will start automatically whenever OS/2 starts. @@ -449,7 +452,7 @@ Privoxy can be reached by the special URL http://p.p/ (or alternately http:// config.privoxy.org/), which is an internal page. You will see the following section: - Please choose from the following options: +Please choose from the following options: * Show information about the current configuration * Show the source code version numbers @@ -1782,6 +1785,23 @@ note: ------------------------------------------------------------------------------- +6.1. Submitting Ads and "Action" Problems + +Ads and banners that are not stopped by Privoxy can be submitted to the +developers by accessing a special page and filling out the brief, required +form. Conversely, you can also report pages, images, etc. that Privoxy is +blocking, but should not. The form itself does require Internet access. + +To do this, point your browser to Privoxy at http://p.p/, and then select +Actions file feedback system, near the bottom of the page. Paste in the URL +that is the cause of the unwanted behavior, and follow the prompts. The +developers will try to incorporate your submission into future versions. + +New default.actions files will occasionally be made available based on your +feedback. These will be announced on the ijbswa-announce list. + +------------------------------------------------------------------------------- + 7. Copyright and History 7.1. Copyright @@ -2100,7 +2120,7 @@ basically what Privoxy would do if there were not any "actions" defined, i.e. it does nothing. Every action is disabled. This is not particularly informative for our purposes here. OK, next section: - Matches for http://google.com: + Matches for http://google.com: { -add-header -block +deanimate-gifs -downgrade +fast-redirects +filter{html-annoyances} +filter{js-annoyances} +filter{no-popups} @@ -2140,7 +2160,7 @@ referenced in these sections. And now we pull it altogether in the bottom section and summarize how Privoxy is appying all its "actions" to "google.com": - Final results: + Final results: -add-header -block -deanimate-gifs -downgrade -fast-redirects +filter{html-annoyances} +filter{js-annoyances} +filter{no-popups} @@ -2154,7 +2174,7 @@ is appying all its "actions" to "google.com": Now another example, "ad.doubleclick.net": - { +block +image } + { +block +image } .ad.doubleclick.net { +block +image } @@ -2181,7 +2201,7 @@ defined as "ad.doubleclick.net" is done here -- as both a "+block" and an One last example. Let's try "http://www.rhapsodyk.net/adsl/HOWTO/". This one is giving us problems. We are getting a blank page. Hmmm... - Matches for http://www.rhapsodyk.net/adsl/HOWTO/: + Matches for http://www.rhapsodyk.net/adsl/HOWTO/: { -add-header -block +deanimate-gifs -downgrade +fast-redirects +filter{html-annoyances} +filter{js-annoyances} +filter{no-popups} @@ -2202,7 +2222,7 @@ see why we get the blank page. We could now add a new action below this that explictly does not block (-block) pages with "adsl". There are various ways to handle such exceptions. Example: - { -block } + { -block } /adsl @@ -2213,7 +2233,7 @@ such changes. Or, try using Shift+Reload. But now what about a situation where we get no explicit matches like we did with: - { -block } + { -block } /adsl @@ -2225,7 +2245,7 @@ and maybe a little trial and error to isolate the offending rule. One likely cause would be one of the "{+filter}" actions. Try adding the URL for the site to one of aliases that turn off "+filter": - {shop} + {shop} .quietpc.com .worldpay.com # for quietpc.com .jungle.com @@ -2237,7 +2257,7 @@ to one of aliases that turn off "+filter": "{shop}" is an "alias" that expands to "{ -filter -no-cookies -no-cookies-keep }". Or you could do your own exception to negate filtering: - {-filter} + {-filter} .forbes.com