NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
REL="HOME"
-TITLE="Privoxy 3.0.7 User Manual"
+TITLE="Privoxy 3.0.8 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Installation"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 3.0.7 User Manual</TH
+>Privoxy 3.0.8 User Manual</TH
></TR
><TR
><TD
><UL
><LI
><P
-> Header filtering can be done with dedicated header filters now. As a result
+> Two new actions <A
+HREF="actions-file.html#SERVER-HEADER-TAGGER"
+>server-header-tagger</A
+>
+ and <A
+HREF="actions-file.html#CLIENT-HEADER-TAGGER"
+>client-header-tagger</A
+>
+ that can be used to create arbitrary <SPAN
+CLASS="QUOTE"
+>"tags"</SPAN
+>
+ based on client and server headers.
+ These <SPAN
+CLASS="QUOTE"
+>"tags"</SPAN
+> can then subsequently be used
+ to control the other actions used for the current request,
+ greatly increasing <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+>'s flexibility and selectivity. See <A
+HREF="actions-file.html#TAG-PATTERN"
+>tag patterns</A
+> for more information on tags.
+ </P
+></LI
+><LI
+><P
+> Header filtering is done with dedicated header filters now. As a result
the actions <SPAN
CLASS="QUOTE"
>"filter-client-headers"</SPAN
CLASS="APPLICATION"
>Privoxy 3.0.5</SPAN
> to apply
- the content filters to the headers as, well have been removed again.
+ content filters to the headers have been removed.
+ See the new actions <A
+HREF="actions-file.html#SERVER-HEADER-FILTER"
+>server-header-filter</A
+>
+ and <A
+HREF="actions-file.html#CLIENT-HEADER-FILTER"
+>client-header-filter</A
+> for details.
+ </P
+></LI
+><LI
+><P
+> There are four new options for the main <TT
+CLASS="FILENAME"
+>config</TT
+> file:
+ </P
+><P
+></P
+><UL
+><LI
+><P
+> <A
+HREF="config.html#ALLOW-CGI-REQUEST-CRUNCHING"
+>allow-cgi-request-crunching</A
+>
+ which allows requests for Privoxy's internal CGI pages to be
+ blocked, redirected or (un)trusted like ordinary requests.
+ </P
+></LI
+><LI
+><P
+> <A
+HREF="config.html#SPLIT-LARGE-FORMS"
+>split-large-forms</A
+>
+ that will work around a browser bug that caused IE6 and IE7 to
+ ignore the Submit button on the Privoxy's edit-actions-for-url CGI
+ page.
+ </P
+></LI
+><LI
+><P
+> <A
+HREF="config.html#ACCEPT-INTERCEPTED-REQUESTS"
+>accept-intercepted-requests</A
+>
+ which allows to combine Privoxy with any packet filter to create an
+ intercepting proxy for HTTP/1.1 requests (and for HTTP/1.0 requests
+ with Host header set). This means clients can be forced to use
+ <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+> even if their proxy settings are configured differently.
+ </P
+></LI
+><LI
+><P
+> <A
+HREF="config.html#TEMPLDIR"
+>templdir</A
+>
+ to designate an alternate location for <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+>'s
+ locally customized CGI templates so that
+ these are not overwritten during upgrades.
+ </P
+></LI
+></UL
+></LI
+><LI
+><P
+> A new command line option <TT
+CLASS="LITERAL"
+>--pre-chroot-nslookup hostname</TT
+> to
+ initialize the resolver library before chroot'ing. On some systems this
+ reduces the number of files that must be copied into the chroot tree.
+ (Patch provided by Stephen Gildea)
+ </P
+></LI
+><LI
+><P
+> The <A
+HREF="actions-file.html#FORWARD-OVERRIDE"
+>forward-override</A
+> action
+ allows changing of the forwarding settings through the actions files.
+ Combined with tags, this allows to choose the forwarder based on
+ client headers like the <TT
+CLASS="LITERAL"
+>User-Agent</TT
+>, or the request origin.
+ </P
+></LI
+><LI
+><P
+> The <A
+HREF="actions-file.html#REDIRECT"
+>redirect</A
+> action can now use regular
+ expression substitutions against the original URL.
+ </P
+></LI
+><LI
+><P
+> <SPAN
+CLASS="APPLICATION"
+>zlib</SPAN
+> support is now available as a compile
+ time option to filter compressed content. Patch provided by Wil Mahan.
+ </P
+></LI
+><LI
+><P
+> Improve various filters, and add new ones.
+ </P
+></LI
+><LI
+><P
+> Include support for RFC 3253 so that <TT
+CLASS="FILENAME"
+>Subversion</TT
+> works
+ with <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+>. Patch provided by Petr Kadlec.
+ </P
+></LI
+><LI
+><P
+> Logging can be completely turned off by not specifying a logfile directive.
+ </P
+></LI
+><LI
+><P
+> A number of improvements to Privoxy's internal CGI pages, including the
+ use of favicons for error and control pages.
+ </P
+></LI
+><LI
+><P
+> Many bugfixes, memory leaks addressed, code improvements, and logging
+ improvements.
</P
></LI
></UL
></P
+><P
+> For a more detailed list of changes please have a look at the ChangeLog.</P
><DIV
CLASS="SECT2"
><H2
><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
- in the <A
-HREF="config.html#LOGFILE"
->config file</A
->.
- </P
+> In the default configuration only fatal errors are logged now.
+ You can change that in the <A
+HREF="config.html#DEBUG"
+>debug section</A
+>
+ of the configuration file. You may also want to enable more verbose
+ logging until you verified that the new <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+> version is working
+ as expected.
+ </P
></LI
><LI
><P
be aware of the security issues involved.
</P
></LI
+><LI
+><P
+> The <SPAN
+CLASS="QUOTE"
+>"filter-client-headers"</SPAN
+> and
+ <SPAN
+CLASS="QUOTE"
+>"filter-server-headers"</SPAN
+> actions that were introduced with
+ <SPAN
+CLASS="APPLICATION"
+>Privoxy 3.0.5</SPAN
+> to apply content filters to
+ the headers have been removed and replaced with new actions.
+ See the <A
+HREF="whatsnew.html"
+>What's New section</A
+> above.
+ </P
+></LI
></UL
></P
></DIV
projects / privoxy.git / blobdiff