X-Git-Url: http://www.privoxy.org/gitweb/?a=blobdiff_plain;f=doc%2Fwebserver%2Fuser-manual%2Fwhatsnew.html;h=4e15cf16426a94bdad9a867bf87c57751e0e65c8;hb=3b3e93244ab9a04daf15de964593063779e382ed;hp=54a7fa962c91b37557fbc835426138450fb84fda;hpb=d74ec2c8f9726f42df2ce1e45749d74dee43b781;p=privoxy.git diff --git a/doc/webserver/user-manual/whatsnew.html b/doc/webserver/user-manual/whatsnew.html index 54a7fa96..4e15cf16 100644 --- a/doc/webserver/user-manual/whatsnew.html +++ b/doc/webserver/user-manual/whatsnew.html @@ -1,13 +1,13 @@ +
There are many new features in There are many improvements and new features since Privoxy 3.0.4 - :
Privoxy 3.0.6, the last stable release:
Mulitiple filter files can now be specifed in config. +> Two new actions server-header-tagger + and client-header-tagger + that can be used to create arbitrary "tags" + based on client and server headers. + These "tags" can then subsequently be used + to control the other actions used for the current request, + greatly increasing Privoxy's flexibility and selectivity. See tag patterns for more information on tags.
- There are a number of new actions: -
content-type-overwrite Header filtering is done with dedicated header filters now. As a result + the actions "filter-client-headers" and "filter-server-headers" -
crunch-client-headerPrivoxy 3.0.5 to apply + content filters to the headers have been removed. + See the new actions server-header-filter -
client-header-filter for details. +A new command line option hide-content-disposition -
--pre-chroot-nslookup hostname 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) +The forward-override 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 hide-if-modified-since -
User-Agent, or the request origin. +redirect -
Include support for RFC 3253 so that Subversion works + with Privoxy. Patch provided by Petr Kadlec. +MS-Windows versions can now be installed and - started as a service. +> A number of improvements to Privoxy's internal CGI pages, including the + use of favicons for error and control pages.
In addition, there are various bug fixes and enhancements, including - error pages are no longer cached, better DNS error handling, and logging - improvements. +> Many bugfixes, memory leaks addressed, code improvements, and logging + improvements.
For a more detailed list of changes please have a look at the ChangeLog.
A quick list of things to be aware of before upgrading from earlier
versions of 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.
+ 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.
+
- 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!
- What constitutes a "default" configuration has changed,
- and you may want to review which actions are "on" by
- default. This is primarily a matter of emphasis, but some features
- you may have been used to, may now be "off" by default.
+ On the other hand, other installers don't overwrite existing configuration
+ files, thinking you will want to do that yourself.
- Some installers may not automatically start
-
+ 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. You may also want
+ to enable logging until you verified that the new Privoxy after installation.
+> 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.
+ If you use or want these, you will need to explicitly enable them, and
+ be aware of the security issues involved.
+ The "filter-client-headers" and
+ "filter-server-headers" actions that were introduced with
+ Privoxy 3.0.5 to apply content filters to
+ the headers have been removed and replaced with new actions.
+ See the What's New section above.
+