6.1. Controlling Privoxy with Your Web Browser

Privoxy's user interface can be reached through the special +>'s user interface can be reached through the special URL http://p.p/), +>), which is a built-in page and works without Internet access. - You will see the following section:

Privoxy Menu

▪ Documentation @@ -211,35 +214,26 @@ CLASS="APPLICATION" CLASS="APPLICATION" >Privoxy configuration. The actions - file, and other configuration files, are explained in detail below.

"Toggle Privoxy On or Off" is handy for sites that might +> is handy for sites that might have problems with your current actions and filters. You can in fact use it as a test to see whether it is Privoxy +> causing the problem or not. Privoxy continues +> continues to run as a proxy in this case, but all manipulation is disabled, i.e. Privoxy acts like a normal forwarding proxy. There - is even a toggle Bookmarklet offered, so - that you can toggle Privoxy with one click from - your browser.

acts like a normal forwarding proxy.

Note that several of the features described above are disabled by default in /etc/privoxy/ by default. For MS Windows, OS/2, and - AmigaOS these are all in the same directory as the + AmigaOS these are all in the same directory as the Privoxy

The installed defaults provide a reasonable starting point, though +> The installed defaults provide a reasonable starting point, though some settings may be aggressive by some standards. For the time being, the principle configuration files are:

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 +>. These + are processed in the order they are defined. Local customizations and locally + 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 only 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.
- There is also a web based editor that can be accessed from +> There is also a web based editor that can be accessed from http://p.p/show-status) for the - various actions files. + various actions files.
) 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 +> 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 +> as you can with actions files. We suggest user.filter for any +> 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. @@ -421,12 +407,12 @@ CLASS="LITERAL" valid configuration line to prevent it from being interpreted is called "commenting out" that line. Blank lines are ignored.

The actions files and filter files +> The actions files and filter files can use Perl style regular expressions for - maximum flexibility.

After making any changes, there is no need to restart Privoxy detects such changes +> detects such changes automatically. Note, however, that it may take one or two additional requests for the change to take effect. When changing the listening address of 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. +> 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 +> setting, may change, so please check all your configuration files on important issues.