<!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.21 User Manual" href="index.html">
+ <meta name="GENERATOR" content="Modular DocBook HTML Stylesheet Version 1.79">
+ <link rel="HOME" title="Privoxy 3.0.29 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.21 User Manual</th>
+ <th colspan="3" align="center">Privoxy 3.0.29 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.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>
-
+ <h1 class="SECT1"><a name="WHATSNEW" id="WHATSNEW">3. What's New in this Release</a></h1>
+ <p><span class="APPLICATION">Privoxy 3.0.27</span> stable scales better in multi-user environments and brings a
+ couple of tuning directives. <span class="APPLICATION">Privoxy 3.0.28</span> stable fixes two regressions
+ introduced in 3.0.27.</p>
+ <p>Changes in <span class="APPLICATION">Privoxy 3.0.28</span> stable:</p>
<ul>
<li>
- <p>Bug fixes:</p>
-
- <ul>
- <li>
- <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>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 them 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>
-
- <li>
- <p>General improvements:</p>
-
- <ul>
- <li>
- <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>Added an LSB info block to the generic start script. Based on
- a patch from Natxo Asenjo.</p>
- </li>
-
- <li>
- <p>The max-client-connections default has been changed to 128
- which should be more than enough for most setups.</p>
- </li>
- </ul>
- </li>
-
- <li>
- <p>Action file improvements:</p>
-
- <ul>
- <li>
- <p>Block rover.ebay./ar.*\&adtype= instead of
- "/.*\&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>
-
- <li>
- <p>Filter file improvements:</p>
-
+ <p>Bug fixes for regressions in 3.0.27:</p>
<ul>
<li>
- <p>Added an iframes filter.</p>
- </li>
- </ul>
- </li>
-
- <li>
- <p>Documentation improvements:</p>
-
- <ul>
- <li>
- <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>
+ <p>Fixed misplaced parentheses. Reported by David Binderman.</p>
</li>
-
<li>
- <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>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>Factor generate-config-file out of config-file to make testing
- more convenient.</p>
- </li>
-
- <li>
- <p>The clean target now also takes care of patch leftovers.</p>
+ <p>Changed two regression tests to depend on config directive enable-remote-toggle instead of
+ FEATURE_TOGGLE.</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>
-
+ <p>Changes in <span class="APPLICATION">Privoxy 3.0.27</span> stable:</p>
<ul>
<li>
- <p>Bug fixes:</p>
-
+ <p>General improvements:</p>
<ul>
<li>
- <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>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>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>
+ <p>Add a receive-buffer-size directive which can be used to set the size of the previously statically
+ allocated buffer in handle_established_connection(). Increasing the buffer size increases Privoxy's memory
+ usage but can lower the number of context switches and thereby reduce the CPU usage and potentially
+ increase the throughput. This is mostly relevant for fast network connections and large downloads that
+ don't require filtering. Sponsored by: Robert Klemme</p>
</li>
-
<li>
- <p>The default-server-timeout and socket-timeout directives
- accept 0 as valid value.</p>
+ <p>Add a listen-backlog directive which specifies the backlog value passed to listen(). Sponsored by:
+ Robert Klemme</p>
</li>
-
<li>
- <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>
+ <p>Add an enable-accept-filter directive which allows to toggle accept filter support at run time when
+ compiled with FEATURE_ACCEPT_FILTER support. It makes testing more convenient and now that it's optional we
+ can emit an error message if enabling the accept filter fails. Sponsored by: Robert Klemme</p>
</li>
-
<li>
- <p>Fix the compilation on Windows when configured without IPv6
- support.</p>
+ <p>Add a delay-response{} action. This is useful to tar pit JavaScript requests that are endlessly retried
+ in case of blocks. It can also be used to simulate a slow Internet connection. Sponsored by: Robert
+ Klemme</p>
</li>
-
<li>
- <p>Fix an assertion that could cause debug builds to abort() in
- case of socks5 connection failures with "debug 2" enabled.</p>
+ <p>Add a 'trusted-cgi-referrer' directive. It allows to configure another page or site that can be used to
+ reach sensitive CGI resources. Sponsored by: Robert Klemme</p>
</li>
-
- <li>
- <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>
-
- <li>
- <p>General improvements:</p>
-
- <ul>
<li>
- <p>Significantly improved keep-alive support for both client and
- server connections.</p>
+ <p>Add a --fuzz mode which exposes Privoxy internals to input from files or stdout. Mainly tested with
+ American Fuzzy Lop. For details see: https://www.fabiankeil.de/talks/fuzzing-on-freebsd/ This work was
+ partially funded with donations and done as part of the Privoxy month in 2015.</p>
</li>
-
<li>
- <p>New debug log level 65536 which logs all actions that were
- applied to the request.</p>
+ <p>Consistently use the U(ngreedy) flag in the 'img-reorder' filter.</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>
+ <p>listen_loop(): Reuse a single thread attribute object The object doesn't change and creating a new one
+ for every thread is a waste of (CPU) time. Sponsored by: Robert Klemme</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>
+ <p>Free csp resources in the thread that belongs to the csp instead of the main thread which has enough on
+ its plate already. Sponsored by: Robert Klemme</p>
</li>
-
<li>
- <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>
+ <p>Improve 'socket timeout reached' message. Log the timeout that was triggered and downgrade the log level
+ to LOG_LEVEL_CONNECT to reduce the log noise with common debug settings. The timeout isn't necessary the
+ result of an error and usually merely indicates that Privoxy's socket timeout is lower than the relevant
+ timeouts used by client and server. Sponsored by: Robert Klemme</p>
</li>
-
<li>
- <p>New limit-cookie-lifetime{} action to let cookies expire
- before the end of the session. Suggested by Rick Sykes in
- #1049575.</p>
+ <p>Explicitly taint the server socket in case of CONNECT requests. This doesn't fix any known problems, but
+ makes some log messages less confusing.</p>
</li>
-
<li>
- <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>
+ <p>Let write_pid_file() terminate if the pid file can't be opened. Logging the issue at info level is
+ unlikely to help.</p>
</li>
-
<li>
- <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>
+ <p>log_error(): Reduce the mutex-protected area by not using a heap-allocated buffer that is shared between
+ all threads. This increases performance and reduces the latency with verbose debug settings and multiple
+ concurrent connections. Sponsored by: Robert Klemme</p>
</li>
-
<li>
- <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>
+ <p>Let zalloc() use calloc() if it's available. In some situations using calloc() can be faster than
+ malloc() + memset() and it should never be slower. In the real world the impact of this change is not
+ expected to be noticeable. Sponsored by: Robert Klemme</p>
</li>
-
<li>
- <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>
+ <p>Never use select() when poll() is available. On most platforms select() is limited by FD_SETSIZE while
+ poll() is not. This was a scaling issue for multi-user setups. Using poll() has no downside other than the
+ usual risk that code modifications may introduce new bugs that have yet to be found and fixed. At least in
+ theory this commit could also reduce the latency when there are lots of connections and select() would use
+ "bit fields in arrays of integers" to store file descriptors. Another side effect is that Privoxy no longer
+ has to stop monitoring the client sockets when pipelined requests are waiting but can't be read yet. This
+ code keeps the select()-based code behind ifdefs for now but hopefully it can be removed soonish to make
+ the code more readable. Sponsored by: Robert Klemme</p>
</li>
-
<li>
- <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>
+ <p>Add a 'reproducible-tarball-dist' target. It's currently separate from the "tarball-dist" target because
+ it requires a tar implementation with mtree spec support. It's far from being perfect and does not enforce
+ a reproducible mode, but it's better than nothing.</p>
</li>
-
<li>
- <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>
+ <p>Use arc4random() if it's available. While Privoxy doesn't need high quality pseudo-random numbers
+ there's no reason not to use them when we can and this silences a warning emitted by code checkers that
+ can't tell whether or not the quality matters.</p>
</li>
-
<li>
- <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>
+ <p>Show the FEATURE_EXTERNAL_FILTERS status on the status page. Better late than never. Previously a couple
+ of tests weren't executed as Privoxy-Regression-Test couldn't detect that the FEATURE_EXTERNAL_FILTERS
+ dependency was satisfied.</p>
</li>
-
<li>
- <p>Set the socket option SO_LINGER for the client socket.</p>
+ <p>Ditch FEATURE_IMAGE_DETECT_MSIE. It's an obsolete workaround we inherited from Junkbuster and was
+ already disabled by default. Users that feel the urge to work around issues with image requests coming from
+ an Internet Explorer version from more than 15 years ago can still do this using tags.</p>
</li>
-
<li>
- <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>
+ <p>Consistently use strdup_or_die() instead of strdup() in cases where allocation failures aren't expected.
+ Using strdup_or_die() allows to remove a couple of explicit error checks which slightly reduces the size of
+ the binary.</p>
</li>
-
<li>
- <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>
+ <p>Insert a refresh tag into the /client-tags CGI page when serving it while a client-specific tag is
+ temporarily enabled. This makes it less likely that the user ends up looking at tag state that is out of
+ date.</p>
</li>
-
<li>
- <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>
+ <p>Use absolute URLs in the client-tag forms. It's more consistent with the rest of the CGI page URLs and
+ makes it more convenient to copy the forms to external pages.</p>
</li>
-
<li>
- <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>
+ <p>cgi_error_disabled(): Use status code 403 and an appropriate response line</p>
</li>
-
<li>
- <p>Allow closing curly braces as part of action values as long as
- they are escaped.</p>
+ <p>Use a dedicated CGI handler to deal with tag-toggle requests As a result the /client-tags page is now
+ safe to reach without trusted Referer header which makes bookmarking or linking to it more convenient.
+ Finally, refreshing the /client-tags page to show the current state can no longer unintentionally repeat
+ the previous toggle request.</p>
</li>
-
<li>
- <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>
+ <p>Don't add a "Connection" header for CONNECT requests. Explicitly sending "Connection: close" is not
+ necessary and apparently it causes problems with some forwarding proxies that will close the connection
+ prematurely. Reported by Marc Thomas.</p>
</li>
-
<li>
- <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>Decrease the chances of parse failures after requests with
- unsupported methods were sent to the CGI interface.</p>
+ <p>Fix compiler warnings.</p>
</li>
</ul>
</li>
-
<li>
- <p>Action file improvements:</p>
-
+ <p>Bug fixes:</p>
<ul>
<li>
- <p>Remove the comment that indicated that updated default.action
- versions are released on their own.</p>
- </li>
-
- <li>
- <p>Block 'optimize.indieclick.com/' and
- 'optimized-by.rubiconproject.com/'</p>
- </li>
-
- <li>
- <p>Unblock 'adjamblog.wordpress.com/' and
- 'adjamblog.files.wordpress.com/'. Reported by Ryan Farmer in
- #3496116.</p>
- </li>
-
- <li>
- <p>Unblock '/.*Bugtracker'. Reported by pwhk in #3522341.</p>
- </li>
-
- <li>
- <p>Add test URLs for '.freebsd.org' and '.watson.org'.</p>
- </li>
-
- <li>
- <p>Unblock '.urbandictionary.com/popular'.</p>
- </li>
-
- <li>
- <p>Block '.adnxs.com/'.</p>
- </li>
-
- <li>
- <p>Block 'farm.plista.com/widgetdata.php'.</p>
- </li>
-
- <li>
- <p>Block 'rotation.linuxnewmedia.com/'.</p>
- </li>
-
- <li>
- <p>Block 'reklamy.sfd.pl/'. Reported by kacperdominik in
- #3399948.</p>
- </li>
-
- <li>
- <p>Block 'g.adspeed.net/'.</p>
- </li>
-
- <li>
- <p>Unblock 'websupport.wdc.com/'. Reported by Adam Piggot in
- #3577851.</p>
- </li>
-
- <li>
- <p>Block '/openx/www/delivery/'.</p>
- </li>
-
- <li>
- <p>Disable fast-redirects for '.googleapis.com/'.</p>
- </li>
-
- <li>
- <p>Block 'imp.double.net/'. Reported by David Bo in #3070411.</p>
- </li>
-
- <li>
- <p>Block 'gm-link.com/' which is used for email tracking.
- Reported by David Bo in #1812733.</p>
- </li>
-
- <li>
- <p>Verify that requests to "bwp." are blocked. URL taken from
- #1736879 submitted by Francois Marier.</p>
- </li>
-
- <li>
- <p>Block '/.*bannerid='. Reported by Adam Piggott in
- #2975779.</p>
- </li>
-
- <li>
- <p>Block 'cltomedia.info/delivery/' and '.adexprt.com/'.
- Anonymously reported in #2965254.</p>
- </li>
-
- <li>
- <p>Block 'de17a.com/'. Reported by David Bo in #3061472.</p>
+ <p>rfc2553_connect_to(): Properly detect and log when poll() reached the time out. Previously this was
+ logged as: Could not connect to [...]: No error: 0. which isn't very helpful. Sponsored by: Robert
+ Klemme</p>
</li>
-
<li>
- <p>Block 'oskar.tradera.com/'. Reported by David Bo in
- #3060596.</p>
+ <p>add_tag_for_client(): Set time_to_live properly. Previously the time_to_live was always set for the
+ first tag. Attempts to temporarily enable a tag would result in enabling it permanently unless no tag was
+ enabled already.</p>
</li>
-
<li>
- <p>Block '/scripts/webtrends\.js'. Reported by johnd16 in
- #3002729.</p>
+ <p>Revert r1.165 which didn't perform as advertised. While the idea was to use "https:// when creating
+ links for the user manual on the website", the actual effect was to use "https://" when Privoxy was
+ supposed to serve the user manual itself. Reported by Yossi Zahn on Privoxy-devel@.</p>
</li>
-
<li>
- <p>Block requests for 'pool.*.adhese.com/'. Reported by johnd16
- in #3002716.</p>
+ <p>socks5_connect(): Fail in case of unsupported address types. Previously they would not be detected right
+ away and Privoxy would fail later on with an error message that didn't make it obvious that the problem was
+ socks-related. So far, no such problems have actually been reported.</p>
</li>
-
<li>
- <p>Update path pattern for Coremetrics and add tests. Pattern and
- URLs submitted by Adam Piggott #3168443.</p>
- </li>
-
- <li>
- <p>Enable +fast-redirects{check-decoded-url} for 'tr.anp.se/'.
- Reported by David Bo in #3268832.</p>
- </li>
-
- <li>
- <p>Unblock '.conrad.se/newsletter/banners/'. Reported by David Bo
- in #3413824.</p>
- </li>
-
- <li>
- <p>Block '.tynt.com/'. Reported by Dan Stahlke in #3421767.</p>
- </li>
-
- <li>
- <p>Unblock '.bbci.co.uk/radio/'. Reported by Adam Piggott in
- #3569603.</p>
- </li>
-
- <li>
- <p>Block requests to 'service.maxymiser.net/'. Reported by
- johnd16 in #3118401 (with a previous URL).</p>
- </li>
-
- <li>
- <p>Disable fast-redirects for Google's "let's pretend your
- computer is infected" page.</p>
- </li>
-
- <li>
- <p>Unblock '/.*download' to resolve actionsfile feedback
- #3498129. Submitted by Steven Kolins (soundcloud.com not
- working).</p>
- </li>
-
- <li>
- <p>Unblock '.wlxrs.com/' which is required by hotmail.com. Fixes
- #3413827 submitted by David Bo.</p>
- </li>
-
- <li>
- <p>Add two unblock patterns for popup radio and TV players.
- Submitted by Adam Piggott in #3596089.</p>
- </li>
- </ul>
- </li>
-
- <li>
- <p>Filter file improvements & bug fixes:</p>
-
- <ul>
- <li>
- <p>Add a referer tagger.</p>
- </li>
-
- <li>
- <p>Reduce the likelihood that the google filter messes up
- HTML-generating JavaScript. Reported by Zeno Kugy in
- #3520260.</p>
+ <p>socks5_connect(): Properly deal with socks replies that contain IPv6 addresses. Previously parts of the
+ reply were left unread and later on treated as invalid HTTP response data. Fixes #904 reported by Danny
+ Goossen who also provided the initial version of this patch.</p>
</li>
</ul>
</li>
-
<li>
- <p>Documentation improvements:</p>
-
+ <p>Action file improvements:</p>
<ul>
<li>
- <p>Revised all OS X sections due to new packaging module
- (OSXPackageBuilder).</p>
- </li>
-
- <li>
- <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>Update 'Signals' section, the only explicitly handled signals
- are SIGINT, SIGTERM and SIGHUP.</p>
- </li>
-
- <li>
- <p>Add Haiku to the list of operating systems on which Privoxy is
- known to run.</p>
- </li>
-
- <li>
- <p>Add DragonFly to the list of BSDs on which Privoxy is known to
- run.</p>
- </li>
-
- <li>
- <p>Removed references to redhat-specific documentation set since
- it no longer exists.</p>
- </li>
-
- <li>
- <p>Removed references to building PDFs since we no longer do
- so.</p>
- </li>
-
- <li>
- <p>Multiple listen-address directives are supported since 3.0.18,
- correct the documentation to say so.</p>
- </li>
-
- <li>
- <p>Remove bogus section about long and short being preferable to
- int.</p>
+ <p>Unblock 'msdn.microsoft.com/'. It (presumably) isn't used to serve the kind of ads Privoxy should block
+ by default but happens to serve lots of pages with URLs that are likely to result in false positives.
+ Reported by bugreporter1694 in AF#939.</p>
</li>
-
<li>
- <p>Corrected some Internet JunkBuster references to Privoxy.</p>
+ <p>Disable gif deanimation for requests tagged with CSS-REQUEST. The action will ignore content that isn't
+ considered text anyway and explicitly disabling it makes this more obvious if "action" debugging (debug
+ 65536) is enabled while "gif deanimation" debugging (debug 256) isn't.</p>
</li>
-
<li>
- <p>Removed references to www.junkbusters.com since it is no
- longer maintained. Reported by Angelina Matson.</p>
+ <p>Explicitly disable HTML filters for requests with CSS-REQUEST tag. The filters are unlikely to break CSS
+ files but executing them without (intentionally) getting any hits is a waste of cpu time and makes the log
+ more noisy when running with "debug 64".</p>
</li>
-
<li>
- <p>Various grammar and spelling corrections</p>
+ <p>Unblock 'adventofcode.com/'. Reported by Clint Adams in Debian bug #848211. Fixes Roland's AF#937.</p>
</li>
-
<li>
- <p>Add a client-header-tagger{} example for disabling filtering
- for range requests.</p>
+ <p>Unblock 'adlibris.com'. Reported by Wyrex in #935</p>
</li>
-
<li>
- <p>Correct a URL in the "Privoxy with Tor" FAQ.</p>
+ <p>Unblock .golang.org/</p>
</li>
-
<li>
- <p>Spell 'refresh-tags' correctly. Reported by Don in
- #3571927.</p>
- </li>
-
- <li>
- <p>Sort manpage options alphabetically.</p>
- </li>
-
- <li>
- <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>Add new contributors since 3.0.19.</p>
+ <p>Add fast-redirects exception for '.youtube.com/.*origin=http'</p>
</li>
</ul>
</li>
-
<li>
- <p>Log message improvements:</p>
-
+ <p>Privoxy-Log-Parser:</p>
<ul>
<li>
- <p>When stopping to watch a client socket due to pipelining,
- additionally log the socket number.</p>
+ <p>Don't gather host and resource statistics if they aren't requested. While the performance impact seems
+ negligible this significantly reduces the memory usage if there are lots of requests.</p>
</li>
-
<li>
- <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>
+ <p>Bump version as the behaviour (slightly) changed.</p>
</li>
-
<li>
- <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>
+ <p>Count connection failures as well in statistics mode. Sponsored by: Robert Klemme</p>
</li>
-
<li>
- <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>
+ <p>Count connection timeouts as well in statistics mode. Sponsored by: Robert Klemme</p>
+ </li>
+ <li>
+ <p>Fix an 'uninitialized value' warning when generating statistics for a log file without response headers.
+ While privoxy-log-parser was supposed to detect this already, the check was flawed and the message the user
+ didn't see was somewhat confusing anyway. Now the message is less confusing, more helpful and actually
+ printed. Reported by: Robert Klemme</p>
</li>
</ul>
</li>
-
<li>
- <p>Code cleanups:</p>
-
+ <p>Documentation improvements:</p>
<ul>
<li>
- <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>Removed the 'Functions declared include:' comment sections
- since they tend to be incomplete, incorrect and out of date and
- the benefit seems questionable.</p>
+ <p>Refer to the git sources instead of CVS.</p>
</li>
-
<li>
- <p>Various comment grammar and comprehensibility
- improvements.</p>
+ <p>Use GNU/Linux when referring to the OS instead of the kernel.</p>
</li>
-
<li>
- <p>Remove a pointless fflush() call in chat(). Flushing all
- streams pretty much all the time for no obvious reason is
- ridiculous.</p>
+ <p>Add FAQ entry for what to do if editing the config file is access denied.</p>
</li>
-
<li>
- <p>Relocate ijb_isupper()'s definition to project.h and get the
- ijb_tolower() definition from there, too.</p>
+ <p>Add brief HTTP/2 FAQ.</p>
</li>
-
<li>
- <p>Relocate ijb_isdigit()'s definition to project.h.</p>
+ <p>Add a small fuzzing section to the developer documentation.</p>
</li>
-
<li>
- <p>Rename ijb_foo macros to privoxy_foo.</p>
+ <p>Add a client-header-tagger{client-ip-address} example.</p>
</li>
-
<li>
- <p>Add malloc_or_die() which will allow to simplify code paths
- where malloc() failures don't need to be handled gracefully.</p>
+ <p>Stop suggesting that Privoxy is an anonymizing proxy. The term could lead to Privoxy users
+ overestimating what it can do on its own (without Tor).</p>
</li>
-
<li>
- <p>Add strdup_or_die() which will allow to simplify code paths
- where strdup() failures don't need to be handled gracefully.</p>
+ <p>Make it more obvious that SPI accepts Paypal, too. Currently most donations are made through the Paypal
+ account managed by Zwiebelfreunde e.V. and a more even distribution would be useful.</p>
</li>
-
<li>
- <p>Replace strdup() calls with strdup_or_die() calls where it's
- safe and simplifies the code.</p>
+ <p>Suggest to log applying actions as well when reproducing problems.</p>
</li>
-
<li>
- <p>Fix white-space around parentheses.</p>
+ <p>Explicitly mention that Privoxy binaries are built by individuals on their own systems. Buyer
+ beware!</p>
</li>
-
<li>
- <p>Add missing white-space behind if's and the following
- parentheses.</p>
+ <p>Mention the release feed on the homepage.</p>
</li>
-
<li>
- <p>Unwrap a memcpy() call in resolve_hostname_to_ip().</p>
- </li>
-
- <li>
- <p>Declare pcrs_get_delimiter()'s delimiters[] static const.</p>
- </li>
-
- <li>
- <p>Various optimisations to remove dead code and merge
- inefficient code structures for improved clarity, performance or
- code compactness.</p>
- </li>
-
- <li>
- <p>Various data type corrections.</p>
- </li>
-
- <li>
- <p>Change visibility of several code segments when compiling
- without FEATURE_CONNECTION_KEEP_ALIVE enabled for clarity.</p>
- </li>
-
- <li>
- <p>In pcrs_get_delimiter(), do not use delimiters outside the
- ASCII range. Fixes a clang complaint.</p>
- </li>
-
- <li>
- <p>Fix an error message in get_last_url() nobody is supposed to
- see. Reported by Matthew Fischer in #3507301.</p>
- </li>
-
- <li>
- <p>Fix a typo in the no-zlib-support complaint. Patch submitted
- by Matthew Fischer in #3507304.</p>
- </li>
-
- <li>
- <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>Use an enum for the type of the action value.</p>
- </li>
-
- <li>
- <p>Rename action_name's member takes_value to value_type as it
- isn't used as boolean.</p>
- </li>
-
- <li>
- <p>Turn family mismatches in match_sockaddr() into fatal
- errors.</p>
- </li>
-
- <li>
- <p>Let enlist_unique_header() verify that the caller didn't pass
- a header containing either \r or \n.</p>
- </li>
-
- <li>
- <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>Use privoxy_tolower() instead of vanilla tolower() with manual
- casting of the argument.</p>
- </li>
-
- <li>
- <p>Catch ssplit() failures in parse_cgi_parameters().</p>
+ <p>Remove a mysterious comment with a GNU FDL link as it isn't useful and could confuse license scanners.
+ In May 2002 it was briefly claimed that "this document" was covered by the GNU FDL. The commit message
+ (r1.5) doesn't explain the motivation or whether all copyright holders were actually asked and agreed to
+ the declared license change. It's thus hard to tell whether or not the license change was legit, but
+ luckily two days later the "doc license" was "put" "back to GPL" anyway (r1.6). At the same time the
+ offending comment with a link to the FDL (not the GPL) was added for no obvious reason. Now it's gone
+ again.</p>
</li>
</ul>
</li>
-
<li>
- <p>Privoxy-Regression-Test:</p>
-
+ <p>Regression tests:</p>
<ul>
<li>
- <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>Log to STDOUT instead of STDERR.</p>
- </li>
-
- <li>
- <p>Include the Privoxy version in the output.</p>
- </li>
-
- <li>
- <p>Various grammar and spelling corrections in documentation and
- code.</p>
- </li>
-
- <li>
- <p>Additional tests for range requests with filtering
- enabled.</p>
- </li>
-
- <li>
- <p>Tests with mostly invalid range request.</p>
- </li>
-
- <li>
- <p>Add a couple of hide-if-modified-since{} tests with different
- date formats.</p>
- </li>
-
- <li>
- <p>Cleaned up the format of the regression-tests.action file to
- match the format of default.action.</p>
+ <p>Bump for-privoxy-version to 3.0.27 as we now rely on untrusted CGI request being rejected with status
+ code 403 (instead of 200).</p>
</li>
-
<li>
- <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>
+ <p>Update test for /send-stylesheet and add another one</p>
</li>
</ul>
</li>
-
<li>
- <p>Privoxy-Log-Parser:</p>
-
+ <p>Templates:</p>
<ul>
<li>
- <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>The distribution of client requests per connection is included
- in the --statistic output.</p>
+ <p>Consistently use https:// when linking to the Privoxy website.</p>
</li>
-
<li>
- <p>The --accept-unknown-messages option has been removed and the
- behavior is now the default.</p>
+ <p>Remove SourceForge references in Copyright header.</p>
</li>
-
<li>
- <p>Accept and (mostly) highlight new log messages introduced with
- Privoxy 3.0.20.</p>
+ <p>Remove a couple of SourceForge references in a comment. While at it, fix the grammar.</p>
</li>
- </ul>
- </li>
-
- <li>
- <p>uagen:</p>
-
- <ul>
<li>
- <p>Bump generated Firefox version to 17.</p>
+ <p>Move the site-specific documentation block before the generic one. While most Privoxy installations
+ don't have a site-specific documentation block, in cases were it exists it's likely to be more relevant
+ than the generic one. Showing it first makes it less likely that users stop reading before they reach it,
+ especially on pages that don't fit on the screen.</p>
</li>
</ul>
</li>
-
<li>
- <p>GNUmakefile improvements:</p>
-
+ <p>Build system improvements:</p>
<ul>
<li>
- <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>
+ <p>Prefer openjade to jade. On some systems Jade produces HTML with unescaped ampersands in URLs.</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>
+ <p>Prefer OpenSP to SP to be consistent.</p>
</li>
-
<li>
- <p>Leave it up to the user whether or not smart tags are
- inserted.</p>
+ <p>Have Docbook generated HTML files be straight ASCII. Dealing with a mixture of ISO-8859 and UTF-8 files
+ is problematic.</p>
</li>
-
<li>
- <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>
+ <p>Echo the filename to stderr for 'make dok-tidy'. Make it a bit easier to find errors in docbook
+ generated HTML.</p>
</li>
-
<li>
- <p>Ditch a pointless '-r' passed to rm to delete files.</p>
+ <p>Warn when still using select().</p>
</li>
-
<li>
- <p>The config-file target now requires less manual intervention
- and updates the original config.</p>
+ <p>Warn when compiling without calloc().</p>
</li>
-
<li>
- <p>Change WDUMP to generate ASCII. Add WDUMP_UTF8 to allow UTF-8
- in the AUTHORS file so the names are right.</p>
+ <p>Make it more obvious that the --with-fdsetsize configure switch is pointless if poll() is available.</p>
</li>
-
<li>
- <p>Stop pretending that lynx and links are supported for the
- documentation.</p>
+ <p>Remove support for AmigaOS.</p>
</li>
- </ul>
- </li>
-
- <li>
- <p>configure improvements:</p>
-
- <ul>
<li>
- <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>
+ <p>Update windows build system to use supported software. The cygwin gcc -mno-cygwin option is no longer
+ supported, so convert the windows build system to use the cygwin cross-compiler to build "native" code.</p>
</li>
-
<li>
- <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>
+ <p>Add --enable-static-linking option for configure does the same thing as LDFLAGS=-static; ./configure but
+ nicer than mixing evars and configure options.</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>