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.14 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.14 User Manual</TH
53 HREF="installation.html"
67 HREF="quickstart.html"
82 >3. What's New in this Release</A
87 >Privoxy 3.0.14 Beta</SPAN
89 for the previous beta which introduced IPv6 support, improved keep-alive
90 support and a bunch of minor improvements. The changes since 3.0.12:</P
97 > Added IPv6 support. Thanks to Petr Pisar who not only provided
98 the initial patch but also helped a lot with the integration.
103 > Added client-side keep-alive support.
108 > The connection sharing code is only used if the connection-sharing
114 > The latency is taken into account when evaluating whether or not to
115 reuse a connection. This should significantly reduce the number of
116 connections problems several users reported.
121 > The max-client-connections option has been added to restrict
122 the number of client connections below a value enforced by
123 the operating system.
128 > If the server doesn't specify how long the connection stays alive,
129 Privoxy errs on the safe side of caution and assumes it's only a second.
134 > Setting keep-alive-timeout to 0 disables keep-alive support. Previously
135 Privoxy would claim to allow persistence but not reuse the connection.
140 > Pipelined requests are less likely to be mistaken for the request
141 body of the previous request. Note that Privoxy still has no real
142 pipeline support and will either serialize pipelined requests or
143 drop them in which case the client has to resent them.
148 > Fixed a crash on some Windows versions when header randomization
149 is enabled and the date couldn't be parsed.
154 > Privoxy's keep-alive timeout for the current connection is reduced
155 to the one specified in the client's Keep-Alive header.
160 > For HTTP/1.1 requests, Privoxy implies keep-alive support by not
161 setting any Connection header instead of using 'Connection: keep-alive'.
166 > If the socket isn't reusable, Privoxy doesn't temporarily waste
167 a socket slot to remember the connection.
172 > If keep-alive support is disabled but compiled in, the client's
173 Keep-Alive header is removed.
178 > Fixed a bug on mingw32 where downloading large files failed if
179 keep-alive support was enabled.
184 > Fixed a bug that (at least theoretically) could cause log
185 timestamps to be occasionally off by about a second.
190 > The configure script respects the $PATH variable when searching
196 > Compressed content with extra fields couldn't be decompressed
197 and would get passed to the client unfiltered. This problem
198 has only be detected through statical analysis with clang as
199 nobody seems to be using extra fields anyway.
204 > If the server resets the Connection after sending only the headers
205 Privoxy forwards what it got to the client. Previously Privoxy
206 would deliver an error message instead.
211 > Error messages in case of connection timeouts use the right
217 > If spawning a child to handle a request fails, the client
218 gets an error message and Privoxy continues to listen for
219 new requests right away.
224 > The error messages in case of server-connection timeouts or
225 prematurely closed server connections are now template-based.
230 > If zlib support isn't compiled in, Privoxy no longer tries to
231 filter compressed content unless explicitly asked to do so.
236 > In case of connections that are denied based on ACL directives,
237 the memory used for the client IP is no longer leaked.
242 > Fixed another small memory leak if the client request times out
243 while waiting for client headers other than the request line.
248 > The client socket is kept open until the server socket has
249 been marked as unused. This should increase the chances that
250 the still-open connection will be reused for the client's next
251 request to the same destination. Note that this only matters
252 if connection-sharing is enabled.
257 > A TODO list has been added to the source tarballs to give potential
258 volunteers a better idea of what the current goals are. Donations
259 are still welcome too: http://www.privoxy.org/faq/general.html#DONATE
270 >3.1. Note to Upgraders</A
273 > A quick list of things to be aware of before upgrading from earlier
284 > The recommended way to upgrade <SPAN
287 > is to backup your old
288 configuration files, install the new ones, verify that <SPAN
292 is working correctly and finally merge back your changes using
302 > There are a number of new features in each <SPAN
306 most of them have to be explicitly enabled in the configuration
307 files. Old configuration files obviously don't do that and due
308 to syntax changes using old configuration files with a new
312 > isn't always possible anyway.
318 Note that some installers remove earlier versions completely,
319 including configuration files, therefore you should really save
320 any important configuration files!
326 On the other hand, other installers don't overwrite existing configuration
327 files, thinking you will want to do that yourself.
336 > has been merged into
345 > In the default configuration only fatal errors are logged now.
346 You can change that in the <A
347 HREF="config.html#DEBUG"
350 of the configuration file. You may also want to enable more verbose
351 logging until you verified that the new <SPAN
360 > Three other config file settings are now off by default:
362 HREF="config.html#ENABLE-REMOTE-TOGGLE"
363 >enable-remote-toggle</A
366 HREF="config.html#ENABLE-REMOTE-HTTP-TOGGLE"
367 >enable-remote-http-toggle</A
370 HREF="config.html#ENABLE-EDIT-ACTIONS"
371 >enable-edit-actions</A
373 If you use or want these, you will need to explicitly enable them, and
374 be aware of the security issues involved.
386 SUMMARY="Footer navigation table"
397 HREF="installation.html"
415 HREF="quickstart.html"
435 >Quickstart to Using Privoxy</TD