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.11 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.11 User Manual</TH
53 HREF="installation.html"
67 HREF="quickstart.html"
82 >3. What's New in this Release</A
85 > There are only a few improvements and new features since
89 >, the last stable release:</P
96 > On most platforms, outgoing connections can be kept alive and
97 reused if the server supports it. Whether or not this improves
98 things depends on the connection.
103 > When dropping privileges, membership in supplementary groups
104 is given up as well. Not doing that can lead to Privoxy running
105 with more rights than necessary and violates the principle of
106 least privilege. Users of the --user option are advised to update.
107 Thanks to Matthias Drochner for reporting the problem,
108 providing the initial patch and testing the final version.
113 > Passing invalid users or groups with the --user option
114 didn't lead to program exit. Regression introduced in 3.0.7.
119 > The match all section has been moved from default.action
120 to a new file called match-all.action. As a result the
121 default.action no longer needs to be touched by the user
122 and can be safely overwritten by updates.
127 > The standard.action file has been removed. Its content
128 is now part of the default.action file.
133 > In some situations the logged content length was slightly too low.
138 > Crunched requests are logged with their own log level.
139 If you used "debug 1" in the past, you'll probably want
140 to additionally enable "debug 1024", otherwise only passed
141 requests will be logged. If you only care about crunched
142 requests, simply replace "debug 1" with "debug 1024".
147 > The crunch reason has been moved to the beginning of the
148 crunch message. For HTTP URLs, the protocol is logged as well.
153 > Log messages are shortened by printing the thread id on its
154 own (as opposed to putting it inside the string "Privoxy()").
159 > The config option socket-timeout has been added to control
160 the time Privoxy waits for data to arrive on a socket.
165 > Support for remote toggling is controlled by the configure
166 option --disable-toggle only. In previous versions it also
167 depended on the action editor and thus configuring with the
168 --disable-editor option would disable remote toggling support
174 > Requests with invalid HTTP versions are rejected.
179 > The template symbol @date@ can be used to include a date(1)-like
180 time string. Initial patch submitted by Endre Szabo.
185 > Responses from shoutcast servers are accepted again.
186 Problem reported and fix suggested by Stefan.
191 > The hide-forwarded-for-headers action has been replaced with
192 the change-x-forwarded-for{} action which can also be used to
193 add X-Forwarded-For headers. The latter functionality already
194 existed in Privoxy versions prior to 3.0.7 but has been removed
195 as it was often used unintentionally (by not using the
196 hide-forwarded-for-headers action).
201 > A "clear log" view option was added to the mingw32 version
202 to clear out all of the lines in the Privoxy log window.
203 Based on a patch submitted by T Ford.
208 > The mingw32 version uses "critical sections" now, which prevents
209 log message corruption under load. As a side effect, the
210 "no thread-safe PRNG" warning could be removed as well.
215 > The mingw32 version's task bar icon is crossed out and
216 the color changed to gray if Privoxy is toggled off.
222 > This release marks a departure for Privoxy development.</P
224 > Previously, odd numbered releases were considered beta versions and
225 were only released at the end of the development cycle when the code
226 was already believed to be stable. Usually it was, so the stable release
227 contained pretty much the same code, but got a higher version number.
228 In the future we intend to release several snapshots between stable releases.
229 There will probably still be about two stable releases per year,
230 but hopefully about six snapshots instead of the two betas we have now.
231 The intentions is to make testing without CVS access easier.</P
238 >3.1. Note to Upgraders</A
241 > A quick list of things to be aware of before upgrading from earlier
252 > The recommended way to upgrade <SPAN
255 > is to backup your old
256 configuration files, install the new ones, verify that <SPAN
260 is working correctly and finally merge back your changes using
270 > There are a number of new features in each <SPAN
274 most of them have to be explicitly enabled in the configuration
275 files. Old configuration files obviously don't do that and due
276 to syntax changes using old configuration files with a new
280 > isn't always possible anyway.
286 Note that some installers remove earlier versions completely,
287 including configuration files, therefore you should really save
288 any important configuration files!
294 On the other hand, other installers don't overwrite existing configuration
295 files, thinking you will want to do that yourself.
304 > has been merged into
313 > In the default configuration only fatal errors are logged now.
314 You can change that in the <A
315 HREF="config.html#DEBUG"
318 of the configuration file. You may also want to enable more verbose
319 logging until you verified that the new <SPAN
328 > Three other config file settings are now off by default:
330 HREF="config.html#ENABLE-REMOTE-TOGGLE"
331 >enable-remote-toggle</A
334 HREF="config.html#ENABLE-REMOTE-HTTP-TOGGLE"
335 >enable-remote-http-toggle</A
338 HREF="config.html#ENABLE-EDIT-ACTIONS"
339 >enable-edit-actions</A
341 If you use or want these, you will need to explicitly enable them, and
342 be aware of the security issues involved.
354 SUMMARY="Footer navigation table"
365 HREF="installation.html"
383 HREF="quickstart.html"
403 >Quickstart to Using Privoxy</TD