1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
2 "http://www.w3.org/TR/html4/loose.dtd">
5 <title>What's New in this Release</title>
6 <meta name="GENERATOR" content=
7 "Modular DocBook HTML Stylesheet Version 1.79">
8 <link rel="HOME" title="Privoxy 3.0.27 User Manual" href="index.html">
9 <link rel="PREVIOUS" title="Installation" href="installation.html">
10 <link rel="NEXT" title="Quickstart to Using Privoxy" href=
12 <link rel="STYLESHEET" type="text/css" href="../p_doc.css">
13 <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
14 <link rel="STYLESHEET" type="text/css" href="p_doc.css">
16 <body class="SECT1" bgcolor="#EEEEEE" text="#000000" link="#0000FF" vlink=
17 "#840084" alink="#0000FF">
18 <div class="NAVHEADER">
19 <table summary="Header navigation table" width="100%" border="0"
20 cellpadding="0" cellspacing="0">
22 <th colspan="3" align="center">Privoxy 3.0.27 User Manual</th>
25 <td width="10%" align="left" valign="bottom"><a href=
26 "installation.html" accesskey="P">Prev</a></td>
27 <td width="80%" align="center" valign="bottom"></td>
28 <td width="10%" align="right" valign="bottom"><a href=
29 "quickstart.html" accesskey="N">Next</a></td>
32 <hr align="left" width="100%">
35 <h1 class="SECT1"><a name="WHATSNEW" id="WHATSNEW">3. What's New in this
37 <p><span class="APPLICATION">Privoxy 3.0.26</span> stable is a bug-fix
38 release for the previously released 3.0.25 beta which introduced
39 client-specific tags and included a couple of minor improvements.</p>
45 <p>Fixed crashes with "listen-addr :8118" (SF Bug #902). The
46 regression was introduced in 3.0.25 beta and reported by Marvin
47 Renich in Debian bug #834941.</p>
52 <p>General improvements:</p>
55 <p>Log when privoxy is toggled on or off via cgi interface.</p>
58 <p>Highlight the "Info: Now toggled " on/off log message in the
59 Windows log viewer.</p>
62 <p>Highlight the loading actions/filter file log message in the
63 Windows log viewer.</p>
66 <p>Mention client-specific tags on the toggle page as a
67 potentionally more appropriate alternative.</p>
72 <p>Documentation improvements:</p>
75 <p>Update download section on the homepage. The downloads are
76 available from the website now.</p>
79 <p>Add sponsor FAQ.</p>
82 <p>Remove obsolete reference to mailing lists hosted at
86 <p>Update the "Before the Release" section of the developer
92 <p>Infrastructure improvements:</p>
95 <p>Add perl script to generate an RSS feed for the packages
96 Submitted by "Unknown".</p>
101 <p>Build system improvements:</p>
104 <p>strptime.h: fix a compiler warning about ambiguous else.</p>
107 <p>configure.in: Check for Docbook goo on the BSDs as well.</p>
110 <p>GNUMakefile.in: Let the dok-user target remove temporary
116 <p>Changes between <span class="APPLICATION">Privoxy 3.0.25 beta</span>
117 and the previous release:</p>
123 <p>Always use the current toggle state for new requests.
124 Previously new requests on reused connections inherited the
125 toggle state from the previous request even though the toggle
126 state could have changed. Reported by Robert Klemme.</p>
129 <p>Fixed two buffer-overflows in the (deprecated) static pcre
130 code. These bugs are not considered security issues as the input
131 is trusted. Found with afl-fuzz and ASAN.</p>
136 <p>General improvements:</p>
139 <p>Added support for client-specific tags which allow Privoxy
140 admins to pre-define tags that are set for all requests from
141 clients that previously opted in through the CGI interface. They
142 are useful in multi-user setups where admins may want to allow
143 users to disable certain actions and filters for themselves
144 without affecting others. In single-user setups they are useful
145 to allow more fine-grained toggling. For example to disable
146 request blocking while still crunching cookies, or to disable
147 experimental filters only. This is an experimental feature, the
148 syntax and behaviour may change in future versions. Sponsored by
152 <p>Dynamic filters and taggers now support a $listen-address
153 variable which contains the address the request came in on. For
154 external filters the variable is called $PRIVOXY_LISTEN_ADDRESS.
155 Original patch contributed by pursievro.</p>
158 <p>Add client-header-tagger 'listen-address'.</p>
161 <p>Include the listen-address in the log message when logging new
162 requests. Patch contributed by pursievro.</p>
165 <p>Turn invalid max-client-connections values into fatal
169 <p>The show-status page now shows whether or not dates before
170 1970 and after 2038 are expected to be handled properly. This is
171 mainly useful for Privoxy-Regression-Test but could also come
172 handy when dealing with time-related support requests.</p>
175 <p>On Mac OS X the thread id in log messages are more likely to
179 <p>When complaining about missing filters, the filter type is
183 <p>A couple of harmless coverity warnings were silenced (CID
184 #161202, CID #161203, CID #161211).</p>
189 <p>Action file improvements:</p>
192 <p>Filtering is disabled for Range requests to let download
193 resumption and Windows updates work with the default
197 <p>Unblock ".ardmediathek.de/". Reported by ThTomate in #932.</p>
202 <p>Documentation improvements:</p>
205 <p>Add FAQ entry for crashes caused by memory limits.</p>
208 <p>Remove obsolete FAQ entry about a bug in PHP 4.2.3.</p>
211 <p>Mention the new mailing lists were appropriate. As the
212 archives have not been migrated, continue to mention the archives
213 at SF in the contacting section for now.</p>
216 <p>Note that the templates should be adjusted if Privoxy is
217 running as intercepting proxy without getting all requests.</p>
220 <p>A bunch of links were converted to https://.</p>
223 <p>Rephrase onion service paragraph to make it more obvious that
224 Tor is involved and that the whole website (and not just the
225 homepage) is available as onion service.</p>
228 <p>Streamline the "More information" section on the homepage
229 further by additionally ditching the link to the 'See also'
230 section of the user manual. The section contains mostly links
231 that are directly reachable from the homepage already and the
232 rest is not significant enough to get a link from the
236 <p>Change the add-header{} example to set the DNT header and use
237 a complete section to make copy and pasting more convenient. Add
238 a comment to make it obvious that adding the header is not
239 recommended for obvious reasons. Using the DNT header as example
240 was suggested by Leo Wzukw.</p>
243 <p>Streamline the support-and-service template Instead of linking
244 to the various support trackers (whose URLs hopefully change
245 soon), link to the contact section of the user manual to increase
246 the chances that users actually read it.</p>
249 <p>Add a FAQ entry for tainted sockets.</p>
252 <p>More sections in the documentation have stable URLs now.</p>
255 <p>FAQ: Explain why 'ping config.privoxy.org' is not expected to
256 reach a local Privoxy installation.</p>
259 <p>Note that donations done through Zwiebelfreunde e.V. currently
260 can't be checked automatically.</p>
263 <p>Updated section regarding starting Privoxy under OS X.</p>
266 <p>Use dedicated start instructions for FreeBSD and
270 <p>Removed release instructions for AIX. They haven't been
271 working for years and unsurprisingly nobody seems to care.</p>
274 <p>Removed obsolete reference to the solaris-dist target.</p>
277 <p>Updated the release instructions for FreeBSD.</p>
280 <p>Removed unfinished release instructions for Amiga OS and HP-UX
284 <p>Added a pointer to the Cygwin Time Machine for getting the
285 last release of Cygwin version 1.5 to use for building Privoxy on
289 <p>Various typos have been fixed.</p>
294 <p>Infrastructure improvements:</p>
297 <p>The website is no longer hosted at SourceForge and can be
298 reached through https now.</p>
301 <p>The mailing lists at SourceForge have been deprecated, you can
302 subscribe to the new ones at: https://lists.privoxy.org/</p>
305 <p>Migrating the remaining services from SourceForge is work in
306 progress (TODO list item #53).</p>
311 <p>Build system improvements:</p>
314 <p>Add configure argument to optimistically redefine FD_SETSIZE
315 with the intent to change the maximum number of client
316 connections Privoxy can handle. Only works with some libcs.
317 Sponsored by Robert Klemme.</p>
320 <p>Let the tarball-dist target skip files in ".git".</p>
323 <p>Let the tarball-dist target work in cwds other than
327 <p>Make the 'clean' target faster when run from a git
331 <p>Include tools in the generic distribution.</p>
334 <p>Let the gen-dist target work in cwds other than current.</p>
337 <p>Sort find output that is used for distribution tarballs to get
338 reproducible results.</p>
341 <p>Don't add '-src' to the name of the tar ball generated by the
342 gen-dist target. The package isn't a source distribution but a
343 binary package. While at it, use a variable for the name to
344 reduce the chances that the various references get out of sync
345 and fix the gen-upload target which was looking in the wrong
349 <p>Add regression-tests.action to the files that are
353 <p>The gen-dist target which was broken since 2002 (r1.92) has
357 <p>Remove genclspec.sh which has been obsolete since 2009.</p>
360 <p>Remove obsolete reference to Redhat spec file.</p>
363 <p>Remove the obsolete announce target which has been commented
367 <p>Let rsync skip files if the checksums match.</p>
372 <p>Privoxy-Regression-Test:</p>
375 <p>Add a "Default level offset" directive which can be used to
376 change the default level by a given value. This directive affects
377 all tests located after it until the end of the file or a another
378 "Default level offset" directive is reached. The purpose of this
379 directive is to make it more convenient to skip similar tests in
380 a given file without having to remove or disable the tests
384 <p>Let test level 17 depend on FEATURE_64_BIT_TIME_T instead of
385 FEATURE_PTHREAD which has no direct connection to the time_t
389 <p>Fix indentation in perldoc examples.</p>
392 <p>Don't overlook directives in the first line of the action
396 <p>Bump version to 0.7.</p>
399 <p>Fix detection of the Privoxy version now that https:// is used
406 <h2 class="SECT2"><a name="UPGRADERSNOTE" id="UPGRADERSNOTE">3.1. Note
407 to Upgraders</a></h2>
408 <p>A quick list of things to be aware of before upgrading from earlier
409 versions of <span class="APPLICATION">Privoxy</span>:</p>
412 <p>The recommended way to upgrade <span class=
413 "APPLICATION">Privoxy</span> is to backup your old configuration
414 files, install the new ones, verify that <span class=
415 "APPLICATION">Privoxy</span> is working correctly and finally merge
416 back your changes using <span class="APPLICATION">diff</span> and
417 maybe <span class="APPLICATION">patch</span>.</p>
418 <p>There are a number of new features in each <span class=
419 "APPLICATION">Privoxy</span> release and most of them have to be
420 explicitly enabled in the configuration files. Old configuration
421 files obviously don't do that and due to syntax changes using old
422 configuration files with a new <span class=
423 "APPLICATION">Privoxy</span> isn't always possible anyway.</p>
426 <p>Note that some installers remove earlier versions completely,
427 including configuration files, therefore you should really save any
428 important configuration files!</p>
431 <p>On the other hand, other installers don't overwrite existing
432 configuration files, thinking you will want to do that
436 <p>In the default configuration only fatal errors are logged now.
437 You can change that in the <a href="config.html#DEBUG">debug
438 section</a> of the configuration file. You may also want to enable
439 more verbose logging until you verified that the new <span class=
440 "APPLICATION">Privoxy</span> version is working as expected.</p>
443 <p>Three other config file settings are now off by default:
444 <a href="config.html#ENABLE-REMOTE-TOGGLE">enable-remote-toggle</a>,
446 "config.html#ENABLE-REMOTE-HTTP-TOGGLE">enable-remote-http-toggle</a>,
448 "config.html#ENABLE-EDIT-ACTIONS">enable-edit-actions</a>. If you
449 use or want these, you will need to explicitly enable them, and be
450 aware of the security issues involved.</p>
455 <div class="NAVFOOTER">
456 <hr align="left" width="100%">
457 <table summary="Footer navigation table" width="100%" border="0"
458 cellpadding="0" cellspacing="0">
460 <td width="33%" align="left" valign="top"><a href="installation.html"
461 accesskey="P">Prev</a></td>
462 <td width="34%" align="center" valign="top"><a href="index.html"
463 accesskey="H">Home</a></td>
464 <td width="33%" align="right" valign="top"><a href="quickstart.html"
465 accesskey="N">Next</a></td>
468 <td width="33%" align="left" valign="top">Installation</td>
469 <td width="34%" align="center" valign="top"> </td>
470 <td width="33%" align="right" valign="top">Quickstart to Using