<!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.22 User Manual" href="index.html">
+ <meta name="GENERATOR" content="Modular DocBook HTML Stylesheet Version 1.79">
+ <link rel="HOME" title="Privoxy 3.0.32 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="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=us-ascii">
+ <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">
+<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">
+ <table summary="Header navigation table" width="100%" border="0" cellpadding="0" cellspacing="0">
<tr>
- <th colspan="3" align="center">Privoxy 3.0.22 User Manual</th>
+ <th colspan="3" align="center">Privoxy 3.0.32 User Manual</th>
</tr>
-
<tr>
- <td width="10%" align="left" valign="bottom"><a href=
- "installation.html" accesskey="P">Prev</a></td>
-
+ <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>
+ <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.22</span> stable is mainly a
- bug-fix release, it also has a couple of new features, though. Note that
- the first two entries in the ChangeLog below refer to security
- issues:</p>
-
+ <h1 class="SECT1"><a name="WHATSNEW" id="WHATSNEW">3. What's New in this Release</a></h1>
+ <p><span class="APPLICATION">Privoxy 3.0.31</span> fixes two security issues that were discovered while preparing
+ the 3.0.30 release. The issues also affect earlier Privoxy releases.</p>
+ <p>Changes in <span class="APPLICATION">Privoxy 3.0.31</span> stable:</p>
+ <ul>
+ <li>
+ <p>Security/Reliability:</p>
+ <ul>
+ <li>
+ <p>Prevent an assertion from getting triggered by a crafted CGI request. Commit 5bba5b89193fa.
+ OVE-20210130-0001. Reported by: Joshua Rogers (Opera)</p>
+ </li>
+ <li>
+ <p>Fixed a memory leak when decompression fails "unexpectedly". Commit f431d61740cc0.
+ OVE-20210128-0001.</p>
+ </li>
+ </ul>
+ </li>
+ <li>
+ <p>Bug fixes:</p>
+ <ul>
+ <li>
+ <p>Fixed detection of insufficient data for decompression. Previously Privoxy could try to decompress a
+ partly uninitialized buffer.</p>
+ </li>
+ </ul>
+ </li>
+ </ul>
+ <p>Changes in <span class="APPLICATION">Privoxy 3.0.30</span> stable:</p>
<ul>
<li>
<p>Bug fixes:</p>
-
<ul>
<li>
- <p>Fixed a memory leak when rejecting client connections due to
- the socket limit being reached (CID 66382). This affected Privoxy
- 3.0.21 when compiled with IPv6 support (on most platforms this is
- the default).</p>
+ <p>Check the actual URL for redirects when https inspecting requests. Previously Privoxy would only check
+ the path which resulted in rewrite results being rejected as invalid URLs. Reported by withoutname in
+ #1736.</p>
</li>
-
<li>
- <p>Fixed an immediate-use-after-free bug (CID 66394) and two
- additional unconfirmed use-after-free complaints made by Coverity
- scan (CID 66391, CID 66376).</p>
+ <p>Let the hide-referrer code tolerate Referer headers with https:// URLs. Previously they would always be
+ treated like a changed host.</p>
</li>
-
<li>
- <p>Actually show the FORCE_PREFIX value on the show-status
- page.</p>
+ <p>Use the https headers if the show-request handler is reached through https://. Previously Privoxy would
+ use the http headers which may be empty on a reused connection.</p>
</li>
-
<li>
- <p>Properly deal with Keep-Alive headers with timeout= parameters
- If the timeout still can't be parsed, use the configured timeout
- instead of preventing the client from keeping the connection
- alive. Fixes #3615312/#870 reported by Bernard Guillot.</p>
+ <p>Make CGI_PREFIX protocol-relative when building with FEATURE_HTTPS_INSPECTION. This unbreaks (at least)
+ https://config.privoxy.org/client-tags whose buttons would previously use a http:// URL resulting in
+ browser warnings.</p>
</li>
-
<li>
- <p>Not using any filter files no longer results in warning
- messages unless an action file is referencing header taggers or
- filters. Reported by Stefan Kurtz in #3614835.</p>
+ <p>Support using https-inspection and client-header-order at the same time. Previously Privoxy would crash.
+ Reported by: Kai Raven</p>
</li>
-
<li>
- <p>Fixed a bug that prevented Privoxy from reusing some reusable
- connections. Two bit masks with different purpose unintentionally
- shared the same bit.</p>
+ <p>Properly reject rewrites from http to https as they currently aren't supported. Previously Privoxy would
+ wait for the client to establish an encrypted connection which obviously would not happen.</p>
</li>
-
<li>
- <p>A couple of additional bugs were discovered by Coverity Scan.
- The fixes that are not expected to affect users are not
- explicitly mentioned here, for details please have a look at the
- CVS logs.</p>
+ <p>When https inspection is enabled and Privoxy has been compiled with FEATURE_GRACEFUL_TERMINATION (not
+ recommended for production builds), the TLS backend resources are free'd later on and only if no active
+ connections are left. Prevents crashes when exiting "gracefully" at the wrong time.</p>
+ </li>
+ <li>
+ <p>Let the uninstall target remove the config file even if DESTDIR is set and properly announce the
+ deletion of the configuration files.</p>
</li>
</ul>
</li>
-
<li>
<p>General improvements:</p>
-
<ul>
<li>
- <p>Introduced negative tag patterns NO-REQUEST-TAG and
- NO-RESPONSE-TAG. They apply if no matching tag is found after
- parsing client or server headers.</p>
+ <p>Allow to rewrite the request destination for https-inspected requests behind the client's back. The
+ documentation already sort of claimed that it was supported by not especially mentioning that it didn't
+ work for https-inspected requests. Fixes SF bug #923 reported by withoutname.</p>
+ </li>
+ <li>
+ <p>Add support for filtering client request bodies by using CLIENT-BODY-FILTER filters which can be enabled
+ with the client-body-filter action. Patch submitted by Maxim Antonov. Sponsored by: Robert Klemme</p>
</li>
-
<li>
- <p>Add support for external filters which allow to process the
- response body with a script or program written in any language
- the platform supports. External filters are enabled with
- +external-filter{} after they have been defined in one of the
- filter files with a header line starting with "EXTERNAL-FILTER:".
- External filter support is experimental, not compiled by default
- and known not to work on all platforms.</p>
+ <p>Add the new action suppress-tag{} which can be used to prevent a tagger from adding a tag. Patch
+ submitted by Maxim Antonov. Sponsored by: Robert Klemme</p>
</li>
-
<li>
- <p>Add support for the 'PATCH' method as defined in RFC5789.</p>
+ <p>Gracefully handle existing website keys without matching certificates. This can happen if Privoxy was
+ previously running with an invalid TLS configuration that didn't allow it to create a certificate.</p>
</li>
-
<li>
- <p>Reject requests with unsupported Expect header values. Fixes a
- couple of Co-Advisor tests.</p>
+ <p>Recycle debug bit 4 for Tagging-related messages.</p>
</li>
-
<li>
- <p>Normalize the HTTP-version in forwarded requests and
- responses. This is an explicit RFC 2616 MUST and RFC 7230
- mandates that intermediaries send their own HTTP-version in
- forwarded messages.</p>
+ <p>Improve the message shown when the client-tags CGI page is requested with no tags configured.</p>
</li>
-
<li>
- <p>Client 'Keep-Alive' headers are no longer forwarded. From a
- user's point of view it doesn't really matter, but RFC 2616
- (obsolete) mandates that the header is removed and this fixes a
- Co-Advisor complaint.</p>
+ <p>Shorten the 'donate' and 'participate' links used by templates using redirects. Currently the redirects
+ lead to the FAQ entries but in the future we may want to relocate the content and using redirects makes
+ this more convenient.</p>
</li>
-
<li>
- <p>Change declared template file encoding to UTF-8. The templates
- already used a subset of UTF-8 anyway and changing the
- declaration allows to properly display UTF-8 characters used in
- the action files. This change may require existing action files
- with ISO-8859-1 characters that aren't valid UTF-8 to be
- converted to UTF-8. Requested by Sam Chen in #582.</p>
+ <p>Log an error when a PCRE-HOST-PATTERN is used with FEATURE_PCRE_HOST_PATTERNS disabled. Don't treat this
+ a fatal error so the regression tests can be used with and without FEATURE_PCRE_HOST_PATTERNS.</p>
</li>
-
<li>
- <p>Do not pass rejected keep-alive timeouts to the server. It
- might not have caused any problems (we know of), but doing the
- right thing shouldn't hurt either.</p>
+ <p>The code compiles with older C compilers again.</p>
</li>
-
<li>
- <p>Let log_error() use its own buffer size #define to make
- changing the log buffer size slightly less inconvenient.</p>
+ <p>The chdir() return code is checked to fix a compiler warning.</p>
</li>
-
<li>
- <p>Turned single-threaded into a "proper" toggle directive with
- arguments.</p>
+ <p>The packages feed has been removed from the source tarball. It's usually out of date when the source
+ tarball is generated for the release.</p>
</li>
-
<li>
- <p>CGI templates no longer enforce new windows for some
- links.</p>
+ <p>Fixed harmless compiler warnings from GCC9 with -D_FORTIFY_SOURCE=2.</p>
</li>
-
<li>
- <p>Remove an undocumented workaround ('HOST' header removal) for
- an Apple iTunes bug that according to #729900 got fixed in
- 2003.</p>
+ <p>windows: Remove obsolete '$(DEST)/doc/images' target.</p>
+ </li>
+ <li>
+ <p>windows: Install the images referenced in the user manual.</p>
+ </li>
+ <li>
+ <p>Remove obsolete 'gnu_regex.@OBJEXT@' target.</p>
+ </li>
+ <li>
+ <p>When installing from the GNUMAkefile, don't create an 'images' directory which is no longer used. The
+ images were relocated to the user-manual directory years ago.</p>
+ </li>
+ <li>
+ <p>Add new FEATURES to the show-status page and resort list.</p>
+ </li>
+ <li>
+ <p>Remove unused variable in the OpenSSL-specific code.</p>
+ </li>
+ <li>
+ <p>Update bug tracker URL in cgi_error_unknown().</p>
+ </li>
+ <li>
+ <p>Saved a couple of memory allocations when sorting client headers.</p>
+ </li>
+ <li>
+ <p>Improved a couple of error messages.</p>
+ </li>
+ <li>
+ <p>Saved memory allocations when using OpenSSL and checking if a key already exists.</p>
+ </li>
+ <li>
+ <p>The configure script will bail out if OpenSSL and mbedTLS are enabled at the same time.</p>
+ </li>
+ <li>
+ <p>Log a message right before exiting gracefully.</p>
+ </li>
+ <li>
+ <p>A couple of structures have been rearranged to require slightly less memory.</p>
+ </li>
+ <li>
+ <p>When https inspection is enabled and the certificate is invalid the error message is now sent with
+ status code 403 instead of 200.</p>
+ </li>
+ <li>
+ <p>The Slackware rc script template has been renamed to slackware/rc.privoxy.in to silence complaints when
+ building Debian packages.</p>
+ </li>
+ <li>
+ <p>When building with MbedTLS support, mbedtls_md5_ret() is used instead of mbedtls_md5() which is
+ deprecated and causes a warning on Debian GNU/Linux.</p>
</li>
</ul>
</li>
-
<li>
<p>Action file improvements:</p>
-
<ul>
<li>
- <p>The pattern 'promotions.' is no longer being blocked. Reported
- by rakista in #3608540.</p>
+ <p>Block requests to eu-tlp03.kameleoon.com/.</p>
+ </li>
+ <li>
+ <p>Unblock metrics.sr.ht/.</p>
+ </li>
+ <li>
+ <p>Disable fast-redirects for .fsf.org/.</p>
+ </li>
+ <li>
+ <p>Disable fast-redirects for .gravater.com/.</p>
+ </li>
+ <li>
+ <p>Disable fast-redirects for .ksta.de/.</p>
+ </li>
+ <li>
+ <p>Block requests to tag.crsspxl.com/.</p>
+ </li>
+ <li>
+ <p>Block requests to analytics.slashdotmedia.com/.</p>
+ </li>
+ <li>
+ <p>Block requests to ml314.com/.</p>
+ </li>
+ <li>
+ <p>Block requests to .adroll.com/.</p>
+ </li>
+ <li>
+ <p>Block requests to fastlane.rubiconproject.com/.</p>
+ </li>
+ <li>
+ <p>Block requests to api.theadex.com/.</p>
+ </li>
+ <li>
+ <p>Block requests to ih.adscale.de/.</p>
+ </li>
+ <li>
+ <p>Block requests to .s400.meetrics.net/.</p>
+ </li>
+ <li>
+ <p>Block requests for pp.lp4.io/.</p>
+ </li>
+ <li>
+ <p>Block requests for trc-events.taboola.com/.</p>
+ </li>
+ </ul>
+ </li>
+ <li>
+ <p>Filter file improvements:</p>
+ <ul>
+ <li>
+ <p>A allow-autocompletion filter has been added which changes autocomplete="off" to "on" on input fields to
+ allow autocompletion. Requested by Jamie Zawinski in #370. Filter based on a submission by Aaron
+ Linville.</p>
</li>
-
<li>
- <p>Disable fast-redirects for .microsofttranslator.com/.</p>
+ <p>Added an imdb filter.</p>
</li>
-
<li>
- <p>Disable filter{banners-by-size} for
- .dgb-tagungszentren.de/.</p>
+ <p>Added a sourceforge filter that reduces the amount of ads for proprietary software.</p>
</li>
-
<li>
- <p>Add adn.speedtest.net as a site-specific unblocker. Support
- request #3612908.</p>
+ <p>Added a github filter that removes the annoying "Sign-Up" banner and the Cookie disclaimer.</p>
</li>
-
<li>
- <p>Disable filter{banners-by-size} for creativecommons.org/.</p>
+ <p>Removed a duplicated pcrs command from the js-annoyances filter.</p>
</li>
-
<li>
- <p>Block requests to data.gosquared.com/. Reported by cbug in
- #3613653.</p>
+ <p>The crude-parental filter now provides a short reason when blocking, inserts a link to Privoxy's
+ webinterface and adds a new line at the end of the generated page.</p>
</li>
-
+ </ul>
+ </li>
+ <li>
+ <p>Privoxy-Log-Parser:</p>
+ <ul>
<li>
- <p>Unblock .conrad./newsletter/. Reported by David Bo in
- #3614238.</p>
+ <p>Highlight a few more messages.</p>
</li>
-
<li>
- <p>Unblock .bundestag.de/.</p>
+ <p>Add a handler for tagging messages.</p>
</li>
-
<li>
- <p>Unblock .rote-hilfe.de/.</p>
+ <p>Properly deal with 'Certificate error' crunches Previously the error description was highlighted as
+ 'host'.</p>
</li>
-
<li>
- <p>Disable fast-redirects for .facebook.com/plugins/like.php.</p>
+ <p>Log truncated LOG_LEVEL_CLF messages more gracefully and note that the statistics will be imprecise.</p>
</li>
-
<li>
- <p>Unblock Stackexchange popup URLs that aren't used to serve
- ads. Reported by David Wagner in #3615179.</p>
+ <p>Fixed perldoc typo.</p>
</li>
-
<li>
- <p>Disable fast-redirects for creativecommons.org/.</p>
+ <p>Bump version to 0.9.2.</p>
</li>
-
+ </ul>
+ </li>
+ <li>
+ <p>Privoxy-Regression-Test:</p>
+ <ul>
<li>
- <p>Unblock .stopwatchingus.info/.</p>
+ <p>Use http://127.0.0.1:8118/ as default Privoxy address unless http_proxy is set through the
+ environment.</p>
</li>
-
<li>
- <p>Block requests for .adcash.com/script/. Reported by
- Tyrexionibus in #3615289.</p>
+ <p>Add a --privoxy-cgi-prefix option that specifies the prefix to use when building URLs that are supposed
+ to reach Privoxy's CGI interface. If it's not set, http://p.p/ is used, which is supposed to work with the
+ default Privoxy configuration. If Privoxy has been built with FEATURE_HTTPS_INSPECTION enabled, and if
+ https inspection is activated with the +https-inspection action, this option can be used with
+ "https://p.p/" provided the system running Privoxy-Regression-Test has been configured to trust the
+ certificate used by Privoxy. Note that there are currently two tests in the official
+ regression-tests.action file that are expected to fail when using "https://p.p/" as privoxy-cgi-prefix.</p>
</li>
-
<li>
- <p>Disable HTML filters if the response was tagged as JavaScript.
- Filtering JavaScript code with filters intended to deal with HTML
- is usually a waste of time and, more importantly, may break
- stuff.</p>
+ <p>Skip the connection-established response in get_status_code() when looking for the status code with a
+ CGI prefix that starts with https://. We care about the status code sent by the impersonated web
+ server.</p>
</li>
-
<li>
- <p>Use a custom redirect{} for
- .washingtonpost.com/wp-apps/imrs\.php\?src= Previously enabling
- the 'Advanced' settings (or manually enabling +fast-redirects{})
- prevented some images from being loaded properly.</p>
+ <p>Use --proxy-header when using a CGI prefix with https:// and a "Host:" header.</p>
</li>
-
<li>
- <p>Unblock "adina*." Fixes #919 reported by Morton A.
- Goldberg.</p>
+ <p>Allow '|' in tokens and values to allow tag patterns like
+ "TAG:^(application|text)/(x-)?javascript$".</p>
</li>
-
<li>
- <p>Block '/.*DigiAd'.</p>
+ <p>When get_cgi_page_or_else() fails, include the URL of the requested page in the log message.</p>
</li>
-
<li>
- <p>Unblock 'adele*.'. Reported by Adele Lime in #1663.</p>
+ <p>Added a --check-bad-ssl option that can be used to verify that Privoxy detects certificate problems when
+ accessing the test sites from badssl.com.</p>
</li>
-
<li>
- <p>Disable banners-by-size for kggp.de/.</p>
+ <p>Bumped version to 0.7.2</p>
</li>
</ul>
</li>
-
<li>
- <p>Filter file improvements & bug fixes:</p>
-
+ <p>uagen:</p>
<ul>
<li>
- <p>Decrease the chances that js-annoyances creates invalid
- JavaScript. Submitted by John McGowan on ijbswa-users@.</p>
+ <p>Update example output.</p>
+ </li>
+ <li>
+ <p>Recommend the use of the https-inspection action in the documentation.</p>
+ </li>
+ <li>
+ <p>Upgrade a couple of URLs to https://.</p>
</li>
-
<li>
- <p>Let the msn filter hide 'related' ads again.</p>
+ <p>Add ElectroBSD to the list of operating systems.</p>
</li>
-
<li>
- <p>Remove a stray '1' in the 'html-annoyances' filter.</p>
+ <p>Bumped generated Firefox version to 78 (ESR).</p>
</li>
-
<li>
- <p>Prevent img-reorder from messing up img tags with empty src
- attributes. Fixes #880 reported by Duncan.</p>
+ <p>Bumped version to 1.2.2.</p>
</li>
</ul>
</li>
-
<li>
- <p>Documentation improvements:</p>
-
+ <p>User documentation:</p>
<ul>
<li>
- <p>Updated the 'Would you like to donate?' section.</p>
+ <p>Remove reference to 'How to Report Bugs Effectively'. It was only rendered as text without URL in the
+ README anyway and there's no indication that users read it ...</p>
</li>
-
<li>
- <p>Note that invalid forward-override{} parameter syntax isn't
- detected until the parameter is used.</p>
+ <p>Let the dok-readme target fix the location embedded into the README file. This used to be done by CVS
+ but since the git migration it has to be done through other means.</p>
</li>
-
<li>
- <p>Add another +redirect{} example: a shortcut for illumos
- bugs.</p>
+ <p>Remove 'experimental' warning for client-specific-tag-related directives. They seem to work reliably and
+ there is no obvious reason why we would change the syntax in the near future.</p>
</li>
-
<li>
- <p>Make it more obvious that many operating systems support log
- rotation out of the box.</p>
+ <p>Describe how to check if Privoxy has been built with FEATURE_HTTPS_INSPECTION.</p>
</li>
-
<li>
- <p>Fixed dead links. Reported by Mark Nelson in #3614557.</p>
+ <p>Add a link to the trusted-cas-file documentation that explains how the user can create the file
+ herself.</p>
</li>
-
<li>
- <p>Rephrased the 'Why is the configuration so complicated?'
- answer to be slightly less condescending. Anonymously suggested
- in #3615122.</p>
+ <p>Don't explicitly mention the license for the code coming from 'Anonymous Coders' and Junkbusters. It's
+ obviously licensed under the GNU GPL like the rest of Privoxy or we wouldn't be allowed to distribute
+ it.</p>
</li>
-
<li>
- <p>Be more explicit about accept-intercepted-requests's lack of
- MITM support.</p>
+ <p>Update the +hide-user-agent example with uagen output.</p>
</li>
-
<li>
- <p>Make 'demoronizer' FAQ entries more generic.</p>
+ <p>Slightly improve the wording of the ca-key-file documentation.</p>
</li>
-
<li>
- <p>Add an example hostname to the --pre-chroot-nslookup
- description.</p>
+ <p>Explicitly mention Windows 10 as supported so search engines and users looking for it can find it.</p>
</li>
-
<li>
- <p>Add an example for a host pattern that matches an IP
- address.</p>
+ <p>Import a bunch of contributors from the ChangeLog.</p>
</li>
-
<li>
- <p>Rename the 'domain pattern' to 'host pattern' as it may
- contain IP addresses as well.</p>
+ <p>Remove obsolete doc/gpl.html.</p>
+ </li>
+ <li>
+ <p>Upgrade a couple of links to https://.</p>
+ </li>
+ <li>
+ <p>Don't prefer the SourceForge patch tracker over the privoxy-devel mailing list. While at it, link to the
+ SourceForge patch tracker.</p>
+ </li>
+ <li>
+ <p>Mention http-inspection in the 'my browser warns me about unauthenticated content' FAQ entry.</p>
+ </li>
+ <li>
+ <p>Simplify the 'Is there is a license or fee?' FAQ entry.</p>
+ </li>
+ <li>
+ <p>Add another +redirect{} example.</p>
+ </li>
+ <li>
+ <p>Explicitly mention that interested sponsors should include the link target in their first mail.</p>
+ </li>
+ <li>
+ <p>Clarify that only Privoxy team members can object to new sponsors and link to the list of current team
+ members.</p>
+ </li>
+ <li>
+ <p>Note that sponsor URLs may not contain keyword spam.</p>
+ </li>
+ <li>
+ <p>Garbage collect doc/webserver/images which isn't referenced anymore.</p>
+ </li>
+ <li>
+ <p>Update the method to reach the proxy settings in Firefox.</p>
+ </li>
+ <li>
+ <p>Update proxy_setup.jpg description to refer to Firefox.</p>
+ </li>
+ <li>
+ <p>Regenerate proxy_setup.jpg with a more recent Firefox (78.0).</p>
+ </li>
+ <li>
+ <p>Regenerate files-in-use.jpg without obsolete standard.action with modern colors and a slightly better
+ quality.</p>
+ </li>
+ <li>
+ <p>Update URL to the actionsfile tracker.</p>
+ </li>
+ <li>
+ <p>Update a support request URL.</p>
+ </li>
+ <li>
+ <p>Rephrase the 'Can Privoxy run as service' FAQ entry and remove an obsolete paragraph.</p>
+ </li>
+ <li>
+ <p>Let the 'Where can I get updated Actions Files?' entry link to the gitweb version of
+ default.action.master.</p>
+ </li>
+ <li>
+ <p>Update a link to the default.action file.</p>
+ </li>
+ <li>
+ <p>Update URLs for trackers and mailing lists.</p>
+ </li>
+ <li>
+ <p>Replace CVS reference with git.</p>
+ </li>
+ <li>
+ <p>Mention regression-tests.action in the config file.</p>
+ </li>
+ <li>
+ <p>Explicitly mention in the config file that access to the CA key should be limited to Privoxy.</p>
+ </li>
+ <li>
+ <p>List more client-specific-tag examples for inspiration.</p>
+ </li>
+ <li>
+ <p>Add additional headers to the client-header-order example.</p>
+ </li>
+ <li>
+ <p>Note that actions aren't updated after rewrites.</p>
+ </li>
+ <li>
+ <p>Explicitly mention that upgrading from http to https with a client-header filter is not supported</p>
+ </li>
+ <li>
+ <p>Note that protocol and host have to be added when rewriting the destination host for https-inspected
+ requests.</p>
+ </li>
+ <li>
+ <p>Explicitly mention that the CA key is used to sign certificates.</p>
+ </li>
+ <li>
+ <p>Put openssl command in 'command' tags.</p>
+ </li>
+ <li>
+ <p>The man page has been moved from section 1 to man section 8.</p>
+ </li>
+ </ul>
+ </li>
+ <li>
+ <p>Developer manual:</p>
+ <ul>
+ <li>
+ <p>Flesh out the build instructions for Debian.</p>
+ </li>
+ <li>
+ <p>Remove the packaging instructions for RPM-based systems. They don't work and we don't release RPM
+ packages anymore anyway.</p>
+ </li>
+ <li>
+ <p>Remove the packaging instructions for Solaris. They don't work and we don't release Solaris packages
+ anymore anyway.</p>
+ </li>
+ <li>
+ <p>Update the suggested subject for the announce mails.</p>
+ </li>
+ <li>
+ <p>Update upload instructions. ftp://upload.sourceforge.net is no longer functional.</p>
+ </li>
+ <li>
+ <p>Remove a couple of package-dependent upload instructions that don't actually work.</p>
+ </li>
+ <li>
+ <p>Remove 'cd current' that no longer works.</p>
+ </li>
+ <li>
+ <p>Add regression-tests.action to the list of files that should be installed.</p>
+ </li>
+ <li>
+ <p>Stop claiming that there are text versions of the manuals. We stopped building them in 2008
+ (9ed36a3c5e6f12).</p>
+ </li>
+ <li>
+ <p>Note that the 'webserver' target creates the link needed for the user-manual.</p>
+ </li>
+ <li>
+ <p>Suggest to use the master branch as reference when creating the ChangeLog so the steps work when the
+ current branch differs from master which is likely as the developer manual suggests to use a local branch
+ for development.</p>
+ </li>
+ <li>
+ <p>Add the -s flag to the suggested 'git tag' command. We prefer signed tags.</p>
+ </li>
+ <li>
+ <p>Mention that merges into 'master' should be avoided.</p>
+ </li>
+ <li>
+ <p>Add git commands that should result in a merge-free history.</p>
+ </li>
+ <li>
+ <p>Mention Privoxy-Regression-Test.</p>
+ </li>
+ <li>
+ <p>Add a section id to reduce link churn.</p>
+ </li>
+ <li>
+ <p>Recommend the dok-tidy target when building docs for the webserver.</p>
+ </li>
+ <li>
+ <p>Add another plug for the privoxy-devel mailing list.</p>
+ </li>
+ <li>
+ <p>Let the intro link the copyright section in the user manual instead of giving an incomplete summary of
+ the license status.</p>
+ </li>
+ <li>
+ <p>Clarify that the webserver target uploads to the SourceForge webserver.</p>
+ </li>
+ <li>
+ <p>Mark the documentation for the Mac OS X installers as out of date and change the SCM name back to
+ CVS.</p>
+ </li>
+ <li>
+ <p>Fix the location of the installer modules for Mac OS X. They are not actually available through git
+ (yet).</p>
+ </li>
+ <li>
+ <p>Don't speak of Privoxy version 3 in the past tense.</p>
+ </li>
+ <li>
+ <p>Update the list of programs required for the release process.</p>
+ </li>
+ <li>
+ <p>Update description of the webserver target which uses ssh, not scp.</p>
+ </li>
+ <li>
+ <p>Remove obsolete reference to config.new.</p>
+ </li>
+ </ul>
+ </li>
+ <li>
+ <p>Tests:</p>
+ <ul>
+ <li>
+ <p>Add another hide-referrer{conditional-block} test.</p>
</li>
-
<li>
- <p>Recommend forward-socks5t when using Tor. It seems to work
- fine and modifying the Tor configuration to profit from it hasn't
- been necessary for a while now.</p>
+ <p>Add another hide-referrer{conditional-forge} test.</p>
</li>
-
<li>
- <p>Add another redirect{} example to stress that redirect loops
- can and should be avoided.</p>
+ <p>Fix a hide-referrer{conditional-forge} test that expected an acceptable header to be forged.</p>
</li>
-
<li>
- <p>The usual spelling and grammar fixes. Parts of them were
- reported by Reuben Thomas in #3615276.</p>
+ <p>Fix a hide-referrer{conditional-block} test that expected an acceptable Referer to be removed.</p>
</li>
-
<li>
- <p>Mention the PCRS option letters T and D in the filter
- section.</p>
+ <p>Explain why the "Set Header = Host: whatever.example.org" test is expected to fail when using a CGI
+ prefix that starts with "https://".</p>
</li>
-
<li>
- <p>Clarify that handle-as-empty-doc-returns-ok is still useful
- and will not be removed without replacement.</p>
+ <p>Explain why a connection-sharing test is known to fail when using "https://p.p/" as CGI prefix.</p>
</li>
-
<li>
- <p>Note that security issues shouldn't be reported using the bug
- tracker.</p>
+ <p>Add a link to Privoxy-Regression-Test to regression-tests.action in case it isn't packaged.</p>
</li>
-
<li>
- <p>Clarify what Privoxy does if both +block{} and +redirect{}
- apply.</p>
+ <p>Add regression tests for pcre host patterns.</p>
</li>
-
<li>
- <p>Removed the obsolete bookmarklets section.</p>
+ <p>Fixed a regression test that is executed when FEATURE_GRACEFUL_TERMINATION is enabled.</p>
</li>
</ul>
</li>
-
<li>
- <p>Build system improvements:</p>
-
+ <p>Privoxy infrastructure:</p>
<ul>
<li>
- <p>Let --with-group properly deal with secondary groups. Patch
- submitted by Anatoly Arzhnikov in #3615187.</p>
+ <p>Import a Privoxy logo for the website.</p>
</li>
-
<li>
- <p>Fix web-actions target.</p>
+ <p>Update Tor onion service to HiddenServiceVersion 3.</p>
</li>
-
<li>
- <p>Add a web-faq target that only updates the FAQ on the
- webserver.</p>
+ <p>Display the "model" photos in a single row and remove placeholder images.</p>
</li>
-
<li>
- <p>Remove already-commented-out non-portable DOSFILTER
- alternatives.</p>
+ <p>Regenerate homepage with updated sponsor list.</p>
</li>
-
<li>
- <p>Remove the obsolete targets dok-put and dok-get.</p>
+ <p>Use the '/sponsor' redirect for the link to the sponsor page.</p>
</li>
-
<li>
- <p>Add a sf-shell target.</p>
+ <p>Git commit messages are sent to the Privoxy-commits mailing list.</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>
-
+ <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=
+ <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>
+ <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>
+ <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>
+ <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>
+ <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">
+ <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>
+ <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>
+ <td width="33%" align="right" valign="top">Quickstart to Using Privoxy</td>
</tr>
</table>
</div>
projects / privoxy.git / blobdiff