-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>Privoxy Configuration</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
+"><LINK
REL="HOME"
-TITLE="Privoxy 3.0.3 User Manual"
+TITLE="Privoxy 3.0.4 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Starting Privoxy"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 3.0.3 User Manual</TH
+>Privoxy 3.0.4 User Manual</TH
></TR
><TR
><TD
CLASS="SECT1"
><A
NAME="CONFIGURATION"
+></A
>6. <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
-> Configuration</A
-></H1
+> Configuration</H1
><P
> All <SPAN
CLASS="APPLICATION"
><H2
CLASS="SECT2"
><A
-NAME="AEN585"
+NAME="AEN724"
+></A
>6.1. Controlling <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
-> with Your Web Browser</A
-></H2
+> with Your Web Browser</H2
><P
> <SPAN
CLASS="APPLICATION"
> <H2
CLASS="BRIDGEHEAD"
><A
-NAME="AEN594"
+NAME="AEN733"
></A
> Privoxy Menu</H2
><P
><TR
><TD
> ▪ <A
-HREF="http://www.privoxy.org/3.0.3/user-manual/"
+HREF="http://www.privoxy.org/ 3.0.4/user-manual/"
TARGET="_top"
>Documentation</A
>
CLASS="SECT2"
><A
NAME="CONFOVERVIEW"
->6.2. Configuration Files Overview</A
-></H2
+></A
+>6.2. Configuration Files Overview</H2
><P
> For Unix, *BSD and Linux, all configuration files are located in
<TT
<SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
-> executable. </P
+> executable. The name
+ 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
some settings may be aggressive by some standards. For the time being, the
></LI
><LI
><P
-> <TT
-CLASS="FILENAME"
->default.filter</TT
+> <SPAN
+CLASS="QUOTE"
+>"Filter files"</SPAN
> (the <A
HREF="filter-file.html"
>filter
>) 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. Only one filter
- file may be defined.
+ 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
+ filter files in <TT
+CLASS="FILENAME"
+>config</TT
+> as you can with
+ actions files. We suggest <TT
+CLASS="FILENAME"
+>user.filter</TT
+> for any
+ locally defined filters or customizations.
</P
></LI
></UL
><P
> All files use the <SPAN
CLASS="QUOTE"
->"<VAR
+>"<TT
CLASS="LITERAL"
->#</VAR
+>#</TT
>"</SPAN
> character to denote a
comment (the rest of the line will be ignored) and understand line continuation
- through placing a backslash ("<VAR
+ through placing a backslash ("<TT
CLASS="LITERAL"
->\</VAR
+>\</TT
>") as the very last character
- in a line. If the <VAR
+ in a line. If the <TT
CLASS="LITERAL"
->#</VAR
+>#</TT
> is preceded by a backslash, it looses
- its special function. Placing a <VAR
+ its special function. Placing a <TT
CLASS="LITERAL"
->#</VAR
+>#</TT
> in front of an otherwise
valid configuration line to prevent it from being interpreted is called "commenting
out" that line.</P
><P
-> The actions files and <TT
-CLASS="FILENAME"
->default.filter</TT
->
+> The actions files and filter files
can use Perl style <A
HREF="appendix.html#REGEX"
>regular expressions</A
>old</I
></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.
+ Also, what constitutes a <SPAN
+CLASS="QUOTE"
+>"default"</SPAN
+> setting, may change, so
+ please check all your configuration files on important issues.</P
></DIV
></DIV
><DIV