-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
-<HTML
-><HEAD
-><TITLE
->What's New in this Release</TITLE
-><META
-NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
-REL="HOME"
-TITLE="Privoxy 3.0.11 User Manual"
-HREF="index.html"><LINK
-REL="PREVIOUS"
-TITLE="Installation"
-HREF="installation.html"><LINK
-REL="NEXT"
-TITLE="Quickstart to Using Privoxy"
-HREF="quickstart.html"><LINK
-REL="STYLESHEET"
-TYPE="text/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
-CLASS="SECT1"
-BGCOLOR="#EEEEEE"
-TEXT="#000000"
-LINK="#0000FF"
-VLINK="#840084"
-ALINK="#0000FF"
-><DIV
-CLASS="NAVHEADER"
-><TABLE
-SUMMARY="Header navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TH
-COLSPAN="3"
-ALIGN="center"
->Privoxy 3.0.11 User Manual</TH
-></TR
-><TR
-><TD
-WIDTH="10%"
-ALIGN="left"
-VALIGN="bottom"
-><A
-HREF="installation.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="80%"
-ALIGN="center"
-VALIGN="bottom"
-></TD
-><TD
-WIDTH="10%"
-ALIGN="right"
-VALIGN="bottom"
-><A
-HREF="quickstart.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-></TABLE
-><HR
-ALIGN="LEFT"
-WIDTH="100%"></DIV
-><DIV
-CLASS="SECT1"
-><H1
-CLASS="SECT1"
-><A
-NAME="WHATSNEW"
->3. What's New in this Release</A
-></H1
-><P
-> There are many improvements and new features since <SPAN
-CLASS="APPLICATION"
->Privoxy 3.0.8</SPAN
->, the last stable release:</P
-><P
-> <P
-></P
-><UL
-><LI
-><P
-> Added SOCKS5 support (with address resolution done by
- the SOCKS5 server). Patch provided by Eric M. Hopper.
- </P
-></LI
-><LI
-><P
-> The "blocked" CGI pages include a block reason that was
- provided as argument to the last-applying block action.
- </P
-></LI
-><LI
-><P
-> If enable-edit-actions is disabled (the default since 3.0.7 beta)
- the show-status page hides the edit buttons and explains why.
- Previously the user would get the "this feature has been disabled"
- message after using the edit button.
- </P
-></LI
-><LI
-><P
-> Forbidden CONNECT requests are treated like blocks by default.
- The now-pointless treat-forbidden-connects-like-blocks action
- has been removed.
- </P
-></LI
-><LI
-><P
-> Not enabling limit-connect now allows CONNECT requests to all ports.
- In previous versions it would only allow CONNECT requests to port 443.
- Use +limit-connect{443} if you think you need the old default behaviour.
- </P
-></LI
-><LI
-><P
-> The CGI editor gets turned off after three edit requests with invalid
- file modification timestamps. This makes life harder for attackers
- who can leverage browser bugs to send fake Referers and intend to
- brute-force edit URLs.
- </P
-></LI
-><LI
-><P
-> Action settings for multiple patterns in the same section are
- shared in memory. As a result these sections take up less space
- (and are loaded slightly faster). Problem reported by Franz Schwartau.
- </P
-></LI
-><LI
-><P
-> Linear white space in HTTP headers will be normalized to single
- spaces before parsing the header's content, headers split across
- multiple lines get merged first.
- </P
-></LI
-><LI
-><P
-> Host information is gathered outside the main thread so it's less
- likely to delay other incoming connections if the host is misconfigured.
- </P
-></LI
-><LI
-><P
-> New config option "hostname" to use a hostname other than
- the one returned by the operating system. Useful to speed-up responses
- for CGI requests on misconfigured systems. Requested by Max Khon.
- </P
-></LI
-><LI
-><P
-> The CGI editor supports the "disable all filters of this type"
- directives "-client-header-filter", "-server-header-filter",
- "-client-header-tagger" and "-server-header-tagger".
- </P
-></LI
-><LI
-><P
-> Fixed false-positives with the link-by-url filter and URLs that
- contain the pattern "/jump/".
- </P
-></LI
-><LI
-><P
-> The less-download-windows filter no longer messes
- "Content-Type: application/x-shockwave-flash" headers up.
- </P
-></LI
-><LI
-><P
-> In the show-url-info page's "Final results" section active and
- inactive actions are listed separately. Patch provided by Lee.
- </P
-></LI
-><LI
-><P
-> The GNUmakefile supports the DESTDIR variable. Patch for
- the install target submitted by Radoslaw Zielinski.
- </P
-></LI
-><LI
-><P
-> Embedding the content of configuration files in the show-status
- page is significantly faster now. For a largish action file (1 MB)
- a speedup of about 2450 times has been measured. This is mostly
- interesting if you are using large action files or regularly use
- Privoxy-Regression-Test while running Privoxy through Valgrind,
- for stock configuration files it doesn't really matter.
- </P
-></LI
-><LI
-><P
-> If zlib support is unavailable and there are content
- filters active but the prevent-compression action is disabled,
- the show-url-info page includes a warning that compression
- might prevent filtering.
- </P
-></LI
-><LI
-><P
-> The show-url-info page provides an OpenSearch Description that
- allows to access the page through browser search plugins.
- </P
-></LI
-><LI
-><P
-> The obsolete kill-popups action has been removed as the
- PCRS-based popup filters can do the same and are slightly
- less unreliable.
- </P
-></LI
-><LI
-><P
-> The inspect-jpegs action has been removed.
- </P
-></LI
-><LI
-><P
-> The send-wafer and send-vanilla-wafer actions have been removed.
- They weren't particular useful and their behaviour could be emulated
- with add-header anyway.
- </P
-></LI
-><LI
-><P
-> Privoxy-Regression-Test has been significantly improved.
- </P
-></LI
-><LI
-><P
-> Most sections in the default.action file contain tests for
- Privoxy-Regression-Test to verify that they are working as intended.
- </P
-></LI
-><LI
-><P
-> Parts of Privoxy have been refactored to increase maintainability.
- </P
-></LI
-><LI
-><P
-> Building with zlib (if available) is done by default.
- </P
-></LI
-><LI
-><P
-> Ordinary configuration file changes no longer cause program
- termination on OS/2 if the name of the logfile hasn't been
- changed as well. This regression probably crept in with the
- logging improvements in 3.0.7. Reported by Maynard.
- </P
-></LI
-><LI
-><P
-> The img-reorder filter is less likely to mess up JavaScript code in
- img tags. Problem and solution reported by Glenn Washburn in #2014552.
- </P
-></LI
-><LI
-><P
-> The source tar ball now includes Privoxy-Log-Parser,
- a syntax-highlighter for Privoxy logs. Documentation is available
- through perldoc(1), for fancy screenshots see:
- <A
-HREF="http://www.fabiankeil.de/sourcecode/privoxy-log-parser/"
-TARGET="_top"
->http://www.fabiankeil.de/sourcecode/privoxy-log-parser/</A
->.
- </P
-></LI
-></UL
-></P
-><P
-> For a more detailed list of changes please have a look at the ChangeLog.</P
-><DIV
-CLASS="SECT2"
-><H2
-CLASS="SECT2"
-><A
-NAME="UPGRADERSNOTE"
->3.1. Note to Upgraders</A
-></H2
-><P
-> A quick list of things to be aware of before upgrading from earlier
- versions of <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
->:</P
-><P
-> <P
-></P
-><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
->
- 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 don't overwrite existing configuration
- files, thinking you will want to do that yourself.
- </P
-></LI
-><LI
-><P
->
- <TT
-CLASS="FILENAME"
->standard.action</TT
-> now only includes the enabled actions.
- Not all actions as before.
- </P
-></LI
-><LI
-><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
-> Three other config file settings are now off by default:
- <A
-HREF="config.html#ENABLE-REMOTE-TOGGLE"
->enable-remote-toggle</A
->,
- <A
-HREF="config.html#ENABLE-REMOTE-HTTP-TOGGLE"
->enable-remote-http-toggle</A
->,
- and <A
-HREF="config.html#ENABLE-EDIT-ACTIONS"
->enable-edit-actions</A
->.
- If you use or want these, you will need to explicitly enable them, and
- be aware of the security issues involved.
- </P
-></LI
-><LI
-><P
-> The <SPAN
-CLASS="QUOTE"
->"filter-client-headers"</SPAN
-> and
- <SPAN
-CLASS="QUOTE"
->"filter-server-headers"</SPAN
-> actions that were introduced with
- <SPAN
-CLASS="APPLICATION"
->Privoxy 3.0.5</SPAN
-> to apply content filters to
- the headers have been removed and replaced with new actions.
- See the <A
-HREF="whatsnew.html"
->What's New section</A
-> above.
- </P
-></LI
-></UL
-></P
-></DIV
-></DIV
-><DIV
-CLASS="NAVFOOTER"
-><HR
-ALIGN="LEFT"
-WIDTH="100%"><TABLE
-SUMMARY="Footer navigation table"
-WIDTH="100%"
-BORDER="0"
-CELLPADDING="0"
-CELLSPACING="0"
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
-><A
-HREF="installation.html"
-ACCESSKEY="P"
->Prev</A
-></TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-><A
-HREF="index.html"
-ACCESSKEY="H"
->Home</A
-></TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
-><A
-HREF="quickstart.html"
-ACCESSKEY="N"
->Next</A
-></TD
-></TR
-><TR
-><TD
-WIDTH="33%"
-ALIGN="left"
-VALIGN="top"
->Installation</TD
-><TD
-WIDTH="34%"
-ALIGN="center"
-VALIGN="top"
-> </TD
-><TD
-WIDTH="33%"
-ALIGN="right"
-VALIGN="top"
->Quickstart to Using Privoxy</TD
-></TR
-></TABLE
-></DIV
-></BODY
-></HTML
->
\ No newline at end of file
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
+"http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+ <title>What's New in this Release</title>
+ <meta name="GENERATOR" content="Modular DocBook HTML Stylesheet Version 1.79">
+ <link rel="HOME" title="Privoxy 3.0.30 User Manual" href="index.html">
+ <link rel="PREVIOUS" title="Installation" href="installation.html">
+ <link rel="NEXT" title="Quickstart to Using Privoxy" href="quickstart.html">
+ <link rel="STYLESHEET" type="text/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 class="SECT1" bgcolor="#EEEEEE" text="#000000" link="#0000FF" vlink="#840084" alink="#0000FF">
+ <div class="NAVHEADER">
+ <table summary="Header navigation table" width="100%" border="0" cellpadding="0" cellspacing="0">
+ <tr>
+ <th colspan="3" align="center">Privoxy 3.0.30 User Manual</th>
+ </tr>
+ <tr>
+ <td width="10%" align="left" valign="bottom"><a href="installation.html" accesskey="P">Prev</a></td>
+ <td width="80%" align="center" valign="bottom"></td>
+ <td width="10%" align="right" valign="bottom"><a href="quickstart.html" accesskey="N">Next</a></td>
+ </tr>
+ </table>
+ <hr align="left" width="100%">
+ </div>
+ <div class="SECT1">
+ <h1 class="SECT1"><a name="WHATSNEW" id="WHATSNEW">3. What's New in this Release</a></h1>
+ <p><span class="APPLICATION">Privoxy 3.0.29</span> fixes a couple of memory leaks and introduces https inspection
+ which allows to filter encrypted requests and responses.</p>
+ <p>Changes in <span class="APPLICATION">Privoxy 3.0.29</span> stable:</p>
+ <ul>
+ <li>
+ <p>Security/Reliability:</p>
+ <ul>
+ <li>
+ <p>Fixed memory leaks when a response is buffered and the buffer limit is reached or Privoxy is running out
+ of memory. Commits bbd53f1010b and 4490d451f9b. OVE-20201118-0001. Sponsored by: Robert Klemme</p>
+ </li>
+ <li>
+ <p>Fixed a memory leak in the show-status CGI handler when no action files are configured. Commit
+ c62254a686. OVE-20201118-0002. Sponsored by: Robert Klemme</p>
+ </li>
+ <li>
+ <p>Fixed a memory leak in the show-status CGI handler when no filter files are configured. Commit
+ 1b1370f7a8a. OVE-20201118-0003. Sponsored by: Robert Klemme</p>
+ </li>
+ <li>
+ <p>Fixes a memory leak when client tags are active. Commit 245e1cf32. OVE-20201118-0004. Sponsored by:
+ Robert Klemme</p>
+ </li>
+ <li>
+ <p>Fixed a memory leak if multiple filters are executed and the last one is skipped due to a pcre error.
+ Commit 5cfb7bc8fe. OVE-20201118-0005.</p>
+ </li>
+ <li>
+ <p>Prevent an unlikely dereference of a NULL-pointer that could result in a crash if
+ accept-intercepted-requests was enabled, Privoxy failed to get the request destination from the Host header
+ and a memory allocation failed. Commit 7530132349. CID 267165. OVE-20201118-0006.</p>
+ </li>
+ <li>
+ <p>Fixed memory leaks in the client-tags CGI handler when client tags are configured and memory allocations
+ fail. Commit cf5640eb2a. CID 267168. OVE-20201118-0007.</p>
+ </li>
+ <li>
+ <p>Fixed memory leaks in the show-status CGI handler when memory allocations fail. Commit 064eac5fd0 and
+ commit fdee85c0bf3. CID 305233. OVE-20201118-0008.</p>
+ </li>
+ </ul>
+ </li>
+ <li>
+ <p>General improvements:</p>
+ <ul>
+ <li>
+ <p>Added experimental https inspection support which allows to filter https traffic. To enable it, install
+ MbedTLS and configure with --with-mbedtls, or install OpenSSL or LibreSSL and configure with
+ --with-openssl. Afterwards configure the directives in section 7 of the config file and enable the
+ +https-inspection action. Initial MbedTLS-based code contributed by Vaclav Svec, initial OpenSSL support
+ contributed by Maxim Antonov. With help from Nedzad Hrnjica and Ho+ Ho+ Ho+. Integration and improvements
+ sponsored by Robert Klemme.</p>
+ </li>
+ <li>
+ <p>pcrs: Request JIT compilation if it's supported and the filter isn't dynamic. This can speed up
+ filtering.</p>
+ </li>
+ <li>
+ <p>Added support for Brotli decompression. Sponsored by: Robert Klemme</p>
+ </li>
+ <li>
+ <p>Added FEATURE_EXTENDED_STATISTICS to gather statistics for block reasons and filter executions. To
+ enable it, configure with --enable-extended-statistics and visit http://config.privoxy.org/show-status.
+ Sponsored by: Robert Klemme</p>
+ </li>
+ <li>
+ <p>Use the IP_FREEBIND socket option, if defined. This allows Privoxy to bind to not-yet assigned IP
+ addresses which is useful in failover environments. Patch by Sam Varshavchik.</p>
+ </li>
+ <li>
+ <p>Allow to use extended host patterns and vanilla host patterns at the same time by prefixing extended
+ host patterns with "PCRE-HOST-PATTERN:". To enable this, configure with --enable-pcre-host-patterns.
+ Sponsored by: Robert Klemme</p>
+ </li>
+ <li>
+ <p>Added "Cross-origin resource sharing" (CORS) support. This allows to access Privoxy's CGI interface via
+ JavaScript from another domain (white-listed with the new cors-allowed-origin directive). Based on a patch
+ by Nedzad Hrnjica. Sponsored by: Robert Klemme.</p>
+ </li>
+ <li>
+ <p>Add SOCKS5 username/password support. Based on a patch by Sam, improved by Ivan Romanov. Closes
+ Patch#141 and solves TODO#105.</p>
+ </li>
+ <li>
+ <p>Bump the maximum number of action and filter files to 100 each. Sponsored by: Robert Klemme</p>
+ </li>
+ <li>
+ <p>Fixed handling of filters with "split-large-forms 1" when using the CGI editor. Reported by withoutname
+ in #921.</p>
+ </li>
+ <li>
+ <p>Better detect a mismatch of connection details when figuring out whether or not a connection can be
+ reused.</p>
+ </li>
+ <li>
+ <p>Don't send a "Connection failure" message instead of the "DNS failure" message. Sponsored by: Robert
+ Klemme</p>
+ </li>
+ <li>
+ <p>Let LOG_LEVEL_REQUEST log all requests. Previously unencrypted requests were only logged with
+ LOG_LEVEL_REQUEST when they weren't crunched (in which case they were logged with LOG_LEVEL_CRUNCH). This
+ was documented behaviour, but logging all requests seems more useful.</p>
+ </li>
+ <li>
+ <p>Fixed locking around localtime() and gmtime().</p>
+ </li>
+ <li>
+ <p>Removed OS/2 support. We haven't provided OS/2 packages in years, it complicated the code and it
+ depended on a fallback snprintf() implementation which is GPLv2 only.</p>
+ </li>
+ <li>
+ <p>Remove the fallback snprintf() implementation Now that OS/2 support is gone we no longer need it.</p>
+ </li>
+ <li>
+ <p>Fixed a bunch of format specifiers log messages.</p>
+ </li>
+ <li>
+ <p>Added a missing apostrophe in the 'More Privoxy' menu.</p>
+ </li>
+ <li>
+ <p>Explicitly prevent use of FEATURE_CONNECTION_SHARING without FEATURE_CONNECTION_KEEP_ALIVE. It makes no
+ sense and does not compile anyway. Sponsored by: Robert Klemme</p>
+ </li>
+ <li>
+ <p>Fix build without FEATURE_CONNECTION_KEEP_ALIVE. Sponsored by: Robert Klemme</p>
+ </li>
+ <li>
+ <p>Downgrade the 'Graceful termination requested' message to LOG_LEVEL_INFO as it isn't an error. Sponsored
+ by: Robert Klemme</p>
+ </li>
+ <li>
+ <p>decompress_iob(): Downgrade the no-content message to LOG_LEVEL_RE_FILTER While at it, fix a typo in a
+ comment. Sponsored by: Robert Klemme</p>
+ </li>
+ <li>
+ <p>Fixed a couple of cppcheck warnings.</p>
+ </li>
+ <li>
+ <p>Rename LOG_LEVEL_GPC to LOG_LEVEL_REQUEST. Only the shadow knows what "GPC" is supposed to stand
+ for.</p>
+ </li>
+ <li>
+ <p>Remove SourceForge references in copyright headers.</p>
+ </li>
+ <li>
+ <p>Upgrade a bunch of links to the homepage to https://.</p>
+ </li>
+ <li>
+ <p>Add 'no-brotli-accepted' filter which prevents the use of Brotli compression.</p>
+ </li>
+ <li>
+ <p>Changed license for pcrs to GPLv2+ after getting the permission from Andreas. This allows to
+ redistribute Privoxy under the GPLv3 which is required when linking to future mbedTLS versions which are
+ expected to be licensed under the Apache 2.0 license only.</p>
+ </li>
+ <li>
+ <p>Updated a bunch of tests that have to expect status code 403 now after r1.168/070e904afa5.</p>
+ </li>
+ <li>
+ <p>Lowercase the host name in the request line.</p>
+ </li>
+ <li>
+ <p>Only set SOURCE_DATE_EPOCH if it's not already set so distributions can overwrite it through the
+ environment.</p>
+ </li>
+ </ul>
+ </li>
+ <li>
+ <p>Documentation changes:</p>
+ <ul>
+ <li>
+ <p>Explain that Privoxy has to be distributed under the GPLv3 (or later) when linked with an MbedTLS
+ version that is licensed under the Apache 2.0 license.</p>
+ </li>
+ <li>
+ <p>Import the GNU GPLv3 and include it the user manual.</p>
+ </li>
+ <li>
+ <p>Clarify FEATURE_FORCE_LOAD's description. It allows to bypass blocking not filtering and only does it if
+ blocks aren't enforced. Reported by: Robert Klemme</p>
+ </li>
+ <li>
+ <p>FAQ: Remove Zwiebelfreunde e.V. from the list of fiduciary sponsors As of 2021 they no longer handle
+ donations for foreign organisations due to lack of resources.</p>
+ </li>
+ <li>
+ <p>FAQ: Remove an obsolete comment with a link to the long-gone PDF manual.</p>
+ </li>
+ <li>
+ <p>FAQ: Add a link to the TODO list.</p>
+ </li>
+ <li>
+ <p>FAQ: Change the sponsor amounts to USD slightly rounding the converted amounts up to get simple numbers.
+ Receiving USD is apparently easier for SPI and SPI is preferred by sponsors as they can send invoices.</p>
+ </li>
+ <li>
+ <p>Advertise the client-tags CGI page in the user manual.</p>
+ </li>
+ <li>
+ <p>Stop advertising the show-version CGI page which no longer exists.</p>
+ </li>
+ <li>
+ <p>Add yet another reason why +prevent-compression may cause problems.</p>
+ </li>
+ <li>
+ <p>Don't claim that contributors need ssh. It's only needed for committers.</p>
+ </li>
+ <li>
+ <p>Replace obsolete CVS instructions with Git instructions.</p>
+ </li>
+ <li>
+ <p>Remove an obsolete comment</p>
+ </li>
+ </ul>
+ </li>
+ <li>
+ <p>Config file changes:</p>
+ <ul>
+ <li>
+ <p>Change the suggested default-server-timeout to 5 to match the suggested keep-alive-timeout. Otherwise
+ using the defaults would result in Privoxy reducing the default-server-timeout and logging an error
+ message. Sponsored by: Robert Klemme</p>
+ </li>
+ <li>
+ <p>Update the 'debug 1' description.</p>
+ </li>
+ <li>
+ <p>Add a missing 'client-specific-tag' directive.</p>
+ </li>
+ <li>
+ <p>Comment out trusted-cgi-referer pointing to example.org.</p>
+ </li>
+ </ul>
+ </li>
+ <li>
+ <p>Action file improvements:</p>
+ <ul>
+ <li>
+ <p>Block requests to /(.*/)?piwik\.php</p>
+ </li>
+ <li>
+ <p>Block requests to .connectaserver.de/</p>
+ </li>
+ <li>
+ <p>Block requests to pixel.inforsea.com/</p>
+ </li>
+ <li>
+ <p>Block requests to t.vi-serve.com/</p>
+ </li>
+ <li>
+ <p>Block requests to .ioam.de/</p>
+ </li>
+ <li>
+ <p>Block requests to t.9gag.com/img.gif</p>
+ </li>
+ <li>
+ <p>Block requests to .pixel.parsely.com/ as image</p>
+ </li>
+ <li>
+ <p>Block requests to pixel.wp.com/</p>
+ </li>
+ <li>
+ <p>Disable fast-redirects for .librarything.com/</p>
+ </li>
+ <li>
+ <p>Disable fast-redirects for issue.freebsdfoundation.org/</p>
+ </li>
+ <li>
+ <p>Disable fast-redirects for .twitter.com/.*origin=http</p>
+ </li>
+ <li>
+ <p>Unblock belco24.de/</p>
+ </li>
+ <li>
+ <p>Add fast-redirects exception for .wikipedia.org/</p>
+ </li>
+ <li>
+ <p>Add fast-redirects exception for oss-fuzz.com/</p>
+ </li>
+ <li>
+ <p>Disable fast-redirects for .consensu.org/delivery/pixel\.php and block the requests as image instead</p>
+ </li>
+ <li>
+ <p>Unblock .adbinstaller.com/ Reported by lvm in #942.</p>
+ </li>
+ <li>
+ <p>Unblock .adbshell.com Reported by lvm in #942.</p>
+ </li>
+ <li>
+ <p>Unblock .tagesschau.de/</p>
+ </li>
+ <li>
+ <p>Disable fast-redirects for collector.githubapp.com/ and block requests to it as image instead</p>
+ </li>
+ <li>
+ <p>Unblock 'ada*.'</p>
+ </li>
+ <li>
+ <p>Add fast-redirects{} exception for sourcepoint.vice.com/</p>
+ </li>
+ <li>
+ <p>Unblock adaway.org/ Reported by DRS David Soft in AF#945.</p>
+ </li>
+ <li>
+ <p>Change two block reasons that previously were the same. Sponsored by: Robert Klemme</p>
+ </li>
+ <li>
+ <p>Added a +delay-response{} test.</p>
+ </li>
+ <li>
+ <p>Updated the location of the development version of default.action.master.</p>
+ </li>
+ </ul>
+ </li>
+ <li>
+ <p>Privoxy-Log-Parser:</p>
+ <ul>
+ <li>
+ <p>Added a --keep-date option to keep the date in highlighted messages.</p>
+ </li>
+ <li>
+ <p>Highlight new log messages.</p>
+ </li>
+ <li>
+ <p>Make gather_loglevel_clf_stats() more tolerant. While at it, count all CLF messages as requests, even if
+ the request is invalid.</p>
+ </li>
+ <li>
+ <p>Only show HTTP version distribution if at least one version has been detected.</p>
+ </li>
+ <li>
+ <p>Only show crunch statistics if crunches were detected.</p>
+ </li>
+ <li>
+ <p>Warn if the request counts differ.</p>
+ </li>
+ <li>
+ <p>Generate statistics if the log only contains LOG_LEVEL_CLF messages so it can be used with vanilla
+ webserver logs. Previously Privoxy-specific "Request:" messages were required.</p>
+ </li>
+ <li>
+ <p>Align the client-HTTP-version distribution like other distributions</p>
+ </li>
+ <li>
+ <p>Bump version to 0.9.1</p>
+ </li>
+ <li>
+ <p>Include status code distribution in the stats.</p>
+ </li>
+ <li>
+ <p>Let the statistics include the size of the content Privoxy transferred excluding HTTP headers.</p>
+ </li>
+ <li>
+ <p>Get with the program and expect all requests to be logged with LOG_LEVEL_REQUEST. It's no longer
+ necessary to count both LOG_LEVEL_REQUEST and LOG_LEVEL_CRUNCH messages to get the total number of
+ requests.</p>
+ </li>
+ <li>
+ <p>Leverage the LOG_LEVEL_CLF message to gather statistics that where previously taken from
+ LOG_LEVEL_HEADER lines. This results in less confusing results if https inspection is enabled in which case
+ there are two LOG_LEVEL_HEADER lines with request lines. Sponsored by: Robert Klemme</p>
+ </li>
+ <li>
+ <p>Properly highlight the filter results message. Previously a brace got lost.</p>
+ </li>
+ <li>
+ <p>Prefer the number of CLF lines to get the total number of requests as it works with older Privoxy
+ versions as well.</p>
+ </li>
+ </ul>
+ </li>
+ <li>
+ <p>Privoxy-Regression-Test:</p>
+ <ul>
+ <li>
+ <p>Turn curl's globbing mode off so we can allow more characters in URLs.</p>
+ </li>
+ <li>
+ <p>Allow '[' and ']' in URLs.</p>
+ </li>
+ <li>
+ <p>Include the action file when complaining about missing Sticky Actions.</p>
+ </li>
+ <li>
+ <p>Fix a sentence in the documentation.</p>
+ </li>
+ <li>
+ <p>Bump version to 0.7.1</p>
+ </li>
+ </ul>
+ </li>
+ <li>
+ <p>url-pattern-translator:</p>
+ <ul>
+ <li>
+ <p>Detect a couple of pattern prefixes case-insensitively. Sponsored by: Robert Klemme</p>
+ </li>
+ <li>
+ <p>Skip CLIENT-TAG patterns. Sponsored by: Robert Klemme</p>
+ </li>
+ <li>
+ <p>Skip patterns that have already been converted. It should now be safe to "convert" a file multiple
+ times. Sponsored by: Robert Klemme</p>
+ </li>
+ <li>
+ <p>Add the new 'PCRE-HOST-PATTERN:' prefix. Sponsored by: Robert Klemme</p>
+ </li>
+ </ul>
+ </li>
+ </ul>
+ <div class="SECT2">
+ <h2 class="SECT2"><a name="UPGRADERSNOTE" id="UPGRADERSNOTE">3.1. Note to Upgraders</a></h2>
+ <p>A quick list of things to be aware of before upgrading from earlier versions of <span class=
+ "APPLICATION">Privoxy</span>:</p>
+ <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>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 don't overwrite existing configuration files, thinking you will want
+ to do that yourself.</p>
+ </li>
+ <li>
+ <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>Three other config file settings are now off by default: <a href=
+ "config.html#ENABLE-REMOTE-TOGGLE">enable-remote-toggle</a>, <a href=
+ "config.html#ENABLE-REMOTE-HTTP-TOGGLE">enable-remote-http-toggle</a>, and <a href=
+ "config.html#ENABLE-EDIT-ACTIONS">enable-edit-actions</a>. If you use or want these, you will need to
+ explicitly enable them, and be aware of the security issues involved.</p>
+ </li>
+ </ul>
+ </div>
+ </div>
+ <div class="NAVFOOTER">
+ <hr align="left" width="100%">
+ <table summary="Footer navigation table" width="100%" border="0" cellpadding="0" cellspacing="0">
+ <tr>
+ <td width="33%" align="left" valign="top"><a href="installation.html" accesskey="P">Prev</a></td>
+ <td width="34%" align="center" valign="top"><a href="index.html" accesskey="H">Home</a></td>
+ <td width="33%" align="right" valign="top"><a href="quickstart.html" accesskey="N">Next</a></td>
+ </tr>
+ <tr>
+ <td width="33%" align="left" valign="top">Installation</td>
+ <td width="34%" align="center" valign="top"> </td>
+ <td width="33%" align="right" valign="top">Quickstart to Using Privoxy</td>
+ </tr>
+ </table>
+ </div>
+</body>
+</html>
projects / privoxy.git / blobdiff