From: Fabian Keil Date: Thu, 4 Feb 2010 09:33:27 +0000 (+0000) Subject: Add changes in 3.0.16 stable. X-Git-Tag: v_3_0_16~40 X-Git-Url: http://www.privoxy.org/gitweb/show-status?a=commitdiff_plain;h=80a05a9be053821195f56f5f0d88b0041123549f;p=privoxy.git Add changes in 3.0.16 stable. --- diff --git a/ChangeLog b/ChangeLog index 4ce627dc..ece7ce54 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,6 +1,51 @@ -------------------------------------------------------------------- ChangeLog for Privoxy -------------------------------------------------------------------- +*** Version 3.0.16 Stable *** + +- The config file option handle-as-empty-doc-returns-ok has + been added to work around Firefox bug #492459, which causes + Firefox to hang if JavaScripts are blocked in certain situations. +- Privoxy-Log-Parser is roughly 40% faster in highlighting mode. +- In daemon mode, fd 0, 1 and 2 are bound to /dev/null. +- Accepts quoted expiration dates even though RFC 2109 10.1.2 + doesn't seem to allow them. Reported anonymously. +- uagen, a Firefox User-Agent generator for Privoxy and Mozilla + browsers has been imported and is available in the tarballs + tools directory. +- Added optional support for FreeBSD's accf_http(9). Use the + configure option --enable-accept-filter to enable it. +- Added fancier Privoxy icons for win32. Contributed by Jeff H. +- Resolve localhost using whatever address family the operating + system feels like. Previous betas would try to use IPv4 as this + is what most users expect, but this didn't work reliable on + GNU/Linux systems. +- Added the config option default-server-timeout to control + the assumed default server timeout. Since Privoxy no longer + returns an error message for connection resets on reused client + connections, assuming larger server timeout values appears to + actually work pretty well as long as connections aren't shared. +- Several log messages about client connections also mention + the socket number. +- Don't try to forget connections if connection sharing is disabled. + This wasn't a real problem but caused an unnecessary log message. +- The scripts in the tools directory treat unknown parameters + as fatal errors. +- The still undocumented --enable-extended-host-patterns configure + option has a better description. +- Fixed an error message that would claim a write to the + server failed when actually writing to the client failed. +- Log the crunch reason before trying to write to the client. + The log is easier to read that way. +- In the action lists on CGI pages, actions and their parameters are + no longer separated with a space. The action file parser doesn't + actually allow this and will throw an invalid syntax error if + actions and parameters in the action files are separated. + Not adding the spaces means copy and pasting CGI output into + the action files works. +- handle-as-empty-document no longer depends on the image blocking + code being enabled. + *** Version 3.0.15 Beta *** - In case of missing server data, no error message is send to the