NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
REL="HOME"
-TITLE="Privoxy 3.0.7 User Manual"
+TITLE="Privoxy 3.0.12 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Installation"
HREF="quickstart.html"><LINK
REL="STYLESHEET"
TYPE="text/css"
-HREF="../p_doc.css">
+HREF="../p_doc.css"><META
+HTTP-EQUIV="Content-Type"
+CONTENT="text/html;
+charset=ISO-8859-1">
<LINK REL="STYLESHEET" TYPE="text/css" HREF="p_doc.css">
</head
><BODY
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 3.0.7 User Manual</TH
+>Privoxy 3.0.12 User Manual</TH
></TR
><TR
><TD
>3. What's New in this Release</A
></H1
><P
-> There are many improvements and new features since <SPAN
+> <SPAN
CLASS="APPLICATION"
->Privoxy 3.0.6</SPAN
->, the last stable release:</P
+>Privoxy 3.0.12</SPAN
+> is mainly a bugfix release:</P
><P
> <P
></P
><UL
><LI
><P
-> Header filtering can be done with dedicated header filters now. As a result
- the actions <SPAN
-CLASS="QUOTE"
->"filter-client-headers"</SPAN
-> and <SPAN
-CLASS="QUOTE"
->"filter-server-headers"</SPAN
->
- that were introduced with <SPAN
-CLASS="APPLICATION"
->Privoxy 3.0.5</SPAN
-> to apply
- the content filters to the headers as, well have been removed again.
+> The socket-timeout option now also works on platforms whose
+ select() implementation modifies the timeout structure.
+ Previously the timeout was triggered even if the connection
+ didn't stall. Reported by cyberpatrol.
+ </P
+></LI
+><LI
+><P
+> The Connection: keep-alive code properly deals with files
+ larger than 2GB. Previously the connection was closed too
+ early.
+ </P
+></LI
+><LI
+><P
+> The content length for files above 2GB is logged correctly.
+ </P
+></LI
+><LI
+><P
+> The user-manual directive on the show-status page links to
+ the documentation location specified with the directive,
+ not to the Privoxy website.
+ </P
+></LI
+><LI
+><P
+> When running in daemon mode, Privoxy doesn't log anything
+ to the console unless there are errors before the logfile
+ has been opened.
+ </P
+></LI
+><LI
+><P
+> The show-status page prints warnings about invalid directives
+ on the same line as the directives themselves.
+ </P
+></LI
+><LI
+><P
+> Fixed several justified (but harmless) compiler warnings,
+ mostly on 64 bit platforms.
+ </P
+></LI
+><LI
+><P
+> The mingw32 version explicitly requests the default charset
+ to prevent display problems with some fonts available on more
+ recent Windows versions. Patch by Burberry.
+ </P
+></LI
+><LI
+><P
+> The mingw32 version uses the Privoxy icon in the alt-tab
+ windows. Patch by Burberry.
+ </P
+></LI
+><LI
+><P
+> The timestamp and the thread id is omitted in the "Fatal error"
+ message box on mingw32.
+ </P
+></LI
+><LI
+><P
+> Fixed two related mingw32-only buffer overflows. Triggering
+ them required control over the configuration file, therefore
+ this isn't seen as a security issue.
+ </P
+></LI
+><LI
+><P
+> In verbose mode, or if the new option --show-skipped-tests
+ is used, Privoxy-Regression-Test logs skipped tests and the
+ skip reason.
</P
></LI
></UL
><UL
><LI
><P
+> The recommended way to upgrade <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+> is to backup your old
+ configuration files, install the new ones, verify that <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+>
+ is working correctly and finally merge back your changes using
+ <SPAN
+CLASS="APPLICATION"
+>diff</SPAN
+> and maybe <SPAN
+CLASS="APPLICATION"
+>patch</SPAN
+>.
+ </P
+><P
+> There are a number of new features in each <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+> release and
+ most of them have to be explicitly enabled in the configuration
+ files. Old configuration files obviously don't do that and due
+ to syntax changes using old configuration files with a new
+ <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+> isn't always possible anyway.
+ </P
+></LI
+><LI
+><P
>
- Some installers may remove earlier versions completely, including
- configuration files. Save any important configuration files!
+ Note that some installers remove earlier versions completely,
+ including configuration files, therefore you should really save
+ any important configuration files!
</P
></LI
><LI
><P
>
- On the other hand, other installers may not overwrite any existing configuration
- files, thinking you will want to do that. You may want to manually check
- your saved files against the newer versions to see if the improvements have
- merit, or whether there are new options that you may want to consider.
- There are a number of new features, but most won't be available unless
- these features are incorporated into your configuration somehow.
+ On the other hand, other installers don't overwrite existing configuration
+ files, thinking you will want to do that yourself.
</P
></LI
><LI
<TT
CLASS="FILENAME"
>standard.action</TT
-> now only includes the enabled actions.
- Not all actions as before.
+> has been merged into
+ the <TT
+CLASS="FILENAME"
+>default.action</TT
+> file.
</P
></LI
><LI
><P
-> Logging is off by default now. If you need logging, it can be turned on
- in the <A
-HREF="config.html#LOGFILE"
->config file</A
->.
- </P
+> In the default configuration only fatal errors are logged now.
+ You can change that in the <A
+HREF="config.html#DEBUG"
+>debug section</A
+>
+ of the configuration file. You may also want to enable more verbose
+ logging until you verified that the new <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+> version is working
+ as expected.
+ </P
></LI
><LI
><P
projects / privoxy.git / blobdiff