NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
REL="HOME"
-TITLE="Privoxy 3.0.7 User Manual"
+TITLE="Privoxy 3.0.11 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Installation"
HREF="quickstart.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.7 User Manual</TH
+>Privoxy 3.0.11 User Manual</TH
></TR
><TR
><TD
>3. What's New in this Release</A
></H1
><P
-> There are many improvements and new features since <SPAN
+> There are only a few improvements and new features since
+ <SPAN
CLASS="APPLICATION"
->Privoxy 3.0.6</SPAN
+>Privoxy 3.0.10</SPAN
>, the last stable release:</P
><P
> <P
><UL
><LI
><P
-> 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 apply arbitrary <SPAN
-CLASS="QUOTE"
->"tags"</SPAN
-> to
- each request's headers. These <SPAN
-CLASS="QUOTE"
->"tags"</SPAN
-> can then
- subsequently be used by other actions, greatly increasing
- <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
->'s flexibity and selectivity. See <A
-HREF="actions-file.html#TAG-PATTERN"
->tag patterns</A
-> for more on tags.
-
+> On most platforms, outgoing connections can be kept alive and
+ reused if the server supports it. Whether or not this improves
+ things depends on the connection.
</P
></LI
><LI
><P
-> Header filtering can be done with dedicated header filters now. As a result
- the actions <SPAN
-CLASS="QUOTE"
->"filter-client-headers"</SPAN
-> and <SPAN
-CLASS="QUOTE"
->"filter-server-headers"</SPAN
->
- that were introduced with <SPAN
-CLASS="APPLICATION"
->Privoxy 3.0.5</SPAN
-> to apply
- the content filters to the headers as, well have been removed again.
- 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
->.
+> When dropping privileges, membership in supplementary groups
+ is given up as well. Not doing that can lead to Privoxy running
+ with more rights than necessary and violates the principle of
+ least privilege. Users of the --user option are advised to update.
+ Thanks to Matthias Drochner for reporting the problem,
+ providing the initial patch and testing the final version.
</P
></LI
><LI
><P
-> There are four new options for the main <TT
-CLASS="FILENAME"
->config</TT
-> file:
+> Passing invalid users or groups with the --user option
+ didn't lead to program exit. Regression introduced in 3.0.7.
</P
+></LI
+><LI
><P
-></P
-><UL
+> The match all section has been moved from default.action
+ to a new file called match-all.action. As a result the
+ default.action no longer needs to be touched by the user
+ and can be safely overwritten by updates.
+ </P
+></LI
><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
+> The standard.action file has been removed. Its content
+ is now part of the default.action file.
+ </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
+> In some situations the logged content length was slightly too low.
+ </P
></LI
><LI
><P
-> <A
-HREF="config.html#ACCEPT-INTERCEPTED-REQUESTS"
->accept-intercepted-requests</A
->
- which will 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) so that explicitly setting the browser's proxy settings
- is not necessary.
- </P
+> Crunched requests are logged with their own log level.
+ If you used "debug 1" in the past, you'll probably want
+ to additionally enable "debug 1024", otherwise only passed
+ requests will be logged. If you only care about crunched
+ requests, simply replace "debug 1" with "debug 1024".
+ </P
></LI
><LI
><P
-> <A
-HREF="config.html#TEMPLDIR"
->templdir</A
->
- to designate an alternate location for Privoxy's own CGI templates
- to make sure any locally customized templates aren't overwritten
- during upgrades.
- </P
+> The crunch reason has been moved to the beginning of the
+ crunch message. For HTTP URLs, the protocol is logged as well.
+ </P
></LI
-></UL
+><LI
+><P
+> Log messages are shortened by not printing the thread id
+ on its own (as opposed to putting it inside "Privoxy()".
+ </P
></LI
><LI
><P
-> A new command line option <TT
-CLASS="LITERAL"
->--pre-chroot-nslookup hostname</TT
-> to
- intialize 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)
+> The config option socket-timeout has been added to control
+ the time Privoxy waits for data to arrive on a socket.
</P
></LI
><LI
><P
-> The <A
-HREF="actions-file.html#FORWARD-OVERRIDE"
->forward-override</A
-> action
- allows changing of the forwarding settings based on client headers like the
- User-Agent, or the request origin.
- </P
+> Support for remote toggling is controlled by the configure
+ option --disable-toggle only. In previous versions it also
+ depended on the action editor and thus configuring with the
+ --disable-editor option would disable remote toggling support
+ as well.
+ </P
></LI
><LI
><P
-> The <A
-HREF="actions-file.html#REDIRECT"
->redirect</A
-> action can now use regular
- expression substitutions against the original URL.
+> Requests with invalid HTTP versions are rejected.
</P
></LI
><LI
><P
-> <SPAN
-CLASS="APPLICATION"
->zlib</SPAN
-> support is now available as a compile
- time option for compressed documents.
+> The template symbol @date@ can be used to include a date(1)-like
+ time string. Initial patch submitted by Endre Szabo.
</P
></LI
><LI
><P
-> Improve various filters, and add new ones.
+> Responses from shoutcast servers are accepted again.
+ Problem reported and fix suggested by Stefan.
</P
></LI
><LI
><P
-> Include support for RFC 3253 so that <TT
-CLASS="FILENAME"
->Subversion</TT
-> works
- with <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
->.
+> The hide-forwarded-for-headers action has been replaced with
+ the change-x-forwarded-for{} action which can also be used to
+ add X-Forwarded-For headers. The latter functionality already
+ existed in Privoxy versions prior to 3.0.7 but has been removed
+ as it was often used unintentionally (by not using the
+ hide-forwarded-for-headers action).
</P
></LI
><LI
><P
-> Logging can be turned on or off.
+> A "clear log" view option was added to the mingw32 version
+ to clear out all of the lines in the Privoxy log window.
+ Based on a patch submitted by T Ford.
</P
></LI
><LI
><P
-> A number of improvements to Privoxy's internal CGI pages, including the
- use of favicons for error and control pages.
+> The mingw32 version uses "critical sections" now, which prevents
+ log message corruption under load. As a side effect, the
+ "no thread-safe PRNG" warning could be removed as well.
</P
></LI
><LI
><P
-> Many bugfixes, memory leaks addressed, code improvements, and logging
- improvments.
+> The mingw32 version's task bar icon is crossed out and
+ the color changed to gray if Privoxy is toggled off.
</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
<TT
CLASS="FILENAME"
>standard.action</TT
-> now only includes the enabled actions.
- Not all actions as before.
+> has been merged into
+ the <TT
+CLASS="FILENAME"
+>default.action</TT
+> file.
</P
></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 the content filters to
- the headers as, well 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