From: hal9 Date: Wed, 22 May 2002 04:27:01 +0000 (+0000) Subject: Catch up on recent source changes. X-Git-Tag: v_3_0_branchpoint~31 X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=commitdiff_plain;h=2d6b5d2e894f920d7e376a9dc4fa436a8dbefcec Catch up on recent source changes. --- diff --git a/doc/webserver/developer-manual/coding.html b/doc/webserver/developer-manual/coding.html index 06b207ca..364af8e1 100644 --- a/doc/webserver/developer-manual/coding.html +++ b/doc/webserver/developer-manual/coding.html @@ -2019,7 +2019,7 @@ WIDTH="100%" >
const char FILENAME_rcs[] = "$Id: developer-manual.sgml,v 1.42 2002/05/05 20:26:02 hal9 Exp $";
+>const char FILENAME_rcs[] = "$Id: developer-manual.sgml,v 1.45 2002/05/19 23:01:54 hal9 Exp $";
 /*********************************************************************
  *
  * File        :  $Source$
@@ -2097,7 +2097,7 @@ WIDTH="100%"
 CLASS="PROGRAMLISTING"
 >#ifndef _FILENAME_H
 #define _FILENAME_H
-#define FILENAME_H_VERSION "$Id: developer-manual.sgml,v 1.42 2002/05/05 20:26:02 hal9 Exp $"
+#define FILENAME_H_VERSION "$Id: developer-manual.sgml,v 1.45 2002/05/19 23:01:54 hal9 Exp $"
 /*********************************************************************
  *
  * File        :  $Source$
diff --git a/doc/webserver/developer-manual/contact.html b/doc/webserver/developer-manual/contact.html
index 3848767a..c9112352 100644
--- a/doc/webserver/developer-manual/contact.html
+++ b/doc/webserver/developer-manual/contact.html
@@ -74,8 +74,13 @@ NAME="CONTACT"
 >8. Contacting the developers, Bug Reporting and Feature Requests
 We value your feedback. However, to provide you with the best support, please
- note the following sections.
 We value your feedback. In fact, we rely on it to improve
+ Privoxy and its configuration.
+ However, please note the following hints, so we can 
+ provide you with the best support:
8.1. Get Support
   
To get support, use the Sourceforge Support Forum:

-

-     For casual users, our support forum at
+ SourceForge
+ is probably best suited:
+ http://sourceforge.net/tracker/?group_id=11118&atid=211118

-  
 All users are of course welcome to discuss their issues on the users
+ mailing list, where the developers also hang around.
8.2. Report bugs8.2. Report Bugs
   
To submit bugs, use the Sourceforge Bug Forum:

-

-     Please report all bugs only through our
+ bug tracker: 
+ http://sourceforge.net/tracker/?group_id=11118&atid=111118. 

- 
. 
  Before doing so, please make sure that the bug has not already been submitted
+  and observe the aditional hints at the top of the submit
+  form.
   Make sure that the bug has not already been submitted.  Please try to
-   verify that it is a  
+  Please try to verify that it is a Privoxy bug, and not a
-   browser or site bug first. If you are using your own custom configuration,
-   please try the stock configs to see if the problem is a configuration
-   related bug.  And if not using the latest development snapshot, please try
-   the latest one. Or even better, CVS sources. Please be sure to include the
-    bug,
+  and not a browser or site bug first. If unsure,
+  try toggling
+  off Privoxy version, platform, browser, any
-   pertinent log data, any other relevant details (please be specific) and,
-   if possible, some way to reproduce the bug.
-  
, and see if the problem persists.
+  The appendix
+  of the user manual also has helpful information 
+  on action debugging. If you are using your own custom configuration, please try
+  the stock configs to see if the problem is configuration related.
  If not using the latest version, chances are that the bug has been found
+  and fixed in the meantime. We would appreciate if you could take the time
+  to upgrade
+  to the latest version (or  even the latest CVS snapshot) and verify
+  your bug, but this is not required for reporting.
8.3. Request new features8.3. Request New Features
   
To submit ideas on new features, use the Sourceforge feature request forum:

-

-     You are welcome to submit ideas on new features or other proposals
+ for improvement through our feature request tracker at
+ http://sourceforge.net/tracker/?atid=361118&group_id=11118&func=browsehttp://sourceforge.net/tracker/?atid=361118&group_id=11118.

-  
8.4. Report ads or other filter problems8.4. Report Ads or Other Actions-Related Problems
You can also send feedback on websites that Privoxy has problems with. Please bookmark
-the following link:  Please send feedback on ads that slipped through, innocent images that were blocked,
+ and any other problems relating to the default.action file through
+ our actions feedback mechanism located at
+ "Privoxy - Submit Filter Feedback". Once you surf to a page with problems, use the
-bookmark to send us feedback. We will look into the issue as soon as possible.
-  
http://www.privoxy.org/actions/.
+ On this page, you will also find a bookmark which will take you back there from
+ any troubled site and even pre-fill the form!
 New, improved ijbswa-announce
- list.
project page.
8.5. Other
   
For any other issues, feel free to use the mailing lists:

- 

-    For any other issues, feel free to use the mailing lists. Technically interested users
+and people who wish to contribute to the project are also welcome on the developers list!
+You can find an overview of all Prixoxy-related mailing lists,
+including list archives, at:
+http://sourceforge.net/mail/?group_id=11118.

- 
  Anyone interested in actively participating in development and related
-  discussions can also join the appropriate mailing list. Archives are
-  available, too. See the page on Sourceforge.
- 
9.1. License
9.2. History
 Privoxy is evolved, and derived from, 
-  In the beginning, there was the
+ the Internet Junkbuster, with many 
- improvments and enhancements over the original.
Internet Junkbuster, 
+ by Anonymous Coders and Junkbusters
+ Corporation. It saved many users a lot of pain in the early days of
+ web advertising and user tracking.
  But the web, its protocols and standards, and with it, the techniques for
+ forcing  users to consume ads, give up autonomy over their browsing, and
+ for spying on them, kept evolving. Unfortunately, the Junkbuster was originally written by Anonymous
- Coders and Internet
+ Junkbuster did not. Version 2.0.2, published in 1998, was 
+ (and is) the last official
+ release
+ available from Junkbusters
- Corporation, and was released as free open-source software under the
- GNU GPL. Junkbusters Corporation.
+ Fortunately, it had been released under the GNU
+  GPL, which allowed further
+ development by others.
 So Stefan Waldherr started maintaining an
+ Stefan
- Waldherr made many improvements, and started the improved version of the
+ software, to which eventually a number of people contributed patches.
+ It could already replace banners with a transparent image, and had a first
+ version of pop-up killing, but it was still very closely based on the
+ original, with all its limitations, such as the lack of HTTP/1.1 support,
+ flexible per-site configuration, or content modification. The last release
+ from this effort was version 2.0.2-10, published in 2000.
 Then, some
+ developers
+ picked up the thread, and started turning the software inside out, upside down,
+ and then reassembled it, adding many
+ SourceForge project
- Privoxy to rekindle development. There are now several active
- developers contributing.  The last stable release of
- new
+ features along the way.
 The result of this is Junkbuster was v2.0.2, which has now
- grown whiskers ;-).
Privoxy, whose first
+ stable release, 3.0, is due in May 2002.
$Id: developer-manual.sgml,v 1.42 2002/05/05 20:26:02 hal9 Exp $
$Id: developer-manual.sgml,v 1.45 2002/05/19 23:01:54 hal9 Exp $
.
  Please see the Contact section 
  on how to contact the developers.
6.3.1. Note on Privoxy Packaging
6.3.2. Source Tarball
6.3.2. 6.3.3. SuSE or Red Hat RPMSuSE, Conectiva or Red Hat RPM
6.3.3. 6.3.4. OS/2
6.3.4. 6.3.5. Solaris
6.3.5. 6.3.6. Windows
6.3.6. 6.3.7. Debian
6.3.7. 6.3.8. Mac OSX
6.3.8. 6.3.9. FreeBSD
6.3.9. 6.3.10. HP-UX 11
6.3.10. 6.3.11. Amiga OS
6.3.11. 6.3.12. AIX
8.2. Report bugsReport Bugs
8.3. Request new featuresRequest New Features
8.4. Report ads or other filter problemsReport Ads or Other Actions-Related Problems
8.5. 
9.1. License
9.2. History
     Please find additional instructions for the source tarball and the
-     individual platform dependent binary packages below.
+     individual platform dependent binary packages below. And details 
+     on the Sourceforge release process below that.
     
6.3.1. Note on Privoxy Packaging
      Please keep these general guidelines in mind when putting together 
+      your package. These apply to all platforms!
+     
      
  •           Privoxy requires
+          write access to: all *.action files, all 
+          logfiles, and the trust file. You will 
+          need to determine the best way to do this for your platform.
+        
  •           Please include up to date documentation. At a bare minimum:
+        
              LICENSE (toplevel directory)
+         
              README (toplevel directory)
+         
              AUTHORS (toplevel directory)
+         
              man page (toplevel directory, Unix-like
+          platforms only)
+         
              The User Manual (doc/webserver/user-manual/)
+         
              FAQ (doc/webserver/faq/)
+         
              Also suggested: Developer Manual
+          (doc/webserver/devel-manual) and ChangeLog
+          (toplevel directory). FAQ and the manuals are
+          HTML docs. There are also text versions in
+          doc/text/ which could conceivably also be
+          included.
+        
             The documentation has been designed such that the manuals are linked
+         to each other from parallel directories, and should be packaged 
+         that way. index.html can also be included and 
+         can serve as a focal point for docs and other links of interest.
+         This should be one level up from the manuals. There are two 
+         css stylesheets that can be included for better presentation:
+         p_doc.css and p_web.css.
+         These should be in the same directory with
+         index.html, (i.e. one level up from the manual 
+         directories).
+        
  •         user.action is designed for local preferences. 
+        Make sure this does not get overwritten!
+       
  •         Other configuration files should be installed as the new defaults, 
+        but all previously installed configuration files should be preserved
+        as backups. This is just good manners :-)
+       
  •        Please check platform specific notes in this doc, if you haven't 
+       done "Privoxy" packaging before for other platform 
+       specific issues. Conversely, please add any notes that you know 
+       are important for your platform (or contact one of the doc 
+       maintainers to do this if you can't).
+      

+     
6.3.1. Source Tarball6.3.2. Source Tarball
	First, 6.3.2. SuSE or Red Hat RPM6.3.3. SuSE, Conectiva or Red Hat RPM
        In following text, replace 6.3.3. OS/26.3.4. OS/2
	First, 6.3.4. Solaris6.3.5. Solaris
	Login to Sourceforge's compilefarm via ssh:
@@ -805,7 +1029,7 @@ CLASS="SECT3"
 CLASS="SECT3"
 >6.3.5. Windows6.3.6. Windows
        You should ensure you have the latest version of Cygwin (from
@@ -882,7 +1106,7 @@ CLASS="SECT3"
 CLASS="SECT3"
 >6.3.6. Debian6.3.7. Debian
	First, 6.3.7. Mac OSX6.3.8. Mac OSX
	First, 6.3.8. FreeBSD6.3.9. FreeBSD
	Login to Sourceforge's compilefarm via ssh:
@@ -1103,7 +1327,7 @@ CLASS="SECT3"
 CLASS="SECT3"
 >6.3.9. HP-UX 116.3.10. HP-UX 11
	First, 6.3.10. Amiga OS6.3.11. Amiga OS
	First, 6.3.11. AIX6.3.12. AIX
	Login to Sourceforge's compilefarm via ssh:
@@ -1296,6 +1520,12 @@ CLASS="LITERAL"
 >
     
     Or use the make targets as described above.
+    
     Once this done go to        http://www.privoxy.org/, 
-   The Privoxy Home page. 
@@ -104,10 +104,33 @@ BORDER="0"
 >       http://www.privoxy.org/faq/, 
+   the Privoxy FAQ. 
+  

+ 
   http://sourceforge.net/projects/ijbswahttp://sourceforge.net/projects/ijbswa/, 
    the Project Page for SourceforgeSourceForge.
   
       http://p.p/, access
-   http://config.privoxy.org/,
+   the web-based user interface. Privoxy from your browser. Alternately, 
-    must be
+   running for this to work. Shortcut: http://config.privoxy.orghttp://p.p/
-   may work in some situations where the first does not.
   
    http://p.p/, and select    "Privoxy - Submit Filter Feedback" to submit http://www.privoxy.org/actions/, to submit "misses" to the developers. 
@@ -190,11 +205,32 @@ BORDER="0"
 >
       http://www.junkbusters.com/ht/en/cookies.html,
+   an explanation how cookies are used to track web users.
+  

+ 
http://www.squid-cache.org/, a very popular
+   caching proxy, which is often used together with Privoxy.
+  
   http://www.junkbusters.com/ijb.html,
+   the original Internet Junkbuster.
   
       http://www.waldherr.org/junkbuster/
+>,
+   Stefan Waldherr's version of Junkbuster, from which Privoxy was
+   derived.
   
       http://privacy.net/analyze/
+>, a useful site
+   to check what information about you is leaked while you browse the web.
   

+ 
   http://www.privoxy.org/developer-manual/, 
+   the Privoxy developer manual. 
   

6. Contacting the developers, Bug Reporting and Feature Requests
 We value your feedback. However, to provide you with the best support, please
- note the following sections.
 We value your feedback. In fact, we rely on it to improve
+ Privoxy and its configuration.
+ However, please note the following hints, so we can 
+ provide you with the best support:
6.1. Get Support
   
To get support, use the Sourceforge Support Forum:

-

-     For casual users, our support forum at
+ SourceForge
+ is probably best suited:
+ http://sourceforge.net/tracker/?group_id=11118&atid=211118

-  
 All users are of course welcome to discuss their issues on the users
+ mailing list, where the developers also hang around.
6.2. Report bugs6.2. Report Bugs
   
To submit bugs, use the Sourceforge Bug Forum:

-

-     Please report all bugs only through our
+ bug tracker: 
+ http://sourceforge.net/tracker/?group_id=11118&atid=111118. 

- 
. 
  Before doing so, please make sure that the bug has not already been submitted
+  and observe the aditional hints at the top of the submit
+  form.
   Make sure that the bug has not already been submitted.  Please try to
-   verify that it is a  
+  Please try to verify that it is a Privoxy bug, and not a
-   browser or site bug first. If you are using your own custom configuration,
-   please try the stock configs to see if the problem is a configuration
-   related bug.  And if not using the latest development snapshot, please try
-   the latest one. Or even better, CVS sources. Please be sure to include the
-    bug,
+  and not a browser or site bug first. If unsure,
+  try toggling
+  off Privoxy version, platform, browser, any
-   pertinent log data, any other relevant details (please be specific) and,
-   if possible, some way to reproduce the bug.
-  
, and see if the problem persists.
+  The appendix
+  of the user manual also has helpful information 
+  on action debugging. If you are using your own custom configuration, please try
+  the stock configs to see if the problem is configuration related.
  If not using the latest version, chances are that the bug has been found
+  and fixed in the meantime. We would appreciate if you could take the time
+  to upgrade
+  to the latest version (or  even the latest CVS snapshot) and verify
+  your bug, but this is not required for reporting.
6.3. Request new features6.3. Request New Features
   
To submit ideas on new features, use the Sourceforge feature request forum:

-

-     You are welcome to submit ideas on new features or other proposals
+ for improvement through our feature request tracker at
+ http://sourceforge.net/tracker/?atid=361118&group_id=11118&func=browsehttp://sourceforge.net/tracker/?atid=361118&group_id=11118.

-  
6.4. Report ads or other filter problems6.4. Report Ads or Other Actions-Related Problems
You can also send feedback on websites that Privoxy has problems with. Please bookmark
-the following link:  Please send feedback on ads that slipped through, innocent images that were blocked,
+ and any other problems relating to the default.action file through
+ our actions feedback mechanism located at
+ "Privoxy - Submit Filter Feedback". Once you surf to a page with problems, use the
-bookmark to send us feedback. We will look into the issue as soon as possible.
-  
http://www.privoxy.org/actions/.
+ On this page, you will also find a bookmark which will take you back there from
+ any troubled site and even pre-fill the form!
 New, improved ijbswa-announce
- list.
project page.
6.5. Other
   
For any other issues, feel free to use the mailing lists:

- 

-    For any other issues, feel free to use the mailing lists. Technically interested users
+and people who wish to contribute to the project are also welcome on the developers list!
+You can find an overview of all Prixoxy-related mailing lists,
+including list archives, at:
+http://sourceforge.net/mail/?group_id=11118.

- 
  Anyone interested in actively participating in development and related
-  discussions can also join the appropriate mailing list. Archives are
-  available, too. See the page on Sourceforge.
- 
7.1. License
7.2. History
 Privoxy is evolved, and derived from, 
-  In the beginning, there was the
+ the Internet Junkbuster, with many 
- improvments and enhancements over the original.
Internet Junkbuster, 
+ by Anonymous Coders and Junkbusters
+ Corporation. It saved many users a lot of pain in the early days of
+ web advertising and user tracking.
  But the web, its protocols and standards, and with it, the techniques for
+ forcing  users to consume ads, give up autonomy over their browsing, and
+ for spying on them, kept evolving. Unfortunately, the Junkbuster was originally written by Anonymous
- Coders and Internet
+ Junkbuster did not. Version 2.0.2, published in 1998, was 
+ (and is) the last official
+ release
+ available from Junkbusters
- Corporation, and was released as free open-source software under the
- GNU GPL. Junkbusters Corporation.
+ Fortunately, it had been released under the GNU
+  GPL, which allowed further
+ development by others.
 So Stefan Waldherr started maintaining an
+ Stefan
- Waldherr made many improvements, and started the improved version of the
+ software, to which eventually a number of people contributed patches.
+ It could already replace banners with a transparent image, and had a first
+ version of pop-up killing, but it was still very closely based on the
+ original, with all its limitations, such as the lack of HTTP/1.1 support,
+ flexible per-site configuration, or content modification. The last release
+ from this effort was version 2.0.2-10, published in 2000.
 Then, some
+ SourceForge project
- Privoxy to rekindle development. There are now several active
- developers contributing.  The last stable release of
- developers
+ picked up the thread, and started turning the software inside out, upside down,
+ and then reassembled it, adding many
+ new
+ features along the way.
 The result of this is Junkbuster was v2.0.2, which has now
- grown whiskers ;-).
Privoxy, whose first
+ stable release, 3.0, is due in May 2002.
   Modularized configuration that allows for standard settings and
    user settings to reside in separate files, so that installing updated
-   actions files won't overwrite idividual user settings.
+   actions files won't overwrite individual user settings.
   
  • See the Troubleshooting section below.)

    • $Id: faq.sgml,v 1.57 2002/05/05 20:26:02 hal9 Exp $
    $Id: faq.sgml,v 1.59 2002/05/15 04:03:30 hal9 Exp $
    5.1. I just upgraded and am getting "connection refused"
    5.2. I just added a new rule, but the steenkin ad is 
 still getting through. How?
    5.3. One of my favorite sites does not work with Privoxy
    6.2. Report bugsReport Bugs
    6.3. Request new featuresRequest New Features
    6.4. Report ads or other filter problemsReport Ads or Other Actions-Related Problems
    6.5. 
    7.1. License
    7.2. History
    Please see the Contact section.
           http://www.privoxy.org/, 
-   The Privoxy Home page. 
@@ -627,10 +626,33 @@ BORDER="0"
 >       http://www.privoxy.org/faq/, 
+   the Privoxy FAQ. 
+  
    
+ 
       http://sourceforge.net/projects/ijbswahttp://sourceforge.net/projects/ijbswa/, 
    the Project Page for SourceforgeSourceForge.
   
           http://p.p/, access
-   http://config.privoxy.org/,
+   the web-based user interface. Privoxy from your browser. Alternately, 
-    must be
+   running for this to work. Shortcut: http://config.privoxy.orghttp://p.p/
-   may work in some situations where the first does not.
   
        http://p.p/, and select    "Privoxy - Submit Filter Feedback" to submit http://www.privoxy.org/actions/, to submit "misses" to the developers. 
@@ -713,11 +727,32 @@ BORDER="0"
 >
           http://www.junkbusters.com/ht/en/cookies.html,
+   an explanation how cookies are used to track web users.
+  
    
+ 
    http://www.squid-cache.org/, a very popular
+   caching proxy, which is often used together with Privoxy.
+  
       http://www.junkbusters.com/ijb.html,
+   the original Internet Junkbuster.
   
           http://www.waldherr.org/junkbuster/
+>,
+   Stefan Waldherr's version of Junkbuster, from which Privoxy was
+   derived.
   
           http://privacy.net/analyze/
+>, a useful site
+   to check what information about you is leaked while you browse the web.
   
    
+ 
       http://www.privoxy.org/developer-manual/, 
+   the Privoxy developer manual. 
   
    
    5.1. I just upgraded and am getting "connection refused"
    5.2. I just added a new rule, but the steenkin ad is 
 still getting through. How?
    5.3. One of my favorite sites does not work with Privoxy
    Report bugsReport Bugs
    Request new featuresRequest New Features
    Report ads or other filter problemsReport Ads or Other Actions-Related Problems
    License
    History
    Support and Service via Sourceforge
     We value your feedback. However, to provide you with the best support, please
- note the following sections.
     We value your feedback. In fact, we rely on it to improve
+ Privoxy and its configuration.
+ However, please note the following hints, so we can 
+ provide you with the best support:
    Get Support
       
    To get support, use the Sourceforge Support Forum:
    
-
    
-     For casual users, our support forum at
+ SourceForge
+ is probably best suited:
+ http://sourceforge.net/tracker/?group_id=11118&atid=211118
    
-  
     All users are of course welcome to discuss their issues on the users
+ mailing list, where the developers also hang around.
    Report bugsReport Bugs
       
    To submit bugs, use the Sourceforge Bug Forum:
    
-
    
-     Please report all bugs only through our
+ bug tracker: 
+ http://sourceforge.net/tracker/?group_id=11118&atid=111118. 
    
- 
    . 
      Before doing so, please make sure that the bug has not already been submitted
+  and observe the aditional hints at the top of the submit
+  form.
       Make sure that the bug has not already been submitted.  Please try to
-   verify that it is a  
+  Please try to verify that it is a Privoxy bug, and not a
-   browser or site bug first. If you are using your own custom configuration,
-   please try the stock configs to see if the problem is a configuration
-   related bug.  And if not using the latest development snapshot, please try
-   the latest one. Or even better, CVS sources. Please be sure to include the
-    bug,
+  and not a browser or site bug first. If unsure,
+  try toggling
+  off Privoxy version, platform, browser, any
-   pertinent log data, any other relevant details (please be specific) and,
-   if possible, some way to reproduce the bug.
-  
    , and see if the problem persists.
+  The appendix
+  of the user manual also has helpful information 
+  on action debugging. If you are using your own custom configuration, please try
+  the stock configs to see if the problem is configuration related.
      If not using the latest version, chances are that the bug has been found
+  and fixed in the meantime. We would appreciate if you could take the time
+  to upgrade
+  to the latest version (or  even the latest CVS snapshot) and verify
+  your bug, but this is not required for reporting.
    Request new featuresRequest New Features
       
    To submit ideas on new features, use the Sourceforge feature request forum:
    
-
    
-     You are welcome to submit ideas on new features or other proposals
+ for improvement through our feature request tracker at
+ http://sourceforge.net/tracker/?atid=361118&group_id=11118&func=browsehttp://sourceforge.net/tracker/?atid=361118&group_id=11118.
    
-  
    Report ads or other filter problemsReport Ads or Other Actions-Related Problems
    You can also send feedback on websites that Privoxy has problems with. Please bookmark
-the following link:  Please send feedback on ads that slipped through, innocent images that were blocked,
+ and any other problems relating to the default.action file through
+ our actions feedback mechanism located at
+ "Privoxy - Submit Filter Feedback". Once you surf to a page with problems, use the
-bookmark to send us feedback. We will look into the issue as soon as possible.
-  
    http://www.privoxy.org/actions/.
+ On this page, you will also find a bookmark which will take you back there from
+ any troubled site and even pre-fill the form!
     New, improved ijbswa-announce
- list.
    project page.
    Other
       
    For any other issues, feel free to use the mailing lists:
    
- 
    
-    For any other issues, feel free to use the mailing lists. Technically interested users
+and people who wish to contribute to the project are also welcome on the developers list!
+You can find an overview of all Prixoxy-related mailing lists,
+including list archives, at:
+http://sourceforge.net/mail/?group_id=11118.
    
- 
      Anyone interested in actively participating in development and related
-  discussions can also join the appropriate mailing list. Archives are
-  available, too. See the page on Sourceforge.
- 
    License
    History
     Privoxy is evolved, and derived from, 
-  In the beginning, there was the
+ the Internet Junkbuster, with many 
- improvments and enhancements over the original.
    Internet Junkbuster, 
+ by Anonymous Coders and Junkbusters
+ Corporation. It saved many users a lot of pain in the early days of
+ web advertising and user tracking.
      But the web, its protocols and standards, and with it, the techniques for
+ forcing  users to consume ads, give up autonomy over their browsing, and
+ for spying on them, kept evolving. Unfortunately, the Junkbuster was originally written by Anonymous
- Coders and Internet
+ Junkbuster did not. Version 2.0.2, published in 1998, was 
+ (and is) the last official
+ release
+ available from Junkbusters
- Corporation, and was released as free open-source software under the
- GNU GPL. Junkbusters Corporation.
+ Fortunately, it had been released under the GNU
+  GPL, which allowed further
+ development by others.
     So Stefan Waldherr started maintaining an
+ Stefan
- Waldherr made many improvements, and started the improved version of the
+ software, to which eventually a number of people contributed patches.
+ It could already replace banners with a transparent image, and had a first
+ version of pop-up killing, but it was still very closely based on the
+ original, with all its limitations, such as the lack of HTTP/1.1 support,
+ flexible per-site configuration, or content modification. The last release
+ from this effort was version 2.0.2-10, published in 2000.
     Then, some
+ SourceForge project
- Privoxy to rekindle development. There are now several active
- developers contributing.  The last stable release of
- developers
+ picked up the thread, and started turning the software inside out, upside down,
+ and then reassembled it, adding many
+ new
+ features along the way.
     The result of this is Junkbuster was v2.0.2, which has now
- grown whiskers ;-).
    Privoxy, whose first
+ stable release, 3.0, is due in May 2002.
    Actions Files
    8.1. Finding the Right Mix
    8.2. How to Edit
    8.4.1. The Domain Pattern
    8.4.2. The Path Pattern
    8.5.21. Summary
    8.7.1. default.action
    8.7.2. user.action
    Appendix
    14.2. Privoxy
       Short cuts. Turn off, then on: 
   
     Matches for http://google.com:
 
---- File standard ---
-(no matches in this file)
-
---- File default ---
+ In file: default.action [ View ] [ Edit ]
 
-{ -add-header -block +deanimate-gifs{last} -downgrade-http-version +fast-redirects 
- -filter{popups} -filter{fun} -filter{shockwave-flash} -filter{crude-parental} 
- +filter{html-annoyances} +filter{js-annoyances} +filter{content-cookies} 
- +filter{webbugs} +filter{refresh-tags} +filter{nimda} +filter{banners-by-size} 
- +hide-forwarded-for-headers +hide-from-header{block} +hide-referer{forge} 
- -hide-user-agent -handle-as-image +set-image-blocker{pattern} -limit-connect 
- +prevent-compression +session-cookies-only -crunch-outgoing-cookies 
- -crunch-incoming-cookies -kill-popups -send-vanilla-wafer -send-wafer }
+{-add-header 
+ -block 
+ -crunch-outgoing-cookies 
+ -crunch-incoming-cookies 
+ +deanimate-gifs{last} 
+ -downgrade-http-version 
+ +fast-redirects 
+ -filter{popups} 
+ -filter{fun} 
+ -filter{shockwave-flash} 
+ -filter{crude-parental} 
+ +filter{html-annoyances} 
+ +filter{js-annoyances} 
+ +filter{content-cookies} 
+ +filter{webbugs} 
+ +filter{refresh-tags} 
+ +filter{nimda} 
+ +filter{banners-by-size} 
+ +hide-forwarded-for-headers 
+ +hide-from-header{block} 
+ +hide-referer{forge} 
+ -hide-user-agent 
+ -handle-as-image 
+ -kill-popups 
+ -limit-connect 
+ +prevent-compression 
+ -send-vanilla-wafer 
+ -send-wafer 
+ +session-cookies-only 
+ +set-image-blocker{pattern} }
 /
 
  { -session-cookies-only }
@@ -1384,7 +1410,13 @@ CLASS="SCREEN"
  { -fast-redirects }
  .google.com
 
---- File user ---
+In file: user.action [ View ] [ Edit ]
 (no matches in this file)  
    
 Final results:
- -add-header -block +deanimate-gifs{last} -downgrade-http-version -fast-redirects 
- -filter{popups} -filter{fun} -filter{shockwave-flash} -filter{crude-parental} 
- +filter{html-annoyances} +filter{js-annoyances} +filter{content-cookies} 
- +filter{webbugs} +filter{refresh-tags} +filter{nimda} +filter{banners-by-size} 
- +hide-forwarded-for-headers +hide-from-header{block} +hide-referer{forge} 
- -hide-user-agent -handle-as-image +set-image-blocker{pattern} -limit-connect 
- +prevent-compression -session-cookies-only -crunch-outgoing-cookies 
- -crunch-incoming-cookies -kill-popups -send-vanilla-wafer -send-wafer
    Matches for http://www.rhapsodyk.net/adsl/HOWTO/: - { -add-header -block +deanimate-gifs -downgrade-http-version +fast-redirects - +filter{html-annoyances} +filter{js-annoyances} +filter{kill-popups} - +filter{webbugs} +filter{nimda} +filter{banners-by-size} +filter{hal} - +filter{fun} +hide-forwarded-for-headers +hide-from-header{block} - +hide-referer{forge} -hide-user-agent -handle-as-image +set-image-blocker{blank} - +prevent-compression +session-cookies-only -crunch-incoming-cookies - -crunch-outgoing-cookies +kill-popups -send-vanilla-wafer -send-wafer } + In file: default.action [ View ] [ Edit ] + + {-add-header + -block + -crunch-incoming-cookies + -crunch-outgoing-cookies + +deanimate-gifs + -downgrade-http-version + +fast-redirects + +filter{html-annoyances} + +filter{js-annoyances} + +filter{kill-popups} + +filter{webbugs} + +filter{nimda} + +filter{banners-by-size} + +filter{hal} + +filter{fun} + +hide-forwarded-for-headers + +hide-from-header{block} + +hide-referer{forge} + -hide-user-agent + -handle-as-image + +kill-popups + +prevent-compression + -send-vanilla-wafer + -send-wafer + +session-cookies-only + +set-image-blocker{blank} } / { +block +handle-as-image } diff --git a/doc/webserver/user-manual/config.html b/doc/webserver/user-manual/config.html index e16e47af..c51c4ea4 100644 --- a/doc/webserver/user-manual/config.html +++ b/doc/webserver/user-manual/config.html @@ -4,7 +4,8 @@ >The Main Configuration FilePrivoxy Configuration

    6.1. Controlling PrivoxyPrivoxy Copyright, License and History

    12.1. License

    The Filter File

    9.1. Filter File Tutorial

    Privoxy User Manual

    $Id: user-manual.sgml,v 1.117 2002/05/17 13:56:16 oes Exp $

    $Id: user-manual.sgml,v 1.118 2002/05/21 04:54:55 hal9 Exp $

    2.1.1. Red Hat, SuSE RPMs and ConectivaRed Hat, SuSE and Conectiva RPMs
    2.1.2. Privoxy
    4.1. Quickstart to Ad Blocking
    5.
    6.1. Controlling Privoxy
    8.1. Finding the Right Mix
    8.2. How to Edit
    22
    8.4.1. The Domain Pattern
    8.4.2. The Path Pattern
    8.5.21. Summary
    8.7.1. default.action
    8.7.2. user.action
    9.1. Filter File Tutorial
    12.1. License
    14.2. PrivoxyInstallation2.1.1. Red Hat, SuSE RPMs and Conectiva2.1.1. Red Hat, SuSE and Conectiva RPMs

    RPMs can be installed with If you have problems with failed dependencies, try rebuilding the SRC RPM: rpm --rebuild privoxy-2.9.15-1.src.rpm;rpm --rebuild privoxy-2.9.15-1.src.rpm. This will use your locally installed libraries and RPM version.

    IntroductionQuickstart to Using Privoxy

    4.1. Quickstart to Ad Blocking

    Ad blocking is but one of Privoxy's + array of features. Many of these features are for the technically minded advanced + user. But, ad and banner blocking is surely common ground for everybody.

    + This section will provide a quick summary of ad blocking so + you can get up to speed quickly without having to read the more extensive + information provided below, though this is highly recommeneded.

    First a bit of a warning ... blocking ads is much like blocking SPAM: the + more aggressive you are about it, the more likely you are to block + things that were not intended. So there is a trade off here. If you want + extreme ad free browsing, be prepared to deal with more + "problem" sites, and to spend more time adjusting the + configuration to solve these unintended consequences. In short, there is + not an easy way to eliminate all ads. Either take + the easy way and settle for most ads blocked with the + default configuration, or jump in and tweak it for your personal surfing + habits and preferences.

    Secondly, a brief explanation of Privoxy's + "actions". "Actions" in this context, are + the directives we use to tell Privoxy to perform + some task relating to HTTP transactions (i.e. web browsing). We tell + Privoxy to take some "action". Each + action has a unique name and function. While there are many potential + actions in Privoxy's + arsenal, only a few are used for ad blocking. Actions, and action + configuration files, are explained in depth below.

    Actions are specified in Privoxy's configuration, + followed by one or more URLs to which the action should apply. URLs + can actually be URL type patterns that use + wildcards so they can apply potentially to a range of similar URLs.

    When you connect to a website, the full path of the URL will either match one + of the "actions" as defined in + Privoxy's configuration, or not. If so, then + Privoxy will perform the action accordingly. If + not, then nothing special happens. Futhermore, web pages may contain + embedded, secondary URLs that your web browser will display as it parses the + original page's HTML content. An ad image for instance, is just a URL + embedded in the page somewhere. The image itself may be on the same server, + or a server somewhere else on the Internet. Complex web pages will have many + such embedded URLs.

    The actions we need to know about for ad blocking are: block, handle-as-image, and set-image-blocker:

    • block - this action stops + any contact between your browser and any URL patterns that match this + action's configuration. It can be used for blocking ads, but also anything + that is determined to be unwanted. By itself, it simply stops any + communication with the remote server. If this is the only action that + matches for this particular URL, then Privoxy will + display its own BLOCKED page to let you now what has happened. +

    • handle-as-image - + forces Privoxy to treat this URL as if it were + an image. Privoxy knows about common image + types (e.g. GIF), but there are many situations where this does not apply. + So we'll force it. This is particularly important for ad blocking, since + once we can treat it as an image, we can make more intelligent decisisions + on how to handle it. There are some limitations to this though. For + instance, you can't just force an image substituion for an entire HTML page + in most situations. +

    • set-image-blocker - + tells Privoxy what to display in place of + an ad image that has hit a block rule. For this to come into play, + the URL must match a block action somewhere in the configuration. + And, it must also either be of a known image type, or + match an handle-as-image + action. +

      The configuration options on what to display instead of the ad are: +

         pattern - a checkboard pattern, so that an ad + replacement is obvious. This is the default. +

         blank - A very small empty GIF image is displayed. + This is the so-called "invisible" configuration option. +

         http://<URL> - A redirect to any URL of the + user's choosing (advanced usage). +

    The quickest way to adjust any of these settings is with your browser through + the special Privoxy editor at http://config.privoxy.org/show-status + (shortcut: http://p.p/show-status). This + is an internal page, and does not require Internet access. Select the + appropriate "actions" file, and click + "Edit". It is best to put personal or + local preferences in user.action since this is not + meant to be overwritten during upgrades, and will over-ride the settings in + other files. Here you can insert new "actions", and URLs for ad + blocking or other purposes, and make other adjustments to the configuration. + Privoxy will detect these changes automatically.

    A quick and simple step by step example:

    • Right click on the ad image to be blocked, then select + "Copy Link Location" from the + pop-up menu. +

    • Set your browser to + http://config.privoxy.org/show-status +

    • Find user.action in the top section, and click + on "Edit": +

      Figure 1. Actions Files in Use

      +

    • You should have an Actions section labeled +block. + If not, click the "Edit" button just + under the word "Actions". This will bring up a list of all + actions. Find block near the top, and click in the + "Enabled" column, then + "Submit" just below the list. +

    • Now, in the +block actions section, click the + "Add" button, and paste the URL the + browser got from "Copy Link + Location". Remove the http:// at + the beginning of the URL. Then, click + "Submit". +

    • Now go back to the original page, and press SHIFT-Reload + (or flush all browser caches). The image should be gone now. +

    This is a very crude and simple example. There might be good reasons to use a + wildcard pattern match to include potentially similar images from the same + site. For a more extensive explanation of "patterns", and + the entire actions concept, see the Actions + section.

    For advanced users who want to hand edit their config files, you might want + to now go to the Actions Files Tutorial.

    See Also

    +

    http://www.privoxy.org/developer-manual/, + the Privoxy developer manual. +

    Starting PrivoxyTemplatesNote to Upgraders