1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
5 >What's New in this Release</TITLE
8 CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
10 TITLE="Privoxy 3.0.15 User Manual"
11 HREF="index.html"><LINK
14 HREF="installation.html"><LINK
16 TITLE="Quickstart to Using Privoxy"
17 HREF="quickstart.html"><LINK
20 HREF="../p_doc.css"><META
21 HTTP-EQUIV="Content-Type"
24 <LINK REL="STYLESHEET" TYPE="text/css" HREF="p_doc.css">
36 SUMMARY="Header navigation table"
45 >Privoxy 3.0.15 User Manual</TH
53 HREF="installation.html"
67 HREF="quickstart.html"
82 >3. What's New in this Release</A
87 >Privoxy 3.0.15 beta</SPAN
88 > is a bug-fix release
89 for the previous beta. The changes since 3.0.14 are:</P
96 > In case of missing server data, no error message is send to the
97 client if the request arrived on a reused connection. The client
98 is then supposed to silently retry the request without bothering
99 the user. This should significantly reduce the frequency of the
100 "No server or forwarder data received" error message many users
106 > More reliable detection of prematurely closed client sockets
107 with keep-alive enabled.
112 > FEATURE_CONNECTION_KEEP_ALIVE is decoupled from
113 FEATURE_CONNECTION_SHARING and now available on
119 > Improved handling of POST requests on reused connections.
120 Should fix problems with stalled connections after submitting
121 form data with some browser configurations.
126 > Fixed various latency calculation issues.
131 > Allows the client to pass NTLM authentication requests to a
132 forwarding proxy. This was already assumed and hinted to work
133 in 3.0.13 beta but actually didn't. Now it's confirmed to work
134 with IE, Firefox and Chrome.
135 Thanks to Francois Botha and Wan-Teh Chang
140 > Fixed a calculation problem if receiving the server headers
141 takes more than two reads, that could cause Privoxy to terminate
142 the connection prematurely. Reported by Oliver.
147 > Compiles again on platforms such as OpenBSD and systems
148 using earlier glibc version that don't support AI_ADDRCONFIG.
149 Anonymously submitted in #2872591.
154 > A bunch of MS VC project files and Suse and Redhat RPM spec
155 files have been removed as they were no longer maintained for
161 > Overly long action lines are properly rejected with a proper
162 error message. Previously they would be either rejected as
163 invalid or cause a core dump through abort().
168 > Already timed-out connections are no longer temporarily remembered.
169 They weren't reused anyway, but wasted a socket slot.
174 > len refers to the number of bytes actually read which might
175 differ from the ones received. Adjust log messages accordingly.
180 > The optional JavaScript on the CGI page uses encodeURIComponent()
181 instead of escape() which doesn't encode all characters that matter.
182 Anonymously reported in #2832722.
187 > Fix gcc45 warnings in decompress_iob().
192 > Various log message improvements.
197 > Privoxy-Regression-Test supports redirect tests.
202 > Privoxy-Log-Parser can gather some connection statistics.
208 > If you missed the previous two beta versions, you may also be
209 interested in the additional changes since since 3.0.12, the
210 last stable release:</P
217 > Added IPv6 support. Thanks to Petr Pisar who not only provided
218 the initial patch but also helped a lot with the integration.
223 > Added client-side keep-alive support.
228 > The connection sharing code is only used if the connection-sharing
234 > The latency is taken into account when evaluating whether or not to
235 reuse a connection. This should significantly reduce the number of
236 connections problems several users reported.
241 > The max-client-connections option has been added to restrict
242 the number of client connections below a value enforced by
243 the operating system.
248 > If the server doesn't specify how long the connection stays alive,
249 Privoxy errs on the safe side of caution and assumes it's only a second.
254 > Setting keep-alive-timeout to 0 disables keep-alive support. Previously
255 Privoxy would claim to allow persistence but not reuse the connection.
260 > Pipelined requests are less likely to be mistaken for the request
261 body of the previous request. Note that Privoxy still has no real
262 pipeline support and will either serialize pipelined requests or
263 drop them in which case the client has to resent them.
268 > Fixed a crash on some Windows versions when header randomization
269 is enabled and the date couldn't be parsed.
274 > Privoxy's keep-alive timeout for the current connection is reduced
275 to the one specified in the client's Keep-Alive header.
280 > For HTTP/1.1 requests, Privoxy implies keep-alive support by not
281 setting any Connection header instead of using 'Connection: keep-alive'.
286 > If the socket isn't reusable, Privoxy doesn't temporarily waste
287 a socket slot to remember the connection.
292 > If keep-alive support is disabled but compiled in, the client's
293 Keep-Alive header is removed.
298 > Fixed a bug on mingw32 where downloading large files failed if
299 keep-alive support was enabled.
304 > Fixed a bug that (at least theoretically) could cause log
305 timestamps to be occasionally off by about a second.
310 > The configure script respects the $PATH variable when searching
316 > Compressed content with extra fields couldn't be decompressed
317 and would get passed to the client unfiltered. This problem
318 has only be detected through statical analysis with clang as
319 nobody seems to be using extra fields anyway.
324 > If the server resets the Connection after sending only the headers
325 Privoxy forwards what it got to the client. Previously Privoxy
326 would deliver an error message instead.
331 > Error messages in case of connection timeouts use the right
337 > If spawning a child to handle a request fails, the client
338 gets an error message and Privoxy continues to listen for
339 new requests right away.
344 > The error messages in case of server-connection timeouts or
345 prematurely closed server connections are now template-based.
350 > If zlib support isn't compiled in, Privoxy no longer tries to
351 filter compressed content unless explicitly asked to do so.
356 > In case of connections that are denied based on ACL directives,
357 the memory used for the client IP is no longer leaked.
362 > Fixed another small memory leak if the client request times out
363 while waiting for client headers other than the request line.
368 > The client socket is kept open until the server socket has
369 been marked as unused. This should increase the chances that
370 the still-open connection will be reused for the client's next
371 request to the same destination. Note that this only matters
372 if connection-sharing is enabled.
377 > A TODO list has been added to the source tarballs to give potential
378 volunteers a better idea of what the current goals are. Donations
379 are still welcome too: http://www.privoxy.org/faq/general.html#DONATE
390 >3.1. Note to Upgraders</A
393 > A quick list of things to be aware of before upgrading from earlier
404 > The recommended way to upgrade <SPAN
407 > is to backup your old
408 configuration files, install the new ones, verify that <SPAN
412 is working correctly and finally merge back your changes using
422 > There are a number of new features in each <SPAN
426 most of them have to be explicitly enabled in the configuration
427 files. Old configuration files obviously don't do that and due
428 to syntax changes using old configuration files with a new
432 > isn't always possible anyway.
438 Note that some installers remove earlier versions completely,
439 including configuration files, therefore you should really save
440 any important configuration files!
446 On the other hand, other installers don't overwrite existing configuration
447 files, thinking you will want to do that yourself.
456 > has been merged into
465 > In the default configuration only fatal errors are logged now.
466 You can change that in the <A
467 HREF="config.html#DEBUG"
470 of the configuration file. You may also want to enable more verbose
471 logging until you verified that the new <SPAN
480 > Three other config file settings are now off by default:
482 HREF="config.html#ENABLE-REMOTE-TOGGLE"
483 >enable-remote-toggle</A
486 HREF="config.html#ENABLE-REMOTE-HTTP-TOGGLE"
487 >enable-remote-http-toggle</A
490 HREF="config.html#ENABLE-EDIT-ACTIONS"
491 >enable-edit-actions</A
493 If you use or want these, you will need to explicitly enable them, and
494 be aware of the security issues involved.
506 SUMMARY="Footer navigation table"
517 HREF="installation.html"
535 HREF="quickstart.html"
555 >Quickstart to Using Privoxy</TD