X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=doc%2Fwebserver%2Fuser-manual%2Fwhatsnew.html;h=07a5a2897a35e223a11bcd37026e002ddbda76e4;hp=d12d16be0a9c4040fb44da4290df618bc666885d;hb=6d60ac0445984436221788b6967c6c1459efe08c;hpb=69b45dc21f48175fb34a8e1e2f45d46870e37941

diff --git a/doc/webserver/user-manual/whatsnew.html b/doc/webserver/user-manual/whatsnew.html
index d12d16be..07a5a289 100644
--- a/doc/webserver/user-manual/whatsnew.html
+++ b/doc/webserver/user-manual/whatsnew.html
@@ -6,7 +6,7 @@
   <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.19 User Manual" href="index.html">
+  <link rel="HOME" title="Privoxy 3.0.21 User Manual" href="index.html">
   <link rel="PREVIOUS" title="Installation" href="installation.html">
   <link rel="NEXT" title="Quickstart to Using Privoxy" href=
   "quickstart.html">
@@ -21,7 +21,7 @@
     <table summary="Header navigation table" width="100%" border="0"
     cellpadding="0" cellspacing="0">
       <tr>
-        <th colspan="3" align="center">Privoxy 3.0.19 User Manual</th>
+        <th colspan="3" align="center">Privoxy 3.0.21 User Manual</th>
       </tr>
 
       <tr>
@@ -41,8 +41,10 @@
     <h1 class="SECT1"><a name="WHATSNEW" id="WHATSNEW">3. What's New in this
     Release</a></h1>
 
-    <p><span class="APPLICATION">Privoxy 3.0.19</span> is a stable release.
-    The changes since 3.0.18 stable are:</p>
+    <p><span class="APPLICATION">Privoxy 3.0.21</span> stable is a bug-fix
+    release for Privoxy 3.0.20 beta. It also addresses two security issues
+    that affect all previous Privoxy versions. The changes since 3.0.20 beta
+    are:</p>
 
     <ul>
       <li>
@@ -50,21 +52,23 @@
 
         <ul>
           <li>
-            <p>Prevent a segmentation fault when de-chunking buffered
-            content. It could be triggered by malicious web servers if
-            Privoxy was configured to filter the content and running on a
-            platform where SIZE_T_MAX isn't larger than UINT_MAX, which
-            probably includes most 32-bit systems. On those platforms, all
-            Privoxy versions before 3.0.19 appear to be affected. To be on
-            the safe side, this bug should be presumed to allow code
-            execution as proving that it doesn't seems unrealistic.</p>
+            <p>On POSIX-like platforms, network sockets with file descriptor
+            values above FD_SETSIZE are properly rejected. Previously they
+            could cause memory corruption in configurations that allowed the
+            limit to be reached.</p>
           </li>
 
           <li>
-            <p>Do not expect a response from the SOCKS4/4A server until it
-            got something to respond to. This regression was introduced in
-            3.0.18 and prevented the SOCKS4/4A negotiation from working.
-            Reported by qqqqqw in #3459781.</p>
+            <p>Proxy authentication headers are removed unless the new
+            directive enable-proxy-authentication-forwarding is used.
+            Forwarding the headers potentionally allows malicious sites to
+            trick the user into providing it with login information. Reported
+            by Chris John Riley.</p>
+          </li>
+
+          <li>
+            <p>Compiles on OS/2 again now that unistd.h is only included on
+            platforms that have it.</p>
           </li>
         </ul>
       </li>
@@ -74,133 +78,173 @@
 
         <ul>
           <li>
-            <p>Fix an off-by-one in an error message about connect
-            failures.</p>
+            <p>The show-status page shows the FEATURE_STRPTIME_SANITY_CHECKS
+            status.</p>
+          </li>
+
+          <li>
+            <p>A couple of assert()s that could theoretically dereference
+            NULL pointers in debug builds have been relocated.</p>
           </li>
 
           <li>
-            <p>Use a GNUMakefile variable for the webserver root directory
-            and update the path. Sourceforge changed it which broke various
-            web-related targets.</p>
+            <p>Added an LSB info block to the generic start script. Based on
+            a patch from Natxo Asenjo.</p>
           </li>
 
           <li>
-            <p>Update the CODE_STATUS description.</p>
+            <p>The max-client-connections default has been changed to 128
+            which should be more than enough for most setups.</p>
           </li>
         </ul>
       </li>
-    </ul>
 
-    <p>The following changes were made between 3.0.17 and 3.0.18:</p>
+      <li>
+        <p>Action file improvements:</p>
+
+        <ul>
+          <li>
+            <p>Block rover.ebay./ar.*\&amp;adtype= instead of
+            "/.*\&amp;adtype=" which caused too man false positives. Reported
+            by u302320 in #360284, additional feedback from Adam Piggott.</p>
+          </li>
+
+          <li>
+            <p>Unblock '.advrider.com/' and '/.*ADVrider'. Anonymously
+            reported in #3603636.</p>
+          </li>
+
+          <li>
+            <p>Stop blocking '/js/slider\.js'. Reported by Adam Piggott in
+            #3606635 and _lvm in #2791160.</p>
+          </li>
+        </ul>
+      </li>
 
-    <ul>
       <li>
-        <p>Bug fixes:</p>
+        <p>Filter file improvements:</p>
+
+        <ul>
+          <li>
+            <p>Added an iframes filter.</p>
+          </li>
+        </ul>
+      </li>
+
+      <li>
+        <p>Documentation improvements:</p>
 
         <ul>
           <li>
-            <p>If a generated redirect URL contains characters RFC 3986
-            doesn't permit, they are (re)encoded. Not doing this makes
-            Privoxy versions from 3.0.5 to 3.0.17 susceptible to HTTP
-            response splitting (CWE-113) attacks if the
-            +fast-redirects{check-decoded-url} action is used.</p>
+            <p>The whole GPLv2 text is included in the user manual now, so
+            Privoxy can serve it itself and the user can read it without
+            having to wade through GPLv3 ads first.</p>
+          </li>
+
+          <li>
+            <p>Properly numbered and underlined a couple of section titles in
+            the config that where previously overlooked due to a flaw in the
+            conversion script. Reported by Ralf Jungblut.</p>
           </li>
 
           <li>
-            <p>Fix a logic bug that could cause Privoxy to reuse a server
-            socket after it got tainted by a server-header-tagger-induced
-            block that was triggered before the whole server response had
-            been read. If keep-alive was enabled and the request following
-            the blocked one was to the same host and using the same
-            forwarding settings, Privoxy would send it on the tainted server
-            socket. While the server would simply treat it as a pipelined
-            request, Privoxy would later on fail to properly parse the
-            server's response as it would try to parse the unread data from
-            the first response as server headers for the second one.
-            Regression introduced in 3.0.17.</p>
+            <p>Improved the support instruction to hopefully make it harder
+            to unintentionally provide insufficient information when
+            requesting support. Previously it wasn't obvious that the
+            information we need in bug reports is usually also required in
+            support requests.</p>
           </li>
 
           <li>
-            <p>When implying keep-alive in client_connection(), remember that
-            the client didn't. Fixes a regression introduced in 3.0.13 that
-            would cause Privoxy to wait for additional client requests after
-            receiving a HTTP/1.1 request with "Connection: close" set and
-            connection sharing enabled. With clients which terminates the
-            client connection after detecting that the whole body has been
-            received it doesn't really matter, but with clients that don't
-            the connection would be kept open until it timed out.</p>
+            <p>Removed documentation about packages that haven't been
+            provided in years.</p>
+          </li>
+        </ul>
+      </li>
+
+      <li>
+        <p>Privoxy-Regression-Test:</p>
+
+        <ul>
+          <li>
+            <p>Only log the test number when not running in verbose mode The
+            position of the test is rarely relevant and it previously wasn't
+            exactly obvious which one of the numbers was useful to repeat the
+            test with --test-number.</p>
           </li>
+        </ul>
+      </li>
+
+      <li>
+        <p>GNUmakefile improvements:</p>
 
+        <ul>
           <li>
-            <p>Fix a subtle race condition between
-            prepare_csp_for_next_request() and sweep(). A thread preparing
-            itself for the next client request could briefly appear to be
-            inactive. If all other threads were already using more recent
-            files, the thread could get its files swept away under its feet.
-            So far this has only been reproduced while stress testing in
-            valgrind while touching action files in a loop. It's unlikely to
-            have caused any actual problems in the real world.</p>
+            <p>Factor generate-config-file out of config-file to make testing
+            more convenient.</p>
           </li>
 
           <li>
-            <p>Disable filters if SDCH compression is used unless filtering
-            is forced. If SDCH was combined with a supported compression
-            algorithm, Privoxy previously could try to decompress it and
-            ditch the Content-Encoding header even though the SDCH
-            compression wasn't dealt with. Reported by zebul666 in
-            #3225863.</p>
+            <p>The clean target now also takes care of patch leftovers.</p>
           </li>
+        </ul>
+      </li>
+    </ul>
+
+    <p><span class="APPLICATION">Privoxy 3.0.20</span> beta contained the
+    following changes compared to the previous stable release:</p>
+
+    <ul>
+      <li>
+        <p>Bug fixes:</p>
 
+        <ul>
           <li>
-            <p>Make a copy of the --user value and only mess with that when
-            splitting user and group. On some operating systems modifying the
-            value directly is reflected in the output of ps and friends and
-            can be misleading. Reported by zepard in #3292710.</p>
+            <p>Client sockets are now properly shutdown and drained before
+            being closed. This fixes page truncation issues with clients that
+            aggressively pipeline data on platforms that otherwise discard
+            already written data. The issue mainly affected Opera users and
+            was initially reported by Kevin in #3464439, szotsaki provided
+            additional information to track down the cause.</p>
           </li>
 
           <li>
-            <p>If forwarded-connect-retries is set, only retry if Privoxy is
-            actually forwarding the request. Previously direct connections
-            would be retried as well.</p>
+            <p>Fix latency calculation for shared connections (disabled by
+            default). It was broken since their introduction in 2009. The
+            calculated latency for most connections would be 0 in which case
+            the timeout detection failed to account for the real latency.</p>
           </li>
 
           <li>
-            <p>Fixed a small memory leak when retrying connections with IPv6
-            support enabled.</p>
+            <p>Reject URLs with invalid port. Previously they were parsed
+            incorrectly and characters between the port number and the first
+            slash were silently dropped as shown by curl test 187.</p>
           </li>
 
           <li>
-            <p>Remove an incorrect assertion in
-            compile_dynamic_pcrs_job_list() It could be triggered by a pcrs
-            job with an invalid pcre pattern (for example one that contains a
-            lone quantifier).</p>
+            <p>The default-server-timeout and socket-timeout directives
+            accept 0 as valid value.</p>
           </li>
 
           <li>
-            <p>If the --user argument user[.group] contains a dot, always
-            bail out if no group has been specified. Previously the intended,
-            but undocumented (and apparently untested), behaviour was to try
-            interpreting the whole argument as user name, but the detection
-            was flawed and checked for '0' instead of '\0', thus merely
-            preventing group names beginning with a zero.</p>
+            <p>Fix a race condition on Windows that could cause Privoxy to
+            become unresponsive after toggling it on or off through the
+            taskbar icon. Reported by Tim H. in #3525694.</p>
           </li>
 
           <li>
-            <p>In html_code_map[], use a numeric character reference instead
-            of ' which wasn't standardized before XHTML 1.0.</p>
+            <p>Fix the compilation on Windows when configured without IPv6
+            support.</p>
           </li>
 
           <li>
-            <p>Fix an invalid free when compiled with
-            FEATURE_GRACEFUL_TERMINATION and shut down through
-            http://config.privoxy.org/die</p>
+            <p>Fix an assertion that could cause debug builds to abort() in
+            case of socks5 connection failures with "debug 2" enabled.</p>
           </li>
 
           <li>
-            <p>In get_actions(), fix the "temporary" backwards compatibility
-            hack to accept block actions without reason. It also covered
-            other actions that should be rejected as invalid. Reported by
-            Billy Crook.</p>
+            <p>Fix an assertion that could cause debug builds to abort() if a
+            filter contained nul bytes in the replacement text.</p>
           </li>
         </ul>
       </li>
@@ -210,746 +254,761 @@
 
         <ul>
           <li>
-            <p>Privoxy can (re)compress buffered content before delivering it
-            to the client. Disabled by default as most users wouldn't benefit
-            from it.</p>
+            <p>Significantly improved keep-alive support for both client and
+            server connections.</p>
+          </li>
+
+          <li>
+            <p>New debug log level 65536 which logs all actions that were
+            applied to the request.</p>
+          </li>
+
+          <li>
+            <p>New directive client-header-order to forward client headers in
+            a different order than the one in which they arrived.</p>
+          </li>
+
+          <li>
+            <p>New directive tolerate-pipelining to allow client-side
+            pipelining. If enabled (3.0.20 beta enables it by default),
+            Privoxy will keep pipelined client requests around to deal with
+            them once the current request has been served.</p>
           </li>
 
           <li>
-            <p>The +fast-redirects{check-decoded-url} action checks URL
-            segments separately. If there are other parameters behind the
-            redirect URL, this makes it unnecessary to cut them off by
-            additionally using a +redirect{} pcrs command. Initial patch
-            submitted by Jamie Zawinski in #3429848.</p>
+            <p>New --config-test option to let Privoxy exit after checking
+            whether or not the configuration seems valid. The limitations
+            noted in TODO #22 and #23 still apply. Based on a patch by
+            Ramkumar Chinchani.</p>
           </li>
 
           <li>
-            <p>When loading action sections, verify that the referenced
-            filters exist. Currently missing filters only result in an error
-            message, but eventually the severity will be upgraded to
-            fatal.</p>
+            <p>New limit-cookie-lifetime{} action to let cookies expire
+            before the end of the session. Suggested by Rick Sykes in
+            #1049575.</p>
           </li>
 
           <li>
-            <p>Allow to bind to multiple separate addresses. Patch set
-            submitted by Petr Pisar in #3354485.</p>
+            <p>Increase the hard-coded maximum number of actions and filter
+            files from 10 to 30 (each). It doesn't significantly affect
+            Privoxy's memory usage and recompiling wasn't an option for all
+            Privoxy users that reached the limit.</p>
           </li>
 
           <li>
-            <p>Set socket_error to errno if connecting fails in
-            rfc2553_connect_to(). Previously rejected direct connections
-            could be incorrectly reported as DNS issues if Privoxy was
-            compiled with IPv6 support.</p>
+            <p>Add support for chunk-encoded client request bodies.
+            Previously chunk-encoded request bodies weren't guaranteed to be
+            forwarded correctly, so this can also be considered a bug fix
+            although chunk-encoded request bodies aren't commonly used in the
+            real world.</p>
           </li>
 
           <li>
-            <p>Adjust url_code_map[] so spaces are replaced with %20 instead
-            of '+' While '+' can be used by client's submitting form data,
-            this is not actually what Privoxy is using the lookups for. This
-            is more of a cosmetic issue and doesn't fix any known
-            problems.</p>
+            <p>Add support for Tor's optimistic-data SOCKS extension, which
+            can reduce the latency for requests on newly created connections.
+            Currently only the headers are sent optimistically and only if
+            the client request has already been read completely which rules
+            out requests with large bodies.</p>
           </li>
 
           <li>
-            <p>When compiled without FEATURE_FAST_REDIRECTS, do not silently
-            ignore +fast-redirect{} directives</p>
+            <p>After preventing the client from pipelining, don't signal
+            keep-alive intentions. When looking at the response headers
+            alone, it previously wasn't obvious from the client's perspective
+            that no additional responses should be expected.</p>
           </li>
 
           <li>
-            <p>Added a workaround for GNU libc's strptime() reporting
-            negative year values when the parsed year is only specified with
-            two digits. On affected systems cookies with such a date would
-            not be turned into session cookies by the +session-cookies-only
-            action. Reported by Vaeinoe in #3403560</p>
+            <p>Stop considering client sockets tainted after receiving a
+            request with body. It hasn't been necessary for a while now and
+            unnecessarily causes test failures when using curl's test
+            suite.</p>
           </li>
 
           <li>
-            <p>Fixed bind failures with certain GNU libc versions if no
-            non-loopback IP address has been configured on the system. This
-            is mainly an issue if the system is using DHCP and Privoxy is
-            started before the network is completely configured. Reported by
-            Raphael Marichez in #3349356. Additional insight from Petr
-            Pisar.</p>
+            <p>Allow HTTP/1.0 clients to signal interest in keep-alive
+            through the Proxy-Connection header. While such client are rare
+            in the real world, it doesn't hurt and couple of curl tests rely
+            on it.</p>
           </li>
 
           <li>
-            <p>Privoxy log messages now use the ISO 8601 date format
-            %Y-%m-%d. It's only slightly longer than the old format, but
-            contains the full date including the year and allows sorting by
-            date (when grepping in multiple log files) without hassle.</p>
+            <p>Only remove duplicated Content-Type headers when filters are
+            enabled. If they are not it doesn't cause ill effects and the
+            user might not want it. Downgrade the removal message to
+            LOG_LEVEL_HEADER to clarify that it's not an error in Privoxy and
+            is unlikely to cause any problems in general. Anonymously
+            reported in #3599335.</p>
           </li>
 
           <li>
-            <p>In get_last_url(), do not bother trying to decode URLs that do
-            not contain at least one '%' sign. It reduces the log noise and a
-            number of unnecessary memory allocations.</p>
+            <p>Set the socket option SO_LINGER for the client socket.</p>
           </li>
 
           <li>
-            <p>In case of SOCKS5 failures, dump the socks response in the log
-            message.</p>
+            <p>Move several variable declarations to the beginning of their
+            code block. It's required when compiling with gcc 2.95 which is
+            still used on some platforms. Initial patch submitted by Simon
+            South in #3564815.</p>
           </li>
 
           <li>
-            <p>Simplify the signal setup in main().</p>
+            <p>Optionally try to sanity-check strptime() results before
+            trusting them. Broken strptime() implementations have caused
+            problems in the past and the most recent offender seems to be
+            FreeBSD's libc (standards/173421).</p>
           </li>
 
           <li>
-            <p>Streamline socks5_connect() slightly.</p>
+            <p>When filtering is enabled, let Range headers pass if the range
+            starts at the beginning. This should work around (or at least
+            reduce) the video playback issues with various Apple clients as
+            reported by Duc in #3426305.</p>
           </li>
 
           <li>
-            <p>In socks5_connect(), require a complete socks response from
-            the server. Previously Privoxy didn't care how much data the
-            server response contained as long as the first two bytes
-            contained the expected values. While at it, shrink the buffer
-            size so Privoxy can't read more than a whole socks response.</p>
+            <p>Do not confuse a client hanging up with a connection time out.
+            If a client closes its side of the connection without sending a
+            request line, do not send the CLIENT_CONNECTION_TIMEOUT_RESPONSE,
+            but report the condition properly.</p>
           </li>
 
           <li>
-            <p>In chat(), do not bother to generate a client request in case
-            of direct CONNECT requests. It will not be used anyway.</p>
+            <p>Allow closing curly braces as part of action values as long as
+            they are escaped.</p>
           </li>
 
           <li>
-            <p>Reduce server_last_modified()'s stack size.</p>
+            <p>On Windows, the logfile is now written before showing the GUI
+            error message which blocks until the user acknowledges it.
+            Reported by Adriaan in #3593603.</p>
           </li>
 
           <li>
-            <p>Shorten get_http_time() by using strftime().</p>
+            <p>Remove an unreasonable parameter limit in the CGI interface.
+            The new parameter limit depends on the memory available and is
+            currently unlikely to be reachable, due to other limits in both
+            Privoxy and common clients. Reported by Andrew on
+            ijbswa-users@.</p>
           </li>
 
           <li>
-            <p>Constify the known_http_methods pointers in
-            unknown_method().</p>
+            <p>Decrease the chances of parse failures after requests with
+            unsupported methods were sent to the CGI interface.</p>
           </li>
+        </ul>
+      </li>
+
+      <li>
+        <p>Action file improvements:</p>
 
+        <ul>
           <li>
-            <p>Constify the time_formats pointers in parse_header_time().</p>
+            <p>Remove the comment that indicated that updated default.action
+            versions are released on their own.</p>
           </li>
 
           <li>
-            <p>Constify the formerly_valid_actions pointers in
-            action_used_to_be_valid().</p>
+            <p>Block 'optimize.indieclick.com/' and
+            'optimized-by.rubiconproject.com/'</p>
           </li>
 
           <li>
-            <p>Introduce a GNUMakefile MAN_PAGE variable that defaults to
-            privoxy.1. The Debian package uses section 8 for the man page and
-            this should simplify the patch.</p>
+            <p>Unblock 'adjamblog.wordpress.com/' and
+            'adjamblog.files.wordpress.com/'. Reported by Ryan Farmer in
+            #3496116.</p>
           </li>
 
           <li>
-            <p>Deduplicate the INADDR_NONE definition for Solaris by moving
-            it to jbsockets.h</p>
+            <p>Unblock '/.*Bugtracker'. Reported by pwhk in #3522341.</p>
           </li>
 
           <li>
-            <p>In block_url(), ditch the obsolete workaround for ancient
-            Netscape versions that supposedly couldn't properly deal with
-            status code 403.</p>
+            <p>Add test URLs for '.freebsd.org' and '.watson.org'.</p>
           </li>
 
           <li>
-            <p>Remove a useless NULL pointer check in load_trustfile().</p>
+            <p>Unblock '.urbandictionary.com/popular'.</p>
           </li>
 
           <li>
-            <p>Remove two useless NULL pointer checks in
-            load_one_re_filterfile().</p>
+            <p>Block '.adnxs.com/'.</p>
           </li>
 
           <li>
-            <p>Change url_code_map[] from an array of pointers to an array of
-            arrays It removes an unnecessary layer of indirection and on
-            64bit system reduces the size of the binary a bit.</p>
+            <p>Block 'farm.plista.com/widgetdata.php'.</p>
           </li>
 
           <li>
-            <p>Fix various typos. Fixes taken from Debian's 29_typos.dpatch
-            by Roland Rosenfeld.</p>
+            <p>Block 'rotation.linuxnewmedia.com/'.</p>
           </li>
 
           <li>
-            <p>Add a dok-tidy GNUMakefile target to clean up the messy HTML
-            generated by the other dok targets.</p>
+            <p>Block 'reklamy.sfd.pl/'. Reported by kacperdominik in
+            #3399948.</p>
           </li>
 
           <li>
-            <p>GNUisms in the GNUMakefile have been removed.</p>
+            <p>Block 'g.adspeed.net/'.</p>
           </li>
 
           <li>
-            <p>Change the HTTP version in static responses to 1.1</p>
+            <p>Unblock 'websupport.wdc.com/'. Reported by Adam Piggot in
+            #3577851.</p>
           </li>
 
           <li>
-            <p>Synced config.sub and config.guess with upstream
-            2011-11-11/386c7218162c145f5f9e1ff7f558a3fbb66c37c5.</p>
+            <p>Block '/openx/www/delivery/'.</p>
           </li>
 
           <li>
-            <p>Add a dedicated function to parse the values of toggles.
-            Reduces duplicated code in load_config() and provides better
-            error handling. Invalid or missing toggle values are now a fatal
-            error instead of being silently ignored.</p>
+            <p>Disable fast-redirects for '.googleapis.com/'.</p>
           </li>
 
           <li>
-            <p>Terminate HTML lines in static error messages with \n instead
-            of \r\n.</p>
+            <p>Block 'imp.double.net/'. Reported by David Bo in #3070411.</p>
           </li>
 
           <li>
-            <p>Simplify cgi_error_unknown() a bit.</p>
+            <p>Block 'gm-link.com/' which is used for email tracking.
+            Reported by David Bo in #1812733.</p>
           </li>
 
           <li>
-            <p>In LogPutString(), don't bother looking at pszText when not
-            actually logging anything.</p>
+            <p>Verify that requests to "bwp." are blocked. URL taken from
+            #1736879 submitted by Francois Marier.</p>
           </li>
 
           <li>
-            <p>Change ssplit()'s fourth parameter from int to size_t. Fixes a
-            clang complaint.</p>
+            <p>Block '/.*bannerid='. Reported by Adam Piggott in
+            #2975779.</p>
           </li>
 
           <li>
-            <p>Add a warning that the statistics currently can't be trusted.
-            Mention Privoxy-Log-Parser's --statistics option as an
-            alternative for the time being.</p>
+            <p>Block 'cltomedia.info/delivery/' and '.adexprt.com/'.
+            Anonymously reported in #2965254.</p>
           </li>
 
           <li>
-            <p>In rfc2553_connect_to(), start setting cgi-&gt;error_message
-            on error.</p>
+            <p>Block 'de17a.com/'. Reported by David Bo in #3061472.</p>
           </li>
 
           <li>
-            <p>Change the expected status code returned for http://p.p/die
-            depending on whether or not FEATURE_GRACEFUL_TERMINATION is
-            available.</p>
+            <p>Block 'oskar.tradera.com/'. Reported by David Bo in
+            #3060596.</p>
           </li>
 
           <li>
-            <p>In cgi_die(), mark the client connection for closing. If the
-            client will fetch the style sheet through another connection it
-            gets the main thread out of the accept() state and should thus
-            trigger the actual shutdown.</p>
+            <p>Block '/scripts/webtrends\.js'. Reported by johnd16 in
+            #3002729.</p>
           </li>
 
           <li>
-            <p>Add a proper CGI message for cgi_die().</p>
+            <p>Block requests for 'pool.*.adhese.com/'. Reported by johnd16
+            in #3002716.</p>
           </li>
 
           <li>
-            <p>Don't enforce a logical line length limit in
-            read_config_line().</p>
+            <p>Update path pattern for Coremetrics and add tests. Pattern and
+            URLs submitted by Adam Piggott #3168443.</p>
           </li>
 
           <li>
-            <p>Slightly refactor server_last_modified() to remove useless
-            gmtime*() calls.</p>
+            <p>Enable +fast-redirects{check-decoded-url} for 'tr.anp.se/'.
+            Reported by David Bo in #3268832.</p>
           </li>
 
           <li>
-            <p>In get_content_type(), also recognize '.jpeg' as JPEG
-            extension.</p>
+            <p>Unblock '.conrad.se/newsletter/banners/'. Reported by David Bo
+            in #3413824.</p>
           </li>
 
           <li>
-            <p>Add '.png' to the list of recognized file extensions in
-            get_content_type().</p>
+            <p>Block '.tynt.com/'. Reported by Dan Stahlke in #3421767.</p>
           </li>
 
           <li>
-            <p>In block_url(), consistently use the block reason "Request
-            blocked by Privoxy" In two places the reason was "Request for
-            blocked URL" which hides the fact that the request got blocked by
-            Privoxy and isn't necessarily correct as the block may be due to
-            tags.</p>
+            <p>Unblock '.bbci.co.uk/radio/'. Reported by Adam Piggott in
+            #3569603.</p>
           </li>
 
           <li>
-            <p>In listen_loop(), reload the configuration files after
-            accepting a new connection instead of before. Previously the
-            first connection that arrived after a configuration change would
-            still be handled with the old configuration.</p>
+            <p>Block requests to 'service.maxymiser.net/'. Reported by
+            johnd16 in #3118401 (with a previous URL).</p>
           </li>
 
           <li>
-            <p>In chat()'s receive-data loop, skip a client socket check if
-            the socket will be written to right away anyway. This can
-            increase the transfer speed for unfiltered content on fast
-            network connections.</p>
+            <p>Disable fast-redirects for Google's "let's pretend your
+            computer is infected" page.</p>
           </li>
 
           <li>
-            <p>The socket timeout is used for SOCKS negotiations as well
-            which previously couldn't timeout.</p>
+            <p>Unblock '/.*download' to resolve actionsfile feedback
+            #3498129. Submitted by Steven Kolins (soundcloud.com not
+            working).</p>
           </li>
 
           <li>
-            <p>Don't keep the client connection alive if any configuration
-            file changed since the time the connection came in. This is
-            closer to Privoxy's behaviour before keep-alive support for
-            client connection has been added and also less confusing in
-            general.</p>
+            <p>Unblock '.wlxrs.com/' which is required by hotmail.com. Fixes
+            #3413827 submitted by David Bo.</p>
           </li>
 
           <li>
-            <p>Treat all Content-Type header values containing the pattern
-            'script' as a sign of text. Reported by pribog in #3134970.</p>
+            <p>Add two unblock patterns for popup radio and TV players.
+            Submitted by Adam Piggott in #3596089.</p>
           </li>
         </ul>
       </li>
 
       <li>
-        <p>Action file improvements:</p>
+        <p>Filter file improvements &amp; bug fixes:</p>
 
         <ul>
           <li>
-            <p>Moved the site-specific block pattern section below the one
-            for the generic patterns so for requests that are matched in
-            both, the block reason for the domain is shown which is usually
-            more useful than showing the one for the generic pattern.</p>
+            <p>Add a referer tagger.</p>
           </li>
 
           <li>
-            <p>Remove -prevent-compression from the fragile alias. It's no
-            longer used anywhere by default and isn't known to break stuff
-            anyway.</p>
+            <p>Reduce the likelihood that the google filter messes up
+            HTML-generating JavaScript. Reported by Zeno Kugy in
+            #3520260.</p>
           </li>
+        </ul>
+      </li>
 
-          <li>
-            <p>Add a (disabled) section to block various Facebook tracking
-            URLs. Reported by Dan Stahlke in #3421764.</p>
-          </li>
+      <li>
+        <p>Documentation improvements:</p>
 
+        <ul>
           <li>
-            <p>Add a (disabled) section to rewrite and redirect
-            click-tracking URLs used on news.google.com. Reported by Dan
-            Stahlke in #3421755.</p>
+            <p>Revised all OS X sections due to new packaging module
+            (OSXPackageBuilder).</p>
           </li>
 
           <li>
-            <p>Unblock linuxcounter.net/. Reported by Dan Stahlke in
-            #3422612.</p>
+            <p>Update the list of supported operating systems to clarify that
+            all Windows versions after 95 are expected to work and note that
+            the platform-specific code for AmigaOS and QNX currently isn't
+            maintained.</p>
           </li>
 
           <li>
-            <p>Block 'www91.intel.com/' which is used by Omniture. Reported
-            by Adam Piggott in #3167370.</p>
+            <p>Update 'Signals' section, the only explicitly handled signals
+            are SIGINT, SIGTERM and SIGHUP.</p>
           </li>
 
           <li>
-            <p>Disable the handle-as-empty-doc-returns-ok option and mark it
-            as deprecated. Reminded by tceverling in #2790091.</p>
+            <p>Add Haiku to the list of operating systems on which Privoxy is
+            known to run.</p>
           </li>
 
           <li>
-            <p>Add ".ivwbox.de/" to the "Cross-site user tracking" section.
-            Reported by Nettozahler in #3172525.</p>
+            <p>Add DragonFly to the list of BSDs on which Privoxy is known to
+            run.</p>
           </li>
 
           <li>
-            <p>Unblock and fast-redirect ".awin1.com/.*=http://". Reported by
-            Adam Piggott in #3170921.</p>
+            <p>Removed references to redhat-specific documentation set since
+            it no longer exists.</p>
           </li>
 
           <li>
-            <p>Block "b.collective-media.net/".</p>
+            <p>Removed references to building PDFs since we no longer do
+            so.</p>
           </li>
 
           <li>
-            <p>Widen the Debian popcon exception to "qa.debian.org/popcon".
-            Seen in Debian's 05_default_action.dpatch by Roland
-            Rosenfeld.</p>
+            <p>Multiple listen-address directives are supported since 3.0.18,
+            correct the documentation to say so.</p>
           </li>
 
           <li>
-            <p>Block ".gemius.pl/" which only seems to be used for user
-            tracking. Reported by johnd16 in #3002731. Additional input from
-            Lee and movax.</p>
+            <p>Remove bogus section about long and short being preferable to
+            int.</p>
           </li>
 
           <li>
-            <p>Disable banners-by-size filters for '.thinkgeek.com/'. The
-            filter only seems to catch pictures of the inventory.</p>
+            <p>Corrected some Internet JunkBuster references to Privoxy.</p>
           </li>
 
           <li>
-            <p>Block requests for 'go.idmnet.bbelements.com/please/showit/'.
-            Reported by kacperdominik in #3372959.</p>
+            <p>Removed references to www.junkbusters.com since it is no
+            longer maintained. Reported by Angelina Matson.</p>
           </li>
 
           <li>
-            <p>Unblock adainitiative.org/.</p>
+            <p>Various grammar and spelling corrections</p>
           </li>
 
           <li>
-            <p>Add a fast-redirects exception for
-            '.googleusercontent.com/.*=cache'.</p>
+            <p>Add a client-header-tagger{} example for disabling filtering
+            for range requests.</p>
           </li>
 
           <li>
-            <p>Add a fast-redirects exception for
-            webcache.googleusercontent.com/.</p>
+            <p>Correct a URL in the "Privoxy with Tor" FAQ.</p>
           </li>
 
           <li>
-            <p>Unblock http://adassier.wordpress.com/ and
-            http://adassier.files.wordpress.com/.</p>
+            <p>Spell 'refresh-tags' correctly. Reported by Don in
+            #3571927.</p>
           </li>
-        </ul>
-      </li>
 
-      <li>
-        <p>Filter file improvements:</p>
-
-        <ul>
           <li>
-            <p>Let the yahoo filter hide '.ads'.</p>
+            <p>Sort manpage options alphabetically.</p>
           </li>
 
           <li>
-            <p>Let the msn filter hide overlay ads for Facebook 'likes' in
-            search results and elements with the id 's_notf_div'. They only
-            seem to be used to advertise site 'enhancements'.</p>
+            <p>Remove an incorrect sentence in the toggle section. The toggle
+            state doesn't affect whether or not the Windows version uses the
+            tray icon. Reported by Zeno Kugy in #3596395.</p>
           </li>
 
           <li>
-            <p>Let the js-events filter additionally disarm setInterval().
-            Suggested by dg1727 in #3423775.</p>
+            <p>Add new contributors since 3.0.19.</p>
           </li>
         </ul>
       </li>
 
       <li>
-        <p>Documentation improvements:</p>
+        <p>Log message improvements:</p>
 
         <ul>
           <li>
-            <p>Clarify the effect of compiling Privoxy with zlib support.
-            Suggested by dg1727 in #3423782.</p>
+            <p>When stopping to watch a client socket due to pipelining,
+            additionally log the socket number.</p>
           </li>
 
           <li>
-            <p>Point out that the SourceForge messaging system works like a
-            black hole and should thus not be used to contact individual
-            developers.</p>
+            <p>Log the client socket and its condition before closing it.
+            This makes it more obvious that the socket actually gets closed
+            and should help when diagnosing problems like #3464439.</p>
           </li>
 
           <li>
-            <p>Mention some of the problems one can experience when not
-            explicitly configuring an IP addresses as listen address.</p>
+            <p>In case of SOCKS5 failures, do not explicitly log the server's
+            response. It hasn't helped so far and the response can already be
+            logged by enabling "debug 32768" anyway. This reverts v1.81 and
+            the follow-up bug fix v1.84.</p>
           </li>
 
           <li>
-            <p>Explicitly mention that hostnames can be used instead of IP
-            addresses for the listen-address, that only the first address
-            returned will be used and what happens if the address is invalid.
-            Requested by Calestyo in #3302213.</p>
+            <p>Relocate the connection-accepted message from listen_loop() to
+            serve(). This way it's printed by the thread that is actually
+            serving the connection which is nice when grepping for thread ids
+            in log files.</p>
           </li>
         </ul>
       </li>
 
       <li>
-        <p>Log message improvements:</p>
+        <p>Code cleanups:</p>
 
         <ul>
           <li>
-            <p>If only the server connection is kept alive, do not pretend to
-            wait for a new client request.</p>
+            <p>Remove compatibility layer for versions prior to 3.0 since it
+            has been obsolete for more than 10 years now.</p>
+          </li>
+
+          <li>
+            <p>Remove the ijb_isupper() and ijb_tolower() macros from
+            parsers.c since they aren't used in this file.</p>
           </li>
 
           <li>
-            <p>Remove a superfluous log message in forget_connection().</p>
+            <p>Removed the 'Functions declared include:' comment sections
+            since they tend to be incomplete, incorrect and out of date and
+            the benefit seems questionable.</p>
           </li>
 
           <li>
-            <p>In chat(), properly report missing server responses as such
-            instead of calling them empty.</p>
+            <p>Various comment grammar and comprehensibility
+            improvements.</p>
           </li>
 
           <li>
-            <p>In forwarded_connect(), fix a log message nobody should ever
-            see.</p>
+            <p>Remove a pointless fflush() call in chat(). Flushing all
+            streams pretty much all the time for no obvious reason is
+            ridiculous.</p>
           </li>
 
           <li>
-            <p>Fix a log message in socks5_connect(), a failed write
-            operation was logged as failed read operation.</p>
+            <p>Relocate ijb_isupper()'s definition to project.h and get the
+            ijb_tolower() definition from there, too.</p>
           </li>
 
           <li>
-            <p>Let load_one_actions_file() properly complain about a missing
-            '{' at the beginning of the file. Simply stating that a line is
-            invalid isn't particularly helpful.</p>
+            <p>Relocate ijb_isdigit()'s definition to project.h.</p>
           </li>
 
           <li>
-            <p>Do not claim to listen on a socket until Privoxy actually
-            does. Patch submitted by Petr Pisar #3354485</p>
+            <p>Rename ijb_foo macros to privoxy_foo.</p>
           </li>
 
           <li>
-            <p>Prevent a duplicated LOG_LEVEL_CLF message when sending out
-            the "no-server-data" response.</p>
+            <p>Add malloc_or_die() which will allow to simplify code paths
+            where malloc() failures don't need to be handled gracefully.</p>
           </li>
 
           <li>
-            <p>Also log the client socket when dropping a connection.</p>
+            <p>Add strdup_or_die() which will allow to simplify code paths
+            where strdup() failures don't need to be handled gracefully.</p>
           </li>
 
           <li>
-            <p>Include the destination host in the 'Request ... marked for
-            blocking. limit-connect{...} doesn't allow CONNECT ...' message
-            Patch submitted by Saperski in #3296250.</p>
+            <p>Replace strdup() calls with strdup_or_die() calls where it's
+            safe and simplifies the code.</p>
           </li>
 
           <li>
-            <p>Prevent a duplicated log message if none of the resolved IP
-            addresses were reachable.</p>
+            <p>Fix white-space around parentheses.</p>
           </li>
 
           <li>
-            <p>In connect_to(), do not pretend to retry if
-            forwarded-connect-retries is zero or unset.</p>
+            <p>Add missing white-space behind if's and the following
+            parentheses.</p>
           </li>
 
           <li>
-            <p>When a specified user or group can't be found, put the name in
-            single-quotes when logging it.</p>
+            <p>Unwrap a memcpy() call in resolve_hostname_to_ip().</p>
           </li>
 
           <li>
-            <p>In rfc2553_connect_to(), explain getnameinfo() errors
-            better.</p>
+            <p>Declare pcrs_get_delimiter()'s delimiters[] static const.</p>
           </li>
 
           <li>
-            <p>Remove a useless log message in chat().</p>
+            <p>Various optimisations to remove dead code and merge
+            inefficient code structures for improved clarity, performance or
+            code compactness.</p>
           </li>
 
           <li>
-            <p>When retrying to connect, also log the maximum number of
-            connection attempts.</p>
+            <p>Various data type corrections.</p>
           </li>
 
           <li>
-            <p>Rephrase a log message in compile_dynamic_pcrs_job_list().
-            Divide the error code and its meaning with a colon. Call the pcrs
-            job dynamic and not the filter. Filters may contain dynamic and
-            non-dynamic pcrs jobs at the same time. Only mention the name of
-            the filter or tagger, but don't claim it's a filter when it could
-            be a tagger.</p>
+            <p>Change visibility of several code segments when compiling
+            without FEATURE_CONNECTION_KEEP_ALIVE enabled for clarity.</p>
           </li>
 
           <li>
-            <p>In a fatal error message in load_one_actions_file(), cover
-            both URL and TAG patterns.</p>
+            <p>In pcrs_get_delimiter(), do not use delimiters outside the
+            ASCII range. Fixes a clang complaint.</p>
           </li>
 
           <li>
-            <p>In pcrs_strerror(), properly report unknown positive error
-            code values as such. Previously they were handled like 0 (no
-            error).</p>
+            <p>Fix an error message in get_last_url() nobody is supposed to
+            see. Reported by Matthew Fischer in #3507301.</p>
           </li>
 
           <li>
-            <p>In compile_dynamic_pcrs_job_list(), also log the actual error
-            code as pcrs_strerror() doesn't handle all errors reported by
-            pcre.</p>
+            <p>Fix a typo in the no-zlib-support complaint. Patch submitted
+            by Matthew Fischer in #3507304.</p>
           </li>
 
           <li>
-            <p>Don't bother trying to continue chatting if the client didn't
-            ask for it. Reduces log noise a bit.</p>
+            <p>Shorten ssplit()'s prototype by removing the last two
+            arguments. We always want to skip empty fields and ignore leading
+            delimiters, so having parameters for this only complicates the
+            API.</p>
           </li>
 
           <li>
-            <p>Make two fatal error message in load_one_actions_file() more
-            descriptive.</p>
+            <p>Use an enum for the type of the action value.</p>
           </li>
 
           <li>
-            <p>In cgi_send_user_manual(), log when rejecting a file name due
-            to '/' or '..'.</p>
+            <p>Rename action_name's member takes_value to value_type as it
+            isn't used as boolean.</p>
           </li>
 
           <li>
-            <p>In load_file(), log a message if opening a file failed. The
-            CGI error message alone isn't too helpful.</p>
+            <p>Turn family mismatches in match_sockaddr() into fatal
+            errors.</p>
           </li>
 
           <li>
-            <p>In connection_destination_matches(), improve two log messages
-            to help understand why the destinations don't match.</p>
+            <p>Let enlist_unique_header() verify that the caller didn't pass
+            a header containing either \r or \n.</p>
           </li>
 
           <li>
-            <p>Rephrase a log message in serve(). Client request arrival
-            should be differentiated from closed client connections now.</p>
+            <p>Change the hashes used in load_config() to unsigned int.
+            That's what hash_string() actually returns and using a
+            potentially larger type is at best useless.</p>
           </li>
 
           <li>
-            <p>In serve(), log if a client connection isn't reused due to a
-            configuration file change.</p>
+            <p>Use privoxy_tolower() instead of vanilla tolower() with manual
+            casting of the argument.</p>
           </li>
 
           <li>
-            <p>Let mark_server_socket_tainted() always mark the server socket
-            tainted, just don't talk about it in cases where it has no
-            effect. It doesn't change Privoxy's behaviour, but makes
-            understanding the log file easier.</p>
+            <p>Catch ssplit() failures in parse_cgi_parameters().</p>
           </li>
         </ul>
       </li>
 
       <li>
-        <p>configure:</p>
+        <p>Privoxy-Regression-Test:</p>
 
         <ul>
           <li>
-            <p>Added a --disable-ipv6-support switch for platforms where
-            support is detected but doesn't actually work.</p>
+            <p>Add an 'Overwrite condition' directive to skip any matching
+            tests before it. As it has a global scope, using it is more
+            convenient than clowning around with the Ignore directive.</p>
           </li>
 
           <li>
-            <p>Do not check for the existence of strerror() and memmove()
-            twice</p>
+            <p>Log to STDOUT instead of STDERR.</p>
           </li>
 
           <li>
-            <p>Remove a useless test for setpgrp(2). Privoxy doesn't need it
-            and it can cause problems when cross-compiling.</p>
+            <p>Include the Privoxy version in the output.</p>
           </li>
 
           <li>
-            <p>Rename the --disable-acl-files switch to
-            --disable-acl-support. Since about 2001, ACL directives are
-            specified in the standard config file.</p>
+            <p>Various grammar and spelling corrections in documentation and
+            code.</p>
           </li>
 
           <li>
-            <p>Update the URL of the 'Removing outdated PCRE version after
-            the next stable release' posting. The old URL stopped working
-            after one of SF's recent site "optimizations". Reported by Han
-            Liu.</p>
+            <p>Additional tests for range requests with filtering
+            enabled.</p>
           </li>
-        </ul>
-      </li>
-
-      <li>
-        <p>Privoxy-Regression-Test:</p>
 
-        <ul>
           <li>
-            <p>Added --shuffle-tests option to increase the chances of
-            detection race conditions.</p>
+            <p>Tests with mostly invalid range request.</p>
           </li>
 
           <li>
-            <p>Added a --local-test-file option that allows to use
-            Privoxy-Regression-Test without Privoxy.</p>
+            <p>Add a couple of hide-if-modified-since{} tests with different
+            date formats.</p>
           </li>
 
           <li>
-            <p>Added tests for missing socks4 and socks4a forwarders.</p>
+            <p>Cleaned up the format of the regression-tests.action file to
+            match the format of default.action.</p>
           </li>
 
           <li>
-            <p>The --privoxy-address option now works with IPv6 addresses
-            containing brackets, too.</p>
+            <p>Remove the "Copyright" line from print_version(). When using
+            --help, every line of screen space matters and thus shouldn't be
+            wasted on things the user doesn't care about.</p>
           </li>
+        </ul>
+      </li>
 
-          <li>
-            <p>Perform limited sanity checks for parameters that are supposed
-            to have numerical values.</p>
-          </li>
+      <li>
+        <p>Privoxy-Log-Parser:</p>
 
+        <ul>
           <li>
-            <p>Added a --sleep-time option to specify a number of seconds to
-            sleep between tests, defaults to 0.</p>
+            <p>Improve the --statistics performance by skipping sanity checks
+            for input that shouldn't affect the results anyway. Add a
+            --strict-checks option that enables some of the checks again,
+            just in case anybody cares.</p>
           </li>
 
           <li>
-            <p>Disable the range-requests tagger for tests that break if it's
-            enabled.</p>
+            <p>The distribution of client requests per connection is included
+            in the --statistic output.</p>
           </li>
 
           <li>
-            <p>Log messages use the ISO 8601 date format %Y-%m-%d.</p>
+            <p>The --accept-unknown-messages option has been removed and the
+            behavior is now the default.</p>
           </li>
 
           <li>
-            <p>Fix spelling in two error messages.</p>
+            <p>Accept and (mostly) highlight new log messages introduced with
+            Privoxy 3.0.20.</p>
           </li>
+        </ul>
+      </li>
 
-          <li>
-            <p>In the --help output, include a list of supported tests and
-            their default levels.</p>
-          </li>
+      <li>
+        <p>uagen:</p>
 
+        <ul>
           <li>
-            <p>Adjust the tests to properly deal with FEATURE_TOGGLE being
-            disabled.</p>
+            <p>Bump generated Firefox version to 17.</p>
           </li>
         </ul>
       </li>
 
       <li>
-        <p>Privoxy-Log-Parser:</p>
+        <p>GNUmakefile improvements:</p>
 
         <ul>
           <li>
-            <p>Perform limited sanity checks for command line parameters that
-            are supposed to have numerical values.</p>
+            <p>The dok-tidy target no longer taints documents with a
+            tidy-mark</p>
+          </li>
+
+          <li>
+            <p>Change RA_MODE from 0664 to 0644. Suggested by Markus Dittrich
+            in #3505445.</p>
+          </li>
+
+          <li>
+            <p>Remove tidy's clean flag as it changes the scope of
+            attributes. Link-specific colors end up being applied to all
+            text. Reported by Adam Piggott in #3569551.</p>
           </li>
 
           <li>
-            <p>Implement a --unbreak-lines-only option to try to revert MUA
-            breakage.</p>
+            <p>Leave it up to the user whether or not smart tags are
+            inserted.</p>
           </li>
 
           <li>
-            <p>Accept and highlight: Added header: Content-Encoding:
-            deflate</p>
+            <p>Let w3m itself do the line wrapping for the config file. It
+            works better than fmt as it can honour pre tags causing less
+            unintentional line breaks.</p>
           </li>
 
           <li>
-            <p>Accept and highlight: Compressed content from 29258 to 8630
-            bytes.</p>
+            <p>Ditch a pointless '-r' passed to rm to delete files.</p>
           </li>
 
           <li>
-            <p>Accept and highlight: Client request arrived in time on socket
-            21.</p>
+            <p>The config-file target now requires less manual intervention
+            and updates the original config.</p>
           </li>
 
           <li>
-            <p>Highlight: Didn't receive data in time: a.fsdn.com:443</p>
+            <p>Change WDUMP to generate ASCII. Add WDUMP_UTF8 to allow UTF-8
+            in the AUTHORS file so the names are right.</p>
           </li>
 
           <li>
-            <p>Accept log messages with ISO 8601 time stamps, too.</p>
+            <p>Stop pretending that lynx and links are supported for the
+            documentation.</p>
           </li>
         </ul>
       </li>
 
       <li>
-        <p>uagen:</p>
+        <p>configure improvements:</p>
 
         <ul>
           <li>
-            <p>Bump generated Firefox version to 8.0.</p>
+            <p>On Haiku, do not pass -lpthread to the compiler. Haiku's
+            pthreads implementation is contained in its system library,
+            libroot, so no additional library needs to be searched. Patch
+            submitted by Simon South in #3564815.</p>
           </li>
 
           <li>
-            <p>Only randomize the release date if the new
-            --randomize-release-date option is enabled. Firefox versions
-            after 4 use a fixed date string without meaning.</p>
+            <p>Additional Haiku-specific improvements. Disable checks
+            intended for multi-user systems as Haiku is presently
+            single-user. Group Haiku-specific settings in their own section,
+            following the pattern for Solaris, OS/2 and AmigaOS. Add
+            additional library-related settings to remove the need for
+            providing configure with custom LDFLAGS. Submitted by Simon South
+            in #3574538.</p>
           </li>
         </ul>
       </li>
@@ -991,11 +1050,6 @@
           yourself.</p>
         </li>
 
-        <li>
-          <p><tt class="FILENAME">standard.action</tt> has been merged into
-          the <tt class="FILENAME">default.action</tt> file.</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