Privoxy 3.0.14 Beta is a bugfix-release for the previous beta which introduced IPv6 support, improved keep-alive support and a bunch of minor improvements. The changes since 3.0.12:
Added IPv6 support. Thanks to Petr Pisar who not only provided the initial patch but also helped a lot with the integration.
Added client-side keep-alive support.
The connection sharing code is only used if the connection-sharing option is enabled.
The latency is taken into account when evaluating whether or not to reuse a connection. This should significantly reduce the number of connections problems several users reported.
The max-client-connections option has been added to restrict the number of client connections below a value enforced by the operating system.
If the server doesn't specify how long the connection stays alive, Privoxy errs on the safe side of caution and assumes it's only a second.
Setting keep-alive-timeout to 0 disables keep-alive support. Previously Privoxy would claim to allow persistence but not reuse the connection.
Pipelined requests are less likely to be mistaken for the request body of the previous request. Note that Privoxy still has no real pipeline support and will either serialize pipelined requests or drop them in which case the client has to resent them.
Fixed a crash on some Windows versions when header randomization is enabled and the date couldn't be parsed.
Privoxy's keep-alive timeout for the current connection is reduced to the one specified in the client's Keep-Alive header.
For HTTP/1.1 requests, Privoxy implies keep-alive support by not setting any Connection header instead of using 'Connection: keep-alive'.
If the socket isn't reusable, Privoxy doesn't temporarily waste a socket slot to remember the connection.
If keep-alive support is disabled but compiled in, the client's Keep-Alive header is removed.
Fixed a bug on mingw32 where downloading large files failed if keep-alive support was enabled.
Fixed a bug that (at least theoretically) could cause log timestamps to be occasionally off by about a second.
The configure script respects the $PATH variable when searching for groups and id.
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.
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.
Error messages in case of connection timeouts use the right HTTP status code.
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.
The error messages in case of server-connection timeouts or prematurely closed server connections are now template-based.
If zlib support isn't compiled in, Privoxy no longer tries to filter compressed content unless explicitly asked to do so.
In case of connections that are denied based on ACL directives, the memory used for the client IP is no longer leaked.
Fixed another small memory leak if the client request times out while waiting for client headers other than the request line.
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.
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
A quick list of things to be aware of before upgrading from earlier versions of Privoxy:
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.
Note that some installers remove earlier versions completely, including configuration files, therefore you should really save any important configuration files!
On the other hand, other installers don't overwrite existing configuration files, thinking you will want to do that yourself.
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 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.