Privoxy 3.0.12 is mainly a bugfix release:
The socket-timeout option now also works on platforms whose select() implementation modifies the timeout structure. Previously the timeout was triggered even if the connection didn't stall. Reported by cyberpatrol.
The Connection: keep-alive code properly deals with files larger than 2GB. Previously the connection was closed too early.
The content length for files above 2GB is logged correctly.
The user-manual directive on the show-status page links to the documentation location specified with the directive, not to the Privoxy website.
When running in daemon mode, Privoxy doesn't log anything to the console unless there are errors before the logfile has been opened.
The show-status page prints warnings about invalid directives on the same line as the directives themselves.
Fixed several justified (but harmless) compiler warnings, mostly on 64 bit platforms.
The mingw32 version explicitly requests the default charset to prevent display problems with some fonts available on more recent Windows versions. Patch by Burberry.
The mingw32 version uses the Privoxy icon in the alt-tab windows. Patch by Burberry.
The timestamp and the thread id is omitted in the "Fatal error" message box on mingw32.
Fixed two related mingw32-only buffer overflows. Triggering them required control over the configuration file, therefore this isn't seen as a security issue.
In verbose mode, or if the new option --show-skipped-tests is used, Privoxy-Regression-Test logs skipped tests and the skip reason.
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.