From ae6beecce49ef10b169c4b843580985430bc698b Mon Sep 17 00:00:00 2001
From: hal9 "Problems" for our purposes, come in two forms: Configuration issues, such as ads that slip through, or sites that
+ don't function properly due to one Privoxy
+ "action" or another being turned "on".
+ "Bugs" in the programming code that makes up
+ Privoxy, such as that might cause a crash.
+ Please send feedback on ads that slipped through, innocent images that were
+ blocked, sites that don't work properly, and other configuration related problem of
+ default.action file, to
+ http://sourceforge.net/tracker/?group_id=11118&atid=460288,
+ the Actions File Tracker. New, improved default.action files may occasionally be made
+ available based on your feedback. These will be announced on the ijbswa-announce
+ list and available from our the files section of
+ our project page. Please report all bugs http://sourceforge.net/tracker/?group_id=11118&atid=111118. Before doing so, please make sure that the bug has not already been submitted
+> Before doing so, please make sure that the bug has not already been submitted
and observe the additional hints at the top of the submit
form.
Please try to verify that it is a Privoxy, 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
+ 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
+> If not using the latest version, the bug may have 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. Please be sure to provide the following information: The exact Privoxy version of the proxy software
+(if you got the source from CVS, please also give the date).
+ The operating system and versions you run
+ Privoxy on, (e.g. Windows
+ XP).
+ The name, platform, and version of the browser
+ you were using (e.g. Internet Explorer v5.5 for Mac).
+ The URL where the problem occurred, or some way for us to duplicate the
+ problem (e.g. http://somesite.example.com?somethingelse=123).
+ Whether your version of Privoxy is one supplied
+ by the developers of Privoxy via SourceForge,
+ or somewhere else.
+ Whether you are using Privoxy in tandem with
+ another proxy such as TOR. If so, please try
+ disabling the other proxy.
+ Whether you are using a personal firewall product. If so, does
+ Privoxy work without it?
+ Any other pertinent information to help identify the problem such as config
+ or log file excerpts (yes, you should have log file entries for each
+ action taken).
+ Please provide your SF login, or email address, in case we
+ need to contact you.
+ The appendix
+ of the Privoxy User Manual also has helpful information
+ on understanding actions, and action debugging. 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
- 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 default.action files will occasionally be made
- available based on your feedback. These will be announced on the ijbswa-announce
- list and available from our the files section of
- our project page. 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!
diff --git a/doc/webserver/developer-manual/copyright.html b/doc/webserver/developer-manual/copyright.html
index 8fe9f30d..ce1e7a5b 100644
--- a/doc/webserver/developer-manual/copyright.html
+++ b/doc/webserver/developer-manual/copyright.html
@@ -77,11 +77,11 @@ NAME="COPYRIGHT"
>9. Privoxy Copyright, License and History Copyright © 2001 - 2004 by Privoxy Developers Copyright © 2001 - 2006 by Privoxy Developers <developers@privoxy.orgijbswa-developers@lists.sourceforge.net> GNU General Public License for
- more details, which is available from the Free Software Foundation, Inc, 59
- Temple Place - Suite 330, Boston, MA 02111-1307, USA. You should have received a copy of the Free Software In the beginning, there was the
+> Along time ago, there was the
Junkbusters
Corporation. It saved many users a lot of pain in the early days of
+>. This 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 Internet
Junkbuster At one time there were two distinct branches: stable and unstable. The
more drastic changes were to be in the unstable branch. These branches
have now been merged to minimize time and effort of maintaining two
- brances.
+ branches.
Copyright © 2001, 2002 by
+> © 2001-2006 by
const char FILENAME_rcs[] = "$Id: developer-manual.sgml,v 2.7 2006/07/18 14:48:50 david__schmidt Exp $";
+>const char FILENAME_rcs[] = "$Id: developer-manual.sgml,v 2.9 2006/09/14 02:30:07 hal9 Exp $";
/*********************************************************************
*
* File : $Source$
*
* Purpose : (Fill me in with a good description!)
*
- * Copyright : Written by and Copyright (C) 2001 the SourceForge
+ * Copyright : Written by and Copyright (C) 2001-2006 the SourceForge
* Privoxy team. http://www.privoxy.org/
*
* Based on the Internet Junkbuster originally written
@@ -2363,8 +2363,9 @@ CLASS="PROGRAMLISTING"
* The GNU General Public License should be included with
* this file. If not, you can view it at
* http://www.gnu.org/copyleft/gpl.html
- * or write to the Free Software Foundation, Inc., 59
- * Temple Place - Suite 330, Boston, MA 02111-1307, USA.
+ * or write to the Free Software Foundation, Inc.,
+ * 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 ,
+ * USA
*
* Revisions :
* $Log$
@@ -2421,14 +2422,14 @@ WIDTH="100%"
CLASS="PROGRAMLISTING"
>#ifndef _FILENAME_H
#define _FILENAME_H
-#define FILENAME_H_VERSION "$Id: developer-manual.sgml,v 2.7 2006/07/18 14:48:50 david__schmidt Exp $"
+#define FILENAME_H_VERSION "$Id: developer-manual.sgml,v 2.9 2006/09/14 02:30:07 hal9 Exp $"
/*********************************************************************
*
* File : $Source$
*
* Purpose : (Fill me in with a good description!)
*
- * Copyright : Written by and Copyright (C) 2001 the SourceForge
+ * Copyright : Written by and Copyright (C) 2001-2006 the SourceForge
* Privoxy team. http://www.privoxy.org/
*
* Based on the Internet Junkbuster originally written
@@ -2450,8 +2451,9 @@ CLASS="PROGRAMLISTING"
* The GNU General Public License should be included with
* this file. If not, you can view it at
* http://www.gnu.org/copyleft/gpl.html
- * or write to the Free Software Foundation, Inc., 59
- * Temple Place - Suite 330, Boston, MA 02111-1307, USA.
+ * or write to the Free Software Foundation, Inc.,
+ * 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 ,
+ * USA
*
* Revisions :
* $Log$
diff --git a/doc/webserver/developer-manual/contact.html b/doc/webserver/developer-manual/contact.html
index c6d655d0..0dae3493 100644
--- a/doc/webserver/developer-manual/contact.html
+++ b/doc/webserver/developer-manual/contact.html
@@ -118,9 +118,96 @@ CLASS="SECT2"
>
8.2. Reporting Problems
8.2.1. Reporting Ads or Other Configuration Problems
8.2. Report Bugs8.2.2. Reporting Bugs
8.4. Report Ads or Other Actions-Related Problems
8.5. Other
8.4. Other9.1. License
Foundation, Inc. 59 Temple Place - Suite 330
+>51 Franklin Street, Fifth Floor
BostonMA 02111-130702110-1301
9.2. History
$Id: developer-manual.sgml,v 2.7 2006/07/18 14:48:50 david__schmidt Exp $
Please note that this document is constantly evolving. This copy represents
- the state at the release of version 3.0.4.
+ the state at the release of version 3.0.5.
You can find the latest version of the this manual at
Warning |
Every significant release of Privoxy has included at least one + package that either had incorrect versions of files, missing files, + or incidental leftovers from a previous build process that gave + unknown numbers of users headaches to try to figure out what was + wrong. PLEASE, make sure you are using pristene sources, and are + following the prescribed process! + |
Please find additional instructions for the source tarball and the individual platform dependent binary packages below. And details @@ -697,15 +727,40 @@ CLASS="FILENAME" > user.action is designed for local preferences. - Make sure this does not get overwritten! +> and user.filter + are designed for local preferences. Make sure these do not get overwritten! + config should not be overwritten either. This + has especially important configuration data in it. + trust should be left in tact as well.
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 :-) +> Other configuration files (default.action, + default.filter and + standard.action) should be installed as the new + defaults, but all previously installed configuration files should be + preserved as backups. This is just good manners :-) These files are + likely to change between releases and contain important new features + and bug fixes.
debchange -v 3.0.4-BETA-1 "New upstream version"debchange -v 3.0.5-BETA-1 "New upstream version"
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/ijbswa/contrib/, cool - and fun ideas from Privoxy users. +> and other + configuration related suggestions to the developers. |
http://www.waldherr.org/junkbuster/, - Stefan Waldherr's version of Junkbuster, from which Privoxy was - derived. +>http://privacy.net/, a useful site + to check what information about you is leaked while you browse the web. | ||||||||||||||||
http://privacy.net/analyze/, a useful site - to check what information about you is leaked while you browse the web. +>http://www.squid-cache.org/, a very popular + caching proxy, which is often used together with Privoxy. | ||||||||||||||||
http://www.squid-cache.org/, a very popular - caching proxy, which is often used together with http://tor.eff.org/, + Privoxy. +>Tor can help anonymize web browsing, + web publishing, instant messaging, IRC, SSH, and other applications. |
Privoxy is developed on: | ||||||||||||||||
> Copyright © 2001 - 2004 by Privoxy Developers +> Copyright © 2001 - 2006 by Privoxy Developers PRIVOXY-Section: (1)Updated: 25 March 2003 Index +Section: (1) Updated: 21 September 2006 Index @@ -13,10 +13,7 @@ privoxy - Privacy Enhancing Proxy SYNOPSIS-privoxy [--help ] [--version ] [--no-daemon ] [--pidfile pidfile ] [--user user[.group] ] [--chroot ] [configfile ] (UNIX) - - -privoxy.exe [configfile ] (Windows) +privoxy [--help ] [--version ] [--no-daemon ] [--pidfile pidfile ] [--user user[.group] ] [--chroot ] [configfile ] OPTIONS@@ -57,8 +54,7 @@ that hierarchy. If the configfile is not specified on the command line, Privoxy will look for a file named -config in the current directory (except on Win32 where -it will try config.txt). If no +config in the current directory . If no configfile is found, Privoxy will fail to start. @@ -66,17 +62,18 @@ fail to start.-Privoxy is a web proxy with advanced filtering -capabilities for protecting privacy, filtering web page content, managing -cookies, controlling access, and removing ads, banners, pop-ups and other -obnoxious Internet junk. Privoxy has a very -flexible configuration and can be customized to suit individual needs and -tastes. Privoxy has application for both -stand-alone systems and multi-user networks. +Privoxy is a +web proxy +with advanced filtering capabilities for protecting +privacy, modifying web page data, managing +cookies, +controlling access, and removing ads, banners, pop-ups and other obnoxious +Internet junk. Privoxy has a very flexible configuration and can be +customized to suit individual needs and tastes. Privoxy has application for +both stand-alone systems and multi-user networks. -Privoxy is based on Internet -Junkbuster (tm). +Privoxy is based on Internet Junkbuster (tm). INSTALLATION AND USAGE@@ -91,6 +88,12 @@ and Mozilla, go through: Edit; View.+For Firefox, go through: Tools; +Options; General; +Connection Settings; +Manual Proxy Configuration. + + For Internet Explorer, go through: Tools; Internet Properties; Connections; LAN Settings. @@ -99,6 +102,8 @@ For Internet Explorer, go through: Tools; The Secure (SSL) Proxy should also be set to the same values, otherwise https: URLs will not be proxied. Note: Privoxy can only proxy HTTP and HTTPS traffic. Do not try it with FTP or other protocols. +HTTPS presents some limitations, and not all features will work with HTTPS +connections. For other browsers, check the documentation. @@ -112,19 +117,19 @@ files. The default configuration files are: config, default.filter, and default.action. user.action should be used for locally defined exceptions to the default rules of -default.action These are all well commented. On Unix +default.action, and user.filter for +locally defined filters. These are well commented. On Unix and Unix-like systems, these are located in -/etc/privoxy/ by default. On Windows, OS/2 and AmigaOS, -these files are in the same directory as the Privoxy -executable. +/etc/privoxy/ by default. -The name and number of configuration files has changed from previous -versions. In fact, the configuration itself is changed and much more -sophisticated. See the user-manual for a complete -explanation of all configuration options and general usage, and notes for -upgrading from Junkbuster and earlier Privoxy -versions. +Privoxy uses the concept of actions +in order to manipulate the data stream between the browser and remote sites. +There are various actions available with specific functions for such things +as blocking web sites, managing cookies, etc. These actions can be invoked +individually or combined, and used against individual URLs, or groups of URLs +that can be defined using wildcards and regular expressions. The result is +that the user has greatly enhanced control and freedom.
The actions list (ad blocks, etc) can also be configured with your
@@ -132,6 +137,11 @@ web browser at http://config.privoxy.org/.<
Privoxy's configuration parameters can also be viewed at
the same page. In addition, Privoxy can be toggled on/off.
This is an internal page, and does not require Internet access.
+
+
+See the User Manual for a detailed
+explanation of installation, general usage, all configuration options, new
+features and notes on upgrading.
See the comments in the configuration files themselves, or the -user-manual -for explanations of the above syntax, and other Privoxy +User Manual +for full explanations of the above syntax, and other Privoxy configuration options. FILES@@ -245,6 +299,7 @@ configuration options. /etc/privoxy/standard.action /etc/privoxy/user.action /etc/privoxy/default.filter + /etc/privoxy/user.filter /etc/privoxy/trust /etc/privoxy/templates/* /var/log/privoxy/logfile @@ -253,7 +308,7 @@ configuration options.Various other files should be included, but may vary depending on platform -and build configuration. More documentation should be included in the local +and build configuration. Additional documentation should be included in the local documentation directory. SIGNALS@@ -272,8 +327,12 @@ automatically.+This is a BETA version of Privoxy. Not +all features are well tested. + + Please see the User Manual on how to contact the -developers for feature requests, reporting problems, and other questions. +developers, for feature requests, reporting problems, and other questions. SEE ALSO@@ -298,10 +357,8 @@ SourceForge. the web-based user interface. Privoxy must be running for this to work. Shortcut: http://p.p/-http://www.privoxy.org/actions/, to submit ``misses'' to the developers. - -http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/ijbswa/contrib/, cool -and fun ideas from Privoxy users. +http://sourceforge.net/tracker/?group_id=11118&atid=460288, to submit ``misses'' and other +configuration related suggestions to the developers. http://www.junkbusters.com/ht/en/cookies.html, an explanation how cookies are used to track web users. @@ -309,16 +366,16 @@ an explanation how cookies are used to track web users. 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 +http://privacy.net/, a useful site to check what information about you is leaked while you browse the web. http://www.squid-cache.org/, a very popular caching proxy, which is often used together with Privoxy. +http://tor.eff.org/, +Tor can help anonymize web browsing, +web publishing, instant messaging, IRC, SSH, and other applications. + http://www.privoxy.org/developer-manual/, the Privoxy developer manual. @@ -326,30 +383,13 @@ the Privoxy developer manual.
- Hal Burgiss (docs) - Jon Foster - Andreas Oesterhelt - David Schmidt (OS/2, Mac OSX ports) - - Johny Agotnes - Rodrigo Barbosa (RPM specfiles) - Moritz Barsnick - Mattes Dolak - Karsten Hopp (Red Hat) - Alexander Lazic - Daniel Leite - Gábor Lipták - Adam Lock (Win32) - Guy Laroche - Haroon Rafique - Roland Rosenfeld (Debian) - Georg Sauthoff (Gentoo) - Thomas Steudten - Joerg Strohmayer (Amiga) - Rodney Stromlund - Sviatoslav Sviridov - Sarantis Paskalis - Stefan Waldherr + Fabian Keil, developer + David Schmidt, developer + + Hal Burgiss + Ian Cummings + Félix Rauch + Roland Rosenfeld@@ -360,7 +400,7 @@ the Privoxy developer manual. -Copyright (C) 2001 - 2003 by Privoxy Developers <developers@privoxy.org> +Copyright (C) 2001 - 2006 by Privoxy Developers <ijbswa-developers@lists.sourceforge.net> Some source code is based on code Copyright (C) 1997 by Anonymous Coders @@ -381,14 +421,14 @@ This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for -more details, which is available from the Free Software Foundation, Inc, 59 -Temple Place - Suite 330, Boston, MA 02111-1307, USA. +more details, which is available from the Free Software Foundation, Inc, +51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software -Foundation, Inc. 59 Temple Place - Suite 330 -Boston, MA 02111-1307 +Foundation, Inc. 51 Franklin Street, Fifth Floor +Boston, MA 02110-1301 USA
@@ -417,6 +457,6 @@ USA
This document was created by
man2html,
using the manual pages. Project Index Page v3.0.3Project Index Page v3.0.5Privoxy is a web proxy with advanced filtering - capabilities for protecting privacy, modifying web page content, managing - cookies, controlling access, and removing ads, banners, pop-ups and other - obnoxious Internet junk. Privoxy has a very - flexible configuration and can be customized to suit individual needs and - tastes. Privoxy has application for both - stand-alone systems and multi-user networks. Privoxy is based on Internet - Junkbuster (tm). Privoxy is a + web proxy + with advanced filtering capabilities for protecting + privacy, modifying web page data, managing + cookies, + controlling access, and removing ads, banners, pop-ups and other obnoxious + Internet junk. Privoxy has a very flexible configuration and can be + customized to suit individual needs and tastes. Privoxy has application for + both stand-alone systems and multi-user networks.Privoxy is based on Internet Junkbuster (tm).
Quickstart after installationDocumentationDocumentation More informationMore information
Copyright © 2001 - 2004 by Privoxy Developers +> Copyright © 2001 - 2006 by Privoxy Developers | Privoxy 3.0.4 User Manual | Privoxy 3.0.5 User Manual|||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
There are three action files included with Privoxy's array of features. So it is - a set of broad rules that should work reasonably well for users everywhere. + a set of broad rules that should work reasonably well as-is for most users. This is the file that the developers are keeping updated, and making available to users. + The user's preferences as set in standard.action, + e.g. either Cautious (the default), + Medium, or Advanced (see + below). Edit Set to Cautious Set to Medium Set to Advanced + These have increasing levels of aggressiveness and have no influence on your browsing unless - you select them explicitly in the editorand have no + influence on your browsing unless you select them explicitly in the + editor. It is not recommend - to edit this file. +>. A default installation should be pre-set to + Cautious (versions prior to 3.0.5 were set to + Medium). New users should try this for a while before + adjusting the settings to more aggressive levels. + The Edit button allows you to turn each + action on/off individually for fine-tuning. The Cautious + button changes the actions list to low/safe settings which will activate + a minimal set of Privoxy's features, and subsequently there will be + less of a chance for accidental problems. The Medium + button sets the list to a medium level of ad blocking and a low level set of + privacy features. The Advanced button + sets the list to a high level of ad blocking and medium level of + privacy. See the chart below. The latter three buttons over-ride + any changes via with the Edit button. More + fine-tuning can be done in the lower sections of this internal page. + It is not recommend to edit the standard.action file + itself. The default profiles, and their associated actions, as pre-defined in @@ -170,7 +256,7 @@ CLASS="FILENAME" > | yes | mediumyes | highyes | high|||||||||||||
yes | yes | yes | ||||||||||||||
GIF de-animation | no | Referer forging | Ad-filtering by linkyes | noCookie handling | Pop-up killingnone | blocks onlysession-only | blocks onlykill | all|||||||||
Pop-up killing | Privacy Featuresunsolicited | lowunsolicited | mediumall | medium/high|||||||||||||
Fast redirects | Cookie handlingno | noneno | session-onlyyes | kill|||||||||||||
HTML taming | Referer forgingyes | noJavaScript taming | GIF de-animationyes | noWeb-bug killing | Fast redirectsyes | noyes | noFun text replacements | HTML tamingno | yesImage tag reordering | JavaScript tamingno | yesAd-filtering by link | Web-bug killingno | yesDemoronizer | Image tag reorderinghttp://config.privoxy.org/show-status..
+ The over-riding principle when applying actions, is that the last action that
+ matches a given URL, wins. The broadest, most general rules go first
+ (defined in default.action),
+ followed by any exceptions (typically also in
+ default.action), which are then followed lastly by any
+ local preferences (typically in user.action).
+ Generally, user.action has the last word.
+ An actions file typically has multiple sections. If you want to use
, like cookie suppression
or script disabling, may render some sites unusable that rely on these
techniques to work properly. Finding the right mix of actions is not always easy and
- certainly a matter of personal taste. In general, it can be said that the more
+ certainly a matter of personal taste. And, things can always change, requiring
+ refinements in the configuration. In general, it can be said that the more
"aggressive" sites you
will have to make later. If, for example, you want to crunch all cookies per
default, you'll have to make exceptions from that rule for sites that you
- regularly use and that require cookies for actually useful puposes, like maybe
+ regularly use and that require cookies for actually useful purposes, like maybe
your bank, favorite shop, or newspaper. We have tried to provide you with reasonable rules to start from in the
@@ -627,7 +718,7 @@ CLASS="SECT2"
> "Medium" If you prefer plain text editing to GUIs, you can of course also directly edit the - the actions files. Look at default.action which is richly - commented. which is richly commented with many + good examples.both actions to apply. actions to apply. And there may well be
+ cases where you will want to combine actions together. Such a section then
+ might look like:
You can trace this process for any given URL by visiting http://config.privoxy.org/show-url-info. More detail on this is provided in the Appendix, Examples and more detail on this is provided in the Appendix, Anatomy of an Action. Troubleshooting: Anatomy of an Action section."patterns"
- to determine what actions might apply to which sites and pages your browser
- attempts to access. These actions might apply to which sites and
+ pages your browser attempts to access. These "patterns" use wild card type
- use wild
+ card type pattern matching to achieve a high degree of
+> matching to achieve a high degree of
flexibility. This allows one expression to be expanded and potentially match
against many similar patterns. be included in the pattern. This is assumed already! The pattern matching syntax is different for the domain and path parts of + the URL. The domain part uses a simple globbing type matching technique, + while the path part uses a more flexible + "Regular + Expressions (PCRE)" based syntax. www.example.com,
- regardless of which document on that server is requested.
+ regardless of which document on that server is requested. So ALL pages in
+ this domain would be covered by the scope of this action. Note that a
+ simple example.com is different and would NOT match.
8.4.1. The Domain Pattern.example. - (Correctly speaking: It matches any FQDN that contains . + And, by the way, also included would be any files or documents that exist + within that domain since no path limitations are specified. (Correctly + speaking: It matches any FQDN that contains example as a domain.) +> as + a domain.) This might be www.example.com, + news.example.de, or + www.example.net/cgi/testing.pl for instance. All these + cases are matched. Additionally, there are wild-cards that you can use in the domain names - themselves. They work pretty similar to shell wild-cards: "*" - stands for zero or more arbitrary characters, represents zero or more arbitrary characters (this is + equivalent to the + "Regular + Expression" based syntax of ".*"), + "?" stands for - any single character, you can define character classes in square - brackets and all of that can be freely mixed: represents any single character (this is equivalent to the + regular expression syntax of a simple "."), and you can define + "character classes" in square brackets which is similar to + the same regular expression technique. All of this can be freely mixed:While flexibile, this is not the sophistication of full regular expression based syntax. 8.4.2. The Path PatternPrivoxy uses Perl compatible regular expressions +> uses Perl compatible (PCRE) + "Regular + Expression" based syntax (through the PCRE library) for - matching the path. There is an exactly this capitalization.
There are many, many good examples to be found in default.action, + and more tutorials below in Appendix on regular expressions. - There are three classes of actions:
Later defined actions always over-ride earlier ones. So exceptions to any rules you make, should come in the latter part of the file (or - in a file that is processed later when using multiple actions files). For - multi-valued actions, the actions are applied in the order they are specified. - Actions files are processed in the order they are defined in - user.action). For multi-valued actions, the actions + are applied in the order they are specified. Actions files are processed in + the order they are defined in config (the default installation has three actions - files). It also quite possible for any given URL pattern to match more than - one pattern and thus more than one set of actions! (the default + installation has three actions files). It also quite possible for any given + URL pattern to match more than one pattern and thus more than one set of + actions! Last match wins. The list of valid Typical use: Block ads or other obnoxious content Requests for URLs to which this action applies are blocked, i.e. the requests are not - forwarded to the remote server, but answered locally with a substitute page or image, - as determined by the Requests for URLs to which this action applies are blocked, i.e. the + requests are trapped by Privoxy and the requested URL is never retrieved, + but is answered locally with a substitute page or image, as determined by + the handle-as-image - and , + set-image-blocker, and + handle-as-empty-document actions. + The |
# Let the browser revalidate cached documents without being tracked across sessions -{+hide-if-modified-since {-1} \ +{+hide-if-modified-since {-60} \ +overwrite-last-modified {randomize} \ +crunch-if-none-match} /
+fast-redirects{simple-check}
+fast-redirects{check-decoded-url}{ +fast-redirects{simple-check} } + .example.com + + { +fast-redirects{check-decoded-url} } + another.example.com/testing |
When used in its negative form, - and without parameters, filtering is completely disabled. + and without parameters, all filtering is completely disabled.
This is very powerful feature, and "rolling your own""Rolling your own" - filters requires a knowledge of regular expressions and HTML. + filters requires a knowledge of + "Regular + Expressions" and + "HTML". + This is very powerful feature, and potentially very intrusive. Use + with caution.
The amount of data that can be filtered is limited to the @@ -2940,7 +3324,7 @@ HREF="config.html" data, and all pending data, is passed through unfiltered.
Inadequate MIME types, such as zipped files, are not filtered at all. +> Inappropriate MIME types, such as zipped files, are not filtered at all. (Again, only text-based types except plain text). Encrypted SSL data (from HTTPS servers) cannot be filtered either, since this would violate the integrity of the secure transaction. In some situations it might @@ -2948,13 +3332,13 @@ HREF="config.html" by defining appropriate -filter sections. +> exceptions.
At this time, Privoxy cannot (yet!) uncompress compressed
+> cannot uncompress compressed
documents. If you want filtering to work on all documents, even those that
would normally be sent compressed, use the
+filter{frameset-borders} # Give frames a border and make them resizable
+filter{frameset-borders} # Give frames a border and make them resizeable
+filter{quicktime-kioskmode} # Make Quicktime movies saveable+filter{quicktime-kioskmode} # Make Quicktime movies savable
Mark URLs as belonging to images (so they'll be replaced by imagee Mark URLs as belonging to images (so they'll be replaced by images if they get blockedif they do get blocked)
, rather than HTML pages)# Let the browser revalidate without being tracked across sessions -{+hide-if-modified-since {-1}\ +{+hide-if-modified-since {-60}\ +overwrite-last-modified {randomize}\ +crunch-if-none-match} /Privoxy relays HTTPS traffic without seeing - the decoded content. Websites can leverage this limitation to circumvent Privoxy's + the decoded content. Websites can leverage this limitation to circumvent Privoxy's filters. By specifying an invalid port range you can disable HTTPS entirely. If you plan to disable SSL by default, consider enabling
# Let the browser revalidate without being tracked across sessions -{+hide-if-modified-since {-1}\ +{+hide-if-modified-since {-60}\ +overwrite-last-modified {randomize}\ +crunch-if-none-match} /Notes:
This action is useful to replace whole documents with your own - ones. For that to work, they have to be available on another server, - and both should resolve. +> This action is useful to replace whole documents with ones of your + choosing. This can be used to enforce safe surfing, or just as a simple + convenience.
You can do the same by combining the actions @@ -5628,7 +6015,7 @@ HREF="actions-file.html#BLOCK"
crunch-outgoing-cookies - block-as-image = +block +handle-as-image + +block-as-image = +block +handle-as-image mercy-for-cookies = -crunch-all-cookies -session-cookies-only
crunch-outgoing-cookies
- block-as-image = +block +handle-as-image
+ +block-as-image = +block +handle-as-image
mercy-for-cookies = -crunch-all-cookies -session-cookies-onlyblock-as-image+block-as-image alias defined above. (We could of
course just as well use # Known ad generators:
#
-{ block-as-image }
+{ +block-as-image }
ar.atwola.com
.ad.doubleclick.net
.ad.*.doubleclick.net
@@ -7571,7 +7962,7 @@ CLASS="SECT3"
>8.7.2. user.action
{ allow-all-cookies } -sourceforge.net -sunsolve.sun.com -.slashdot.org -.yahoo.com -.msdn.microsoft.com -.redhat.comfilter } -.your-home-banking-site.comblock } -www.example.com/nasty-ads/sponsor.gif -another.popular.site.net/more/junk/here/
{ +block-as-image } -.doubleclick.net -/Realmedia/ads/ -ar.atwola.com/Privoxy - that is causing the problem or not.
{ allow-ads } -.sourceforge.net -.slashdot.org -.osdn.net
{ handle-as-text } -/.*\.sh$
Since Short cuts. Turn off, then on:
14.4. Anatomy of an Action14.4. Troubleshooting: Anatomy of an ActionThe way
Another easy troubleshooting step to try is if you have done any + customization of your installation, revert back to the installed + defaults and see if that helps. There are times the developers get complaints + about one thing or another, and the problem is more related to a customized + configuration issue.
Privoxy
The first listing - is any matches for the standard.action file. No hits at - all here on "standard". Then next is "default", or - our default.action file. The large, multi-line listing, - is how the actions are set to match for all URLs, i.e. our default settings. - If you look at your file. The large, multi-line + listing, is how the actions are set to match for all URLs, i.e. our default + settings. If you look at your "actions" file, this would be the section - just below the file, this would be the + section just below the "aliases" section near the top. This will apply to - all URLs as signified by the single forward slash at the end of the listing - -- section near the top. This + will apply to all URLs as signified by the single forward slash at the end + of the listing -- "/"" / ".
But we can define additional actions that would be exceptions to these general - rules, and then list specific URLs (or patterns) that these exceptions would - apply to. Last match wins. Just below this then are two explicit matches for - But we have defined additional actions that would be exceptions to these general + rules, and then we list specific URLs (or patterns) that these exceptions + would apply to. Last match wins. Just below this then are two explicit + matches for ".google.com". The first is negating our previous cookie setting, - which was for . The first is negating our previous + cookie setting, which was for off any - any "www.google.com". So, apparently, we have these two actions - defined somewhere in the lower part of our or "mail.google.com". But it would not + match "www.google.de"! So, apparently, we have these two actions + defined as exceptions to the general rules at the top somewhere in the lower + part of our default.action - file, and file, and + "google.com" is referenced somewhere in these latter - sections.
is referenced somewhere in these latter sections.Then, for our user.action file, we again have no hits. So there is nothing google-specific that we might have added to our own, local - configuration.
default.action. + user.action typically has the last word. This is the + best place to put hard and fast exceptions,And finally we pull it all together in the bottom section and summarize how
{ +block +handle-as-image } - .ad.doubleclick.net - - { +block +handle-as-image } +> { +block } ad*. + { +block } + .ad. + { +block +handle-as-image } - .doubleclick.net
We'll just show the interesting part here, the explicit matches. It is - matched three different times. Each as an We'll just show the interesting part here - the explicit matches. It is + matched three different times. Two "+block" sections, + and a "+block +handle-as-image", which is the expanded form of one of our aliases that had been defined as: "+imageblock""+block-as-image". (. The custom alias "+imageblock" just simplifies the process and make - it more readable.
"+block-as-image" just + simplifies the process and make it more readable.One last example. Let's try "/ads" in our configuration! But we did not want this at all! Now we see why we get the - blank page. We could now add a new action below this that explicitly - Privoxy is told + to treat the block as if it were an image. But this is, of course, all wrong. + We could now add a new action below this (or better in our own + user.action file) that explicitly + un blocks ( blocks ( + "{-block}") paths with - "adsl" in them (remember, last match in the configuration wins). - There are various ways to handle such exceptions. Example:
in them (remember, last match in the configuration + wins). There are various ways to handle such exceptions. Example:
Now the page displays ;-) Be sure to flush your browser's caches when - making such changes. Or, try using Now the page displays ;-) + Remember to flush your browser's caches when making these kinds of changes to + your configuration to insure that you get a freshly delivered page! Or, try + using Shift+Reload.
That actually was very telling and pointed us quickly to where the problem +> That actually was very helpful and pointed us quickly to where the problem was. If you don't get this kind of match, then it means one of the default - rules in the first section is causing the problem. This would require some - guesswork, and maybe a little trial and error to isolate the offending rule. - One likely cause would be one of the default.action is causing + the problem. This would require some guesswork, and maybe a little trial and + error to isolate the offending rule. One likely cause would be one of the + "{+filter}" actions. These - tend to be harder to troubleshoot. Try adding the URL for the site to one of - aliases that turn off "+filter" actions. + These tend to be harder to troubleshoot. + 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 @@ -1954,14 +1995,20 @@ CLASS="SCREEN" > |
This would turn off all filtering for that site. This would probably be most - appropriately put in This would turn off all filtering for these sites. This is best + put in user.action, for local site - exceptions.
Images that are inexplicably being blocked, may well be hitting the - "+filter{banners-by-size}" rule, which assumes - that images of certain sizes are ad banners (works well most of the time - since these tend to be standardized).
+ rule, which assumes + that images of certain sizes are ad banners (works well + most of the time since these tend to be standardized)."{ fragile }" is an alias that disables most + actions that are the most likely to cause trouble. This can be used as a + last resort for problem sites.
{ fragile } + # Handle with care: easy to break + mail.google. + mybank.example.com |
Remember to flush caches! Note that the + mail.google reference lacks the TLD portion (e.g. + "{fragile}" is an alias that disables most actions. This can be - used as a last resort for problem sites. Remember to flush caches! If this - still does not work, you will have to go through the remaining actions one by - one to find which one(s) is causing the problem.
".com". This will effectively match any TLD with + google in it, such as mail.google.de, + just as an example.+ If this still does not work, you will have to go through the remaining + actions one by one to find which one(s) is causing the problem.
Examples: @@ -619,22 +618,6 @@ CLASS="LITERAL" >", please
When development goes modular and multi-user, the blocker, filter, and - per-user config will be stored in subdirectories of "confdir". - For now, the configuration directory structure is flat, except for - confdir/templates, where the HTML templates for CGI - output reside (e.g. Privoxy's 404 error page). -
Specifies:The trust file to use +> The name of the trust file to use
The entire trust mechanism is turned off. +> The entire trust mechanism is disabled.
Or, you can designate sites as + character. The effect is that access to untrusted sites will be granted -- but only if a link from this - trusted referrer was used. The link target will then be added to the - "trustfile" so that future, direct accesses will be granted. - Sites added via this mechanism do not become trusted referrers themselves - (i.e. they are added with a so that future, direct accesses will be + granted. Sites added via this mechanism do not become trusted referrers + themselves (i.e. they are added with a ~ designation). + There is a limit of 512 such entries, after which new entries will not be + made.
If you use the http://www.multiproxy.org/anon_list.htm) - Or to use a caching proxy to speed up browsing. Or chaining to a parent + through an anonymous public proxy. Or to use a caching proxy to speed up browsing. Or chaining to a parent proxy may be necessary because the machine that PrivoxyPrivoxy Configuration
All The syntax of all configuration files has remained the same throughout the
3.x series. There have been enhancements, but no changes that would preclude
- the use of any configuration file from one version to the next. All files use the # in front of an otherwise
valid configuration line to prevent it from being interpreted is called "commenting
- out" that line. The actions files and filter files
can use Perl style Starting Privoxy The operating system and verions you run
+> The operating system and versions you run
Privoxyappendix
- of the user manual also has helpful information
on understanding Templates6.1. Controlling Privoxy with Your Web Browser
6.1. Controlling Privoxy with Your Web Browser Privoxy Menu
▪ Documentation
@@ -389,7 +383,13 @@ CLASS="FILENAME"
> Starting PrivoxyPrivoxy 3.0.4 User Manual Privoxy 3.0.5 User Manual Privoxy's Template FilesPrivoxy Copyright, License and History Privoxy Copyright, License and History
Copyright © 2001 - 2006 by Privoxy Developers 12.1. License
GNU General Public License for - more details, which is available from the Free Software Foundation, Inc, 59 - Temple Place - Suite 330, Boston, MA 02111-1307, USA.
You should have received a copy of the Free Software
Foundation, Inc. 59 Temple Place - Suite 330
+>51 Franklin Street, Fifth Floor
BostonMA 02111-130702110-1301
12.3. Authors
Current Developement Team:
Current Privoxy Team: Fabian Keil
- David Schmidt
-
-Current Contributors:
-
- Johny Agotnes
- Moritz Barsnick
+> Fabian Keil, developer
+ David Schmidt, developer
+
Hal Burgiss
- Mattes Dolak
- Roland Rosenfeld
Former Project Developers and Contributors:
Former Privoxy Team Members:
+> Johny Agotnes
Rodrigo Barbosa
+ Moritz Barsnick
Brian Dessent
Jon Foster
Karsten Hopp
@@ -282,6 +277,7 @@ CLASS="LITERALLAYOUT"
Gábor Lipták
Adam Lock
Guy Laroche
+ Mark Martinec
Andreas Oesterhelt
Haroon Rafique
Georg Sauthoff
@@ -292,14 +288,8 @@ CLASS="LITERALLAYOUT"
Sarantis Paskalis
Stefan Waldherr
Based in part on code originally developed by:
Junkbusters Corp.
- Anonymous Coders
Thanks to the many people who have tested Privoxy, reported bugs, or made - suggestions. These include (in alphabetical order):
Thanks to the many people who have tested Privoxy, reported bugs, made + suggestions or contributed in some way. These include (in alphabetical order): Ken Arromdee
@@ -308,19 +298,30 @@ CLASS="LITERALLAYOUT"
Andrew J. Caines
Clifford Caoile
Michael T. Davis
- Brian Dessent
+ Mattes Dolak
+ Ulrich Drepper
Peter E
Aaron Hamid
Magnus Holmgren
Don Libes
Paul Lieverse
+ Jindrich Makovicka
David Mediavilla
Oliver Stoeneberg
Roberto Ragusa
Maynard Riley
Bart Schelstraete
+ Bobby G. Vinyard
Darren Wiebe
+ Jörg Weinmann
+ Oliver Yeoh
Jamie Zawinski
Privoxy is based in part on code originally developed by:
Junkbusters Corp.
+ Anonymous Coders
If you are new to regular expressions, you might want to take a look at +> If you are new to + "Regular + Expressions", you might want to take a look at the Appendix on regular expressions
\1
is - a backreference to the first parenthesis just like $1 above, @@ -679,7 +688,7 @@ CLASS="EMPHASIS" >pattern, a backslash indicates - a backreference, whereas in theremoves code that causes new windows to be opened with undesired properties, such as being - full-screen, non-resizable, without location, status or menu bar etc. + full-screen, non-resizeable, without location, status or menu bar etc.
Most cookies are set in the HTTP dialogue, where they can be intercepted +> Most cookies are set in the HTTP dialog, where they can be intercepted by the
Technical note: The filter works by redefining the window.open JavaScript function to a dummy function during the loading and rendering phase of each - HTML page access, and restoring the function afterwards. + HTML page access, and restoring the function afterward.
$Id: user-manual.sgml,v 2.17 2006/09/05 13:25:12 david__schmidt Exp $
The User ManualPrivoxy User Manual gives users information on how to install, configure and use PrivoxyPrivoxy.
Privoxy is a web proxy with advanced filtering - capabilities for protecting privacy, modifying web page data, managing - cookies, controlling access, and removing ads, banners, pop-ups and other - obnoxious Internet junk. Privoxy has a very - flexible configuration and can be customized to suit individual needs and - tastes. Privoxy has application for both - stand-alone systems and multi-user networks.
Privoxy is a + web proxy + with advanced filtering capabilities for protecting + privacy, modifying web page data, managing + cookies, + controlling access, and removing ads, banners, pop-ups and other obnoxious + Internet junk. Privoxy has a very flexible configuration and can be + customized to suit individual needs and tastes. Privoxy has application for + both stand-alone systems and multi-user networks.Privoxy is based on Internet - Junkbuster (tm).
Privoxy is based on Internet Junkbuster (tm). You can find the latest version of the User ManualPrivoxy User Manual at
RPMs can be installed with rpm -Uvh privoxy-3.0.4-1.rpmrpm -Uvh privoxy-3.0.5-1.rpm, and will use ntsysv, or similar methods. Note that SuSE will -automatically start Privoxy in the boot process.
, or similar methods.If you have problems with failed dependencies, try rebuilding the SRC RPM: rpm --rebuild privoxy-3.0.4-1.src.rpmrpm --rebuild privoxy-3.0.5-1.src.rpm. This will use your locally installed libraries and RPM version.
Privoxy in.
Version 3.0.4 introduces full Version 3.0.4 introduced full Windows service
@@ -292,7 +291,7 @@ CLASS="APPLICATION"
command: services.msc If you do not take the manual step
+>. If you do not take the manual step
of modifying Privoxy's, the
documentation is in /usr/share/doc/privoxy-3.0.4/usr/share/doc/privoxy-3.0.5
and the Log directory is in tar xzvf privoxy-3.0.4-beta-src* [.tgz or .tar.gz]
- cd privoxy-3.0.4-beta
tar xzvf privoxy-3.0.5-beta-src* [.tgz or .tar.gz]
+ cd privoxy-3.0.5-beta
This documentation is included with the current beta version of +> This documentation is included with the current BETA version of Privoxy, v.3.0.4, +>, v.3.0.5, 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 a new version is currently nearing completion, and includes significant changes and enhancements over earlier versions. .
Since this is a beta version, not all new features are well tested. This
+> Since this is a BETA version, not all new features are well tested. This
documentation may be slightly out of sync as a result (especially with
CVS sources). And there 1.1. Features In addition to the core
- features of ad blocking and cookie management,
+ features of ad blocking and
+ cookie management,
PrivoxyPrivoxy 3.0.4 User Manual
Privoxy as HTTP and - HTTPS (SSL) proxy by setting the proxy configuration for address of + HTTPS (SSL) proxy + by setting the proxy configuration for address of 127.0.0.1Privoxy to manage cookies, you should - remove any currently stored cookies too. +> to manage + cookies, + you should remove any currently stored cookies too.
If you experience ads that slipped through, innocent images that are +> If you experience ads that slip through, innocent images that are blocked, or otherwise feel the need to fine-tune Privoxy's behaviour, take a look at the behavior, take a look at the actions files. As a quick start, you might @@ -205,10 +220,10 @@ TARGET="_top" CLASS="QUOTE" >"Anatomy of an +>Troubleshooting: Anatomy of an Action" has hints how to debug actions that +> has hints how to understand and debug actions that "misbehave"
For easy access to Privoxy's most important controls, drag the provided +> For easy access to Privoxy's most important controls, drag the provided Bookmarklets
@@ -825,10 +843,7 @@ VALIGN="top" WIDTH="33%" ALIGN="right" VALIGN="top" ->Starting PrivoxyBefore launching Privoxy as a HTTP and HTTPS proxy. The default is +> as a HTTP and HTTPS (SSL) + proxy. The default is 127.0.0.1 (or localhost) for the proxy address, and port 8118 (earlier versions - used port 8000). This is the one configuration step that must be done!
that must be done! Please note that Figure 2. Proxy Configuration (Mozilla)Figure 2. Proxy Configuration Showing
+ Mozilla/Netscape HTTP and HTTPS (SSL) Settings
- |_
- -> Options
- |_
- -> General
- |_
- -> Connection Settings
- |_
- -> Manual Proxy Configuration
With Edit
- |_
- -> Preferences
- |_
- -> Advanced
- |_
- -> Proxies
- |_
- -> HTTP Proxy
For Internet ExplorerInternet Explorer v.5-6:
Tools
- |_
- -> Internet Properties
- |_
- Internet Options -> Connections
- |_
- -> LAN Settings
+
After doing this, flush your browser's disk and memory caches to force a - re-reading of all pages and to get rid of any ads that may be cached. You - are now ready to start enjoying the benefits of using + re-reading of all pages and to get rid of any ads that may be cached. Remove + any cookies, + if you want Privoxy to manage that. You are now + ready to start enjoying the benefits of using Privoxy5.1. Red Hat and Conectiva5.1. Red Hat, Fedora and Conectiva
We use a script. Note that Red Hat does not start Privoxy upon booting per - default. It will use the file A default Red Hat installation may not start Privoxy upon boot. It will use + the file /etc/privoxy/config as - its main configuration file.
as its main configuration + file.
Or ...
# service privoxy start |
We use a script. Note that Debian starts Privoxy upon booting per +> We use a script. Note that Debian typically starts Privoxy upon booting per default. It will use the file 5.4. Windows
Click on the Privoxy Icon to start Click on the Privoxy Icon to start Privoxy. If no configuration file is @@ -357,15 +412,24 @@ CLASS="APPLICATION" CLASS="FILENAME" >config.txt. Note that Windows will - automatically start Privoxy when the system starts if you chose that option + automatically start Privoxy when the system starts if you chose that option when installing.
Privoxy can run with full Windows service functionality. - On Windows only, the Privoxy program has two new command line arguments - to install and uninstall Privoxy as a service. See the + On Windows only, the Privoxy program has two new command line arguments + to install and uninstall Privoxy as a service. See the Windows Installation @@ -433,7 +497,10 @@ NAME="START-MACOSX" CLASS="APPLICATION" >Privoxy is configured to - start automatically when the system restarts. To start Privoxy by hand, + start automatically when the system restarts. To start Privoxy manually, double-click on the StartPrivoxy.command--user option, - chroot to that user's home directory, i.e. make the kernel pretend to the Privoxy + chroot to that user's home directory, i.e. make the kernel pretend to the Privoxy process that the directory tree starts there. If set up carefully, this can limit - the impact of possible vulnerabilities in Privoxy to the files contained in that hierarchy. + the impact of possible vulnerabilities in Privoxy to the files contained in that hierarchy. Unix only.
On MS Windows only there are two addition - options to allow only there are two additional + command-line options to allow Privoxy to install and @@ -806,10 +879,7 @@ ACCESSKEY="N" WIDTH="33%" ALIGN="left" VALIGN="top" ->Quickstart to Using PrivoxyAll
Mulitiple Multiple filter files can now be specifed in can now be specified in config. This allows for locally defined filters that can be maintained separately from the filters as - supplied by the developers. + supplied by the developers, i.e. default.filter.
Actions files problems and suggestions are now being directed to: Actions files problems and suggestions are now being directed to: + http://sourceforge.net/tracker/?group_id=11118&atid=460288
In addition, there are various bug fixes and significant enhancements, including - error pages should no longer be cached if the problem is fixed, better DNS - error handling, and various logging improvements. +> In addition, there are numerous bug fixes and significant enhancements, + including error pages should no longer be cached if the problem is fixed, + much better DNS error handling, and various logging improvements. +
The default actions setting is now Cautious. Previous + releases had a default setting of Medium. Experienced + users may want to adjust this, as it is fairly conservative by Privoxy + standards and past practices. See http://config.privoxy.org/edit-actions-list?f=default. New users + should try the default settings for a while before turning up the volume.
- On the other hand, some installers may not overwrite any existing configuration + On the other hand, other installers may not overwrite any existing configuration files, thinking you will want to do that. You may want to manually check your saved files against the newer versions to see if the improvements have merit, or whether there are new options that you may want to consider. @@ -414,15 +440,42 @@ HREF="actions-file.html#FAST-REDIRECTS" >fast-redirects - which has changed syntax, and may require adjustments to local configs. + which has changed syntax, and will require adjustments to local configs, + such as user.action. You must reference the new + syntax:
{ +fast-redirects{check-decoded-url} } + .example.com + mybank.com + .google. |
The jarfile, cookie logger, is off by default now. +>, + cookie logger, is off by default now.