Current Privoxy Team:
Fabian Keil, lead developer
- David Schmidt, developer
-
+ David Schmidt
Hal Burgiss
Lee Rian
Roland Rosenfeld
alphabetical order):
Ken Arromdee
+ Natxo Asenjo
Devin Bayer
Havard Berland
David Bo
Derek Jennings
Andrew Jones
Julien Joubert
+ Ralf Jungblut
Petr Kadlec
Steven Kolins
Zeno Kugy
When building from a source tarball, first unpack the source:
- tar xzvf privoxy-3.0.20-beta-src.tar.gz
- cd privoxy-3.0.20-beta
+ tar xzvf privoxy-3.0.21-stable-src.tar.gz
+ cd privoxy-3.0.21-stable
For retrieving the current CVS sources, you'll need a CVS client installed.
Note that sources from CVS are typically development quality, and may not be
*
*********************************************************************/
-This README is included with the development version of Privoxy 3.0.20. See
-http://www.privoxy.org/ for more information. The current code maturity level
-is "beta", but seems stable to us :).
+This README is included with Privoxy 3.0.21. See http://www.privoxy.org/ for
+more information. The current code maturity level is "stable".
-------------------------------------------------------------------------------
The actions list can be configured via the web interface accessed via http://
p.p/, as well other options.
-All configuration files are subject to unannounced changes during the
-development process.
-
-------------------------------------------------------------------------------
5. DOCUMENTATION
-There should be documentation in the 'doc' subdirectory, but it may not be
-completed at this point. In particular, see the User Manual there, the FAQ, and
-those interested in Privoxy development, should look at developer-manual.
+There should be documentation in the 'doc' subdirectory. In particular, see the
+User Manual there, the FAQ, and those interested in Privoxy development, should
+look at developer-manual.
-The most up to date source of information on the current development version,
-may still be either comments in the source code, or the included configuration
-files. The source and configuration files are all well commented. The main
-configuration files are: 'config', 'default.action', and 'default.filter' in
-the top-level source directory.
+The source and configuration files are all well commented. The main
+configuration files are: 'config', 'default.action', and 'default.filter'.
Included documentation may vary according to platform and packager. All
documentation is posted on http://www.privoxy.org, in case you don't have it,
We value your feedback. In fact, we rely on it to improve Privoxy and its
configuration. However, please note the following hints, so we can provide you
-with the best support:
+with the best support.
-------------------------------------------------------------------------------
-6.1. Get Support
+6.1. Please provide sufficient information
-For casual users, our support forum at SourceForge is probably best suited:
-http://sourceforge.net/tracker/?group_id=11118&atid=211118
+A lot of support requests don't contain enough information and can't be solved
+without a lot of back and forth which causes unnecessary delays. Reading this
+section should help to prevent that.
-All users are of course welcome to discuss their issues on the users mailing
-list, where the developers also hang around.
+Before contacting us to report a problem, please try to verify that it is a
+Privoxy problem, and not a browser or site problem or documented behaviour that
+just happens to be different than what you expected. If unsure, try toggling
+off Privoxy, and see if the problem persists.
-Please don't sent private support requests to individual Privoxy developers,
-either use the mailing lists or the support trackers.
+If you are using your own custom configuration, please try the default
+configuration to see if the problem is configuration related. If you're having
+problems with a feature that is disabled by default, please ask around on the
+mailing list if others can reproduce the problem.
-If you have to contact a Privoxy developer directly for other reasons, please
-send a real mail and do not bother with SourceForge's messaging system. Answers
-to SourceForge messages are usually bounced by SourceForge's mail server in
-which case the developer wasted time writing a response you don't get. From
-your point of view it will look like your message has been completely ignored,
-so this is frustrating for all parties involved.
+If you aren't using the latest Privoxy version, the problem may have been found
+and fixed in the meantime. We would appreciate if you could take the time to
+upgrade to the latest version and verify that the problem still exists.
-Note that the Privoxy mailing lists are moderated. Posts from unsubscribed
-addresses have to be accepted manually by a moderator. This may cause a delay
-of several days and if you use a subject that doesn't clearly mention Privoxy
-or one of its features, your message may be accidentally discarded as spam.
+Please be sure to provide the following information when reporting problems or
+requesting support:
-If you aren't subscribed, you should therefore spend a few seconds to come up
-with a proper subject. Additionally you should make it clear that you want to
-get CC'd. Otherwise some responses will be directed to the mailing list only,
-and you won't see them.
+ * The exact Privoxy version you are using.
--------------------------------------------------------------------------------
-
-6.2. Reporting Problems
-
-"Problems" for our purposes, come in two forms:
-
- * Configuration issues, such as ads that slip through, or sites that don't
- function properly due to one Privoxy "action" or another being turned "on".
-
- * "Bugs" in the programming code that makes up Privoxy, such as that might
- cause a crash.
-
--------------------------------------------------------------------------------
-
-6.2.1. Reporting Ads or Other Configuration Problems
-
-Please send feedback on ads that slipped through, innocent images that were
-blocked, sites that don't work properly, and other configuration related
-problem of default.action file, to http://sourceforge.net/tracker/?group_id=
-11118&atid=460288, the Actions File Tracker.
-
-New, improved default.action files may occasionally be made available based on
-your feedback. These will be announced on the ijbswa-announce list and
-available from our the files section of our project page.
-
--------------------------------------------------------------------------------
-
-6.2.2. Reporting Bugs
-
-Please report all bugs through our bug tracker: http://sourceforge.net/tracker
-/?group_id=11118&atid=111118.
-
-Before doing so, please make sure that the bug has not already been submitted
-and observe the additional hints at the top of the submit form. If already
-submitted, please feel free to add any info to the original report that might
-help to solve the issue.
-
-Please try to verify that it is a Privoxy bug, and not a browser or site bug or
-documented behaviour that just happens to be different than what you expected.
-If unsure, try toggling off Privoxy, and see if the problem persists.
-
-If you are using your own custom configuration, please try the stock configs to
-see if the problem is configuration related. If you're having problems with a
-feature that is disabled by default, please ask around on the mailing list if
-others can reproduce the problem.
-
-If you aren't using the latest Privoxy version, the bug may have been found and
-fixed in the meantime. We would appreciate if you could take the time to
-upgrade to the latest version (or even the latest CVS snapshot) and verify that
-your bug still exists.
-
-Please be sure to provide the following information:
-
- * The exact Privoxy version you are using (if you got the source from CVS,
- please also provide the source code revisions as shown in http://
- config.privoxy.org/show-version).
-
- * The operating system and versions you run Privoxy on, (e.g. Windows XP
- SP2), if you are using a Unix flavor, sending the output of "uname -a"
- should do, in case of GNU/Linux, please also name the distribution.
+ * The operating system and versions you run Privoxy on, e.g. Windows XP SP2.
* The name, platform, and version of the browser you were using (e.g.
Internet Explorer v5.5 for Mac).
* Whether your version of Privoxy is one supplied by the Privoxy developers
via SourceForge, or if you got your copy somewhere else.
- * Whether you are using Privoxy in tandem with another proxy such as Tor. If
+ * Whether you are using Privoxy together with another proxy such as Tor. If
so, please temporary disable the other proxy to see if the symptoms change.
* Whether you are using a personal firewall product. If so, does Privoxy work
* Any other pertinent information to help identify the problem such as config
or log file excerpts (yes, you should have log file entries for each action
taken). To get a meaningful logfile, please make sure that the logfile
- directive is being used and the following debug options are enabled:
+ directive is being used and the following debug options are enabled (all of
+ them):
debug 1 # Log the destination for each request Privoxy let through. See also debug 1024.
debug 2 # show each connection status
debug 32768 # log all data read from the network
+ It's easy for us to ignore log messages that aren't relevant but missing
+ log messages may make it impossible to investigate a problem. If you aren't
+ sure which of the debug directives are relevant, please just enable all of
+ them and let us worry about it.
+
Note that Privoxy log files may contain sensitive information so please
don't submit any logfiles you didn't read first. You can mask sensitive
information as long as it's clear that you removed something.
-------------------------------------------------------------------------------
-6.3. Request New Features
+6.2. Get Support
+
+For casual users, our support forum at SourceForge is probably best suited:
+http://sourceforge.net/tracker/?group_id=11118&atid=211118
+
+All users are of course welcome to discuss their issues on the users mailing
+list, where the developers also hang around.
+
+Please don't send private support requests to individual Privoxy developers,
+either use the mailing lists or the support trackers.
+
+If you have to contact a Privoxy developer directly for other reasons, please
+send a real mail and do not bother with SourceForge's messaging system. Answers
+to SourceForge messages are usually bounced by SourceForge's mail server in
+which case the developer wasted time writing a response you don't get. From
+your point of view it will look like your message has been completely ignored,
+so this is frustrating for all parties involved.
+
+Note that the Privoxy mailing lists are moderated. Posts from unsubscribed
+addresses have to be accepted manually by a moderator. This may cause a delay
+of several days and if you use a subject that doesn't clearly mention Privoxy
+or one of its features, your message may be accidentally discarded as spam.
+
+If you aren't subscribed, you should therefore spend a few seconds to come up
+with a proper subject. Additionally you should make it clear that you want to
+get CC'd. Otherwise some responses will be directed to the mailing list only,
+and you won't see them.
+
+-------------------------------------------------------------------------------
+
+6.3. Reporting Problems
+
+"Problems" for our purposes, come in two forms:
+
+ * Configuration issues, such as ads that slip through, or sites that don't
+ function properly due to one Privoxy "action" or another being turned "on".
+
+ * "Bugs" in the programming code that makes up Privoxy, such as that might
+ cause a crash.
+
+-------------------------------------------------------------------------------
+
+6.3.1. Reporting Ads or Other Configuration Problems
+
+Please send feedback on ads that slipped through, innocent images that were
+blocked, sites that don't work properly, and other configuration related
+problem of default.action file, to http://sourceforge.net/tracker/?group_id=
+11118&atid=460288, the Actions File Tracker.
+
+New, improved default.action files may occasionally be made available based on
+your feedback. These will be announced on the ijbswa-announce list and
+available from our the files section of our project page.
+
+-------------------------------------------------------------------------------
+
+6.3.2. Reporting Bugs
+
+Please report all bugs through our bug tracker: http://sourceforge.net/tracker
+/?group_id=11118&atid=111118.
+
+Before doing so, please make sure that the bug has not already been submitted
+and observe the additional hints at the top of the submit form. If already
+submitted, please feel free to add any info to the original report that might
+help to solve the issue.
+
+-------------------------------------------------------------------------------
+
+6.4. Request New Features
You are welcome to submit ideas on new features or other proposals for
improvement through our feature request tracker at http://sourceforge.net/
-------------------------------------------------------------------------------
-6.4. Mailing Lists
+6.5. Mailing Lists
If you prefer to communicate through email, instead of using a web interface,
feel free to use one of the mailing lists. To discuss issues that haven't been
<p class="PUBDATE"><sub><a href=
"http://www.privoxy.org/user-manual/copyright.html" target=
- "_top">Copyright</a> © 2001-201
2 by <a href=
+ "_top">Copyright</a> © 2001-201
3 by <a href=
"http://www.privoxy.org/" target="_top">Privoxy
Developers</a></sub><br></p>
- <p class="PUBDATE">$Id: developer-manual.sgml,v 2.53 2013/02/26
- 15:09:35 fabiankeil Exp $<br></p>
+ <p class="PUBDATE">$Id: developer-manual.sgml,v 2.57 2013/03/01
+ 17:44:24 fabiankeil Exp $<br></p>
<div>
<div class="ABSTRACT">
target="_top">users mailing list</a>, where the developers also hang
around.</p>
- <p>Please don't sent private support requests to individual Privoxy
+ <p>Please don't send private support requests to individual Privoxy
developers, either use the mailing lists or the support trackers.</p>
<p>If you have to contact a Privoxy developer directly for other
2001-2011 by <a href="http://www.privoxy.org/" target="_top">Privoxy
Developers</a></sub><br></p>
- <p class="PUBDATE">$Id: faq.sgml,v 2.91 2013/02/26 15:09:35 fabiankeil
+ <p class="PUBDATE">$Id: faq.sgml,v 2.92 2013/03/01 17:44:24 fabiankeil
Exp $<br></p>
<div>
<body>
<h1>PRIVOXY</h1>Section: (1)<br>
- Updated: 06 Januar 2013<br>
+ Updated: 02 March 2013<br>
<a href="#index">Index</a>
<hr>
<a name="lbAB" id="lbAB"> </a>
<h2>NOTES</h2>
- <p>This is a beta version of <b>Privoxy</b>. Not all features are well
- tested.</p>
-
<p>Please see the <i>User Manual</i> on how to contact the developers, for
feature requests, reporting problems, and other questions. <a name="lbAK"
id="lbAK"> </a></p>
Shortcut: <a href="http://p.p/">http://p.p/</a></p>
<p><a href=
- "https://sourceforge.net/tracker/?group_id=11118&atid=460288">https://sourceforge.net/tracker/?group_id=11118&atid=460288</a>,
+ "https://sourceforge.net/tracker/?group_id=11118">https://sourceforge.net/tracker/?group_id=11118</a>&atid=460288,
to submit ``misses'' and other configuration related suggestions to the
developers. <a name="lbAL" id="lbAL"> </a></p>
<h2>DEVELOPMENT TEAM</h2>
<pre>
Fabian Keil, lead developer
- David Schmidt, developer
-
+ David Schmidt
Hal Burgiss
Lee Rian
Roland Rosenfeld
it under the terms of the <i>GNU General Public License</i>, version 2, as
published by the Free Software Foundation.</p>
- <p>This program is distributed in the hope that it will be useful, but
+ <p><b>Privoxy</b> is distributed in the hope that it will be useful, but
WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY
- or FITNESS FOR A PARTICULAR PURPOSE. See the <i>GNU General Public
- License</i> for details.</p>
-
- <p>You should have received a copy of the <i>GNU GPL</i> along with this
- program; if not, write to the Free Software Foundation, Inc. 51 Franklin
- Street, Fifth Floor Boston, MA 02110-1301 USA</p>
+ or FITNESS FOR A PARTICULAR PURPOSE. See the <i>license</i> for
+ details.</p>
<hr>
<a name="index" id="index"> </a>
</dl>
<hr>
This document was created by man2html, using the manual pages.<br>
- Time: 18:35:36 GMT, January 06, 2013
+ Time: 14:21:31 GMT, March 02, 2013
</body>
</html>
in <tt class="FILENAME">default.action</tt> are:</p>
<div class="TABLE">
- <a name="AEN2822" id="AEN2822"></a>
+ <a name="AEN2826" id="AEN2826"></a>
<p><b>Table 1. Default Configurations</b></p>
actions</a>.</p>
<div class="SECT2">
- <h2 class="SECT2"><a name="AEN2921" id="AEN2921">8.1. Finding the Right
+ <h2 class="SECT2"><a name="AEN2925" id="AEN2925">8.1. Finding the Right
Mix</a></h2>
<p>Note that some <a href="actions-file.html#ACTIONS">actions</a>, like
</div>
<div class="SECT2">
- <h2 class="SECT2"><a name="AEN2928" id="AEN2928">8.2. How to
+ <h2 class="SECT2"><a name="AEN2932" id="AEN2932">8.2. How to
Edit</a></h2>
<p>The easiest way to edit the actions files is with a browser by using
</div>
<div class="SECT3">
- <h3 class="SECT3"><a name="AEN3040" id="AEN3040">8.4.1. The Domain
+ <h3 class="SECT3"><a name="AEN3044" id="AEN3044">8.4.1. The Domain
Pattern</a></h3>
<p>The matching of the domain part offers some flexible options: if
</div>
<div class="SECT3">
- <h3 class="SECT3"><a name="AEN3116" id="AEN3116">8.4.2. The Path
+ <h3 class="SECT3"><a name="AEN3120" id="AEN3120">8.4.2. The Path
Pattern</a></h3>
<p><span class="APPLICATION">Privoxy</span> uses <span class=
<tr>
<td>
<pre class="SCREEN">
-+filter{js-events} # Kill all JS event bindings and timers (Radically destructive! Only for extra nasty sites).
++filter{js-events} # Kill JavaScript event bindings and timers (Radically destructive! Only for extra nasty sites).
</pre>
</td>
</tr>
<tr>
<td>
<pre class="SCREEN">
-+filter{refresh-tags} # Kill automatic refresh tags (for dial-on-demand setups).
++filter{refresh-tags} # Kill automatic refresh tags if refresh time is larger than 9 seconds.
</pre>
</td>
</tr>
<tr>
<td>
<pre class="SCREEN">
-+filter{unsolicited-popups} # Disable only unsolicited pop-up windows. Useful if your browser lacks this ability.
++filter{unsolicited-popups} # Disable only unsolicited pop-up windows.
</pre>
</td>
</tr>
<tr>
<td>
<pre class="SCREEN">
-+filter{all-popups} # Kill all popups in JavaScript and HTML. Useful if your browser lacks this ability.
++filter{all-popups} # Kill all popups in JavaScript and HTML.
</pre>
</td>
</tr>
</tr>
</table>
+ <p><a name="FILTER-IFRAMES" id="FILTER-IFRAMES"></a></p>
+
+ <table border="0" bgcolor="#E0E0E0" width="90%">
+ <tr>
+ <td>
+ <pre class="SCREEN">
++filter{iframes} # Removes all detected iframes. Should only be enabled for individual sites.
+</pre>
+ </td>
+ </tr>
+ </table>
+
<p><a name="FILTER-DEMORONIZER" id=
"FILTER-DEMORONIZER"></a></p>
</div>
<div class="SECT3">
- <h3 class="SECT3"><a name="AEN4788" id="AEN4788">8.5.35.
+ <h3 class="SECT3"><a name="AEN4795" id="AEN4795">8.5.35.
Summary</a></h3>
<p>Note that many of these actions have the potential to cause a page
together:</p>
<div class="SECT3">
- <h3 class="SECT3"><a name="AEN4852" id="AEN4852">8.7.1.
+ <h3 class="SECT3"><a name="AEN4859" id="AEN4859">8.7.1.
match-all.action</a></h3>
<p>Remember <span class="emphasis"><i class="EMPHASIS">all actions
</div>
<div class="SECT3">
- <h3 class="SECT3"><a name="AEN4874" id="AEN4874">8.7.2.
+ <h3 class="SECT3"><a name="AEN4881" id="AEN4881">8.7.2.
default.action</a></h3>
<p>If you aren't a developer, there's no need for you to edit the
</div>
<div class="SECT3">
- <h3 class="SECT3"><a name="AEN4987" id="AEN4987">8.7.3.
+ <h3 class="SECT3"><a name="AEN4994" id="AEN4994">8.7.3.
user.action</a></h3>
<p>So far we are painting with a broad brush by setting general
</div>
<div class="SECT2">
- <h2 class="SECT2"><a name="AEN5863" id="AEN5863">14.2. Privoxy's
+ <h2 class="SECT2"><a name="AEN5870" id="AEN5870">14.2. Privoxy's
Internal Pages</a></h2>
<p>Since <span class="APPLICATION">Privoxy</span> proxies each
<ul>
<li>
- <p>Privoxy main page:</p><a name="AEN5877" id="AEN5877"></a>
+ <p>Privoxy main page:</p><a name="AEN5884" id="AEN5884"></a>
<blockquote class="BLOCKQUOTE">
<p><a href="http://config.privoxy.org/" target=
<li>
<p>Show information about the current configuration, including
- viewing and editing of actions files:</p><a name="AEN5885" id=
- "AEN5885"></a>
+ viewing and editing of actions files:</p><a name="AEN5892" id=
+ "AEN5892"></a>
<blockquote class="BLOCKQUOTE">
<p><a href="http://config.privoxy.org/show-status" target=
</li>
<li>
- <p>Show the source code version numbers:</p><a name="AEN5890" id=
- "AEN5890"></a>
+ <p>Show the source code version numbers:</p><a name="AEN5897" id=
+ "AEN5897"></a>
<blockquote class="BLOCKQUOTE">
<p><a href="http://config.privoxy.org/show-version" target=
</li>
<li>
- <p>Show the browser's request headers:</p><a name="AEN5895" id=
- "AEN5895"></a>
+ <p>Show the browser's request headers:</p><a name="AEN5902" id=
+ "AEN5902"></a>
<blockquote class="BLOCKQUOTE">
<p><a href="http://config.privoxy.org/show-request" target=
</li>
<li>
- <p>Show which actions apply to a URL and why:</p><a name="AEN5900"
- id="AEN5900"></a>
+ <p>Show which actions apply to a URL and why:</p><a name="AEN5907"
+ id="AEN5907"></a>
<blockquote class="BLOCKQUOTE">
<p><a href="http://config.privoxy.org/show-url-info" target=
<span class="QUOTE">"off"</span>, <span class=
"QUOTE">"Privoxy"</span> continues to run, but only as a
pass-through proxy, with no actions taking place:</p><a name=
- "AEN5908" id="AEN5908"></a>
+ "AEN5915" id="AEN5915"></a>
<blockquote class="BLOCKQUOTE">
<p><a href="http://config.privoxy.org/toggle" target=
"_top">http://config.privoxy.org/toggle</a></p>
</blockquote>
- <p>Short cuts. Turn off, then on:</p><a name="AEN5912" id=
- "AEN5912"></a>
+ <p>Short cuts. Turn off, then on:</p><a name="AEN5919" id=
+ "AEN5919"></a>
<blockquote class="BLOCKQUOTE">
<p><a href="http://config.privoxy.org/toggle?set=disable" target=
"_top">http://config.privoxy.org/toggle?set=disable</a></p>
- </blockquote><a name="AEN5915" id="AEN5915"></a>
+ </blockquote><a name="AEN5922" id="AEN5922"></a>
<blockquote class="BLOCKQUOTE">
<p><a href="http://config.privoxy.org/toggle?set=enable" target=
controlled easily with a web browser.</p>
<div class="SECT2">
- <h2 class="SECT2"><a name="AEN1070" id="AEN1070">6.1. Controlling
+ <h2 class="SECT2"><a name="AEN1074" id="AEN1074">6.1. Controlling
Privoxy with Your Web Browser</a></h2>
<p><span class="APPLICATION">Privoxy</span>'s user interface can be
</pre>
- <h2 class="BRIDGEHEAD"><a name="AEN1078" id=
- "AEN1078"></a> Privoxy Menu</h2>
- <pre>
-</pre>
+ <h2 class="BRIDGEHEAD"><a name="AEN1082" id=
+ "AEN1082"></a> Privoxy Menu</h2>
<table border="0">
<tbody>
target="_top">users mailing list</a>, where the developers also hang
around.</p>
- <p>Please don't sent private support requests to individual Privoxy
+ <p>Please don't send private support requests to individual Privoxy
developers, either use the mailing lists or the support trackers.</p>
<p>If you have to contact a Privoxy developer directly for other
started.</p>
<div class="SECT2">
- <h2 class="SECT2"><a name="AEN5142" id="AEN5142">9.1. Filter File
+ <h2 class="SECT2"><a name="AEN5149" id="AEN5149">9.1. Filter File
Tutorial</a></h2>
<p>Now, let's complete our <span class="QUOTE">"foo"</span> content
2001-2013 by <a href="http://www.privoxy.org/" target="_top">Privoxy
Developers</a></sub><br></p>
- <p class="PUBDATE">$Id: user-manual.sgml,v 2.169 2013/02/26 15:10:49
+ <p class="PUBDATE">$Id: user-manual.sgml,v 2.173 2013/03/01 17:44:24
fabiankeil Exp $<br></p>
<div>
<dd>
<dl>
- <dt>6.1. <a href="configuration.html#AEN1070">Controlling Privoxy
+ <dt>6.1. <a href="configuration.html#AEN1074">Controlling Privoxy
with Your Web Browser</a></dt>
<dt>6.2. <a href="configuration.html#CONFOVERVIEW">Configuration
<dd>
<dl>
- <dt>8.1. <a href="actions-file.html#AEN2921">Finding the Right
+ <dt>8.1. <a href="actions-file.html#AEN2925">Finding the Right
Mix</a></dt>
- <dt>8.2. <a href="actions-file.html#AEN2928">How to Edit</a></dt>
+ <dt>8.2. <a href="actions-file.html#AEN2932">How to Edit</a></dt>
<dt>8.3. <a href="actions-file.html#ACTIONS-APPLY">How Actions
are Applied to Requests</a></dt>
<dd>
<dl>
- <dt>8.4.1. <a href="actions-file.html#AEN3040">The Domain
+ <dt>8.4.1. <a href="actions-file.html#AEN3044">The Domain
Pattern</a></dt>
- <dt>8.4.2. <a href="actions-file.html#AEN3116">The Path
+ <dt>8.4.2. <a href="actions-file.html#AEN3120">The Path
Pattern</a></dt>
<dt>8.4.3. <a href="actions-file.html#TAG-PATTERN">The Tag
"actions-file.html#SET-IMAGE-BLOCKER">set-image-blocker</a></dt>
<dt>8.5.35. <a href=
- "actions-file.html#AEN4788">Summary</a></dt>
+ "actions-file.html#AEN4795">Summary</a></dt>
</dl>
</dd>
<dd>
<dl>
<dt>8.7.1. <a href=
- "actions-file.html#AEN4852">match-all.action</a></dt>
+ "actions-file.html#AEN4859">match-all.action</a></dt>
<dt>8.7.2. <a href=
- "actions-file.html#AEN4874">default.action</a></dt>
+ "actions-file.html#AEN4881">default.action</a></dt>
<dt>8.7.3. <a href=
- "actions-file.html#AEN4987">user.action</a></dt>
+ "actions-file.html#AEN4994">user.action</a></dt>
</dl>
</dd>
</dl>
<dd>
<dl>
- <dt>9.1. <a href="filter-file.html#AEN5142">Filter File
+ <dt>9.1. <a href="filter-file.html#AEN5149">Filter File
Tutorial</a></dt>
<dt>9.2. <a href="filter-file.html#PREDEFINED-FILTERS">The
<dt>14.1. <a href="appendix.html#REGEX">Regular
Expressions</a></dt>
- <dt>14.2. <a href="appendix.html#AEN5863">Privoxy's Internal
+ <dt>14.2. <a href="appendix.html#AEN5870">Privoxy's Internal
Pages</a></dt>
<dd>
"GUIBUTTON">Edit</span>"</span>:</p>
<div class="FIGURE">
- <a name="AEN846" id="AEN846"></a>
+ <a name="AEN850" id="AEN850"></a>
<p><b>Figure 1. Actions Files in Use</b></p>
protocols.</p>
<div class="FIGURE">
- <a name="AEN901" id="AEN901"></a>
+ <a name="AEN905" id="AEN905"></a>
<p><b>Figure 2. Proxy Configuration Showing Mozilla/Netscape HTTP and
HTTPS (SSL) Settings</b></p>
only HTTP and HTTPS (SSL)!</p>
<div class="FIGURE">
- <a name="AEN946" id="AEN946"></a>
+ <a name="AEN950" id="AEN950"></a>
<p><b>Figure 3. Proxy Configuration Showing Internet Explorer HTTP and
HTTPS (Secure) Settings</b></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.21</span> is UNRELEASED. The
- changes since 3.0.20 beta 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 a security issue that
+ affects all previous Privoxy versions (on some platforms). The changes
+ since 3.0.20 beta are:</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>Compiles on OS/2 again now that unistd.h is only included on
platforms that have it.</p>
<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>
projects / privoxy.git / commitdiff