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
88 > introduces IPv6 support,
89 improved keep-alive support and a bunch of minor improvements:</P
96 > Added IPv6 support. Thanks to Petr Pisar who not only provided
97 the initial patch but also helped a lot with the integration.
102 > Added client-side keep-alive support. This should also allow
103 NTLM authentication through Privoxy, but this hasn't been
109 > The connection sharing code is only used if the connection-sharing
115 > The max-client-connections option has been added to restrict
116 the number of client connections below a value enforced by
117 the operating system.
122 > Fixed a regression reintroduced in 3.0.12 that could cause
123 crashes on mingw32 if header date randomization was enabled.
128 > Compressed content with extra fields couldn't be decompressed
129 and would get passed to the client unfiltered. This problem
130 has only be detected through statical analysis with clang as
131 nobody seems to be using extra fields anyway.
136 > If the server resets the Connection after sending only the headers
137 Privoxy forwards what it got to the client. Previously Privoxy
138 would deliver an error message instead.
143 > Error messages in case of connection timeouts use the right
149 > If spawning a child to handle a request fails, the client
150 gets an error message and Privoxy continues to listen for
151 new requests right away.
156 > The error messages in case of server-connection timeouts or
157 prematurely closed server connections are now template-based.
162 > If zlib support isn't compiled in, Privoxy no longer tries to
163 filter compressed content unless explicitly asked to do so.
168 > In case of connections that are denied based on ACL directives,
169 the memory used for the client IP is no longer leaked.
174 > Fixed another small memory leak if the client request times out
175 while waiting for client headers other than the request line.
180 > The client socket is kept open until the server socket has
181 been marked as unused. This should increase the chances that
182 the still-open connection will be reused for the client's next
183 request to the same destination. Note that this only matters
184 if connection-sharing is enabled.
189 > A TODO list has been added to the source tarballs to give potential
190 volunteers a better idea of what the current goals are. Donations
191 are still welcome too: http://www.privoxy.org/faq/general.html#DONATE
202 >3.1. Note to Upgraders</A
205 > A quick list of things to be aware of before upgrading from earlier
216 > The recommended way to upgrade <SPAN
219 > is to backup your old
220 configuration files, install the new ones, verify that <SPAN
224 is working correctly and finally merge back your changes using
234 > There are a number of new features in each <SPAN
238 most of them have to be explicitly enabled in the configuration
239 files. Old configuration files obviously don't do that and due
240 to syntax changes using old configuration files with a new
244 > isn't always possible anyway.
250 Note that some installers remove earlier versions completely,
251 including configuration files, therefore you should really save
252 any important configuration files!
258 On the other hand, other installers don't overwrite existing configuration
259 files, thinking you will want to do that yourself.
268 > has been merged into
277 > In the default configuration only fatal errors are logged now.
278 You can change that in the <A
279 HREF="config.html#DEBUG"
282 of the configuration file. You may also want to enable more verbose
283 logging until you verified that the new <SPAN
292 > Three other config file settings are now off by default:
294 HREF="config.html#ENABLE-REMOTE-TOGGLE"
295 >enable-remote-toggle</A
298 HREF="config.html#ENABLE-REMOTE-HTTP-TOGGLE"
299 >enable-remote-http-toggle</A
302 HREF="config.html#ENABLE-EDIT-ACTIONS"
303 >enable-edit-actions</A
305 If you use or want these, you will need to explicitly enable them, and
306 be aware of the security issues involved.
318 SUMMARY="Footer navigation table"
329 HREF="installation.html"
347 HREF="quickstart.html"
367 >Quickstart to Using Privoxy</TD