X-Git-Url: http://www.privoxy.org/gitweb/?a=blobdiff_plain;f=doc%2Fwebserver%2Fuser-manual%2Fwhatsnew.html;h=b894a6659ee187c0572f5509613816ec8e87bf11;hb=473cfd051580edfa1e2a3f6beeb9a0d09a8253fd;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..b894a665 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.8, the last stable release:
Mulitiple filter files can now be specifed in config. +> Added SOCKS5 support (with address resolution done by + the SOCKS5 server). Patch provided by Eric M. Hopper.
- There are a number of new actions: -
The "blocked" CGI pages include a block reason that was + provided as argument to the last-applying block action. +
redirect -
If zlib support is unavailable and there are content + filters active but the prevent-compression action is disabled, + the show-url-info page includes a warning that compression + might prevent filtering. +The obsolete kill-popups action has been removed as the + PCRS-based popup filters can do the same and are slightly + less unreliable. +
MS-Windows versions can now be installed and - started as a service. +> The inspect-jpegs action has been removed. +
The send-wafer and send-vanilla-wafer actions have been removed. + They weren't particular useful and their behaviour could be emulated + with add-header anyway. +
Privoxy-Regression-Test has been significantly improved. +
Most sections in the default.action file contain tests for + Privoxy-Regression-Test to verify that they are working as intended. +
Parts of Privoxy have been refactored to increase maintainability.
In addition, there are various bug fixes and enhancements, including - error pages are no longer cached, better DNS error handling, and logging - improvements. +> Building with zlib (if available) is done by default.
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.
+ In the default configuration only fatal errors are logged now.
+ You can change that in the debug section
+ of the configuration file. You may also want to enable more verbose
+ 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.
+