|
![]() [ View full size screenshot ] |
| Version | Date Released | Status | Release Notes |
| 3.0.19 | Dec 29, 2011 | New Release | |
| 3.0.18 | Nov 22, 2011 | New Release | Bug fixes: · If a generated redirect URL contains characters RFC 3986 doesn't permit, they are (re)encoded. Not doing this makes Privoxy versions from 3.0.5 to 3.0.17 susceptible to HTTP response splitting (CWE-113) attacks if the +fast-redirects{check-decoded-url} action is used. - Fix a logic bug that could cause Privoxy to reuse a server socket after it got tainted by a server-header-tagger-induced block that was triggered before the whole server response had been read. If keep-alive was enabled and the request following the blocked one was to the same host and using the same forwarding settings, Privoxy would send it on the tainted server socket. While the server would simply treat it as a pipelined request, Privoxy would later on fail to properly parse the server's response as it would try to parse the unread data from the first response as server headers for the second one. Regression introduced in 3.0.17. |
| 3.0.17 | Nov 16, 2010 | New Release | · In case of missing server data, no error message is send to the client if the request arrived on a reused connection. The client is then supposed to silently retry the request without bothering the user. This should significantly reduce the frequency of the "No server or forwarder data received" error message many users reported. · More reliable detection of prematurely closed client sockets with keep-alive enabled. · FEATURE_CONNECTION_KEEP_ALIVE is decoupled from FEATURE_CONNECTION_SHARING and now available on all platforms. · Improved handling of POST requests on reused connections. · Should fix problems with stalled connections after submitting form data with some browser configurations. · Fixed various latency calculation issues. · Allows the client to pass NTLM authentication requests to a forwarding proxy. This was already assumed and hinted to work in 3.0.13 beta but actually didn't. Now it's confirmed to work with IE, Firefox and Chrome. |
| 3.0.16 | May 14, 2010 | New Release |