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 many improvements and new features since <SPAN
88 >, the last stable release:</P
95 > Added SOCKS5 support (with address resolution done by
96 the SOCKS5 server). Patch provided by Eric M. Hopper.
101 > The "blocked" CGI pages include a block reason that was
102 provided as argument to the last-applying block action.
107 > If enable-edit-actions is disabled (the default since 3.0.7 beta)
108 the show-status page hides the edit buttons and explains why.
109 Previously the user would get the "this feature has been disabled"
110 message after using the edit button.
115 > Forbidden CONNECT requests are treated like blocks by default.
116 The now-pointless treat-forbidden-connects-like-blocks action
122 > Not enabling limit-connect now allows CONNECT requests to all ports.
123 In previous versions it would only allow CONNECT requests to port 443.
124 Use +limit-connect{443} if you think you need the old default behaviour.
129 > The CGI editor gets turned off after three edit requests with invalid
130 file modification timestamps. This makes life harder for attackers
131 who can leverage browser bugs to send fake Referers and intend to
132 brute-force edit URLs.
137 > Action settings for multiple patterns in the same section are
138 shared in memory. As a result these sections take up less space
139 (and are loaded slightly faster). Problem reported by Franz Schwartau.
144 > Linear white space in HTTP headers will be normalized to single
145 spaces before parsing the header's content, headers split across
146 multiple lines get merged first.
151 > Host information is gathered outside the main thread so it's less
152 likely to delay other incoming connections if the host is misconfigured.
157 > New config option "hostname" to use a hostname other than
158 the one returned by the operating system. Useful to speed-up responses
159 for CGI requests on misconfigured systems. Requested by Max Khon.
164 > The CGI editor supports the "disable all filters of this type"
165 directives "-client-header-filter", "-server-header-filter",
166 "-client-header-tagger" and "-server-header-tagger".
171 > Fixed false-positives with the link-by-url filter and URLs that
172 contain the pattern "/jump/".
177 > The less-download-windows filter no longer messes
178 "Content-Type: application/x-shockwave-flash" headers up.
183 > In the show-url-info page's "Final results" section active and
184 inactive actions are listed separately. Patch provided by Lee.
189 > The GNUmakefile supports the DESTDIR variable. Patch for
190 the install target submitted by Radoslaw Zielinski.
195 > Embedding the content of configuration files in the show-status
196 page is significantly faster now. For a largish action file (1 MB)
197 a speedup of about 2450 times has been measured. This is mostly
198 interesting if you are using large action files or regularly use
199 Privoxy-Regression-Test while running Privoxy through Valgrind,
200 for stock configuration files it doesn't really matter.
205 > If zlib support is unavailable and there are content
206 filters active but the prevent-compression action is disabled,
207 the show-url-info page includes a warning that compression
208 might prevent filtering.
213 > The show-url-info page provides an OpenSearch Description that
214 allows to access the page through browser search plugins.
219 > The obsolete kill-popups action has been removed as the
220 PCRS-based popup filters can do the same and are slightly
226 > The inspect-jpegs action has been removed.
231 > The send-wafer and send-vanilla-wafer actions have been removed.
232 They weren't particular useful and their behaviour could be emulated
233 with add-header anyway.
238 > Privoxy-Regression-Test has been significantly improved.
243 > Most sections in the default.action file contain tests for
244 Privoxy-Regression-Test to verify that they are working as intended.
249 > Parts of Privoxy have been refactored to increase maintainability.
254 > Building with zlib (if available) is done by default.
259 > Ordinary configuration file changes no longer cause program
260 termination on OS/2 if the name of the logfile hasn't been
261 changed as well. This regression probably crept in with the
262 logging improvements in 3.0.7. Reported by Maynard.
267 > The img-reorder filter is less likely to mess up JavaScript code in
268 img tags. Problem and solution reported by Glenn Washburn in #2014552.
273 > The source tar ball now includes Privoxy-Log-Parser,
274 a syntax-highlighter for Privoxy logs. Documentation is available
275 through perldoc(1), for fancy screenshots see:
277 HREF="http://www.fabiankeil.de/sourcecode/privoxy-log-parser/"
279 >http://www.fabiankeil.de/sourcecode/privoxy-log-parser/</A
286 > For a more detailed list of changes please have a look at the ChangeLog.</P
293 >3.1. Note to Upgraders</A
296 > A quick list of things to be aware of before upgrading from earlier
307 > The recommended way to upgrade <SPAN
310 > is to backup your old
311 configuration files, install the new ones, verify that <SPAN
315 is working correctly and finally merge back your changes using
325 > There are a number of new features in each <SPAN
329 most of them have to be explicitly enabled in the configuration
330 files. Old configuration files obviously don't do that and due
331 to syntax changes using old configuration files with a new
335 > isn't always possible anyway.
341 Note that some installers remove earlier versions completely,
342 including configuration files, therefore you should really save
343 any important configuration files!
349 On the other hand, other installers don't overwrite existing configuration
350 files, thinking you will want to do that yourself.
359 > now only includes the enabled actions.
360 Not all actions as before.
365 > In the default configuration only fatal errors are logged now.
366 You can change that in the <A
367 HREF="config.html#DEBUG"
370 of the configuration file. You may also want to enable more verbose
371 logging until you verified that the new <SPAN
380 > Three other config file settings are now off by default:
382 HREF="config.html#ENABLE-REMOTE-TOGGLE"
383 >enable-remote-toggle</A
386 HREF="config.html#ENABLE-REMOTE-HTTP-TOGGLE"
387 >enable-remote-http-toggle</A
390 HREF="config.html#ENABLE-EDIT-ACTIONS"
391 >enable-edit-actions</A
393 If you use or want these, you will need to explicitly enable them, and
394 be aware of the security issues involved.
401 >"filter-client-headers"</SPAN
405 >"filter-server-headers"</SPAN
406 > actions that were introduced with
410 > to apply content filters to
411 the headers have been removed and replaced with new actions.
414 >What's New section</A
427 SUMMARY="Footer navigation table"
438 HREF="installation.html"
456 HREF="quickstart.html"
476 >Quickstart to Using Privoxy</TD