Privoxy Configuration

Note that several of the features described above are disabled by default + in Privoxy 3.0.7 beta and later. + Check the + configuration file to learn why + and in which cases it's safe to enable them again.

6.2. Configuration Files Overview

For Unix, *BSD and Linux, all configuration files are located in Privoxy executable. The name - and number of configuration files has changed from previous versions, and is - subject to change as development progresses.

executable. The installed defaults provide a reasonable starting point, though some settings may be aggressive by some standards. For the time being, the @@ -286,22 +304,24 @@ CLASS="FILENAME" >

default.action (the main actions file) - is used to define which match-all.action is used to define which "actions" relating to banner-blocking, images, pop-ups, - content modification, cookie handling etc should be applied by default. It also defines many - exceptions (both positive and negative) from this default set of actions that enable - Privoxy to selectively eliminate the junk, and only the junk, on - as many websites as possible. +> + relating to banner-blocking, images, pop-ups, content modification, cookie handling + etc should be applied by default. It should be the first actions file loaded. +

default.action defines many exceptions (both positive and negative) + from the default set of actions that's configured in match-all.action. + It should be the second actions file loaded and shouldn't be edited by the user.

Multiple actions files may be defined in config. These are processed in the order they are defined. Local customizations and locally - preferred exceptions to the default policies as defined in + preferred exceptions to the default policies as defined in default.actionmatch-all.action (which you will most probably want - to define sooner or later) are probably best applied in - user.action, where you can preserve them across - upgrades. standard.action is for - Privoxy's internal use. +>, + where you can preserve them across upgrades. The file isn't installed by all + installers, but you can easily create it yourself with a text editor.

@@ -346,9 +359,9 @@ TARGET="_top" >

default.filter "Filter files" (the filter @@ -356,12 +369,31 @@ HREF="filter-file.html" >) can be used to re-write the raw page content, including viewable text as well as embedded HTML and JavaScript, and whatever else lurks on any given web page. The filtering jobs are only pre-defined here; - whether to apply them or not is up to the actions files. + whether to apply them or not is up to the actions files. + default.filter includes various filters made + available for use by the developers. Some are much more intrusive than + others, and all should be used with caution. You may define additional + filter files in config as you can with + actions files. We suggest user.filter for any + locally defined filters or customizations.

The syntax of the configuration and filter files may change between different + Privoxy versions, unfortunately some enhancements cost backwards compatibility. +

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 default.filter +> The actions files and filter files can use Perl style regular expressionsold listening address.

While under development, the configuration content is subject to change. - The below documentation may not be accurate by the time you read this. - Also, what constitutes a "default" setting, may change, so - please check all your configuration files on important issues.

6. Privoxy Configuration

6.1. Controlling Privoxy with Your Web Browser

Privoxy Menu

6.2. Configuration Files Overview