[ Copyright 2001 - 2007 by Privoxy Developers ]
-$Id: user-manual.sgml,v 2.46 2007/11/17 17:24:44 fabiankeil Exp $
+$Id: user-manual.sgml,v 2.47 2007/11/18 14:59:47 fabiankeil Exp $
The Privoxy User Manual gives users information on how to install, configure
and use Privoxy.
A quick list of things to be aware of before upgrading from earlier versions of
Privoxy:
- • Some installers may remove earlier versions completely, including
- configuration files. Save any important configuration files!
+ • The recommended way to upgrade Privoxy is to backup your old configuration
+ files, install the new ones, verify that Privoxy is working correctly and
+ finally merge back your changes using diff and maybe patch.
- • 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. There are a number of new features, but most won't be
- available unless these features are incorporated into your configuration
- somehow.
+ There are a number of new features in each Privoxy release and most of them
+ have to be explicitly enabled in the configuration files. Old configuration
+ files obviously don't do that and due to syntax changes using old
+ configuration files with a new Privoxy isn't always possible anyway.
+
+ • Note that some installers remove earlier versions completely, including
+ configuration files, therefore you should really save any important
+ configuration files!
+
+ • On the other hand, other installers don't overwrite existing configuration
+ files, thinking you will want to do that yourself.
• standard.action now only includes the enabled actions. Not all actions as
before.
• Logging is off by default now. If you need logging, it can be turned on in
- the config file.
+ the config file. You may also want to enable logging until you verified
+ that the new Privoxy version is working as expected.
• Three other config file settings are now off by default:
enable-remote-toggle, enable-remote-http-toggle, and enable-edit-actions.
> <DIV
CLASS="TABLE"
><A
-NAME="AEN2158"
+NAME="AEN2168"
></A
><P
><B
><H2
CLASS="SECT2"
><A
-NAME="AEN2257"
+NAME="AEN2267"
>8.1. Finding the Right Mix</A
></H2
><P
><H2
CLASS="SECT2"
><A
-NAME="AEN2264"
+NAME="AEN2274"
>8.2. How to Edit</A
></H2
><P
><H3
CLASS="SECT3"
><A
-NAME="AEN2355"
+NAME="AEN2365"
>8.4.1. The Domain Pattern</A
></H3
><P
><H3
CLASS="SECT3"
><A
-NAME="AEN2426"
+NAME="AEN2436"
>8.4.2. The Path Pattern</A
></H3
><P
><H3
CLASS="SECT3"
><A
-NAME="AEN4232"
+NAME="AEN4242"
>8.5.39. Summary</A
></H3
><P
><H3
CLASS="SECT3"
><A
-NAME="AEN4297"
+NAME="AEN4307"
>8.7.1. default.action</A
></H3
><P
><H3
CLASS="SECT3"
><A
-NAME="AEN4433"
+NAME="AEN4443"
>8.7.2. user.action</A
></H3
><P
><H2
CLASS="SECT2"
><A
-NAME="AEN5318"
+NAME="AEN5328"
>14.2. Privoxy's Internal Pages</A
></H2
><P
Privoxy main page:
</P
><A
-NAME="AEN5332"
+NAME="AEN5342"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
editing of actions files:
</P
><A
-NAME="AEN5340"
+NAME="AEN5350"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
Show the source code version numbers:
</P
><A
-NAME="AEN5345"
+NAME="AEN5355"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
Show the browser's request headers:
</P
><A
-NAME="AEN5350"
+NAME="AEN5360"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
Show which actions apply to a URL and why:
</P
><A
-NAME="AEN5355"
+NAME="AEN5365"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
place:
</P
><A
-NAME="AEN5363"
+NAME="AEN5373"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
> Short cuts. Turn off, then on:
</P
><A
-NAME="AEN5367"
+NAME="AEN5377"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
</P
></BLOCKQUOTE
><A
-NAME="AEN5370"
+NAME="AEN5380"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
><H2
CLASS="SECT2"
><A
-NAME="AEN803"
+NAME="AEN813"
>6.1. Controlling Privoxy with Your Web Browser</A
></H2
><P
> <H2
CLASS="BRIDGEHEAD"
><A
-NAME="AEN811"
+NAME="AEN821"
></A
> Privoxy Menu</H2
><P
><H2
CLASS="SECT2"
><A
-NAME="AEN5061"
+NAME="AEN5071"
>12.1. License</A
></H2
><P
><H2
CLASS="SECT2"
><A
-NAME="AEN4588"
+NAME="AEN4598"
>9.1. Filter File Tutorial</A
></H2
><P
><BR></P
><P
CLASS="PUBDATE"
->$Id: user-manual.sgml,v 2.46 2007/11/17 17:24:44 fabiankeil Exp $<BR></P
+>$Id: user-manual.sgml,v 2.47 2007/11/18 14:59:47 fabiankeil Exp $<BR></P
><DIV
><DIV
CLASS="ABSTRACT"
><DL
><DT
>6.1. <A
-HREF="configuration.html#AEN803"
+HREF="configuration.html#AEN813"
>Controlling Privoxy with Your Web Browser</A
></DT
><DT
><DL
><DT
>8.1. <A
-HREF="actions-file.html#AEN2257"
+HREF="actions-file.html#AEN2267"
>Finding the Right Mix</A
></DT
><DT
>8.2. <A
-HREF="actions-file.html#AEN2264"
+HREF="actions-file.html#AEN2274"
>How to Edit</A
></DT
><DT
><DL
><DT
>8.4.1. <A
-HREF="actions-file.html#AEN2355"
+HREF="actions-file.html#AEN2365"
>The Domain Pattern</A
></DT
><DT
>8.4.2. <A
-HREF="actions-file.html#AEN2426"
+HREF="actions-file.html#AEN2436"
>The Path Pattern</A
></DT
><DT
></DT
><DT
>8.5.39. <A
-HREF="actions-file.html#AEN4232"
+HREF="actions-file.html#AEN4242"
>Summary</A
></DT
></DL
><DL
><DT
>8.7.1. <A
-HREF="actions-file.html#AEN4297"
+HREF="actions-file.html#AEN4307"
>default.action</A
></DT
><DT
>8.7.2. <A
-HREF="actions-file.html#AEN4433"
+HREF="actions-file.html#AEN4443"
>user.action</A
></DT
></DL
><DL
><DT
>9.1. <A
-HREF="filter-file.html#AEN4588"
+HREF="filter-file.html#AEN4598"
>Filter File Tutorial</A
></DT
><DT
><DL
><DT
>12.1. <A
-HREF="copyright.html#AEN5061"
+HREF="copyright.html#AEN5071"
>License</A
></DT
><DT
></DT
><DT
>14.2. <A
-HREF="appendix.html#AEN5318"
+HREF="appendix.html#AEN5328"
>Privoxy's Internal Pages</A
></DT
><DD
> <DIV
CLASS="FIGURE"
><A
-NAME="AEN556"
+NAME="AEN566"
></A
><P
><B
> <DIV
CLASS="FIGURE"
><A
-NAME="AEN611"
+NAME="AEN621"
></A
><P
><B
> <DIV
CLASS="FIGURE"
><A
-NAME="AEN655"
+NAME="AEN665"
></A
><P
><B
><UL
><LI
><P
+> The recommended way to upgrade <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+> is to backup your old
+ configuration files, install the new ones, verify that <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+>
+ is working correctly and finally merge back your changes using
+ <SPAN
+CLASS="APPLICATION"
+>diff</SPAN
+> and maybe <SPAN
+CLASS="APPLICATION"
+>patch</SPAN
+>.
+ </P
+><P
+> There are a number of new features in each <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+> release and
+ most of them have to be explicitly enabled in the configuration
+ files. Old configuration files obviously don't do that and due
+ to syntax changes using old configuration files with a new
+ <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+> isn't always possible anyway.
+ </P
+></LI
+><LI
+><P
>
- Some installers may remove earlier versions completely, including
- configuration files. Save any important configuration files!
+ Note that some installers remove earlier versions completely,
+ including configuration files, therefore you should really save
+ any important configuration files!
</P
></LI
><LI
><P
>
- 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.
- There are a number of new features, but most won't be available unless
- these features are incorporated into your configuration somehow.
+ On the other hand, other installers don't overwrite existing configuration
+ files, thinking you will want to do that yourself.
</P
></LI
><LI
></LI
><LI
><P
-> Logging is off by default now. If you need logging, it can be turned on
+> Logging is off by default now. If you need logging, it can be turned on
+ in the <A
HREF="config.html#LOGFILE"
>config file</A
->.
- </P
+>. You may also want
+ to enable logging until you verified that the new <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+> version
+ is working as expected.
+ </P
></LI
><LI
><P
projects / privoxy.git / commitdiff