X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=doc%2Fsource%2Fp-config.sgml;h=8cef79706cb6b1e6c46c2b59ebd412eef2ad1195;hp=3c743400d205ca05d4baba65d0d69027524096da;hb=8855a031e62cf14ac96b06e773f8bad01d3a4e25;hpb=c195f95c950b2b89905fce58b4eb560d817ed371

diff --git a/doc/source/p-config.sgml b/doc/source/p-config.sgml
index 3c743400..8cef7970 100644
--- a/doc/source/p-config.sgml
+++ b/doc/source/p-config.sgml
@@ -3,7 +3,7 @@
 
  Purpose     :  Used with other docs and files only.
 
- $Id: p-config.sgml,v 2.15 2007/05/21 10:58:43 fabiankeil Exp $
+ $Id: p-config.sgml,v 2.21 2007/11/07 18:50:39 fabiankeil Exp $
 
  Copyright (C) 2001-2007 Privoxy Developers http://www.privoxy.org/
  See LICENSE.
@@ -95,7 +95,7 @@
  Sample Configuration File for Privoxy v&p-version;
 </title>
 <para>
- $Id: p-config.sgml,v 2.15 2007/05/21 10:58:43 fabiankeil Exp $
+ $Id: p-config.sgml,v 2.21 2007/11/07 18:50:39 fabiankeil Exp $
 </para>
 <para>
 Copyright (C) 2001-2007 Privoxy Developers http://www.privoxy.org/
@@ -172,7 +172,7 @@ II. FORMAT OF THE CONFIGURATION FILE
 <para>
  Note that commenting out an option and leaving it at its default
  are two completely different things! Most options behave very
- differently when unset. See the the "Effect if unset" explanation
+ differently when unset. See the "Effect if unset" explanation
  in each option's description for details.
 </para>
 <para>
@@ -269,12 +269,13 @@ II. FORMAT OF THE CONFIGURATION FILE
    <literal>PATH</literal> to where the <citetitle>User Manual</citetitle> is
    located:
   </para>
-<para>
+  <para>
    <screen>&nbsp;&nbsp;user-manual&nbsp;&nbsp;/usr/share/doc/privoxy/user-manual</screen>
   </para>
   <para>
-   The User Manual is then available to anyone with access to the proxy, by 
-   following the built-in URL: <literal>http://config.privoxy.org/user-manual/</literal>
+   The User Manual is then available to anyone with access to
+   <application>Privoxy</application>, by following the built-in URL:
+   <literal>http://config.privoxy.org/user-manual/</literal>
    (or the shortcut: <literal>http://p.p/user-manual/</literal>).
   </para>
   <para>
@@ -337,7 +338,7 @@ II. FORMAT OF THE CONFIGURATION FILE
  <varlistentry>
   <term>Default value:</term>
   <listitem>
-   <para>Two example URL are provided</para>
+   <para>Two example URLs are provided</para>
   </listitem>
  </varlistentry>
  <varlistentry>
@@ -353,7 +354,7 @@ II. FORMAT OF THE CONFIGURATION FILE
   <listitem>
    <para>
     The value of this option only matters if the experimental trust mechanism has been
-    activated. (See <link linkend="trustfile"><emphasis>trustfile</emphasis></link> above.)
+    activated. (See <link linkend="trustfile"><emphasis>trustfile</emphasis></link> below.)
    </para>
    <para>
     If you use the trust mechanism, it is a good idea to write up some on-line
@@ -381,7 +382,7 @@ II. FORMAT OF THE CONFIGURATION FILE
   <term>Specifies:</term>
   <listitem>
    <para>
-    An email address to reach the proxy administrator.
+    An email address to reach the <application>Privoxy</application> administrator.
    </para>
   </listitem>
  </varlistentry>
@@ -408,7 +409,7 @@ II. FORMAT OF THE CONFIGURATION FILE
  <varlistentry>
   <term>Notes:</term>
   <listitem>
-    <para>
+   <para>
     If both <literal>admin-address</literal> and <literal>proxy-info-url</literal>
     are unset, the whole "Local Privoxy Support" box on all generated pages will
     not be shown.
@@ -503,7 +504,7 @@ II. FORMAT OF THE CONFIGURATION FILE
  <varlistentry>
   <term>Specifies:</term>
   <listitem>
-   <para>The directory where the other configuration files are located</para>
+   <para>The directory where the other configuration files are located.</para>
   </listitem>
  </varlistentry>
  <varlistentry>
@@ -528,7 +529,7 @@ II. FORMAT OF THE CONFIGURATION FILE
   <term>Notes:</term>
   <listitem>
    <para>
-    No trailing <quote><literal>/</literal></quote>, please
+    No trailing <quote><literal>/</literal></quote>, please.
    </para>
   <!-- 
    This is really outdated and not likely to happen. HB 09/20/06
@@ -554,7 +555,7 @@ II. FORMAT OF THE CONFIGURATION FILE
  <varlistentry>
   <term>Specifies:</term>
   <listitem>
-   <para>An alternative directory where the templates are loaded from</para>
+   <para>An alternative directory where the templates are loaded from.</para>
   </listitem>
  </varlistentry>
  <varlistentry>
@@ -579,10 +580,12 @@ II. FORMAT OF THE CONFIGURATION FILE
   <term>Notes:</term>
   <listitem>
    <para>
-    Privoxy's original templates are usually overwritten
-    with each update. Use this option to relocate customized templates
-    that should be kept. Note that you might be missing new features
-    if you use outdated templates.
+    <application>Privoxy's</application> original templates are usually
+    overwritten with each update. Use this option to relocate customized
+    templates that should be kept. As template variables might change
+    between updates, you shouldn't expect templates to work with
+    <application>Privoxy</application> releases other than the one
+    they were part of, though.
    </para>
   </listitem>
  </varlistentry>
@@ -600,8 +603,9 @@ II. FORMAT OF THE CONFIGURATION FILE
   <term>Specifies:</term>
   <listitem>
    <para>
-    The directory where all logging takes place (i.e. where <filename>logfile</filename> and 
-    <filename>jarfile</filename> are located) 
+    The directory where all logging takes place
+    (i.e. where <filename>logfile</filename> and
+    <filename>jarfile</filename> are located).
    </para>
   </listitem>
  </varlistentry>
@@ -627,7 +631,7 @@ II. FORMAT OF THE CONFIGURATION FILE
   <term>Notes:</term>
   <listitem>
    <para>
-    No trailing <quote><literal>/</literal></quote>, please
+    No trailing <quote><literal>/</literal></quote>, please.
    </para>
   </listitem>
  </varlistentry>
@@ -691,13 +695,13 @@ actionsfile
     Multiple <literal>actionsfile</literal> lines are permitted, and are in fact recommended!
    </para>
    <para> 
-    The default values include standard.action, which is used for internal
-    purposes and should be loaded, default.action, which is the
-    <quote>main</quote> actions file maintained by the developers, and
+    The default values include <filename>standard.action</filename>, which is used
+    for internal purposes and should be loaded, <filename>default.action</filename>,
+    which is the <quote>main</quote> actions file maintained by the developers, and
     <filename>user.action</filename>, where you can make your personal additions.
    </para>
    <para> 
-    Actions files are where all the per site and per URL configuration is done for 
+    Actions files contain all the per site and per URL configuration for 
     ad blocking, cookie management, privacy considerations, etc.
     There is no point in using <application>Privoxy</application> without at 
     least one actions file.
@@ -715,6 +719,11 @@ actionsfile
 <!-- html -> text conversion, blah -->
 <![%config-file;[<literallayout>@@actionsfile standard.action  # Internal purpose, recommended</literallayout>]]>
 <![%config-file;[<literallayout>@@actionsfile default.action   # Main actions file</literallayout>]]>
+<!--
+ XXX: Like user.filter, user.action should probably be commented out
+ by default as not all packages install it into the default directory.
+ fk 2007-11-07
+-->
 <![%config-file;[<literallayout>@@actionsfile user.action      # User customizations</literallayout>]]>
 </sect3>
 
@@ -762,7 +771,7 @@ actionsfile
     The <link linkend="filter-file">filter files</link> contain content modification
     rules that use <link linkend="regex">regular expressions</link>. These rules permit
     powerful changes on the content of Web pages, and optionally the headers
-    as well, e.g., you could disable your favorite JavaScript annoyances,
+    as well, e.g., you could try to disable your favorite JavaScript annoyances,
     re-write the actual displayed text, or just have some fun 
     playing buzzword bingo with web pages.
    </para>
@@ -812,14 +821,14 @@ actionsfile
  <varlistentry>
   <term>Default value:</term>
   <listitem>
-   <para>logfile (Unix) <emphasis>or</emphasis> privoxy.log (Windows)</para>
+   <para><emphasis>Unset (commented out)</emphasis>. When activated: logfile (Unix) <emphasis>or</emphasis> privoxy.log (Windows).</para>
   </listitem>
  </varlistentry>
  <varlistentry>
   <term>Effect if unset:</term>
   <listitem>
    <para>
-    No log file is used, all log messages go to the console (<literal>STDERR</literal>).
+    Logging is disabled unless <literal>--no-daemon</literal> mode is used.
    </para>
   </listitem>
  </varlistentry>
@@ -838,29 +847,48 @@ actionsfile
     of detail and number of messages are set with the <literal>debug</literal>
     option (see below). The logfile can be useful for tracking down a problem with
     <application>Privoxy</application> (e.g., it's not blocking an ad you
-    think it should block) but in most cases you probably will never look at it.
+    think it should block) and it can help you to monitor what your browser
+    is doing.
+   </para>
+   <para>
+    Many users will never look at it, however, and it's a privacy risk
+    if third parties can get access to it. It is therefore disabled by
+    default in <application>Privoxy</application> 3.0.7 and later.
+  </para>
+  <para>
+    For troubleshooting purposes, you will have to explicitly enable it.
+    Please don't file any support requests without trying to reproduce
+    the problem with logging enabled first. Once you read the log messages,
+    you may even be able to solve the problem on your own.
    </para>
    <para>
     Your logfile will grow indefinitely, and you will probably want to
     periodically remove it.  On Unix systems, you can do this with a cron job
-    (see <quote>man cron</quote>). For Red Hat, a <command>logrotate</command> 
-    script has been included.
+    (see <quote>man cron</quote>). For Red Hat based Linux distributions, a
+    <command>logrotate</command> script has been included.
    </para> 
+<!--
+No one cares enough about SuSE to build privoxy packages,
+so most Privoxy users seem to use different platforms and
+are thus unlikely to care about these instructions.
+It's also questionable if they still work.
+fk 2007-11-07
    <para>
     On SuSE Linux systems, you can place a line like <quote>/var/log/privoxy.*
     +1024k 644 nobody.nogroup</quote> in <filename>/etc/logfiles</filename>, with
     the effect that cron.daily will automatically archive, gzip, and empty the
     log, when it exceeds 1M size.
    </para>
+-->
    <para>
     Any log files must be writable by whatever user <application>Privoxy</application>
-    is being run as (default on UNIX, user id is <quote>privoxy</quote>).
+    is being run as (on Unix, default user id is <quote>privoxy</quote>).
    </para>
   </listitem>
  </varlistentry>
 </variablelist>
 
-<![%config-file;[<literallayout>@@logfile logfile</literallayout>]]>
+<![%config-file;[<literallayout>@@#logfile logfile</literallayout>]]>
 </sect3>
 
 
@@ -885,7 +913,7 @@ actionsfile
  <varlistentry>
   <term>Default value:</term>
   <listitem>
-   <para>Unset (commented out). When activated: jarfile (Unix) <emphasis>or</emphasis> privoxy.jar (Windows)</para>
+   <para><emphasis>Unset (commented out)</emphasis>. When activated: jarfile (Unix) <emphasis>or</emphasis> privoxy.jar (Windows).</para>
   </listitem>
  </varlistentry>
  <varlistentry>
@@ -904,7 +932,10 @@ actionsfile
    </para>
    <para>
     If debug 8 (show header parsing) is enabled, cookies are
-    written to the logfile with the rest of the headers.
+    also written to the logfile with the rest of the headers.
+    Therefore this option isn't very useful and may be removed
+    in future releases. Please report to the developers if you
+    are still using it.
    </para>
   </listitem>
  </varlistentry>
@@ -1077,10 +1108,16 @@ actionsfile
     a hell of an output (especially 16).
     <!-- LOL -->
    </para>
+<!--
    <para>
     The reporting of <emphasis>fatal</emphasis> errors (i.e. ones which causes 
     <application>Privoxy</application> to exit) is always on and cannot be disabled.
    </para>
+   It can be disabled by not logging at all (now the default)
+   and I doubt that any user would care about not being able
+   to disable it anyway.
+   fk 2007-11-09
+-->
    <para>
     If you want to use CLF (Common Log Format), you should set <quote>debug
     512</quote> <emphasis>ONLY</emphasis> and not enable anything else.
@@ -1108,7 +1145,7 @@ actionsfile
   <term>Specifies:</term>
   <listitem>
    <para>
-    Whether to run only one server thread
+    Whether to run only one server thread.
    </para>
   </listitem>
  </varlistentry>
@@ -1137,8 +1174,8 @@ actionsfile
   <term>Notes:</term>
   <listitem>
    <para>
-    This option is only there for debug purposes and you should never
-    need to use it. <emphasis>It will drastically reduce performance.</emphasis>
+    This option is only there for debugging purposes.
+    <emphasis>It will drastically reduce performance.</emphasis>
    </para>
   </listitem>
  </varlistentry>
@@ -1218,10 +1255,9 @@ actionsfile
    </para>
    <para>
     If you open <application>Privoxy</application> to untrusted users, you will
-    also want to turn off the <literal><link
+    also want to make sure that the following actions are disabled:  <literal><link
     linkend="enable-edit-actions">enable-edit-actions</link></literal> and
     <literal><link linkend="enable-remote-toggle">enable-remote-toggle</link></literal>
-    options!
    </para>
   </listitem>
  </varlistentry>
@@ -1285,11 +1321,16 @@ actionsfile
    <para>
     If set to 0, <application>Privoxy</application> will start in
     <quote>toggled off</quote> mode, i.e. mostly behave like a normal,
-    content-neutral proxy where all ad blocking, filtering, etc are disabled. See
-    <literal>enable-remote-toggle</literal> below. This is not really useful
+    content-neutral proxy with both ad blocking and content filtering
+    disabled. See <literal>enable-remote-toggle</literal> below.
+<!--
+    This is not really useful
     anymore, since toggling is much easier via <ulink
     url="http://config.privoxy.org/toggle">the web interface</ulink> than via
     editing the <filename>conf</filename> file.
+
+    Remote toggling is now disabled by default. fk 2007-11-07)
+-->
    </para>
    <para>
     The windows version will only display the toggle icon in the system tray
@@ -1324,7 +1365,7 @@ actionsfile
  <varlistentry>
   <term>Default value:</term>
   <listitem>
-   <para>1</para>
+   <para>0</para>
   </listitem>
  </varlistentry>
  <varlistentry>
@@ -1340,17 +1381,24 @@ actionsfile
   <listitem>
    <para>
     When toggled off, <application>Privoxy</application> mostly acts like a normal,
-    content-neutral proxy, i.e. it acts as if none of the actions applied to
-    any URL.
+    content-neutral proxy, i.e. doesn't block ads or filter content.
    </para>
    <para>
-    For the time being, access to the toggle feature can <emphasis>not</emphasis> be
+    Access to the toggle feature can <emphasis>not</emphasis> be
     controlled separately by <quote>ACLs</quote> or HTTP authentication,
     so that everybody who can access <application>Privoxy</application> (see
     <quote>ACLs</quote> and <literal>listen-address</literal> above) can
     toggle it for all users. So this option is <emphasis>not recommended</emphasis>
     for multi-user environments with untrusted users.
    </para>
+   <para>
+    Note that malicious client side code (e.g Java) is also
+    capable of using this option.
+   </para>
+   <para>
+    As a lot of <application>Privoxy</application> users don't read
+    documentation, this feature is disabled by default.
+   </para>
    <para>
     Note that you must have compiled <application>Privoxy</application> with
     support for this feature, otherwise this option has no effect. 
@@ -1359,7 +1407,7 @@ actionsfile
  </varlistentry>
 </variablelist>
 
-<![%config-file;[<literallayout>@@enable-remote-toggle  1</literallayout>]]>
+<![%config-file;[<literallayout>@@enable-remote-toggle  0</literallayout>]]>
 </sect3>
 
 
@@ -1383,7 +1431,7 @@ actionsfile
  <varlistentry>
   <term>Default value:</term>
   <listitem>
-   <para>1</para>
+   <para>0</para>
   </listitem>
  </varlistentry>
  <varlistentry>
@@ -1404,16 +1452,20 @@ actionsfile
     the ongoing request, even if it is enabled in one of the action files.
    </para>
    <para>
-    If you are using <application>Privoxy</application> in a
-    multi-user environment or with untrustworthy clients and want to
-    enforce filtering, you will have to disable this option,
-    otherwise you can ignore it. 
+    This feature is disabled by default. If you are using
+    <application>Privoxy</application> in a environment with trusted clients,
+    you may enable this feature at your discretion. Note that malicious client
+    side code (e.g Java) is also capable of using this feature.
+   </para>
+   <para>
+    This option will be removed in future releases as it has been obsoleted
+    by the more general header taggers.
    </para>
   </listitem>
  </varlistentry>
 </variablelist>
 
-<![%config-file;[<literallayout>@@enable-remote-http-toggle  1</literallayout>]]>
+<![%config-file;[<literallayout>@@enable-remote-http-toggle  0</literallayout>]]>
 </sect3>
 
 
@@ -1438,7 +1490,7 @@ actionsfile
  <varlistentry>
   <term>Default value:</term>
   <listitem>
-   <para>1</para>
+   <para>0</para>
   </listitem>
  </varlistentry>
  <varlistentry>
@@ -1453,12 +1505,23 @@ actionsfile
   <term>Notes:</term>
   <listitem>
    <para>
-    For the time being, access to the editor can <emphasis>not</emphasis> be
+    Access to the editor can <emphasis>not</emphasis> be
     controlled separately by <quote>ACLs</quote> or HTTP authentication,
     so that everybody who can access <application>Privoxy</application> (see
     <quote>ACLs</quote> and <literal>listen-address</literal> above) can
-    modify its configuration for all users. So this option is <emphasis>not
-    recommended</emphasis> for multi-user environments with untrusted users.
+    modify its configuration for all users.
+   </para>
+   <para>
+    This option is <emphasis>not recommended</emphasis> for environments
+    with untrusted users and as a lot of <application>Privoxy</application>
+    users don't read documentation, this feature is disabled by default.
+   </para>
+   </para>
+   <para>
+    Note that malicious client side code (e.g Java) is also
+    capable of using the actions editor and you shouldn't enable
+    this options unless you understand the consequences and are
+    sure your browser is configured correctly.
    </para>
    <para>
     Note that you must have compiled <application>Privoxy</application> with
@@ -1468,7 +1531,7 @@ actionsfile
  </varlistentry>
 </variablelist>
 
-<![%config-file;[<literallayout>@@enable-edit-actions 1</literallayout>]]>
+<![%config-file;[<literallayout>@@enable-edit-actions 0</literallayout>]]>
 </sect3>
 
 
@@ -1605,9 +1668,9 @@ ACLs: permit-access and deny-access</title>
     option. 
    </para>
    <para>
-    Please see the warnings in the FAQ that this proxy is not intended to be a substitute
-    for a firewall or to encourage anyone to defer addressing basic security
-    weaknesses.
+    Please see the warnings in the FAQ that <application>Privoxy</application>
+    is not intended to be a substitute for a firewall or to encourage anyone
+    to defer addressing basic security weaknesses.
    </para>
    <para>
     Multiple ACL lines are OK.
@@ -1841,8 +1904,8 @@ ACLs: permit-access and deny-access</title>
    </para>
    <para>
     <screen>
-  forward   /                  caching-proxy.example-isp.net:8000
-  forward   .example-isp.net   .
+  forward   /                  caching-proxy.isp.example.net:8000
+  forward   .isp.example.net   .
 </screen>
    </para>
   </listitem>
@@ -1928,7 +1991,7 @@ forward-socks4 and forward-socks4a</title>
    </para>
    <para>
     <screen>
-  forward-socks4a   /              socks-gw.example.com:1080  www-cache.example-isp.net:8080
+  forward-socks4a   /              socks-gw.example.com:1080  www-cache.isp.example.net:8080
   forward           .example.com   .
 </screen>
    </para>
@@ -1942,18 +2005,19 @@ forward-socks4 and forward-socks4a</title>
    </para>
   
     <para>
-    To chain Privoxy and Tor, both running on the same system, you should use 
-    the rule:
+    To chain Privoxy and Tor, both running on the same system, you would use 
+    something like:
    </para>
    <para>
     <screen>
-  forward-socks4   /               127.0.0.1:9050 .
+  forward-socks4a   /               127.0.0.1:9050 .
 </screen>
    </para>
 
     <para>
-    The public <application>Tor</application> network can't be used to reach your local network,
-    therefore it's a good idea to make some exceptions:
+    The public <application>Tor</application> network can't be used to
+    reach your local network, if you need to access local servers you
+    therefore might want to make some exceptions:
    </para>
    <para>
     <screen>
@@ -1965,7 +2029,9 @@ forward-socks4 and forward-socks4a</title>
    <para>
     Unencrypted connections to systems in these address ranges will
     be as (un)secure as the local network is, but the alternative is that you
-    can't reach the network at all.
+    can't reach the local network through <application>Privoxy</application>
+    at all. Of course this may actually be desired and there is no reason
+    to make these exceptions if you aren't sure you need them.
    </para>
    <para>
     If you also want to be able to reach servers in your local network by
@@ -1995,8 +2061,8 @@ forward-socks4 and forward-socks4a</title>
 </para>
 
 <para>
- Assume that host-a has a PPP connection to isp-a.net. And host-b has a PPP connection to
- isp-b.net. Both run <application>Privoxy</application>. Their forwarding
+ Assume that host-a has a PPP connection to isp-a.example.net. And host-b has a PPP connection to
+ isp-b.example.org. Both run <application>Privoxy</application>. Their forwarding
  configuration can look like this:
 </para>
 
@@ -2007,7 +2073,7 @@ forward-socks4 and forward-socks4a</title>
 <para>
  <screen>
   forward    /           .
-  forward    .isp-b.net  host-b:8118
+  forward    .isp-b.example.net  host-b:8118
 </screen>
 </para>
 
@@ -2018,7 +2084,7 @@ forward-socks4 and forward-socks4a</title>
 <para>
  <screen>
   forward    /           .
-  forward    .isp-a.net  host-a:8118
+  forward    .isp-a.example.org  host-a:8118
 </screen>
 </para>
 
@@ -2030,7 +2096,7 @@ forward-socks4 and forward-socks4a</title>
 
 <para>
  If you intend to chain <application>Privoxy</application> and 
- <application>squid</application> locally, then chain as 
+ <application>squid</application> locally, then chaining as 
  <literal>browser -> squid -> privoxy</literal> is the recommended way. 
 </para>
 
@@ -2060,8 +2126,9 @@ forward-socks4 and forward-socks4a</title>
 </para>
 
 <para>
- You could just as well decide to only forward requests for Windows executables through
- a virus-scanning parent proxy, say, on <literal>antivir.example.com</literal>, port 8010:
+ You could just as well decide to only forward requests you suspect
+ of leading to Windows executables through a virus-scanning parent proxy,
+ say, on <literal>antivir.example.com</literal>, port 8010:
 </para>
 
 <para>
@@ -2120,7 +2187,7 @@ forward-socks4 and forward-socks4a</title>
     that Privoxy forwards through other proxies. This option is not limited to the HTTP CONNECT method.
    </para>
    <para>
-    Only use this option, if you are getting many forwarding related error messages,
+    Only use this option, if you are getting lots of forwarding-related error messages
     that go away when you try again manually. Start with a small value and check Privoxy's
     logfile from time to time, to see how many retries are usually needed.
    </para>
@@ -2201,6 +2268,64 @@ forward-socks4 and forward-socks4a</title>
 <![%config-file;[<literallayout>@@accept-intercepted-requests 0</literallayout>]]>
 </sect3>
 
+<sect3 renderas="sect4" id="allow-cgi-request-crunching"><title>allow-cgi-request-crunching</title>
+<variablelist>
+ <varlistentry>
+  <term>Specifies:</term>
+  <listitem>
+   <para>
+    Whether requests to <application>Privoxy's</application> CGI pages can be blocked or redirected.
+   </para>
+  </listitem>
+ </varlistentry>
+ <varlistentry>
+  <term>Type of value:</term>
+  <listitem>
+   <para>
+    <replaceable>0 or 1</replaceable>
+   </para>
+  </listitem>
+ </varlistentry>
+ <varlistentry>
+  <term>Default value:</term>
+  <listitem>
+   <para><emphasis>0</emphasis></para>
+  </listitem>
+ </varlistentry>
+ <varlistentry>
+  <term>Effect if unset:</term>
+  <listitem>
+   <para>
+    <application>Privoxy</application> ignores block and redirect actions for its CGI pages.
+   </para>
+  </listitem>
+ </varlistentry>
+ <varlistentry>
+  <term>Notes:</term>
+  <listitem>
+   <para>
+    By default <application>Privoxy</application> ignores block or redirect actions
+    for its CGI pages. Intercepting these requests can be useful in multi-user
+    setups to implement fine-grained access control, but it can also render the complete
+    web interface useless and make debugging problems painful if done without care.
+   </para>
+   <para>
+    Don't enable this option unless you're sure that you really need it.
+   </para>
+  </listitem>
+ </varlistentry>
+ <varlistentry>
+  <term>Examples:</term>
+  <listitem>
+   <para>
+    allow-cgi-request-crunching 1
+   </para>
+  </listitem>
+ </varlistentry>
+</variablelist>
+<![%config-file;[<literallayout>@@allow-cgi-request-crunching 0</literallayout>]]>
+</sect3>
+
 <sect3 renderas="sect4" id="split-large-forms"><title>split-large-forms</title>
 <variablelist>
  <varlistentry>
@@ -2476,7 +2601,7 @@ forward-socks4 and forward-socks4a</title>
 <para>
  The <quote>hide-console</quote> option is specific to the MS-Win console
  version of <application>Privoxy</application>. If this option is used,
- <application>Privoxy</application> will disconnect from and hide  the
+ <application>Privoxy</application> will disconnect from and hide the
  command console.
 </para>