+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
<HTML
><HEAD
><TITLE
>Privoxy Configuration</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
REL="HOME"
-TITLE="Privoxy 3.0.4 User Manual"
+TITLE="Privoxy 3.0.27 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Starting Privoxy"
HREF="config.html"><LINK
REL="STYLESHEET"
TYPE="text/css"
-HREF="../p_doc.css">
+HREF="../p_doc.css"><META
+HTTP-EQUIV="Content-Type"
+CONTENT="text/html;
+charset=ISO-8859-1">
<LINK REL="STYLESHEET" TYPE="text/css" HREF="p_doc.css">
</head
><BODY
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 3.0.4 User Manual</TH
+>Privoxy 3.0.27 User Manual</TH
></TR
><TR
><TD
CLASS="SECT1"
><A
NAME="CONFIGURATION"
-></A
->6. <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
-> Configuration</H1
+>6. Privoxy Configuration</A
+></H1
><P
> All <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
-> configuration is stored
+> configuration is stored
in text files. These files can be edited with a text editor.
Many important aspects of <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
-> can
+> can
also be controlled easily with a web browser.
</P
><DIV
><H2
CLASS="SECT2"
><A
-NAME="AEN766"
-></A
->6.1. Controlling <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
-> with Your Web Browser</H2
+NAME="CONTROL-WITH-WEBBROWSER"
+>6.1. Controlling Privoxy with Your Web Browser</A
+></H2
><P
> <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
->'s user interface can be reached through the special
+>'s user interface can be reached through the special
URL <A
HREF="http://config.privoxy.org/"
TARGET="_top"
HREF="http://p.p/"
TARGET="_top"
>http://p.p/</A
->),
+>),
which is a built-in page and works without Internet access.
- You will see the following section: </P
+ You will see the following section:</P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
> <H2
CLASS="BRIDGEHEAD"
><A
-NAME="AEN775"
+NAME="AEN881"
></A
> Privoxy Menu</H2
><P
><TR
><TD
> ▪ <A
-HREF="http://www.privoxy.org/ 3.0.4/user-manual/"
+HREF="https://www.privoxy.org/3.0.27/user-manual/"
TARGET="_top"
>Documentation</A
>
CLASS="APPLICATION"
>Privoxy</SPAN
> configuration. The actions
- file, and other configuration files, are explained in detail below. </P
+ file, and other configuration files, are explained in detail below.</P
><P
> <SPAN
CLASS="QUOTE"
>"Toggle Privoxy On or Off"</SPAN
-> 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 <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
->
+>
causing the problem or not. <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
-> continues
+> continues
to run as a proxy in this case, but all manipulation is disabled, i.e.
<SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
-> acts like a normal forwarding proxy. There
- is even a toggle <A
-HREF="appendix.html#BOOKMARKLETS"
->Bookmarklet</A
-> offered, so
- that you can toggle <SPAN
+> acts like a normal forwarding proxy.</P
+><P
+> Note that several of the features described above are disabled by default
+ in <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
-> with one click from
- your browser.</P
+> 3.0.7 beta and later.
+ Check the
+ <A
+HREF="config.html"
+TARGET="_top"
+>configuration file</A
+> to learn why
+ and in which cases it's safe to enable them again.</P
></DIV
><DIV
CLASS="SECT2"
CLASS="SECT2"
><A
NAME="CONFOVERVIEW"
-></A
->6.2. Configuration Files Overview</H2
+>6.2. Configuration Files Overview</A
+></H2
><P
> For Unix, *BSD and Linux, all configuration files are located in
<TT
CLASS="FILENAME"
>/etc/privoxy/</TT
> 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
<SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
and number of configuration files has changed from previous versions, and is
subject to change as development progresses.</P
><P
-> 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:</P
><P
-> <P
></P
><UL
><LI
><P
> <TT
CLASS="FILENAME"
->default.action</TT
-> (the main <A
-HREF="actions-file.html"
->actions file</A
->)
- is used to define which <SPAN
+>match-all.action</TT
+> is used to define which <SPAN
CLASS="QUOTE"
>"actions"</SPAN
-> 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
- <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
-> 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.
+ </P
+><P
+> <TT
+CLASS="FILENAME"
+>default.action</TT
+> defines many exceptions (both positive and negative)
+ from the default set of actions that's configured in <TT
+CLASS="FILENAME"
+>match-all.action</TT
+>.
+ It should be the second actions file loaded and shouldn't be edited by the user.
</P
><P
> Multiple actions files may be defined in <TT
CLASS="FILENAME"
>config</TT
->. 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
<TT
CLASS="FILENAME"
->default.action</TT
+>match-all.action</TT
> (which you will most probably want
- to define sooner or later) are probably best applied in
- <TT
+ to define sooner or later) are best applied in <TT
CLASS="FILENAME"
>user.action</TT
->, where you can preserve them across
- upgrades. <TT
-CLASS="FILENAME"
->standard.action</TT
-> is for
- <SPAN
-CLASS="APPLICATION"
->Privoxy's</SPAN
-> 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.
</P
><P
->
- There is also a web based editor that can be accessed from
+> There is also a web based editor that can be accessed from
<A
HREF="http://config.privoxy.org/show-status"
TARGET="_top"
TARGET="_top"
>http://p.p/show-status</A
>) for the
- various actions files.
+ various actions files.
</P
></LI
><LI
>) 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.
<TT
CLASS="FILENAME"
>default.filter</TT
-> 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 <TT
CLASS="FILENAME"
>config</TT
-> as you can with
+> as you can with
actions files. We suggest <TT
CLASS="FILENAME"
>user.filter</TT
-> for any
+> for any
locally defined filters or customizations.
</P
></LI
></UL
-></P
><P
-> 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.</P
+> The syntax of the configuration and filter files may change between different
+ Privoxy versions, unfortunately some enhancements cost backwards compatibility.
+ </P
><P
> All files use the <SPAN
CLASS="QUOTE"
>#</TT
> in front of an otherwise
valid configuration line to prevent it from being interpreted is called "commenting
- out" that line.</P
+ out" that line. Blank lines are ignored.</P
><P
-> The actions files and filter files
+> The actions files and filter files
can use Perl style <A
HREF="appendix.html#REGEX"
>regular expressions</A
> for
- maximum flexibility. </P
+ maximum flexibility.</P
><P
> After making any changes, there is no need to restart
<SPAN
effect. <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
-> 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 <SPAN
></SPAN
> listening address.</P
><P
-> 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 <SPAN
CLASS="QUOTE"
>"default"</SPAN
-> setting, may change, so
+> setting, may change, so
please check all your configuration files on important issues.</P
></DIV
></DIV
WIDTH="33%"
ALIGN="left"
VALIGN="top"
->Starting <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
-></TD
+>Starting Privoxy</TD
><TD
WIDTH="34%"
ALIGN="center"