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.9 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.9 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
96 HREF="actions-file.html#SERVER-HEADER-TAGGER"
97 >server-header-tagger</A
100 HREF="actions-file.html#CLIENT-HEADER-TAGGER"
101 >client-header-tagger</A
103 that can be used to create arbitrary <SPAN
107 based on client and server headers.
111 > can then subsequently be used
112 to control the other actions used for the current request,
113 greatly increasing <SPAN
116 >'s flexibility and selectivity. See <A
117 HREF="actions-file.html#TAG-PATTERN"
119 > for more information on tags.
124 > Header filtering is done with dedicated header filters now. As a result
127 >"filter-client-headers"</SPAN
130 >"filter-server-headers"</SPAN
132 that were introduced with <SPAN
136 content filters to the headers have been removed.
137 See the new actions <A
138 HREF="actions-file.html#SERVER-HEADER-FILTER"
139 >server-header-filter</A
142 HREF="actions-file.html#CLIENT-HEADER-FILTER"
143 >client-header-filter</A
149 > There are four new options for the main <TT
160 HREF="config.html#ALLOW-CGI-REQUEST-CRUNCHING"
161 >allow-cgi-request-crunching</A
163 which allows requests for Privoxy's internal CGI pages to be
164 blocked, redirected or (un)trusted like ordinary requests.
170 HREF="config.html#SPLIT-LARGE-FORMS"
171 >split-large-forms</A
173 that will work around a browser bug that caused IE6 and IE7 to
174 ignore the Submit button on the Privoxy's edit-actions-for-url CGI
181 HREF="config.html#ACCEPT-INTERCEPTED-REQUESTS"
182 >accept-intercepted-requests</A
184 which allows to combine Privoxy with any packet filter to create an
185 intercepting proxy for HTTP/1.1 requests (and for HTTP/1.0 requests
186 with Host header set). This means clients can be forced to use
190 > even if their proxy settings are configured differently.
196 HREF="config.html#TEMPLDIR"
199 to designate an alternate location for <SPAN
203 locally customized CGI templates so that
204 these are not overwritten during upgrades.
211 > A new command line option <TT
213 >--pre-chroot-nslookup hostname</TT
215 initialize the resolver library before chroot'ing. On some systems this
216 reduces the number of files that must be copied into the chroot tree.
217 (Patch provided by Stephen Gildea)
223 HREF="actions-file.html#FORWARD-OVERRIDE"
226 allows changing of the forwarding settings through the actions files.
227 Combined with tags, this allows to choose the forwarder based on
228 client headers like the <TT
231 >, or the request origin.
237 HREF="actions-file.html#REDIRECT"
239 > action can now use regular
240 expression substitutions against the original URL.
248 > support is now available as a compile
249 time option to filter compressed content. Patch provided by Wil Mahan.
254 > Improve various filters, and add new ones.
259 > Include support for RFC 3253 so that <TT
266 >. Patch provided by Petr Kadlec.
271 > Logging can be completely turned off by not specifying a logfile directive.
276 > A number of improvements to Privoxy's internal CGI pages, including the
277 use of favicons for error and control pages.
282 > Many bugfixes, memory leaks addressed, code improvements, and logging
289 > For a more detailed list of changes please have a look at the ChangeLog.</P
296 >3.1. Note to Upgraders</A
299 > A quick list of things to be aware of before upgrading from earlier
310 > The recommended way to upgrade <SPAN
313 > is to backup your old
314 configuration files, install the new ones, verify that <SPAN
318 is working correctly and finally merge back your changes using
328 > There are a number of new features in each <SPAN
332 most of them have to be explicitly enabled in the configuration
333 files. Old configuration files obviously don't do that and due
334 to syntax changes using old configuration files with a new
338 > isn't always possible anyway.
344 Note that some installers remove earlier versions completely,
345 including configuration files, therefore you should really save
346 any important configuration files!
352 On the other hand, other installers don't overwrite existing configuration
353 files, thinking you will want to do that yourself.
362 > now only includes the enabled actions.
363 Not all actions as before.
368 > In the default configuration only fatal errors are logged now.
369 You can change that in the <A
370 HREF="config.html#DEBUG"
373 of the configuration file. You may also want to enable more verbose
374 logging until you verified that the new <SPAN
383 > Three other config file settings are now off by default:
385 HREF="config.html#ENABLE-REMOTE-TOGGLE"
386 >enable-remote-toggle</A
389 HREF="config.html#ENABLE-REMOTE-HTTP-TOGGLE"
390 >enable-remote-http-toggle</A
393 HREF="config.html#ENABLE-EDIT-ACTIONS"
394 >enable-edit-actions</A
396 If you use or want these, you will need to explicitly enable them, and
397 be aware of the security issues involved.
404 >"filter-client-headers"</SPAN
408 >"filter-server-headers"</SPAN
409 > actions that were introduced with
413 > to apply content filters to
414 the headers have been removed and replaced with new actions.
417 >What's New section</A
430 SUMMARY="Footer navigation table"
441 HREF="installation.html"
459 HREF="quickstart.html"
479 >Quickstart to Using Privoxy</TD