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.7 User Manual"
11 HREF="index.html"><LINK
14 HREF="installation.html"><LINK
16 TITLE="Quickstart to Using Privoxy"
17 HREF="quickstart.html"><LINK
21 <LINK REL="STYLESHEET" TYPE="text/css" HREF="p_doc.css">
33 SUMMARY="Header navigation table"
42 >Privoxy 3.0.7 User Manual</TH
50 HREF="installation.html"
64 HREF="quickstart.html"
79 >3. What's New in this Release</A
82 > There are many improvements and new features since <SPAN
85 >, the last stable release:</P
93 HREF="actions-file.html#SERVER-HEADER-TAGGER"
94 >server-header-tagger</A
97 HREF="actions-file.html#CLIENT-HEADER-TAGGER"
98 >client-header-tagger</A
100 that can be used to create arbitrary <SPAN
104 based on client and server headers.
108 > can then subsequently be used
109 to control the other actions used for the current request,
110 greatly increasing <SPAN
113 >'s flexibility and selectivity. See <A
114 HREF="actions-file.html#TAG-PATTERN"
116 > for more information on tags.
121 > Header filtering is done with dedicated header filters now. As a result
124 >"filter-client-headers"</SPAN
127 >"filter-server-headers"</SPAN
129 that were introduced with <SPAN
133 content filters to the headers have been removed.
134 See the new actions <A
135 HREF="actions-file.html#SERVER-HEADER-FILTER"
136 >server-header-filter</A
139 HREF="actions-file.html#CLIENT-HEADER-FILTER"
140 >client-header-filter</A
146 > There are four new options for the main <TT
157 HREF="config.html#ALLOW-CGI-REQUEST-CRUNCHING"
158 >allow-cgi-request-crunching</A
160 which allows requests for Privoxy's internal CGI pages to be
161 blocked, redirected or (un)trusted like ordinary requests.
167 HREF="config.html#SPLIT-LARGE-FORMS"
168 >split-large-forms</A
170 that will work around a browser bug that caused IE6 and IE7 to
171 ignore the Submit button on the Privoxy's edit-actions-for-url CGI
178 HREF="config.html#ACCEPT-INTERCEPTED-REQUESTS"
179 >accept-intercepted-requests</A
181 which allows to combine Privoxy with any packet filter to create an
182 intercepting proxy for HTTP/1.1 requests (and for HTTP/1.0 requests
183 with Host header set). This means clients can be forced to use
187 > even if their proxy settings are configured differently.
193 HREF="config.html#TEMPLDIR"
196 to designate an alternate location for <SPAN
200 locally customized CGI templates so that
201 these are not overwritten during upgrades.
208 > A new command line option <TT
210 >--pre-chroot-nslookup hostname</TT
212 initialize the resolver library before chroot'ing. On some systems this
213 reduces the number of files that must be copied into the chroot tree.
214 (Patch provided by Stephen Gildea)
220 HREF="actions-file.html#FORWARD-OVERRIDE"
223 allows changing of the forwarding settings through the actions files.
224 Combined with tags, this allows to choose the forwarder based on
225 client headers like the <TT
228 >, or the request origin.
234 HREF="actions-file.html#REDIRECT"
236 > action can now use regular
237 expression substitutions against the original URL.
245 > support is now available as a compile
246 time option to filter compressed content. Patch provided by Wil Mahan.
251 > Improve various filters, and add new ones.
256 > Include support for RFC 3253 so that <TT
263 >. Patch provided by Petr Kadlec.
268 > Logging can be completely turned off by not specifying a logfile directive.
273 > A number of improvements to Privoxy's internal CGI pages, including the
274 use of favicons for error and control pages.
279 > Many bugfixes, memory leaks addressed, code improvements, and logging
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 > Logging is off by default now. If you need logging, it can be turned on
367 HREF="config.html#LOGFILE"
370 to enable logging until you verified that the new <SPAN
374 is working as expected.
379 > Three other config file settings are now off by default:
381 HREF="config.html#ENABLE-REMOTE-TOGGLE"
382 >enable-remote-toggle</A
385 HREF="config.html#ENABLE-REMOTE-HTTP-TOGGLE"
386 >enable-remote-http-toggle</A
389 HREF="config.html#ENABLE-EDIT-ACTIONS"
390 >enable-edit-actions</A
392 If you use or want these, you will need to explicitly enable them, and
393 be aware of the security issues involved.
400 >"filter-client-headers"</SPAN
404 >"filter-server-headers"</SPAN
405 > actions that were introduced with
409 > to apply content filters to
410 the headers have been removed and replaced with new actions.
413 >What's New section</A
426 SUMMARY="Footer navigation table"
437 HREF="installation.html"
455 HREF="quickstart.html"
475 >Quickstart to Using Privoxy</TD