+ Highlight a few more messages.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Add a handler for tagging messages.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Properly deal with 'Certificate error' crunches
+ Previously the error description was highlighted as 'host'.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Log truncated LOG_LEVEL_CLF messages more gracefully
+ and note that the statistics will be imprecise.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Fixed perldoc typo.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Bump version to 0.9.2.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Privoxy-Regression-Test:
+ <itemizedlist>
+ <listitem>
+ <para>
+ Use http://127.0.0.1:8118/ as default Privoxy address
+ unless http_proxy is set through the environment.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ 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.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ 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.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Use --proxy-header when using a CGI prefix with https://
+ and a "Host:" header.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Allow '|' in tokens and values to allow tag patterns like
+ "TAG:^(application|text)/(x-)?javascript$".
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ When get_cgi_page_or_else() fails, include the URL of the
+ requested page in the log message.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ 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.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Bumped version to 0.7.2
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ uagen:
+ <itemizedlist>
+ <listitem>
+ <para>
+ Update example output.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Recommend the use of the https-inspection action in the documentation.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Upgrade a couple of URLs to https://.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Add ElectroBSD to the list of operating systems.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Bumped generated Firefox version to 78 (ESR).
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Bumped version to 1.2.2.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ User documentation:
+ <itemizedlist>
+ <listitem>
+ <para>
+ 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 ...
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ 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.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ 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.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Describe how to check if Privoxy has been built with
+ FEATURE_HTTPS_INSPECTION.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Add a link to the trusted-cas-file documentation
+ that explains how the user can create the file herself.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ 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.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Update the +hide-user-agent example with uagen output.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Slightly improve the wording of the ca-key-file documentation.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Explicitly mention Windows 10 as supported so search engines and
+ users looking for it can find it.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Import a bunch of contributors from the ChangeLog.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Remove obsolete doc/gpl.html.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Upgrade a couple of links to https://.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Don't prefer the SourceForge patch tracker over the
+ privoxy-devel mailing list. While at it, link to the
+ SourceForge patch tracker.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Mention http-inspection in the 'my browser warns me about
+ unauthenticated content' FAQ entry.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Simplify the 'Is there is a license or fee?' FAQ entry.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Add another +redirect{} example.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Explicitly mention that interested sponsors should include
+ the link target in their first mail.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Clarify that only Privoxy team members can object to new sponsors
+ and link to the list of current team members.