What's New in this Release

X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=doc%2Fwebserver%2Fuser-manual%2Fwhatsnew.html;h=8a2877b6373eeb43f7d7227543e6a5f2019acf57;hp=54a7fa962c91b37557fbc835426138450fb84fda;hb=0114396acb2bab4918dbdf9b8f68b6e21703b2fd;hpb=d74ec2c8f9726f42df2ce1e45749d74dee43b781 diff --git a/doc/webserver/user-manual/whatsnew.html b/doc/webserver/user-manual/whatsnew.html index 54a7fa96..8a2877b6 100644 --- a/doc/webserver/user-manual/whatsnew.html +++ b/doc/webserver/user-manual/whatsnew.html @@ -1,13 +1,13 @@ + What's New in this Release + +Privoxy 3.0.4 User ManualPrivoxy 3.0.14 User Manual3. What's New in this Release3. What's New in this Release

There are many new features in Privoxy 3.0.4 - :

Privoxy 3.0.13 introduces IPv6 support, + improved keep-alive support and a bunch of minor improvements:

Mulitiple filter files can now be specifed in config. +> Added IPv6 support. Thanks to Petr Pisar who not only provided + the initial patch but also helped a lot with the integration.
- There are a number of new actions: -
- content-type-overwrite -
- crunch-client-header -
- crunch-if-none-match -
- crunch-server-header -
  Added client-side keep-alive support. This should also allow + NTLM authentication through Privoxy, but this hasn't been + confirmed yet. +
- fast-redirects -
  The connection sharing code is only used if the connection-sharing + option is enabled. +
- force-text-mode -
  The max-client-connections option has been added to restrict + the number of client connections below a value enforced by + the operating system. +
- handle-as-empty-document -
  Fixed a regression reintroduced in 3.0.12 that could cause + crashes on mingw32 if header date randomization was enabled. +
- hide-accept-language -
  Compressed content with extra fields couldn't be decompressed + and would get passed to the client unfiltered. This problem + has only be detected through statical analysis with clang as + nobody seems to be using extra fields anyway. +
- hide-content-disposition -
  If the server resets the Connection after sending only the headers + Privoxy forwards what it got to the client. Previously Privoxy + would deliver an error message instead. +
- hide-if-modified-since -
  Error messages in case of connection timeouts use the right + HTTP status code. +
- hide-referrer -
  If spawning a child to handle a request fails, the client + gets an error message and Privoxy continues to listen for + new requests right away. +
- inspect-jpegs -
  The error messages in case of server-connection timeouts or + prematurely closed server connections are now template-based. +
- overwrite-last-modified -
  If zlib support isn't compiled in, Privoxy no longer tries to + filter compressed content unless explicitly asked to do so. +
- redirect -
  In case of connections that are denied based on ACL directives, + the memory used for the client IP is no longer leaked. +
- treat-forbidden-connects-like-blocks -
-
Fixed another small memory leak if the client request times out + while waiting for client headers other than the request line. +
MS-Windows versions can now be installed and - started as a service. +> The client socket is kept open until the server socket has + been marked as unused. This should increase the chances that + the still-open connection will be reused for the client's next + request to the same destination. Note that this only matters + if connection-sharing is enabled.
In addition, there are various bug fixes and enhancements, including - error pages are no longer cached, better DNS error handling, and logging - improvements. +> A TODO list has been added to the source tarballs to give potential + volunteers a better idea of what the current goals are. Donations + are still welcome too: http://www.privoxy.org/faq/general.html#DONATE

3.1. Note to Upgraders3.1. Note to Upgraders

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 has been merged into + the default.action file. +
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. +

Quickstart to Using PrivoxyQuickstart to Using Privoxy