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.12 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.12 User Manual</TH
53 HREF="installation.html"
67 HREF="quickstart.html"
82 >3. What's New in this Release</A
88 > is mainly a bugfix release:</P
95 > The socket-timeout option now also works on platforms whose
96 select() implementation modifies the timeout structure.
97 Previously the timeout was triggered even if the connection
98 didn't stall. Reported by cyberpatrol.
103 > The Connection: keep-alive code properly deals with files
104 larger than 2GB. Previously the connection was closed too
110 > The content length for files above 2GB is logged correctly.
115 > The user-manual directive on the show-status page links to
116 the documentation location specified with the directive,
117 not to the Privoxy website.
122 > When running in daemon mode, Privoxy doesn't log anything
123 to the console unless there are errors before the logfile
129 > The show-status page prints warnings about invalid directives
130 on the same line as the directives themselves.
135 > Fixed several justified (but harmless) compiler warnings,
136 mostly on 64 bit platforms.
141 > The mingw32 version explicitly requests the default charset
142 to prevent display problems with some fonts available on more
143 recent Windows versions. Patch by Burberry.
148 > The mingw32 version uses the Privoxy icon in the alt-tab
149 windows. Patch by Burberry.
154 > The timestamp and the thread id is omitted in the "Fatal error"
155 message box on mingw32.
160 > Fixed two related mingw32-only buffer overflows. Triggering
161 them required control over the configuration file, therefore
162 this isn't seen as a security issue.
167 > In verbose mode, or if the new option --show-skipped-tests
168 is used, Privoxy-Regression-Test logs skipped tests and the
180 >3.1. Note to Upgraders</A
183 > A quick list of things to be aware of before upgrading from earlier
194 > The recommended way to upgrade <SPAN
197 > is to backup your old
198 configuration files, install the new ones, verify that <SPAN
202 is working correctly and finally merge back your changes using
212 > There are a number of new features in each <SPAN
216 most of them have to be explicitly enabled in the configuration
217 files. Old configuration files obviously don't do that and due
218 to syntax changes using old configuration files with a new
222 > isn't always possible anyway.
228 Note that some installers remove earlier versions completely,
229 including configuration files, therefore you should really save
230 any important configuration files!
236 On the other hand, other installers don't overwrite existing configuration
237 files, thinking you will want to do that yourself.
246 > has been merged into
255 > In the default configuration only fatal errors are logged now.
256 You can change that in the <A
257 HREF="config.html#DEBUG"
260 of the configuration file. You may also want to enable more verbose
261 logging until you verified that the new <SPAN
270 > Three other config file settings are now off by default:
272 HREF="config.html#ENABLE-REMOTE-TOGGLE"
273 >enable-remote-toggle</A
276 HREF="config.html#ENABLE-REMOTE-HTTP-TOGGLE"
277 >enable-remote-http-toggle</A
280 HREF="config.html#ENABLE-EDIT-ACTIONS"
281 >enable-edit-actions</A
283 If you use or want these, you will need to explicitly enable them, and
284 be aware of the security issues involved.
296 SUMMARY="Footer navigation table"
307 HREF="installation.html"
325 HREF="quickstart.html"
345 >Quickstart to Using Privoxy</TD