doc/webserver/user-manual/config.html

   1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
   2 "http://www.w3.org/TR/html4/loose.dtd">
   3
   4 <html>
   5 <head>
   6   <title>The Main Configuration File</title>
   7   <meta name="GENERATOR" content=
   8   "Modular DocBook HTML Stylesheet Version 1.79">
   9   <link rel="HOME" title="Privoxy 3.0.20 User Manual" href="index.html">
  10   <link rel="PREVIOUS" title="Privoxy Configuration" href=
  11   "configuration.html">
  12   <link rel="NEXT" title="Actions Files" href="actions-file.html">
  13   <link rel="STYLESHEET" type="text/css" href="../p_doc.css">
  14   <meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
  15   <link rel="STYLESHEET" type="text/css" href="p_doc.css">
  16 </head>
  17
  18 <body class="SECT1" bgcolor="#EEEEEE" text="#000000" link="#0000FF" vlink=
  19 "#840084" alink="#0000FF">
  20   <div class="NAVHEADER">
  21     <table summary="Header navigation table" width="100%" border="0"
  22     cellpadding="0" cellspacing="0">
  23       <tr>
  24         <th colspan="3" align="center">Privoxy 3.0.20 User Manual</th>
  25       </tr>
  26
  27       <tr>
  28         <td width="10%" align="left" valign="bottom"><a href=
  29         "configuration.html" accesskey="P">Prev</a></td>
  30
  31         <td width="80%" align="center" valign="bottom"></td>
  32
  33         <td width="10%" align="right" valign="bottom"><a href=
  34         "actions-file.html" accesskey="N">Next</a></td>
  35       </tr>
  36     </table>
  37     <hr align="left" width="100%">
  38   </div>
  39
  40   <div class="SECT1">
  41     <h1 class="SECT1"><a name="CONFIG" id="CONFIG">7. The Main Configuration
  42     File</a></h1>
  43
  44     <p>By default, the main configuration file is named <tt class=
  45     "FILENAME">config</tt>, with the exception of Windows, where it is named
  46     <tt class="FILENAME">config.txt</tt>. Configuration lines consist of an
  47     initial keyword followed by a list of values, all separated by whitespace
  48     (any number of spaces or tabs). For example:</p>
  49
  50     <p class="LITERALLAYOUT"><tt class="LITERAL">&nbsp;&nbsp;<span class=
  51     "emphasis"><i class="EMPHASIS">confdir /etc/privoxy</i></span></tt></p>
  52
  53     <p>Assigns the value <tt class="LITERAL">/etc/privoxy</tt> to the option
  54     <tt class="LITERAL">confdir</tt> and thus indicates that the
  55     configuration directory is named <span class=
  56     "QUOTE">"/etc/privoxy/"</span>.</p>
  57
  58     <p>All options in the config file except for <tt class=
  59     "LITERAL">confdir</tt> and <tt class="LITERAL">logdir</tt> are optional.
  60     Watch out in the below description for what happens if you leave them
  61     unset.</p>
  62
  63     <p>The main config file controls all aspects of <span class=
  64     "APPLICATION">Privoxy</span>'s operation that are not location dependent
  65     (i.e. they apply universally, no matter where you may be surfing). Like
  66     the filter and action files, the config file is a plain text file and can
  67     be modified with a text editor like emacs, vim or notepad.exe.</p>
  68
  69     <div class="SECT2">
  70       <h2 class="SECT2"><a name="LOCAL-SET-UP" id="LOCAL-SET-UP">7.1. Local
  71       Set-up Documentation</a></h2>
  72
  73       <p>If you intend to operate <span class="APPLICATION">Privoxy</span>
  74       for more users than just yourself, it might be a good idea to let them
  75       know how to reach you, what you block and why you do that, your
  76       policies, etc.</p>
  77
  78       <div class="SECT3">
  79         <h4 class="SECT3"><a name="USER-MANUAL" id="USER-MANUAL">7.1.1.
  80         user-manual</a></h4>
  81
  82         <div class="VARIABLELIST">
  83           <dl>
  84             <dt>Specifies:</dt>
  85
  86             <dd>
  87               <p>Location of the <span class="APPLICATION">Privoxy</span>
  88               User Manual.</p>
  89             </dd>
  90
  91             <dt>Type of value:</dt>
  92
  93             <dd>
  94               <p>A fully qualified URI</p>
  95             </dd>
  96
  97             <dt>Default value:</dt>
  98
  99             <dd>
 100               <p><span class="emphasis"><i class=
 101               "EMPHASIS">Unset</i></span></p>
 102             </dd>
 103
 104             <dt>Effect if unset:</dt>
 105
 106             <dd>
 107               <p><a href="http://www.privoxy.org/user-manual/" target=
 108               "_top">http://www.privoxy.org/<tt class=
 109               "REPLACEABLE"><i>version</i></tt>/user-manual/</a> will be
 110               used, where <tt class="REPLACEABLE"><i>version</i></tt> is the
 111               <span class="APPLICATION">Privoxy</span> version.</p>
 112             </dd>
 113
 114             <dt>Notes:</dt>
 115
 116             <dd>
 117               <p>The User Manual URI is the single best source of information
 118               on <span class="APPLICATION">Privoxy</span>, and is used for
 119               help links from some of the internal CGI pages. The manual
 120               itself is normally packaged with the binary distributions, so
 121               you probably want to set this to a locally installed copy.</p>
 122
 123               <p>Examples:</p>
 124
 125               <p>The best all purpose solution is simply to put the full
 126               local <tt class="LITERAL">PATH</tt> to where the <i class=
 127               "CITETITLE">User Manual</i> is located:</p>
 128
 129               <table border="0" bgcolor="#E0E0E0" width="90%">
 130                 <tr>
 131                   <td>
 132                     <pre class="SCREEN">
 133   user-manual  /usr/share/doc/privoxy/user-manual
 134 </pre>
 135                   </td>
 136                 </tr>
 137               </table>
 138
 139               <p>The User Manual is then available to anyone with access to
 140               <span class="APPLICATION">Privoxy</span>, by following the
 141               built-in URL: <tt class=
 142               "LITERAL">http://config.privoxy.org/user-manual/</tt> (or the
 143               shortcut: <tt class=
 144               "LITERAL">http://p.p/user-manual/</tt>).</p>
 145
 146               <p>If the documentation is not on the local system, it can be
 147               accessed from a remote server, as:</p>
 148
 149               <table border="0" bgcolor="#E0E0E0" width="90%">
 150                 <tr>
 151                   <td>
 152                     <pre class="SCREEN">
 153   user-manual  http://example.com/privoxy/user-manual/
 154 </pre>
 155                   </td>
 156                 </tr>
 157               </table>
 158
 159               <div class="WARNING">
 160                 <table class="WARNING" border="1" width="90%">
 161                   <tr>
 162                     <td align="center"><b>Warning</b></td>
 163                   </tr>
 164
 165                   <tr>
 166                     <td align="left">
 167                       <p>If set, this option should be <span class=
 168                       "emphasis"><i class="EMPHASIS">the first option in the
 169                       config file</i></span>, because it is used while the
 170                       config file is being read on start-up.</p>
 171                     </td>
 172                   </tr>
 173                 </table>
 174               </div>
 175             </dd>
 176           </dl>
 177         </div>
 178       </div>
 179
 180       <div class="SECT3">
 181         <h4 class="SECT3"><a name="TRUST-INFO-URL" id="TRUST-INFO-URL">7.1.2.
 182         trust-info-url</a></h4>
 183
 184         <div class="VARIABLELIST">
 185           <dl>
 186             <dt>Specifies:</dt>
 187
 188             <dd>
 189               <p>A URL to be displayed in the error page that users will see
 190               if access to an untrusted page is denied.</p>
 191             </dd>
 192
 193             <dt>Type of value:</dt>
 194
 195             <dd>
 196               <p>URL</p>
 197             </dd>
 198
 199             <dt>Default value:</dt>
 200
 201             <dd>
 202               <p><span class="emphasis"><i class=
 203               "EMPHASIS">Unset</i></span></p>
 204             </dd>
 205
 206             <dt>Effect if unset:</dt>
 207
 208             <dd>
 209               <p>No links are displayed on the "untrusted" error page.</p>
 210             </dd>
 211
 212             <dt>Notes:</dt>
 213
 214             <dd>
 215               <p>The value of this option only matters if the experimental
 216               trust mechanism has been activated. (See <a href=
 217               "config.html#TRUSTFILE"><span class="emphasis"><i class=
 218               "EMPHASIS">trustfile</i></span></a> below.)</p>
 219
 220               <p>If you use the trust mechanism, it is a good idea to write
 221               up some on-line documentation about your trust policy and to
 222               specify the URL(s) here. Use multiple times for multiple
 223               URLs.</p>
 224
 225               <p>The URL(s) should be added to the trustfile as well, so
 226               users don't end up locked out from the information on why they
 227               were locked out in the first place!</p>
 228             </dd>
 229           </dl>
 230         </div>
 231       </div>
 232
 233       <div class="SECT3">
 234         <h4 class="SECT3"><a name="ADMIN-ADDRESS" id="ADMIN-ADDRESS">7.1.3.
 235         admin-address</a></h4>
 236
 237         <div class="VARIABLELIST">
 238           <dl>
 239             <dt>Specifies:</dt>
 240
 241             <dd>
 242               <p>An email address to reach the <span class=
 243               "APPLICATION">Privoxy</span> administrator.</p>
 244             </dd>
 245
 246             <dt>Type of value:</dt>
 247
 248             <dd>
 249               <p>Email address</p>
 250             </dd>
 251
 252             <dt>Default value:</dt>
 253
 254             <dd>
 255               <p><span class="emphasis"><i class=
 256               "EMPHASIS">Unset</i></span></p>
 257             </dd>
 258
 259             <dt>Effect if unset:</dt>
 260
 261             <dd>
 262               <p>No email address is displayed on error pages and the CGI
 263               user interface.</p>
 264             </dd>
 265
 266             <dt>Notes:</dt>
 267
 268             <dd>
 269               <p>If both <tt class="LITERAL">admin-address</tt> and
 270               <tt class="LITERAL">proxy-info-url</tt> are unset, the whole
 271               "Local Privoxy Support" box on all generated pages will not be
 272               shown.</p>
 273             </dd>
 274           </dl>
 275         </div>
 276       </div>
 277
 278       <div class="SECT3">
 279         <h4 class="SECT3"><a name="PROXY-INFO-URL" id="PROXY-INFO-URL">7.1.4.
 280         proxy-info-url</a></h4>
 281
 282         <div class="VARIABLELIST">
 283           <dl>
 284             <dt>Specifies:</dt>
 285
 286             <dd>
 287               <p>A URL to documentation about the local <span class=
 288               "APPLICATION">Privoxy</span> setup, configuration or
 289               policies.</p>
 290             </dd>
 291
 292             <dt>Type of value:</dt>
 293
 294             <dd>
 295               <p>URL</p>
 296             </dd>
 297
 298             <dt>Default value:</dt>
 299
 300             <dd>
 301               <p><span class="emphasis"><i class=
 302               "EMPHASIS">Unset</i></span></p>
 303             </dd>
 304
 305             <dt>Effect if unset:</dt>
 306
 307             <dd>
 308               <p>No link to local documentation is displayed on error pages
 309               and the CGI user interface.</p>
 310             </dd>
 311
 312             <dt>Notes:</dt>
 313
 314             <dd>
 315               <p>If both <tt class="LITERAL">admin-address</tt> and
 316               <tt class="LITERAL">proxy-info-url</tt> are unset, the whole
 317               "Local Privoxy Support" box on all generated pages will not be
 318               shown.</p>
 319
 320               <p>This URL shouldn't be blocked ;-)</p>
 321             </dd>
 322           </dl>
 323         </div>
 324       </div>
 325     </div>
 326
 327     <div class="SECT2">
 328       <h2 class="SECT2"><a name="CONF-LOG-LOC" id="CONF-LOG-LOC">7.2.
 329       Configuration and Log File Locations</a></h2>
 330
 331       <p><span class="APPLICATION">Privoxy</span> can (and normally does) use
 332       a number of other files for additional configuration, help and logging.
 333       This section of the configuration file tells <span class=
 334       "APPLICATION">Privoxy</span> where to find those other files.</p>
 335
 336       <p>The user running <span class="APPLICATION">Privoxy</span>, must have
 337       read permission for all configuration files, and write permission to
 338       any files that would be modified, such as log files and actions
 339       files.</p>
 340
 341       <div class="SECT3">
 342         <h4 class="SECT3"><a name="CONFDIR" id="CONFDIR">7.2.1.
 343         confdir</a></h4>
 344
 345         <div class="VARIABLELIST">
 346           <dl>
 347             <dt>Specifies:</dt>
 348
 349             <dd>
 350               <p>The directory where the other configuration files are
 351               located.</p>
 352             </dd>
 353
 354             <dt>Type of value:</dt>
 355
 356             <dd>
 357               <p>Path name</p>
 358             </dd>
 359
 360             <dt>Default value:</dt>
 361
 362             <dd>
 363               <p>/etc/privoxy (Unix) <span class="emphasis"><i class=
 364               "EMPHASIS">or</i></span> <span class=
 365               "APPLICATION">Privoxy</span> installation dir (Windows)</p>
 366             </dd>
 367
 368             <dt>Effect if unset:</dt>
 369
 370             <dd>
 371               <p><span class="emphasis"><i class=
 372               "EMPHASIS">Mandatory</i></span></p>
 373             </dd>
 374
 375             <dt>Notes:</dt>
 376
 377             <dd>
 378               <p>No trailing <span class="QUOTE">"<tt class=
 379               "LITERAL">/</tt>"</span>, please.</p>
 380             </dd>
 381           </dl>
 382         </div>
 383       </div>
 384
 385       <div class="SECT3">
 386         <h4 class="SECT3"><a name="TEMPLDIR" id="TEMPLDIR">7.2.2.
 387         templdir</a></h4>
 388
 389         <div class="VARIABLELIST">
 390           <dl>
 391             <dt>Specifies:</dt>
 392
 393             <dd>
 394               <p>An alternative directory where the templates are loaded
 395               from.</p>
 396             </dd>
 397
 398             <dt>Type of value:</dt>
 399
 400             <dd>
 401               <p>Path name</p>
 402             </dd>
 403
 404             <dt>Default value:</dt>
 405
 406             <dd>
 407               <p>unset</p>
 408             </dd>
 409
 410             <dt>Effect if unset:</dt>
 411
 412             <dd>
 413               <p>The templates are assumed to be located in
 414               confdir/template.</p>
 415             </dd>
 416
 417             <dt>Notes:</dt>
 418
 419             <dd>
 420               <p><span class="APPLICATION">Privoxy's</span> original
 421               templates are usually overwritten with each update. Use this
 422               option to relocate customized templates that should be kept. As
 423               template variables might change between updates, you shouldn't
 424               expect templates to work with <span class=
 425               "APPLICATION">Privoxy</span> releases other than the one they
 426               were part of, though.</p>
 427             </dd>
 428           </dl>
 429         </div>
 430       </div>
 431
 432       <div class="SECT3">
 433         <h4 class="SECT3"><a name="LOGDIR" id="LOGDIR">7.2.3. logdir</a></h4>
 434
 435         <div class="VARIABLELIST">
 436           <dl>
 437             <dt>Specifies:</dt>
 438
 439             <dd>
 440               <p>The directory where all logging takes place (i.e. where the
 441               <tt class="FILENAME">logfile</tt> is located).</p>
 442             </dd>
 443
 444             <dt>Type of value:</dt>
 445
 446             <dd>
 447               <p>Path name</p>
 448             </dd>
 449
 450             <dt>Default value:</dt>
 451
 452             <dd>
 453               <p>/var/log/privoxy (Unix) <span class="emphasis"><i class=
 454               "EMPHASIS">or</i></span> <span class=
 455               "APPLICATION">Privoxy</span> installation dir (Windows)</p>
 456             </dd>
 457
 458             <dt>Effect if unset:</dt>
 459
 460             <dd>
 461               <p><span class="emphasis"><i class=
 462               "EMPHASIS">Mandatory</i></span></p>
 463             </dd>
 464
 465             <dt>Notes:</dt>
 466
 467             <dd>
 468               <p>No trailing <span class="QUOTE">"<tt class=
 469               "LITERAL">/</tt>"</span>, please.</p>
 470             </dd>
 471           </dl>
 472         </div>
 473       </div>
 474
 475       <div class="SECT3">
 476         <h4 class="SECT3"><a name="ACTIONSFILE" id="ACTIONSFILE">7.2.4.
 477         actionsfile</a></h4><a name="DEFAULT.ACTION" id=
 478         "DEFAULT.ACTION"></a><a name="STANDARD.ACTION" id=
 479         "STANDARD.ACTION"></a><a name="USER.ACTION" id="USER.ACTION"></a>
 480
 481         <div class="VARIABLELIST">
 482           <dl>
 483             <dt>Specifies:</dt>
 484
 485             <dd>
 486               <p>The <a href="actions-file.html">actions file(s)</a> to
 487               use</p>
 488             </dd>
 489
 490             <dt>Type of value:</dt>
 491
 492             <dd>
 493               <p>Complete file name, relative to <tt class=
 494               "LITERAL">confdir</tt></p>
 495             </dd>
 496
 497             <dt>Default values:</dt>
 498
 499             <dd>
 500               <table border="0">
 501                 <tbody>
 502                   <tr>
 503                     <td>
 504                       <p class="LITERALLAYOUT">
 505                       &nbsp;&nbsp;match-all.action&nbsp;#&nbsp;Actions&nbsp;that&nbsp;are&nbsp;applied&nbsp;to&nbsp;all&nbsp;sites&nbsp;and&nbsp;maybe&nbsp;overruled&nbsp;later&nbsp;on.</p>
 506                     </td>
 507                   </tr>
 508
 509                   <tr>
 510                     <td>
 511                       <p class="LITERALLAYOUT">
 512                       &nbsp;&nbsp;default.action&nbsp;&nbsp;&nbsp;#&nbsp;Main&nbsp;actions&nbsp;file</p>
 513                     </td>
 514                   </tr>
 515
 516                   <tr>
 517                     <td>
 518                       <p class="LITERALLAYOUT">
 519                       &nbsp;&nbsp;user.action&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;#&nbsp;User&nbsp;customizations</p>
 520                     </td>
 521                   </tr>
 522                 </tbody>
 523               </table>
 524             </dd>
 525
 526             <dt>Effect if unset:</dt>
 527
 528             <dd>
 529               <p>No actions are taken at all. More or less neutral
 530               proxying.</p>
 531             </dd>
 532
 533             <dt>Notes:</dt>
 534
 535             <dd>
 536               <p>Multiple <tt class="LITERAL">actionsfile</tt> lines are
 537               permitted, and are in fact recommended!</p>
 538
 539               <p>The default values are <tt class=
 540               "FILENAME">default.action</tt>, which is the <span class=
 541               "QUOTE">"main"</span> actions file maintained by the
 542               developers, and <tt class="FILENAME">user.action</tt>, where
 543               you can make your personal additions.</p>
 544
 545               <p>Actions files contain all the per site and per URL
 546               configuration for ad blocking, cookie management, privacy
 547               considerations, etc. There is no point in using <span class=
 548               "APPLICATION">Privoxy</span> without at least one actions
 549               file.</p>
 550
 551               <p>Note that since Privoxy 3.0.7, the complete filename,
 552               including the <span class="QUOTE">".action"</span> extension
 553               has to be specified. The syntax change was necessary to be
 554               consistent with the other file options and to allow previously
 555               forbidden characters.</p>
 556             </dd>
 557           </dl>
 558         </div>
 559       </div>
 560
 561       <div class="SECT3">
 562         <h4 class="SECT3"><a name="FILTERFILE" id="FILTERFILE">7.2.5.
 563         filterfile</a></h4><a name="DEFAULT.FILTER" id="DEFAULT.FILTER"></a>
 564
 565         <div class="VARIABLELIST">
 566           <dl>
 567             <dt>Specifies:</dt>
 568
 569             <dd>
 570               <p>The <a href="filter-file.html">filter file(s)</a> to use</p>
 571             </dd>
 572
 573             <dt>Type of value:</dt>
 574
 575             <dd>
 576               <p>File name, relative to <tt class="LITERAL">confdir</tt></p>
 577             </dd>
 578
 579             <dt>Default value:</dt>
 580
 581             <dd>
 582               <p>default.filter (Unix) <span class="emphasis"><i class=
 583               "EMPHASIS">or</i></span> default.filter.txt (Windows)</p>
 584             </dd>
 585
 586             <dt>Effect if unset:</dt>
 587
 588             <dd>
 589               <p>No textual content filtering takes place, i.e. all
 590               <tt class="LITERAL">+<a href=
 591               "actions-file.html#FILTER">filter</a>{<tt class=
 592               "REPLACEABLE"><i>name</i></tt>}</tt> actions in the actions
 593               files are turned neutral.</p>
 594             </dd>
 595
 596             <dt>Notes:</dt>
 597
 598             <dd>
 599               <p>Multiple <tt class="LITERAL">filterfile</tt> lines are
 600               permitted.</p>
 601
 602               <p>The <a href="filter-file.html">filter files</a> contain
 603               content modification rules that use <a href=
 604               "appendix.html#REGEX">regular expressions</a>. These rules
 605               permit powerful changes on the content of Web pages, and
 606               optionally the headers as well, e.g., you could try to disable
 607               your favorite JavaScript annoyances, re-write the actual
 608               displayed text, or just have some fun playing buzzword bingo
 609               with web pages.</p>
 610
 611               <p>The <tt class="LITERAL">+<a href=
 612               "actions-file.html#FILTER">filter</a>{<tt class=
 613               "REPLACEABLE"><i>name</i></tt>}</tt> actions rely on the
 614               relevant filter (<tt class="REPLACEABLE"><i>name</i></tt>) to
 615               be defined in a filter file!</p>
 616
 617               <p>A pre-defined filter file called <tt class=
 618               "FILENAME">default.filter</tt> that contains a number of useful
 619               filters for common problems is included in the distribution.
 620               See the section on the <tt class="LITERAL"><a href=
 621               "actions-file.html#FILTER">filter</a></tt> action for a
 622               list.</p>
 623
 624               <p>It is recommended to place any locally adapted filters into
 625               a separate file, such as <tt class=
 626               "FILENAME">user.filter</tt>.</p>
 627             </dd>
 628           </dl>
 629         </div>
 630       </div>
 631
 632       <div class="SECT3">
 633         <h4 class="SECT3"><a name="LOGFILE" id="LOGFILE">7.2.6.
 634         logfile</a></h4>
 635
 636         <div class="VARIABLELIST">
 637           <dl>
 638             <dt>Specifies:</dt>
 639
 640             <dd>
 641               <p>The log file to use</p>
 642             </dd>
 643
 644             <dt>Type of value:</dt>
 645
 646             <dd>
 647               <p>File name, relative to <tt class="LITERAL">logdir</tt></p>
 648             </dd>
 649
 650             <dt>Default value:</dt>
 651
 652             <dd>
 653               <p><span class="emphasis"><i class="EMPHASIS">Unset (commented
 654               out)</i></span>. When activated: logfile (Unix) <span class=
 655               "emphasis"><i class="EMPHASIS">or</i></span> privoxy.log
 656               (Windows).</p>
 657             </dd>
 658
 659             <dt>Effect if unset:</dt>
 660
 661             <dd>
 662               <p>No logfile is written.</p>
 663             </dd>
 664
 665             <dt>Notes:</dt>
 666
 667             <dd>
 668               <p>The logfile is where all logging and error messages are
 669               written. The level of detail and number of messages are set
 670               with the <tt class="LITERAL">debug</tt> option (see below). The
 671               logfile can be useful for tracking down a problem with
 672               <span class="APPLICATION">Privoxy</span> (e.g., it's not
 673               blocking an ad you think it should block) and it can help you
 674               to monitor what your browser is doing.</p>
 675
 676               <p>Depending on the debug options below, the logfile may be a
 677               privacy risk if third parties can get access to it. As most
 678               users will never look at it, <span class=
 679               "APPLICATION">Privoxy</span> 3.0.7 and later only log fatal
 680               errors by default.</p>
 681
 682               <p>For most troubleshooting purposes, you will have to change
 683               that, please refer to the debugging section for details.</p>
 684
 685               <p>Your logfile will grow indefinitely, and you will probably
 686               want to periodically remove it. On Unix systems, you can do
 687               this with a cron job (see <span class="QUOTE">"man
 688               cron"</span>).</p>
 689
 690               <p>Any log files must be writable by whatever user <span class=
 691               "APPLICATION">Privoxy</span> is being run as (on Unix, default
 692               user id is <span class="QUOTE">"privoxy"</span>).</p>
 693             </dd>
 694           </dl>
 695         </div>
 696       </div>
 697
 698       <div class="SECT3">
 699         <h4 class="SECT3"><a name="TRUSTFILE" id="TRUSTFILE">7.2.7.
 700         trustfile</a></h4>
 701
 702         <div class="VARIABLELIST">
 703           <dl>
 704             <dt>Specifies:</dt>
 705
 706             <dd>
 707               <p>The name of the trust file to use</p>
 708             </dd>
 709
 710             <dt>Type of value:</dt>
 711
 712             <dd>
 713               <p>File name, relative to <tt class="LITERAL">confdir</tt></p>
 714             </dd>
 715
 716             <dt>Default value:</dt>
 717
 718             <dd>
 719               <p><span class="emphasis"><i class="EMPHASIS">Unset (commented
 720               out)</i></span>. When activated: trust (Unix) <span class=
 721               "emphasis"><i class="EMPHASIS">or</i></span> trust.txt
 722               (Windows)</p>
 723             </dd>
 724
 725             <dt>Effect if unset:</dt>
 726
 727             <dd>
 728               <p>The entire trust mechanism is disabled.</p>
 729             </dd>
 730
 731             <dt>Notes:</dt>
 732
 733             <dd>
 734               <p>The trust mechanism is an experimental feature for building
 735               white-lists and should be used with care. It is <span class=
 736               "emphasis"><i class="EMPHASIS">NOT</i></span> recommended for
 737               the casual user.</p>
 738
 739               <p>If you specify a trust file, <span class=
 740               "APPLICATION">Privoxy</span> will only allow access to sites
 741               that are specified in the trustfile. Sites can be listed in one
 742               of two ways:</p>
 743
 744               <p>Prepending a <tt class="LITERAL">~</tt> character limits
 745               access to this site only (and any sub-paths within this site),
 746               e.g. <tt class="LITERAL">~www.example.com</tt> allows access to
 747               <tt class="LITERAL">~www.example.com/features/news.html</tt>,
 748               etc.</p>
 749
 750               <p>Or, you can designate sites as <span class=
 751               "emphasis"><i class="EMPHASIS">trusted referrers</i></span>, by
 752               prepending the name with a <tt class="LITERAL">+</tt>
 753               character. The effect is that access to untrusted sites will be
 754               granted -- but only if a link from this trusted referrer was
 755               used to get there. The link target will then be added to the
 756               <span class="QUOTE">"trustfile"</span> so that future, direct
 757               accesses will be granted. Sites added via this mechanism do not
 758               become trusted referrers themselves (i.e. they are added with a
 759               <tt class="LITERAL">~</tt> designation). There is a limit of
 760               512 such entries, after which new entries will not be made.</p>
 761
 762               <p>If you use the <tt class="LITERAL">+</tt> operator in the
 763               trust file, it may grow considerably over time.</p>
 764
 765               <p>It is recommended that <span class=
 766               "APPLICATION">Privoxy</span> be compiled with the <tt class=
 767               "LITERAL">--disable-force</tt>, <tt class=
 768               "LITERAL">--disable-toggle</tt> and <tt class=
 769               "LITERAL">--disable-editor</tt> options, if this feature is to
 770               be used.</p>
 771
 772               <p>Possible applications include limiting Internet access for
 773               children.</p>
 774             </dd>
 775           </dl>
 776         </div>
 777       </div>
 778     </div>
 779
 780     <div class="SECT2">
 781       <h2 class="SECT2"><a name="DEBUGGING" id="DEBUGGING">7.3.
 782       Debugging</a></h2>
 783
 784       <p>These options are mainly useful when tracing a problem. Note that
 785       you might also want to invoke <span class="APPLICATION">Privoxy</span>
 786       with the <tt class="LITERAL">--no-daemon</tt> command line option when
 787       debugging.</p>
 788
 789       <div class="SECT3">
 790         <h4 class="SECT3"><a name="DEBUG" id="DEBUG">7.3.1. debug</a></h4>
 791
 792         <div class="VARIABLELIST">
 793           <dl>
 794             <dt>Specifies:</dt>
 795
 796             <dd>
 797               <p>Key values that determine what information gets logged.</p>
 798             </dd>
 799
 800             <dt>Type of value:</dt>
 801
 802             <dd>
 803               <p>Integer values</p>
 804             </dd>
 805
 806             <dt>Default value:</dt>
 807
 808             <dd>
 809               <p>0 (i.e.: only fatal errors (that cause Privoxy to exit) are
 810               logged)</p>
 811             </dd>
 812
 813             <dt>Effect if unset:</dt>
 814
 815             <dd>
 816               <p>Default value is used (see above).</p>
 817             </dd>
 818
 819             <dt>Notes:</dt>
 820
 821             <dd>
 822               <p>The available debug levels are:</p>
 823
 824               <table border="0" bgcolor="#E0E0E0" width="90%">
 825                 <tr>
 826                   <td>
 827                     <pre class="PROGRAMLISTING">
 828   debug     1 # Log the destination for each request <span class=
 829 "APPLICATION">Privoxy</span> let through. See also debug 1024.
 830   debug     2 # show each connection status
 831   debug     4 # show I/O status
 832   debug     8 # show header parsing
 833   debug    16 # log all data written to the network
 834   debug    32 # debug force feature
 835   debug    64 # debug regular expression filters
 836   debug   128 # debug redirects
 837   debug   256 # debug GIF de-animation
 838   debug   512 # Common Log Format
 839   debug  1024 # Log the destination for requests <span class=
 840 "APPLICATION">Privoxy</span> didn't let through, and the reason why.
 841   debug  2048 # CGI user interface
 842   debug  4096 # Startup banner and warnings.
 843   debug  8192 # Non-fatal errors
 844   debug 32768 # log all data read from the network
 845   debug 65536 # Log the applying actions
 846 </pre>
 847                   </td>
 848                 </tr>
 849               </table>
 850
 851               <p>To select multiple debug levels, you can either add them or
 852               use multiple <tt class="LITERAL">debug</tt> lines.</p>
 853
 854               <p>A debug level of 1 is informative because it will show you
 855               each request as it happens. <span class="emphasis"><i class=
 856               "EMPHASIS">1, 1024, 4096 and 8192 are recommended</i></span> so
 857               that you will notice when things go wrong. The other levels are
 858               probably only of interest if you are hunting down a specific
 859               problem. They can produce a hell of an output (especially
 860               16).</p>
 861
 862               <p><span class="APPLICATION">Privoxy</span> used to ship with
 863               the debug levels recommended above enabled by default, but due
 864               to privacy concerns 3.0.7 and later are configured to only log
 865               fatal errors.</p>
 866
 867               <p>If you are used to the more verbose settings, simply enable
 868               the debug lines below again.</p>
 869
 870               <p>If you want to use pure CLF (Common Log Format), you should
 871               set <span class="QUOTE">"debug 512"</span> <span class=
 872               "emphasis"><i class="EMPHASIS">ONLY</i></span> and not enable
 873               anything else.</p>
 874
 875               <p><span class="APPLICATION">Privoxy</span> has a hard-coded
 876               limit for the length of log messages. If it's reached, messages
 877               are logged truncated and marked with <span class="QUOTE">"...
 878               [too long, truncated]"</span>.</p>
 879
 880               <p>Please don't file any support requests without trying to
 881               reproduce the problem with increased debug level first. Once
 882               you read the log messages, you may even be able to solve the
 883               problem on your own.</p>
 884             </dd>
 885           </dl>
 886         </div>
 887       </div>
 888
 889       <div class="SECT3">
 890         <h4 class="SECT3"><a name="SINGLE-THREADED" id=
 891         "SINGLE-THREADED">7.3.2. single-threaded</a></h4>
 892
 893         <div class="VARIABLELIST">
 894           <dl>
 895             <dt>Specifies:</dt>
 896
 897             <dd>
 898               <p>Whether to run only one server thread.</p>
 899             </dd>
 900
 901             <dt>Type of value:</dt>
 902
 903             <dd>
 904               <p><span class="emphasis"><i class=
 905               "EMPHASIS">None</i></span></p>
 906             </dd>
 907
 908             <dt>Default value:</dt>
 909
 910             <dd>
 911               <p><span class="emphasis"><i class=
 912               "EMPHASIS">Unset</i></span></p>
 913             </dd>
 914
 915             <dt>Effect if unset:</dt>
 916
 917             <dd>
 918               <p>Multi-threaded (or, where unavailable: forked) operation,
 919               i.e. the ability to serve multiple requests simultaneously.</p>
 920             </dd>
 921
 922             <dt>Notes:</dt>
 923
 924             <dd>
 925               <p>This option is only there for debugging purposes.
 926               <span class="emphasis"><i class="EMPHASIS">It will drastically
 927               reduce performance.</i></span></p>
 928             </dd>
 929           </dl>
 930         </div>
 931       </div>
 932
 933       <div class="SECT3">
 934         <h4 class="SECT3"><a name="HOSTNAME" id="HOSTNAME">7.3.3.
 935         hostname</a></h4>
 936
 937         <div class="VARIABLELIST">
 938           <dl>
 939             <dt>Specifies:</dt>
 940
 941             <dd>
 942               <p>The hostname shown on the CGI pages.</p>
 943             </dd>
 944
 945             <dt>Type of value:</dt>
 946
 947             <dd>
 948               <p>Text</p>
 949             </dd>
 950
 951             <dt>Default value:</dt>
 952
 953             <dd>
 954               <p><span class="emphasis"><i class=
 955               "EMPHASIS">Unset</i></span></p>
 956             </dd>
 957
 958             <dt>Effect if unset:</dt>
 959
 960             <dd>
 961               <p>The hostname provided by the operating system is used.</p>
 962             </dd>
 963
 964             <dt>Notes:</dt>
 965
 966             <dd>
 967               <p>On some misconfigured systems resolving the hostname fails
 968               or takes too much time and slows Privoxy down. Setting a fixed
 969               hostname works around the problem.</p>
 970
 971               <p>In other circumstances it might be desirable to show a
 972               hostname other than the one returned by the operating system.
 973               For example if the system has several different hostnames and
 974               you don't want to use the first one.</p>
 975
 976               <p>Note that Privoxy does not validate the specified hostname
 977               value.</p>
 978             </dd>
 979           </dl>
 980         </div>
 981       </div>
 982     </div>
 983
 984     <div class="SECT2">
 985       <h2 class="SECT2"><a name="ACCESS-CONTROL" id="ACCESS-CONTROL">7.4.
 986       Access Control and Security</a></h2>
 987
 988       <p>This section of the config file controls the security-relevant
 989       aspects of <span class="APPLICATION">Privoxy</span>'s
 990       configuration.</p>
 991
 992       <div class="SECT3">
 993         <h4 class="SECT3"><a name="LISTEN-ADDRESS" id="LISTEN-ADDRESS">7.4.1.
 994         listen-address</a></h4>
 995
 996         <div class="VARIABLELIST">
 997           <dl>
 998             <dt>Specifies:</dt>
 999
1000             <dd>
1001               <p>The address and TCP port on which <span class=
1002               "APPLICATION">Privoxy</span> will listen for client
1003               requests.</p>
1004             </dd>
1005
1006             <dt>Type of value:</dt>
1007
1008             <dd>
1009               <p>[<tt class="REPLACEABLE"><i>IP-Address</i></tt>]:<tt class=
1010               "REPLACEABLE"><i>Port</i></tt></p>
1011
1012               <p>[<tt class="REPLACEABLE"><i>Hostname</i></tt>]:<tt class=
1013               "REPLACEABLE"><i>Port</i></tt></p>
1014             </dd>
1015
1016             <dt>Default value:</dt>
1017
1018             <dd>
1019               <p>127.0.0.1:8118</p>
1020             </dd>
1021
1022             <dt>Effect if unset:</dt>
1023
1024             <dd>
1025               <p>Bind to 127.0.0.1 (IPv4 localhost), port 8118. This is
1026               suitable and recommended for home users who run <span class=
1027               "APPLICATION">Privoxy</span> on the same machine as their
1028               browser.</p>
1029             </dd>
1030
1031             <dt>Notes:</dt>
1032
1033             <dd>
1034               <p>You will need to configure your browser(s) to this proxy
1035               address and port.</p>
1036
1037               <p>If you already have another service running on port 8118, or
1038               if you want to serve requests from other machines (e.g. on your
1039               local network) as well, you will need to override the
1040               default.</p>
1041
1042               <p>You can use this statement multiple times to make
1043               <span class="APPLICATION">Privoxy</span> listen on more ports
1044               or more <abbr class="ABBREV">IP</abbr> addresses. Suitable if
1045               your operating system does not support sharing <abbr class=
1046               "ABBREV">IPv6</abbr> and <abbr class="ABBREV">IPv4</abbr>
1047               protocols on the same socket.</p>
1048
1049               <p>If a hostname is used instead of an IP address, <span class=
1050               "APPLICATION">Privoxy</span> will try to resolve it to an IP
1051               address and if there are multiple, use the first one
1052               returned.</p>
1053
1054               <p>If the address for the hostname isn't already known on the
1055               system (for example because it's in /etc/hostname), this may
1056               result in DNS traffic.</p>
1057
1058               <p>If the specified address isn't available on the system, or
1059               if the hostname can't be resolved, <span class=
1060               "APPLICATION">Privoxy</span> will fail to start.</p>
1061
1062               <p>IPv6 addresses containing colons have to be quoted by
1063               brackets. They can only be used if <span class=
1064               "APPLICATION">Privoxy</span> has been compiled with IPv6
1065               support. If you aren't sure if your version supports it, have a
1066               look at <tt class=
1067               "LITERAL">http://config.privoxy.org/show-status</tt>.</p>
1068
1069               <p>Some operating systems will prefer IPv6 to IPv4 addresses
1070               even if the system has no IPv6 connectivity which is usually
1071               not expected by the user. Some even rely on DNS to resolve
1072               localhost which mean the "localhost" address used may not
1073               actually be local.</p>
1074
1075               <p>It is therefore recommended to explicitly configure the
1076               intended IP address instead of relying on the operating system,
1077               unless there's a strong reason not to.</p>
1078
1079               <p>If you leave out the address, <span class=
1080               "APPLICATION">Privoxy</span> will bind to all IPv4 interfaces
1081               (addresses) on your machine and may become reachable from the
1082               Internet and/or the local network. Be aware that some GNU/Linux
1083               distributions modify that behaviour without updating the
1084               documentation. Check for non-standard patches if your
1085               <span class="APPLICATION">Privoxy</span> version behaves
1086               differently.</p>
1087
1088               <p>If you configure <span class="APPLICATION">Privoxy</span> to
1089               be reachable from the network, consider using <a href=
1090               "config.html#ACLS">access control lists</a> (ACL's, see below),
1091               and/or a firewall.</p>
1092
1093               <p>If you open <span class="APPLICATION">Privoxy</span> to
1094               untrusted users, you will also want to make sure that the
1095               following actions are disabled: <tt class="LITERAL"><a href=
1096               "config.html#ENABLE-EDIT-ACTIONS">enable-edit-actions</a></tt>
1097               and <tt class="LITERAL"><a href=
1098               "config.html#ENABLE-REMOTE-TOGGLE">enable-remote-toggle</a></tt></p>
1099             </dd>
1100
1101             <dt>Example:</dt>
1102
1103             <dd>
1104               <p>Suppose you are running <span class=
1105               "APPLICATION">Privoxy</span> on a machine which has the address
1106               192.168.0.1 on your local private network (192.168.0.0) and has
1107               another outside connection with a different address. You want
1108               it to serve requests from inside only:</p>
1109
1110               <table border="0" bgcolor="#E0E0E0" width="90%">
1111                 <tr>
1112                   <td>
1113                     <pre class="PROGRAMLISTING">
1114   listen-address  192.168.0.1:8118
1115 </pre>
1116                   </td>
1117                 </tr>
1118               </table>
1119
1120               <p>Suppose you are running <span class=
1121               "APPLICATION">Privoxy</span> on an IPv6-capable machine and you
1122               want it to listen on the IPv6 address of the loopback
1123               device:</p>
1124
1125               <table border="0" bgcolor="#E0E0E0" width="90%">
1126                 <tr>
1127                   <td>
1128                     <pre class="PROGRAMLISTING">
1129   listen-address [::1]:8118
1130 </pre>
1131                   </td>
1132                 </tr>
1133               </table>
1134             </dd>
1135           </dl>
1136         </div>
1137       </div>
1138
1139       <div class="SECT3">
1140         <h4 class="SECT3"><a name="TOGGLE" id="TOGGLE">7.4.2. toggle</a></h4>
1141
1142         <div class="VARIABLELIST">
1143           <dl>
1144             <dt>Specifies:</dt>
1145
1146             <dd>
1147               <p>Initial state of "toggle" status</p>
1148             </dd>
1149
1150             <dt>Type of value:</dt>
1151
1152             <dd>
1153               <p>1 or 0</p>
1154             </dd>
1155
1156             <dt>Default value:</dt>
1157
1158             <dd>
1159               <p>1</p>
1160             </dd>
1161
1162             <dt>Effect if unset:</dt>
1163
1164             <dd>
1165               <p>Act as if toggled on</p>
1166             </dd>
1167
1168             <dt>Notes:</dt>
1169
1170             <dd>
1171               <p>If set to 0, <span class="APPLICATION">Privoxy</span> will
1172               start in <span class="QUOTE">"toggled off"</span> mode, i.e.
1173               mostly behave like a normal, content-neutral proxy with both ad
1174               blocking and content filtering disabled. See <tt class=
1175               "LITERAL">enable-remote-toggle</tt> below.</p>
1176
1177               <p>The windows version will only display the toggle icon in the
1178               system tray if this option is present.</p>
1179             </dd>
1180           </dl>
1181         </div>
1182       </div>
1183
1184       <div class="SECT3">
1185         <h4 class="SECT3"><a name="ENABLE-REMOTE-TOGGLE" id=
1186         "ENABLE-REMOTE-TOGGLE">7.4.3. enable-remote-toggle</a></h4>
1187
1188         <div class="VARIABLELIST">
1189           <dl>
1190             <dt>Specifies:</dt>
1191
1192             <dd>
1193               <p>Whether or not the <a href=
1194               "http://config.privoxy.org/toggle" target="_top">web-based
1195               toggle feature</a> may be used</p>
1196             </dd>
1197
1198             <dt>Type of value:</dt>
1199
1200             <dd>
1201               <p>0 or 1</p>
1202             </dd>
1203
1204             <dt>Default value:</dt>
1205
1206             <dd>
1207               <p>0</p>
1208             </dd>
1209
1210             <dt>Effect if unset:</dt>
1211
1212             <dd>
1213               <p>The web-based toggle feature is disabled.</p>
1214             </dd>
1215
1216             <dt>Notes:</dt>
1217
1218             <dd>
1219               <p>When toggled off, <span class="APPLICATION">Privoxy</span>
1220               mostly acts like a normal, content-neutral proxy, i.e. doesn't
1221               block ads or filter content.</p>
1222
1223               <p>Access to the toggle feature can <span class=
1224               "emphasis"><i class="EMPHASIS">not</i></span> be controlled
1225               separately by <span class="QUOTE">"ACLs"</span> or HTTP
1226               authentication, so that everybody who can access <span class=
1227               "APPLICATION">Privoxy</span> (see <span class=
1228               "QUOTE">"ACLs"</span> and <tt class=
1229               "LITERAL">listen-address</tt> above) can toggle it for all
1230               users. So this option is <span class="emphasis"><i class=
1231               "EMPHASIS">not recommended</i></span> for multi-user
1232               environments with untrusted users.</p>
1233
1234               <p>Note that malicious client side code (e.g Java) is also
1235               capable of using this option.</p>
1236
1237               <p>As a lot of <span class="APPLICATION">Privoxy</span> users
1238               don't read documentation, this feature is disabled by
1239               default.</p>
1240
1241               <p>Note that you must have compiled <span class=
1242               "APPLICATION">Privoxy</span> with support for this feature,
1243               otherwise this option has no effect.</p>
1244             </dd>
1245           </dl>
1246         </div>
1247       </div>
1248
1249       <div class="SECT3">
1250         <h4 class="SECT3"><a name="ENABLE-REMOTE-HTTP-TOGGLE" id=
1251         "ENABLE-REMOTE-HTTP-TOGGLE">7.4.4. enable-remote-http-toggle</a></h4>
1252
1253         <div class="VARIABLELIST">
1254           <dl>
1255             <dt>Specifies:</dt>
1256
1257             <dd>
1258               <p>Whether or not Privoxy recognizes special HTTP headers to
1259               change its behaviour.</p>
1260             </dd>
1261
1262             <dt>Type of value:</dt>
1263
1264             <dd>
1265               <p>0 or 1</p>
1266             </dd>
1267
1268             <dt>Default value:</dt>
1269
1270             <dd>
1271               <p>0</p>
1272             </dd>
1273
1274             <dt>Effect if unset:</dt>
1275
1276             <dd>
1277               <p>Privoxy ignores special HTTP headers.</p>
1278             </dd>
1279
1280             <dt>Notes:</dt>
1281
1282             <dd>
1283               <p>When toggled on, the client can change <span class=
1284               "APPLICATION">Privoxy's</span> behaviour by setting special
1285               HTTP headers. Currently the only supported special header is
1286               <span class="QUOTE">"X-Filter: No"</span>, to disable filtering
1287               for the ongoing request, even if it is enabled in one of the
1288               action files.</p>
1289
1290               <p>This feature is disabled by default. If you are using
1291               <span class="APPLICATION">Privoxy</span> in a environment with
1292               trusted clients, you may enable this feature at your
1293               discretion. Note that malicious client side code (e.g Java) is
1294               also capable of using this feature.</p>
1295
1296               <p>This option will be removed in future releases as it has
1297               been obsoleted by the more general header taggers.</p>
1298             </dd>
1299           </dl>
1300         </div>
1301       </div>
1302
1303       <div class="SECT3">
1304         <h4 class="SECT3"><a name="ENABLE-EDIT-ACTIONS" id=
1305         "ENABLE-EDIT-ACTIONS">7.4.5. enable-edit-actions</a></h4>
1306
1307         <div class="VARIABLELIST">
1308           <dl>
1309             <dt>Specifies:</dt>
1310
1311             <dd>
1312               <p>Whether or not the <a href=
1313               "http://config.privoxy.org/show-status" target="_top">web-based
1314               actions file editor</a> may be used</p>
1315             </dd>
1316
1317             <dt>Type of value:</dt>
1318
1319             <dd>
1320               <p>0 or 1</p>
1321             </dd>
1322
1323             <dt>Default value:</dt>
1324
1325             <dd>
1326               <p>0</p>
1327             </dd>
1328
1329             <dt>Effect if unset:</dt>
1330
1331             <dd>
1332               <p>The web-based actions file editor is disabled.</p>
1333             </dd>
1334
1335             <dt>Notes:</dt>
1336
1337             <dd>
1338               <p>Access to the editor can <span class="emphasis"><i class=
1339               "EMPHASIS">not</i></span> be controlled separately by
1340               <span class="QUOTE">"ACLs"</span> or HTTP authentication, so
1341               that everybody who can access <span class=
1342               "APPLICATION">Privoxy</span> (see <span class=
1343               "QUOTE">"ACLs"</span> and <tt class=
1344               "LITERAL">listen-address</tt> above) can modify its
1345               configuration for all users.</p>
1346
1347               <p>This option is <span class="emphasis"><i class=
1348               "EMPHASIS">not recommended</i></span> for environments with
1349               untrusted users and as a lot of <span class=
1350               "APPLICATION">Privoxy</span> users don't read documentation,
1351               this feature is disabled by default.</p>
1352
1353               <p>Note that malicious client side code (e.g Java) is also
1354               capable of using the actions editor and you shouldn't enable
1355               this options unless you understand the consequences and are
1356               sure your browser is configured correctly.</p>
1357
1358               <p>Note that you must have compiled <span class=
1359               "APPLICATION">Privoxy</span> with support for this feature,
1360               otherwise this option has no effect.</p>
1361             </dd>
1362           </dl>
1363         </div>
1364       </div>
1365
1366       <div class="SECT3">
1367         <h4 class="SECT3"><a name="ENFORCE-BLOCKS" id="ENFORCE-BLOCKS">7.4.6.
1368         enforce-blocks</a></h4>
1369
1370         <div class="VARIABLELIST">
1371           <dl>
1372             <dt>Specifies:</dt>
1373
1374             <dd>
1375               <p>Whether the user is allowed to ignore blocks and can
1376               <span class="QUOTE">"go there anyway"</span>.</p>
1377             </dd>
1378
1379             <dt>Type of value:</dt>
1380
1381             <dd>
1382               <p><tt class="REPLACEABLE"><i>0 or 1</i></tt></p>
1383             </dd>
1384
1385             <dt>Default value:</dt>
1386
1387             <dd>
1388               <p><span class="emphasis"><i class="EMPHASIS">0</i></span></p>
1389             </dd>
1390
1391             <dt>Effect if unset:</dt>
1392
1393             <dd>
1394               <p>Blocks are not enforced.</p>
1395             </dd>
1396
1397             <dt>Notes:</dt>
1398
1399             <dd>
1400               <p><span class="APPLICATION">Privoxy</span> is mainly used to
1401               block and filter requests as a service to the user, for example
1402               to block ads and other junk that clogs the pipes. <span class=
1403               "APPLICATION">Privoxy's</span> configuration isn't perfect and
1404               sometimes innocent pages are blocked. In this situation it
1405               makes sense to allow the user to enforce the request and have
1406               <span class="APPLICATION">Privoxy</span> ignore the block.</p>
1407
1408               <p>In the default configuration <span class=
1409               "APPLICATION">Privoxy's</span> <span class=
1410               "QUOTE">"Blocked"</span> page contains a <span class=
1411               "QUOTE">"go there anyway"</span> link to adds a special string
1412               (the force prefix) to the request URL. If that link is used,
1413               <span class="APPLICATION">Privoxy</span> will detect the force
1414               prefix, remove it again and let the request pass.</p>
1415
1416               <p>Of course <span class="APPLICATION">Privoxy</span> can also
1417               be used to enforce a network policy. In that case the user
1418               obviously should not be able to bypass any blocks, and that's
1419               what the <span class="QUOTE">"enforce-blocks"</span> option is
1420               for. If it's enabled, <span class="APPLICATION">Privoxy</span>
1421               hides the <span class="QUOTE">"go there anyway"</span> link. If
1422               the user adds the force prefix by hand, it will not be accepted
1423               and the circumvention attempt is logged.</p>
1424             </dd>
1425
1426             <dt>Examples:</dt>
1427
1428             <dd>
1429               <p>enforce-blocks 1</p>
1430             </dd>
1431           </dl>
1432         </div>
1433       </div>
1434
1435       <div class="SECT3">
1436         <h4 class="SECT3"><a name="ACLS" id="ACLS">7.4.7. ACLs: permit-access
1437         and deny-access</a></h4><a name="PERMIT-ACCESS" id=
1438         "PERMIT-ACCESS"></a><a name="DENY-ACCESS" id="DENY-ACCESS"></a>
1439
1440         <div class="VARIABLELIST">
1441           <dl>
1442             <dt>Specifies:</dt>
1443
1444             <dd>
1445               <p>Who can access what.</p>
1446             </dd>
1447
1448             <dt>Type of value:</dt>
1449
1450             <dd>
1451               <p><tt class="REPLACEABLE"><i>src_addr</i></tt>[:<tt class=
1452               "REPLACEABLE"><i>port</i></tt>][/<tt class=
1453               "REPLACEABLE"><i>src_masklen</i></tt>] [<tt class=
1454               "REPLACEABLE"><i>dst_addr</i></tt>[:<tt class=
1455               "REPLACEABLE"><i>port</i></tt>][/<tt class=
1456               "REPLACEABLE"><i>dst_masklen</i></tt>]]</p>
1457
1458               <p>Where <tt class="REPLACEABLE"><i>src_addr</i></tt> and
1459               <tt class="REPLACEABLE"><i>dst_addr</i></tt> are IPv4 addresses
1460               in dotted decimal notation or valid DNS names, <tt class=
1461               "REPLACEABLE"><i>port</i></tt> is a port number, and <tt class=
1462               "REPLACEABLE"><i>src_masklen</i></tt> and <tt class=
1463               "REPLACEABLE"><i>dst_masklen</i></tt> are subnet masks in CIDR
1464               notation, i.e. integer values from 2 to 30 representing the
1465               length (in bits) of the network address. The masks and the
1466               whole destination part are optional.</p>
1467
1468               <p>If your system implements <a href=
1469               "http://tools.ietf.org/html/rfc3493" target="_top">RFC
1470               3493</a>, then <tt class="REPLACEABLE"><i>src_addr</i></tt> and
1471               <tt class="REPLACEABLE"><i>dst_addr</i></tt> can be IPv6
1472               addresses delimeted by brackets, <tt class=
1473               "REPLACEABLE"><i>port</i></tt> can be a number or a service
1474               name, and <tt class="REPLACEABLE"><i>src_masklen</i></tt> and
1475               <tt class="REPLACEABLE"><i>dst_masklen</i></tt> can be a number
1476               from 0 to 128.</p>
1477             </dd>
1478
1479             <dt>Default value:</dt>
1480
1481             <dd>
1482               <p><span class="emphasis"><i class=
1483               "EMPHASIS">Unset</i></span></p>
1484
1485               <p>If no <tt class="REPLACEABLE"><i>port</i></tt> is specified,
1486               any port will match. If no <tt class=
1487               "REPLACEABLE"><i>src_masklen</i></tt> or <tt class=
1488               "REPLACEABLE"><i>src_masklen</i></tt> is given, the complete IP
1489               address has to match (i.e. 32 bits for IPv4 and 128 bits for
1490               IPv6).</p>
1491             </dd>
1492
1493             <dt>Effect if unset:</dt>
1494
1495             <dd>
1496               <p>Don't restrict access further than implied by <tt class=
1497               "LITERAL">listen-address</tt></p>
1498             </dd>
1499
1500             <dt>Notes:</dt>
1501
1502             <dd>
1503               <p>Access controls are included at the request of ISPs and
1504               systems administrators, and <span class="emphasis"><i class=
1505               "EMPHASIS">are not usually needed by individual
1506               users</i></span>. For a typical home user, it will normally
1507               suffice to ensure that <span class="APPLICATION">Privoxy</span>
1508               only listens on the localhost (127.0.0.1) or internal (home)
1509               network address by means of the <a href=
1510               "config.html#LISTEN-ADDRESS"><span class="emphasis"><i class=
1511               "EMPHASIS">listen-address</i></span></a> option.</p>
1512
1513               <p>Please see the warnings in the FAQ that <span class=
1514               "APPLICATION">Privoxy</span> is not intended to be a substitute
1515               for a firewall or to encourage anyone to defer addressing basic
1516               security weaknesses.</p>
1517
1518               <p>Multiple ACL lines are OK. If any ACLs are specified,
1519               <span class="APPLICATION">Privoxy</span> only talks to IP
1520               addresses that match at least one <tt class=
1521               "LITERAL">permit-access</tt> line and don't match any
1522               subsequent <tt class="LITERAL">deny-access</tt> line. In other
1523               words, the last match wins, with the default being <tt class=
1524               "LITERAL">deny-access</tt>.</p>
1525
1526               <p>If <span class="APPLICATION">Privoxy</span> is using a
1527               forwarder (see <tt class="LITERAL">forward</tt> below) for a
1528               particular destination URL, the <tt class=
1529               "REPLACEABLE"><i>dst_addr</i></tt> that is examined is the
1530               address of the forwarder and <span class="emphasis"><i class=
1531               "EMPHASIS">NOT</i></span> the address of the ultimate target.
1532               This is necessary because it may be impossible for the local
1533               <span class="APPLICATION">Privoxy</span> to determine the IP
1534               address of the ultimate target (that's often what gateways are
1535               used for).</p>
1536
1537               <p>You should prefer using IP addresses over DNS names, because
1538               the address lookups take time. All DNS names must resolve! You
1539               can <span class="emphasis"><i class="EMPHASIS">not</i></span>
1540               use domain patterns like <span class="QUOTE">"*.org"</span> or
1541               partial domain names. If a DNS name resolves to multiple IP
1542               addresses, only the first one is used.</p>
1543
1544               <p>Some systems allow IPv4 clients to connect to IPv6 server
1545               sockets. Then the client's IPv4 address will be translated by
1546               the system into IPv6 address space with special prefix
1547               ::ffff:0:0/96 (so called IPv4 mapped IPv6 address).
1548               <span class="APPLICATION">Privoxy</span> can handle it and maps
1549               such ACL addresses automatically.</p>
1550
1551               <p>Denying access to particular sites by ACL may have undesired
1552               side effects if the site in question is hosted on a machine
1553               which also hosts other sites (most sites are).</p>
1554             </dd>
1555
1556             <dt>Examples:</dt>
1557
1558             <dd>
1559               <p>Explicitly define the default behavior if no ACL and
1560               <tt class="LITERAL">listen-address</tt> are set: <span class=
1561               "QUOTE">"localhost"</span> is OK. The absence of a <tt class=
1562               "REPLACEABLE"><i>dst_addr</i></tt> implies that <span class=
1563               "emphasis"><i class="EMPHASIS">all</i></span> destination
1564               addresses are OK:</p>
1565
1566               <table border="0" bgcolor="#E0E0E0" width="90%">
1567                 <tr>
1568                   <td>
1569                     <pre class="SCREEN">
1570   permit-access  localhost
1571 </pre>
1572                   </td>
1573                 </tr>
1574               </table>
1575
1576               <p>Allow any host on the same class C subnet as www.privoxy.org
1577               access to nothing but www.example.com (or other domains hosted
1578               on the same system):</p>
1579
1580               <table border="0" bgcolor="#E0E0E0" width="90%">
1581                 <tr>
1582                   <td>
1583                     <pre class="SCREEN">
1584   permit-access  www.privoxy.org/24 www.example.com/32
1585 </pre>
1586                   </td>
1587                 </tr>
1588               </table>
1589
1590               <p>Allow access from any host on the 26-bit subnet
1591               192.168.45.64 to anywhere, with the exception that
1592               192.168.45.73 may not access the IP address behind
1593               www.dirty-stuff.example.com:</p>
1594
1595               <table border="0" bgcolor="#E0E0E0" width="90%">
1596                 <tr>
1597                   <td>
1598                     <pre class="SCREEN">
1599   permit-access  192.168.45.64/26
1600   deny-access    192.168.45.73    www.dirty-stuff.example.com
1601 </pre>
1602                   </td>
1603                 </tr>
1604               </table>
1605
1606               <p>Allow access from the IPv4 network 192.0.2.0/24 even if
1607               listening on an IPv6 wild card address (not supported on all
1608               platforms):</p>
1609
1610               <table border="0" bgcolor="#E0E0E0" width="90%">
1611                 <tr>
1612                   <td>
1613                     <pre class="PROGRAMLISTING">
1614   permit-access  192.0.2.0/24
1615 </pre>
1616                   </td>
1617                 </tr>
1618               </table>
1619
1620               <p>This is equivalent to the following line even if listening
1621               on an IPv4 address (not supported on all platforms):</p>
1622
1623               <table border="0" bgcolor="#E0E0E0" width="90%">
1624                 <tr>
1625                   <td>
1626                     <pre class="PROGRAMLISTING">
1627   permit-access  [::ffff:192.0.2.0]/120
1628 </pre>
1629                   </td>
1630                 </tr>
1631               </table>
1632             </dd>
1633           </dl>
1634         </div>
1635       </div>
1636
1637       <div class="SECT3">
1638         <h4 class="SECT3"><a name="BUFFER-LIMIT" id="BUFFER-LIMIT">7.4.8.
1639         buffer-limit</a></h4>
1640
1641         <div class="VARIABLELIST">
1642           <dl>
1643             <dt>Specifies:</dt>
1644
1645             <dd>
1646               <p>Maximum size of the buffer for content filtering.</p>
1647             </dd>
1648
1649             <dt>Type of value:</dt>
1650
1651             <dd>
1652               <p>Size in Kbytes</p>
1653             </dd>
1654
1655             <dt>Default value:</dt>
1656
1657             <dd>
1658               <p>4096</p>
1659             </dd>
1660
1661             <dt>Effect if unset:</dt>
1662
1663             <dd>
1664               <p>Use a 4MB (4096 KB) limit.</p>
1665             </dd>
1666
1667             <dt>Notes:</dt>
1668
1669             <dd>
1670               <p>For content filtering, i.e. the <tt class=
1671               "LITERAL">+filter</tt> and <tt class=
1672               "LITERAL">+deanimate-gif</tt> actions, it is necessary that
1673               <span class="APPLICATION">Privoxy</span> buffers the entire
1674               document body. This can be potentially dangerous, since a
1675               server could just keep sending data indefinitely and wait for
1676               your RAM to exhaust -- with nasty consequences. Hence this
1677               option.</p>
1678
1679               <p>When a document buffer size reaches the <tt class=
1680               "LITERAL">buffer-limit</tt>, it is flushed to the client
1681               unfiltered and no further attempt to filter the rest of the
1682               document is made. Remember that there may be multiple threads
1683               running, which might require up to <tt class=
1684               "LITERAL">buffer-limit</tt> Kbytes <span class=
1685               "emphasis"><i class="EMPHASIS">each</i></span>, unless you have
1686               enabled <span class="QUOTE">"single-threaded"</span> above.</p>
1687             </dd>
1688           </dl>
1689         </div>
1690       </div>
1691     </div>
1692
1693     <div class="SECT2">
1694       <h2 class="SECT2"><a name="FORWARDING" id="FORWARDING">7.5.
1695       Forwarding</a></h2>
1696
1697       <p>This feature allows routing of HTTP requests through a chain of
1698       multiple proxies.</p>
1699
1700       <p>Forwarding can be used to chain Privoxy with a caching proxy to
1701       speed up browsing. Using a parent proxy may also be necessary if the
1702       machine that <span class="APPLICATION">Privoxy</span> runs on has no
1703       direct Internet access.</p>
1704
1705       <p>Note that parent proxies can severely decrease your privacy level.
1706       For example a parent proxy could add your IP address to the request
1707       headers and if it's a caching proxy it may add the <span class=
1708       "QUOTE">"Etag"</span> header to revalidation requests again, even
1709       though you configured Privoxy to remove it. It may also ignore
1710       Privoxy's header time randomization and use the original values which
1711       could be used by the server as cookie replacement to track your steps
1712       between visits.</p>
1713
1714       <p>Also specified here are SOCKS proxies. <span class=
1715       "APPLICATION">Privoxy</span> supports the SOCKS 4 and SOCKS 4A
1716       protocols.</p>
1717
1718       <div class="SECT3">
1719         <h4 class="SECT3"><a name="FORWARD" id="FORWARD">7.5.1.
1720         forward</a></h4>
1721
1722         <div class="VARIABLELIST">
1723           <dl>
1724             <dt>Specifies:</dt>
1725
1726             <dd>
1727               <p>To which parent HTTP proxy specific requests should be
1728               routed.</p>
1729             </dd>
1730
1731             <dt>Type of value:</dt>
1732
1733             <dd>
1734               <p><tt class="REPLACEABLE"><i>target_pattern</i></tt>
1735               <tt class="REPLACEABLE"><i>http_parent</i></tt>[:<tt class=
1736               "REPLACEABLE"><i>port</i></tt>]</p>
1737
1738               <p>where <tt class="REPLACEABLE"><i>target_pattern</i></tt> is
1739               a <a href="actions-file.html#AF-PATTERNS">URL pattern</a> that
1740               specifies to which requests (i.e. URLs) this forward rule shall
1741               apply. Use <tt class="LITERAL">/</tt> to denote <span class=
1742               "QUOTE">"all URLs"</span>. <tt class=
1743               "REPLACEABLE"><i>http_parent</i></tt>[:<tt class=
1744               "REPLACEABLE"><i>port</i></tt>] is the DNS name or IP address
1745               of the parent HTTP proxy through which the requests should be
1746               forwarded, optionally followed by its listening port (default:
1747               8000). Use a single dot (<tt class="LITERAL">.</tt>) to denote
1748               <span class="QUOTE">"no forwarding"</span>.</p>
1749             </dd>
1750
1751             <dt>Default value:</dt>
1752
1753             <dd>
1754               <p><span class="emphasis"><i class=
1755               "EMPHASIS">Unset</i></span></p>
1756             </dd>
1757
1758             <dt>Effect if unset:</dt>
1759
1760             <dd>
1761               <p>Don't use parent HTTP proxies.</p>
1762             </dd>
1763
1764             <dt>Notes:</dt>
1765
1766             <dd>
1767               <p>If <tt class="REPLACEABLE"><i>http_parent</i></tt> is
1768               <span class="QUOTE">"."</span>, then requests are not forwarded
1769               to another HTTP proxy but are made directly to the web
1770               servers.</p>
1771
1772               <p><tt class="REPLACEABLE"><i>http_parent</i></tt> can be a
1773               numerical IPv6 address (if <a href=
1774               "http://tools.ietf.org/html/rfc3493" target="_top">RFC 3493</a>
1775               is implemented). To prevent clashes with the port delimiter,
1776               the whole IP address has to be put into brackets. On the other
1777               hand a <tt class="REPLACEABLE"><i>target_pattern</i></tt>
1778               containing an IPv6 address has to be put into angle brackets
1779               (normal brackets are reserved for regular expressions
1780               already).</p>
1781
1782               <p>Multiple lines are OK, they are checked in sequence, and the
1783               last match wins.</p>
1784             </dd>
1785
1786             <dt>Examples:</dt>
1787
1788             <dd>
1789               <p>Everything goes to an example parent proxy, except SSL on
1790               port 443 (which it doesn't handle):</p>
1791
1792               <table border="0" bgcolor="#E0E0E0" width="90%">
1793                 <tr>
1794                   <td>
1795                     <pre class="SCREEN">
1796   forward   /      parent-proxy.example.org:8080
1797   forward   :443   .
1798 </pre>
1799                   </td>
1800                 </tr>
1801               </table>
1802
1803               <p>Everything goes to our example ISP's caching proxy, except
1804               for requests to that ISP's sites:</p>
1805
1806               <table border="0" bgcolor="#E0E0E0" width="90%">
1807                 <tr>
1808                   <td>
1809                     <pre class="SCREEN">
1810   forward   /                  caching-proxy.isp.example.net:8000
1811   forward   .isp.example.net   .
1812 </pre>
1813                   </td>
1814                 </tr>
1815               </table>
1816
1817               <p>Parent proxy specified by an IPv6 address:</p>
1818
1819               <table border="0" bgcolor="#E0E0E0" width="90%">
1820                 <tr>
1821                   <td>
1822                     <pre class="PROGRAMLISTING">
1823   forward   /                   [2001:DB8::1]:8000
1824 </pre>
1825                   </td>
1826                 </tr>
1827               </table>
1828
1829               <p>Suppose your parent proxy doesn't support IPv6:</p>
1830
1831               <table border="0" bgcolor="#E0E0E0" width="90%">
1832                 <tr>
1833                   <td>
1834                     <pre class="PROGRAMLISTING">
1835   forward  /                        parent-proxy.example.org:8000
1836   forward  ipv6-server.example.org  .
1837   forward  &lt;[2-3][0-9a-f][0-9a-f][0-9a-f]:*&gt;   .
1838 </pre>
1839                   </td>
1840                 </tr>
1841               </table>
1842             </dd>
1843           </dl>
1844         </div>
1845       </div>
1846
1847       <div class="SECT3">
1848         <h4 class="SECT3"><a name="SOCKS" id="SOCKS">7.5.2. forward-socks4,
1849         forward-socks4a and forward-socks5</a></h4><a name="FORWARD-SOCKS4"
1850         id="FORWARD-SOCKS4"></a><a name="FORWARD-SOCKS4A" id=
1851         "FORWARD-SOCKS4A"></a>
1852
1853         <div class="VARIABLELIST">
1854           <dl>
1855             <dt>Specifies:</dt>
1856
1857             <dd>
1858               <p>Through which SOCKS proxy (and optionally to which parent
1859               HTTP proxy) specific requests should be routed.</p>
1860             </dd>
1861
1862             <dt>Type of value:</dt>
1863
1864             <dd>
1865               <p><tt class="REPLACEABLE"><i>target_pattern</i></tt>
1866               <tt class="REPLACEABLE"><i>socks_proxy</i></tt>[:<tt class=
1867               "REPLACEABLE"><i>port</i></tt>] <tt class=
1868               "REPLACEABLE"><i>http_parent</i></tt>[:<tt class=
1869               "REPLACEABLE"><i>port</i></tt>]</p>
1870
1871               <p>where <tt class="REPLACEABLE"><i>target_pattern</i></tt> is
1872               a <a href="actions-file.html#AF-PATTERNS">URL pattern</a> that
1873               specifies to which requests (i.e. URLs) this forward rule shall
1874               apply. Use <tt class="LITERAL">/</tt> to denote <span class=
1875               "QUOTE">"all URLs"</span>. <tt class=
1876               "REPLACEABLE"><i>http_parent</i></tt> and <tt class=
1877               "REPLACEABLE"><i>socks_proxy</i></tt> are IP addresses in
1878               dotted decimal notation or valid DNS names (<tt class=
1879               "REPLACEABLE"><i>http_parent</i></tt> may be <span class=
1880               "QUOTE">"."</span> to denote <span class="QUOTE">"no HTTP
1881               forwarding"</span>), and the optional <tt class=
1882               "REPLACEABLE"><i>port</i></tt> parameters are TCP ports, i.e.
1883               integer values from 1 to 65535</p>
1884             </dd>
1885
1886             <dt>Default value:</dt>
1887
1888             <dd>
1889               <p><span class="emphasis"><i class=
1890               "EMPHASIS">Unset</i></span></p>
1891             </dd>
1892
1893             <dt>Effect if unset:</dt>
1894
1895             <dd>
1896               <p>Don't use SOCKS proxies.</p>
1897             </dd>
1898
1899             <dt>Notes:</dt>
1900
1901             <dd>
1902               <p>Multiple lines are OK, they are checked in sequence, and the
1903               last match wins.</p>
1904
1905               <p>The difference between <tt class=
1906               "LITERAL">forward-socks4</tt> and <tt class=
1907               "LITERAL">forward-socks4a</tt> is that in the SOCKS 4A
1908               protocol, the DNS resolution of the target hostname happens on
1909               the SOCKS server, while in SOCKS 4 it happens locally.</p>
1910
1911               <p>With <tt class="LITERAL">forward-socks5</tt> the DNS
1912               resolution will happen on the remote server as well.</p>
1913
1914               <p><tt class="REPLACEABLE"><i>socks_proxy</i></tt> and
1915               <tt class="REPLACEABLE"><i>http_parent</i></tt> can be a
1916               numerical IPv6 address (if <a href=
1917               "http://tools.ietf.org/html/rfc3493" target="_top">RFC 3493</a>
1918               is implemented). To prevent clashes with the port delimiter,
1919               the whole IP address has to be put into brackets. On the other
1920               hand a <tt class="REPLACEABLE"><i>target_pattern</i></tt>
1921               containing an IPv6 address has to be put into angle brackets
1922               (normal brackets are reserved for regular expressions
1923               already).</p>
1924
1925               <p>If <tt class="REPLACEABLE"><i>http_parent</i></tt> is
1926               <span class="QUOTE">"."</span>, then requests are not forwarded
1927               to another HTTP proxy but are made (HTTP-wise) directly to the
1928               web servers, albeit through a SOCKS proxy.</p>
1929             </dd>
1930
1931             <dt>Examples:</dt>
1932
1933             <dd>
1934               <p>From the company example.com, direct connections are made to
1935               all <span class="QUOTE">"internal"</span> domains, but
1936               everything outbound goes through their ISP's proxy by way of
1937               example.com's corporate SOCKS 4A gateway to the Internet.</p>
1938
1939               <table border="0" bgcolor="#E0E0E0" width="90%">
1940                 <tr>
1941                   <td>
1942                     <pre class="SCREEN">
1943   forward-socks4a   /              socks-gw.example.com:1080  www-cache.isp.example.net:8080
1944   forward           .example.com   .
1945 </pre>
1946                   </td>
1947                 </tr>
1948               </table>
1949
1950               <p>A rule that uses a SOCKS 4 gateway for all destinations but
1951               no HTTP parent looks like this:</p>
1952
1953               <table border="0" bgcolor="#E0E0E0" width="90%">
1954                 <tr>
1955                   <td>
1956                     <pre class="SCREEN">
1957   forward-socks4   /               socks-gw.example.com:1080  .
1958 </pre>
1959                   </td>
1960                 </tr>
1961               </table>
1962
1963               <p>To chain Privoxy and Tor, both running on the same system,
1964               you would use something like:</p>
1965
1966               <table border="0" bgcolor="#E0E0E0" width="90%">
1967                 <tr>
1968                   <td>
1969                     <pre class="SCREEN">
1970   forward-socks5   /               127.0.0.1:9050 .
1971 </pre>
1972                   </td>
1973                 </tr>
1974               </table>
1975
1976               <p>The public <span class="APPLICATION">Tor</span> network
1977               can't be used to reach your local network, if you need to
1978               access local servers you therefore might want to make some
1979               exceptions:</p>
1980
1981               <table border="0" bgcolor="#E0E0E0" width="90%">
1982                 <tr>
1983                   <td>
1984                     <pre class="SCREEN">
1985   forward         192.168.*.*/     .
1986   forward            10.*.*.*/     .
1987   forward           127.*.*.*/     .
1988 </pre>
1989                   </td>
1990                 </tr>
1991               </table>
1992
1993               <p>Unencrypted connections to systems in these address ranges
1994               will be as (un)secure as the local network is, but the
1995               alternative is that you can't reach the local network through
1996               <span class="APPLICATION">Privoxy</span> at all. Of course this
1997               may actually be desired and there is no reason to make these
1998               exceptions if you aren't sure you need them.</p>
1999
2000               <p>If you also want to be able to reach servers in your local
2001               network by using their names, you will need additional
2002               exceptions that look like this:</p>
2003
2004               <table border="0" bgcolor="#E0E0E0" width="90%">
2005                 <tr>
2006                   <td>
2007                     <pre class="SCREEN">
2008  forward           localhost/     .
2009 </pre>
2010                   </td>
2011                 </tr>
2012               </table>
2013             </dd>
2014           </dl>
2015         </div>
2016       </div>
2017
2018       <div class="SECT3">
2019         <h4 class="SECT3"><a name="ADVANCED-FORWARDING-EXAMPLES" id=
2020         "ADVANCED-FORWARDING-EXAMPLES">7.5.3. Advanced Forwarding
2021         Examples</a></h4>
2022
2023         <p>If you have links to multiple ISPs that provide various special
2024         content only to their subscribers, you can configure multiple
2025         <span class="APPLICATION">Privoxies</span> which have connections to
2026         the respective ISPs to act as forwarders to each other, so that
2027         <span class="emphasis"><i class="EMPHASIS">your</i></span> users can
2028         see the internal content of all ISPs.</p>
2029
2030         <p>Assume that host-a has a PPP connection to isp-a.example.net. And
2031         host-b has a PPP connection to isp-b.example.org. Both run
2032         <span class="APPLICATION">Privoxy</span>. Their forwarding
2033         configuration can look like this:</p>
2034
2035         <p>host-a:</p>
2036
2037         <table border="0" bgcolor="#E0E0E0" width="100%">
2038           <tr>
2039             <td>
2040               <pre class="SCREEN">
2041   forward    /           .
2042   forward    .isp-b.example.net  host-b:8118
2043 </pre>
2044             </td>
2045           </tr>
2046         </table>
2047
2048         <p>host-b:</p>
2049
2050         <table border="0" bgcolor="#E0E0E0" width="100%">
2051           <tr>
2052             <td>
2053               <pre class="SCREEN">
2054   forward    /           .
2055   forward    .isp-a.example.org  host-a:8118
2056 </pre>
2057             </td>
2058           </tr>
2059         </table>
2060
2061         <p>Now, your users can set their browser's proxy to use either host-a
2062         or host-b and be able to browse the internal content of both isp-a
2063         and isp-b.</p>
2064
2065         <p>If you intend to chain <span class="APPLICATION">Privoxy</span>
2066         and <span class="APPLICATION">squid</span> locally, then chaining as
2067         <tt class="LITERAL">browser -&gt; squid -&gt; privoxy</tt> is the
2068         recommended way.</p>
2069
2070         <p>Assuming that <span class="APPLICATION">Privoxy</span> and
2071         <span class="APPLICATION">squid</span> run on the same box, your
2072         <span class="APPLICATION">squid</span> configuration could then look
2073         like this:</p>
2074
2075         <table border="0" bgcolor="#E0E0E0" width="100%">
2076           <tr>
2077             <td>
2078               <pre class="SCREEN">
2079   # Define Privoxy as parent proxy (without ICP)
2080   cache_peer 127.0.0.1 parent 8118 7 no-query
2081
2082   # Define ACL for protocol FTP
2083   acl ftp proto FTP
2084
2085   # Do not forward FTP requests to Privoxy
2086   always_direct allow ftp
2087
2088   # Forward all the rest to Privoxy
2089   never_direct allow all
2090 </pre>
2091             </td>
2092           </tr>
2093         </table>
2094
2095         <p>You would then need to change your browser's proxy settings to
2096         <span class="APPLICATION">squid</span>'s address and port. Squid
2097         normally uses port 3128. If unsure consult <tt class=
2098         "LITERAL">http_port</tt> in <tt class="FILENAME">squid.conf</tt>.</p>
2099
2100         <p>You could just as well decide to only forward requests you suspect
2101         of leading to Windows executables through a virus-scanning parent
2102         proxy, say, on <tt class="LITERAL">antivir.example.com</tt>, port
2103         8010:</p>
2104
2105         <table border="0" bgcolor="#E0E0E0" width="100%">
2106           <tr>
2107             <td>
2108               <pre class="SCREEN">
2109   forward   /                          .
2110   forward   /.*\.(exe|com|dll|zip)$    antivir.example.com:8010
2111 </pre>
2112             </td>
2113           </tr>
2114         </table>
2115       </div>
2116
2117       <div class="SECT3">
2118         <h4 class="SECT3"><a name="FORWARDED-CONNECT-RETRIES" id=
2119         "FORWARDED-CONNECT-RETRIES">7.5.4. forwarded-connect-retries</a></h4>
2120
2121         <div class="VARIABLELIST">
2122           <dl>
2123             <dt>Specifies:</dt>
2124
2125             <dd>
2126               <p>How often Privoxy retries if a forwarded connection request
2127               fails.</p>
2128             </dd>
2129
2130             <dt>Type of value:</dt>
2131
2132             <dd>
2133               <p><tt class="REPLACEABLE"><i>Number of retries.</i></tt></p>
2134             </dd>
2135
2136             <dt>Default value:</dt>
2137
2138             <dd>
2139               <p><span class="emphasis"><i class="EMPHASIS">0</i></span></p>
2140             </dd>
2141
2142             <dt>Effect if unset:</dt>
2143
2144             <dd>
2145               <p>Connections forwarded through other proxies are treated like
2146               direct connections and no retry attempts are made.</p>
2147             </dd>
2148
2149             <dt>Notes:</dt>
2150
2151             <dd>
2152               <p><tt class=
2153               "REPLACEABLE"><i>forwarded-connect-retries</i></tt> is mainly
2154               interesting for socks4a connections, where <span class=
2155               "APPLICATION">Privoxy</span> can't detect why the connections
2156               failed. The connection might have failed because of a DNS
2157               timeout in which case a retry makes sense, but it might also
2158               have failed because the server doesn't exist or isn't
2159               reachable. In this case the retry will just delay the
2160               appearance of Privoxy's error message.</p>
2161
2162               <p>Note that in the context of this option, <span class=
2163               "QUOTE">"forwarded connections"</span> includes all connections
2164               that Privoxy forwards through other proxies. This option is not
2165               limited to the HTTP CONNECT method.</p>
2166
2167               <p>Only use this option, if you are getting lots of
2168               forwarding-related error messages that go away when you try
2169               again manually. Start with a small value and check Privoxy's
2170               logfile from time to time, to see how many retries are usually
2171               needed.</p>
2172             </dd>
2173
2174             <dt>Examples:</dt>
2175
2176             <dd>
2177               <p>forwarded-connect-retries 1</p>
2178             </dd>
2179           </dl>
2180         </div>
2181       </div>
2182     </div>
2183
2184     <div class="SECT2">
2185       <h2 class="SECT2"><a name="MISC" id="MISC">7.6. Miscellaneous</a></h2>
2186
2187       <div class="SECT3">
2188         <h4 class="SECT3"><a name="ACCEPT-INTERCEPTED-REQUESTS" id=
2189         "ACCEPT-INTERCEPTED-REQUESTS">7.6.1.
2190         accept-intercepted-requests</a></h4>
2191
2192         <div class="VARIABLELIST">
2193           <dl>
2194             <dt>Specifies:</dt>
2195
2196             <dd>
2197               <p>Whether intercepted requests should be treated as valid.</p>
2198             </dd>
2199
2200             <dt>Type of value:</dt>
2201
2202             <dd>
2203               <p><tt class="REPLACEABLE"><i>0 or 1</i></tt></p>
2204             </dd>
2205
2206             <dt>Default value:</dt>
2207
2208             <dd>
2209               <p><span class="emphasis"><i class="EMPHASIS">0</i></span></p>
2210             </dd>
2211
2212             <dt>Effect if unset:</dt>
2213
2214             <dd>
2215               <p>Only proxy requests are accepted, intercepted requests are
2216               treated as invalid.</p>
2217             </dd>
2218
2219             <dt>Notes:</dt>
2220
2221             <dd>
2222               <p>If you don't trust your clients and want to force them to
2223               use <span class="APPLICATION">Privoxy</span>, enable this
2224               option and configure your packet filter to redirect outgoing
2225               HTTP connections into <span class=
2226               "APPLICATION">Privoxy</span>.</p>
2227
2228               <p>Make sure that <span class="APPLICATION">Privoxy's</span>
2229               own requests aren't redirected as well. Additionally take care
2230               that <span class="APPLICATION">Privoxy</span> can't
2231               intentionally connect to itself, otherwise you could run into
2232               redirection loops if <span class="APPLICATION">Privoxy's</span>
2233               listening port is reachable by the outside or an attacker has
2234               access to the pages you visit.</p>
2235             </dd>
2236
2237             <dt>Examples:</dt>
2238
2239             <dd>
2240               <p>accept-intercepted-requests 1</p>
2241             </dd>
2242           </dl>
2243         </div>
2244       </div>
2245
2246       <div class="SECT3">
2247         <h4 class="SECT3"><a name="ALLOW-CGI-REQUEST-CRUNCHING" id=
2248         "ALLOW-CGI-REQUEST-CRUNCHING">7.6.2.
2249         allow-cgi-request-crunching</a></h4>
2250
2251         <div class="VARIABLELIST">
2252           <dl>
2253             <dt>Specifies:</dt>
2254
2255             <dd>
2256               <p>Whether requests to <span class=
2257               "APPLICATION">Privoxy's</span> CGI pages can be blocked or
2258               redirected.</p>
2259             </dd>
2260
2261             <dt>Type of value:</dt>
2262
2263             <dd>
2264               <p><tt class="REPLACEABLE"><i>0 or 1</i></tt></p>
2265             </dd>
2266
2267             <dt>Default value:</dt>
2268
2269             <dd>
2270               <p><span class="emphasis"><i class="EMPHASIS">0</i></span></p>
2271             </dd>
2272
2273             <dt>Effect if unset:</dt>
2274
2275             <dd>
2276               <p><span class="APPLICATION">Privoxy</span> ignores block and
2277               redirect actions for its CGI pages.</p>
2278             </dd>
2279
2280             <dt>Notes:</dt>
2281
2282             <dd>
2283               <p>By default <span class="APPLICATION">Privoxy</span> ignores
2284               block or redirect actions for its CGI pages. Intercepting these
2285               requests can be useful in multi-user setups to implement
2286               fine-grained access control, but it can also render the
2287               complete web interface useless and make debugging problems
2288               painful if done without care.</p>
2289
2290               <p>Don't enable this option unless you're sure that you really
2291               need it.</p>
2292             </dd>
2293
2294             <dt>Examples:</dt>
2295
2296             <dd>
2297               <p>allow-cgi-request-crunching 1</p>
2298             </dd>
2299           </dl>
2300         </div>
2301       </div>
2302
2303       <div class="SECT3">
2304         <h4 class="SECT3"><a name="SPLIT-LARGE-FORMS" id=
2305         "SPLIT-LARGE-FORMS">7.6.3. split-large-forms</a></h4>
2306
2307         <div class="VARIABLELIST">
2308           <dl>
2309             <dt>Specifies:</dt>
2310
2311             <dd>
2312               <p>Whether the CGI interface should stay compatible with broken
2313               HTTP clients.</p>
2314             </dd>
2315
2316             <dt>Type of value:</dt>
2317
2318             <dd>
2319               <p><tt class="REPLACEABLE"><i>0 or 1</i></tt></p>
2320             </dd>
2321
2322             <dt>Default value:</dt>
2323
2324             <dd>
2325               <p><span class="emphasis"><i class="EMPHASIS">0</i></span></p>
2326             </dd>
2327
2328             <dt>Effect if unset:</dt>
2329
2330             <dd>
2331               <p>The CGI form generate long GET URLs.</p>
2332             </dd>
2333
2334             <dt>Notes:</dt>
2335
2336             <dd>
2337               <p><span class="APPLICATION">Privoxy's</span> CGI forms can
2338               lead to rather long URLs. This isn't a problem as far as the
2339               HTTP standard is concerned, but it can confuse clients with
2340               arbitrary URL length limitations.</p>
2341
2342               <p>Enabling split-large-forms causes <span class=
2343               "APPLICATION">Privoxy</span> to divide big forms into smaller
2344               ones to keep the URL length down. It makes editing a lot less
2345               convenient and you can no longer submit all changes at once,
2346               but at least it works around this browser bug.</p>
2347
2348               <p>If you don't notice any editing problems, there is no reason
2349               to enable this option, but if one of the submit buttons appears
2350               to be broken, you should give it a try.</p>
2351             </dd>
2352
2353             <dt>Examples:</dt>
2354
2355             <dd>
2356               <p>split-large-forms 1</p>
2357             </dd>
2358           </dl>
2359         </div>
2360       </div>
2361
2362       <div class="SECT3">
2363         <h4 class="SECT3"><a name="KEEP-ALIVE-TIMEOUT" id=
2364         "KEEP-ALIVE-TIMEOUT">7.6.4. keep-alive-timeout</a></h4>
2365
2366         <div class="VARIABLELIST">
2367           <dl>
2368             <dt>Specifies:</dt>
2369
2370             <dd>
2371               <p>Number of seconds after which an open connection will no
2372               longer be reused.</p>
2373             </dd>
2374
2375             <dt>Type of value:</dt>
2376
2377             <dd>
2378               <p><tt class="REPLACEABLE"><i>Time in seconds.</i></tt></p>
2379             </dd>
2380
2381             <dt>Default value:</dt>
2382
2383             <dd>
2384               <p>None</p>
2385             </dd>
2386
2387             <dt>Effect if unset:</dt>
2388
2389             <dd>
2390               <p>Connections are not kept alive.</p>
2391             </dd>
2392
2393             <dt>Notes:</dt>
2394
2395             <dd>
2396               <p>This option allows clients to keep the connection to
2397               <span class="APPLICATION">Privoxy</span> alive. If the server
2398               supports it, <span class="APPLICATION">Privoxy</span> will keep
2399               the connection to the server alive as well. Under certain
2400               circumstances this may result in speed-ups.</p>
2401
2402               <p>By default, <span class="APPLICATION">Privoxy</span> will
2403               close the connection to the server if the client connection
2404               gets closed, or if the specified timeout has been reached
2405               without a new request coming in. This behaviour can be changed
2406               with the <a href="#CONNECTION-SHARING" target=
2407               "_top">connection-sharing</a> option.</p>
2408
2409               <p>This option has no effect if <span class=
2410               "APPLICATION">Privoxy</span> has been compiled without
2411               keep-alive support.</p>
2412
2413               <p>Note that a timeout of five seconds as used in the default
2414               configuration file significantly decreases the number of
2415               connections that will be reused. The value is used because some
2416               browsers limit the number of connections they open to a single
2417               host and apply the same limit to proxies. This can result in a
2418               single website <span class="QUOTE">"grabbing"</span> all the
2419               connections the browser allows, which means connections to
2420               other websites can't be opened until the connections currently
2421               in use time out.</p>
2422
2423               <p>Several users have reported this as a Privoxy bug, so the
2424               default value has been reduced. Consider increasing it to 300
2425               seconds or even more if you think your browser can handle it.
2426               If your browser appears to be hanging, it probably can't.</p>
2427             </dd>
2428
2429             <dt>Examples:</dt>
2430
2431             <dd>
2432               <p>keep-alive-timeout 300</p>
2433             </dd>
2434           </dl>
2435         </div>
2436       </div>
2437
2438       <div class="SECT3">
2439         <h4 class="SECT3"><a name="TOLERATE-PIPELINING" id=
2440         "TOLERATE-PIPELINING">7.6.5. tolerate-pipelining</a></h4>
2441
2442         <div class="VARIABLELIST">
2443           <dl>
2444             <dt>Specifies:</dt>
2445
2446             <dd>
2447               <p>Whether or not pipelined requests should be served.</p>
2448             </dd>
2449
2450             <dt>Type of value:</dt>
2451
2452             <dd>
2453               <p><tt class="REPLACEABLE"><i>0 or 1.</i></tt></p>
2454             </dd>
2455
2456             <dt>Default value:</dt>
2457
2458             <dd>
2459               <p>None</p>
2460             </dd>
2461
2462             <dt>Effect if unset:</dt>
2463
2464             <dd>
2465               <p>If Privoxy receives more than one request at once, it
2466               terminates the client connection after serving the first
2467               one.</p>
2468             </dd>
2469
2470             <dt>Notes:</dt>
2471
2472             <dd>
2473               <p><span class="APPLICATION">Privoxy</span> currently doesn't
2474               pipeline outgoing requests, thus allowing pipelining on the
2475               client connection is not guaranteed to improve the
2476               performance.</p>
2477
2478               <p>By default <span class="APPLICATION">Privoxy</span> tries to
2479               discourage clients from pipelining by discarding aggressively
2480               pipelined requests, which forces the client to resend them
2481               through a new connection.</p>
2482
2483               <p>This option lets <span class="APPLICATION">Privoxy</span>
2484               tolerate pipelining. Whether or not that improves performance
2485               mainly depends on the client configuration.</p>
2486
2487               <p>This options is new and should be considered
2488               experimental.</p>
2489             </dd>
2490
2491             <dt>Examples:</dt>
2492
2493             <dd>
2494               <p>tolerate-pipelining 1</p>
2495             </dd>
2496           </dl>
2497         </div>
2498       </div>
2499
2500       <div class="SECT3">
2501         <h4 class="SECT3"><a name="DEFAULT-SERVER-TIMEOUT" id=
2502         "DEFAULT-SERVER-TIMEOUT">7.6.6. default-server-timeout</a></h4>
2503
2504         <div class="VARIABLELIST">
2505           <dl>
2506             <dt>Specifies:</dt>
2507
2508             <dd>
2509               <p>Assumed server-side keep-alive timeout if not specified by
2510               the server.</p>
2511             </dd>
2512
2513             <dt>Type of value:</dt>
2514
2515             <dd>
2516               <p><tt class="REPLACEABLE"><i>Time in seconds.</i></tt></p>
2517             </dd>
2518
2519             <dt>Default value:</dt>
2520
2521             <dd>
2522               <p>None</p>
2523             </dd>
2524
2525             <dt>Effect if unset:</dt>
2526
2527             <dd>
2528               <p>Connections for which the server didn't specify the
2529               keep-alive timeout are not reused.</p>
2530             </dd>
2531
2532             <dt>Notes:</dt>
2533
2534             <dd>
2535               <p>Enabling this option significantly increases the number of
2536               connections that are reused, provided the <a href=
2537               "#KEEP-ALIVE-TIMEOUT" target="_top">keep-alive-timeout</a>
2538               option is also enabled.</p>
2539
2540               <p>While it also increases the number of connections problems
2541               when <span class="APPLICATION">Privoxy</span> tries to reuse a
2542               connection that already has been closed on the server side, or
2543               is closed while <span class="APPLICATION">Privoxy</span> is
2544               trying to reuse it, this should only be a problem if it happens
2545               for the first request sent by the client. If it happens for
2546               requests on reused client connections, <span class=
2547               "APPLICATION">Privoxy</span> will simply close the connection
2548               and the client is supposed to retry the request without
2549               bothering the user.</p>
2550
2551               <p>Enabling this option is therefore only recommended if the
2552               <a href="#CONNECTION-SHARING" target=
2553               "_top">connection-sharing</a> option is disabled.</p>
2554
2555               <p>It is an error to specify a value larger than the <a href=
2556               "#KEEP-ALIVE-TIMEOUT" target="_top">keep-alive-timeout</a>
2557               value.</p>
2558
2559               <p>This option has no effect if <span class=
2560               "APPLICATION">Privoxy</span> has been compiled without
2561               keep-alive support.</p>
2562             </dd>
2563
2564             <dt>Examples:</dt>
2565
2566             <dd>
2567               <p>default-server-timeout 60</p>
2568             </dd>
2569           </dl>
2570         </div>
2571       </div>
2572
2573       <div class="SECT3">
2574         <h4 class="SECT3"><a name="CONNECTION-SHARING" id=
2575         "CONNECTION-SHARING">7.6.7. connection-sharing</a></h4>
2576
2577         <div class="VARIABLELIST">
2578           <dl>
2579             <dt>Specifies:</dt>
2580
2581             <dd>
2582               <p>Whether or not outgoing connections that have been kept
2583               alive should be shared between different incoming
2584               connections.</p>
2585             </dd>
2586
2587             <dt>Type of value:</dt>
2588
2589             <dd>
2590               <p><tt class="REPLACEABLE"><i>0 or 1</i></tt></p>
2591             </dd>
2592
2593             <dt>Default value:</dt>
2594
2595             <dd>
2596               <p>None</p>
2597             </dd>
2598
2599             <dt>Effect if unset:</dt>
2600
2601             <dd>
2602               <p>Connections are not shared.</p>
2603             </dd>
2604
2605             <dt>Notes:</dt>
2606
2607             <dd>
2608               <p>This option has no effect if <span class=
2609               "APPLICATION">Privoxy</span> has been compiled without
2610               keep-alive support, or if it's disabled.</p>
2611             </dd>
2612
2613             <dt>Notes:</dt>
2614
2615             <dd>
2616               <p>Note that reusing connections doesn't necessary cause
2617               speedups. There are also a few privacy implications you should
2618               be aware of.</p>
2619
2620               <p>If this option is effective, outgoing connections are shared
2621               between clients (if there are more than one) and closing the
2622               browser that initiated the outgoing connection does no longer
2623               affect the connection between <span class=
2624               "APPLICATION">Privoxy</span> and the server unless the client's
2625               request hasn't been completed yet.</p>
2626
2627               <p>If the outgoing connection is idle, it will not be closed
2628               until either <span class="APPLICATION">Privoxy's</span> or the
2629               server's timeout is reached. While it's open, the server knows
2630               that the system running <span class=
2631               "APPLICATION">Privoxy</span> is still there.</p>
2632
2633               <p>If there are more than one client (maybe even belonging to
2634               multiple users), they will be able to reuse each others
2635               connections. This is potentially dangerous in case of
2636               authentication schemes like NTLM where only the connection is
2637               authenticated, instead of requiring authentication for each
2638               request.</p>
2639
2640               <p>If there is only a single client, and if said client can
2641               keep connections alive on its own, enabling this option has
2642               next to no effect. If the client doesn't support connection
2643               keep-alive, enabling this option may make sense as it allows
2644               <span class="APPLICATION">Privoxy</span> to keep outgoing
2645               connections alive even if the client itself doesn't support
2646               it.</p>
2647
2648               <p>You should also be aware that enabling this option increases
2649               the likelihood of getting the "No server or forwarder data"
2650               error message, especially if you are using a slow connection to
2651               the Internet.</p>
2652
2653               <p>This option should only be used by experienced users who
2654               understand the risks and can weight them against the
2655               benefits.</p>
2656             </dd>
2657
2658             <dt>Examples:</dt>
2659
2660             <dd>
2661               <p>connection-sharing 1</p>
2662             </dd>
2663           </dl>
2664         </div>
2665       </div>
2666
2667       <div class="SECT3">
2668         <h4 class="SECT3"><a name="SOCKET-TIMEOUT" id="SOCKET-TIMEOUT">7.6.8.
2669         socket-timeout</a></h4>
2670
2671         <div class="VARIABLELIST">
2672           <dl>
2673             <dt>Specifies:</dt>
2674
2675             <dd>
2676               <p>Number of seconds after which a socket times out if no data
2677               is received.</p>
2678             </dd>
2679
2680             <dt>Type of value:</dt>
2681
2682             <dd>
2683               <p><tt class="REPLACEABLE"><i>Time in seconds.</i></tt></p>
2684             </dd>
2685
2686             <dt>Default value:</dt>
2687
2688             <dd>
2689               <p>None</p>
2690             </dd>
2691
2692             <dt>Effect if unset:</dt>
2693
2694             <dd>
2695               <p>A default value of 300 seconds is used.</p>
2696             </dd>
2697
2698             <dt>Notes:</dt>
2699
2700             <dd>
2701               <p>The default is quite high and you probably want to reduce
2702               it. If you aren't using an occasionally slow proxy like Tor,
2703               reducing it to a few seconds should be fine.</p>
2704             </dd>
2705
2706             <dt>Examples:</dt>
2707
2708             <dd>
2709               <p>socket-timeout 300</p>
2710             </dd>
2711           </dl>
2712         </div>
2713       </div>
2714
2715       <div class="SECT3">
2716         <h4 class="SECT3"><a name="MAX-CLIENT-CONNECTIONS" id=
2717         "MAX-CLIENT-CONNECTIONS">7.6.9. max-client-connections</a></h4>
2718
2719         <div class="VARIABLELIST">
2720           <dl>
2721             <dt>Specifies:</dt>
2722
2723             <dd>
2724               <p>Maximum number of client connections that will be
2725               served.</p>
2726             </dd>
2727
2728             <dt>Type of value:</dt>
2729
2730             <dd>
2731               <p><tt class="REPLACEABLE"><i>Positive number.</i></tt></p>
2732             </dd>
2733
2734             <dt>Default value:</dt>
2735
2736             <dd>
2737               <p>None</p>
2738             </dd>
2739
2740             <dt>Effect if unset:</dt>
2741
2742             <dd>
2743               <p>Connections are served until a resource limit is
2744               reached.</p>
2745             </dd>
2746
2747             <dt>Notes:</dt>
2748
2749             <dd>
2750               <p><span class="APPLICATION">Privoxy</span> creates one thread
2751               (or process) for every incoming client connection that isn't
2752               rejected based on the access control settings.</p>
2753
2754               <p>If the system is powerful enough, <span class=
2755               "APPLICATION">Privoxy</span> can theoretically deal with
2756               several hundred (or thousand) connections at the same time, but
2757               some operating systems enforce resource limits by shutting down
2758               offending processes and their default limits may be below the
2759               ones <span class="APPLICATION">Privoxy</span> would require
2760               under heavy load.</p>
2761
2762               <p>Configuring <span class="APPLICATION">Privoxy</span> to
2763               enforce a connection limit below the thread or process limit
2764               used by the operating system makes sure this doesn't happen.
2765               Simply increasing the operating system's limit would work too,
2766               but if <span class="APPLICATION">Privoxy</span> isn't the only
2767               application running on the system, you may actually want to
2768               limit the resources used by <span class=
2769               "APPLICATION">Privoxy</span>.</p>
2770
2771               <p>If <span class="APPLICATION">Privoxy</span> is only used by
2772               a single trusted user, limiting the number of client
2773               connections is probably unnecessary. If there are multiple
2774               possibly untrusted users you probably still want to
2775               additionally use a packet filter to limit the maximal number of
2776               incoming connections per client. Otherwise a malicious user
2777               could intentionally create a high number of connections to
2778               prevent other users from using <span class=
2779               "APPLICATION">Privoxy</span>.</p>
2780
2781               <p>Obviously using this option only makes sense if you choose a
2782               limit below the one enforced by the operating system.</p>
2783             </dd>
2784
2785             <dt>Examples:</dt>
2786
2787             <dd>
2788               <p>max-client-connections 256</p>
2789             </dd>
2790           </dl>
2791         </div>
2792       </div>
2793
2794       <div class="SECT3">
2795         <h4 class="SECT3"><a name="HANDLE-AS-EMPTY-DOC-RETURNS-OK" id=
2796         "HANDLE-AS-EMPTY-DOC-RETURNS-OK">7.6.10.
2797         handle-as-empty-doc-returns-ok</a></h4>
2798
2799         <div class="VARIABLELIST">
2800           <dl>
2801             <dt>Specifies:</dt>
2802
2803             <dd>
2804               <p>The status code Privoxy returns for pages blocked with
2805               <tt class="LITERAL"><a href=
2806               "actions-file.html#HANDLE-AS-EMPTY-DOCUMENT" target=
2807               "_top">+handle-as-empty-document</a></tt>.</p>
2808             </dd>
2809
2810             <dt>Type of value:</dt>
2811
2812             <dd>
2813               <p><tt class="REPLACEABLE"><i>0 or 1</i></tt></p>
2814             </dd>
2815
2816             <dt>Default value:</dt>
2817
2818             <dd>
2819               <p>0</p>
2820             </dd>
2821
2822             <dt>Effect if unset:</dt>
2823
2824             <dd>
2825               <p>Privoxy returns a status 403(forbidden) for all blocked
2826               pages.</p>
2827             </dd>
2828
2829             <dt>Effect if set:</dt>
2830
2831             <dd>
2832               <p>Privoxy returns a status 200(OK) for pages blocked with
2833               +handle-as-empty-document and a status 403(Forbidden) for all
2834               other blocked pages.</p>
2835             </dd>
2836
2837             <dt>Notes:</dt>
2838
2839             <dd>
2840               <p>This is a work-around for Firefox bug 492459: <span class=
2841               "QUOTE">" Websites are no longer rendered if SSL requests for
2842               JavaScripts are blocked by a proxy. "</span> (<a href=
2843               "https://bugzilla.mozilla.org/show_bug.cgi?id=492459" target=
2844               "_top">https://bugzilla.mozilla.org/show_bug.cgi?id=492459</a>)
2845               As the bug has been fixed for quite some time this option
2846               should no longer be needed and will be removed in a future
2847               release. Please speak up if you have a reason why the option
2848               should be kept around.</p>
2849             </dd>
2850           </dl>
2851         </div>
2852       </div>
2853
2854       <div class="SECT3">
2855         <h4 class="SECT3"><a name="ENABLE-COMPRESSION" id=
2856         "ENABLE-COMPRESSION">7.6.11. enable-compression</a></h4>
2857
2858         <div class="VARIABLELIST">
2859           <dl>
2860             <dt>Specifies:</dt>
2861
2862             <dd>
2863               <p>Whether or not buffered content is compressed before
2864               delivery.</p>
2865             </dd>
2866
2867             <dt>Type of value:</dt>
2868
2869             <dd>
2870               <p><tt class="REPLACEABLE"><i>0 or 1</i></tt></p>
2871             </dd>
2872
2873             <dt>Default value:</dt>
2874
2875             <dd>
2876               <p>0</p>
2877             </dd>
2878
2879             <dt>Effect if unset:</dt>
2880
2881             <dd>
2882               <p>Privoxy does not compress buffered content.</p>
2883             </dd>
2884
2885             <dt>Effect if set:</dt>
2886
2887             <dd>
2888               <p>Privoxy compresses buffered content before delivering it to
2889               the client, provided the client supports it.</p>
2890             </dd>
2891
2892             <dt>Notes:</dt>
2893
2894             <dd>
2895               <p>This directive is only supported if Privoxy has been
2896               compiled with FEATURE_COMPRESSION, which should not to be
2897               confused with FEATURE_ZLIB.</p>
2898
2899               <p>Compressing buffered content is mainly useful if Privoxy and
2900               the client are running on different systems. If they are
2901               running on the same system, enabling compression is likely to
2902               slow things down. If you didn't measure otherwise, you should
2903               assume that it does and keep this option disabled.</p>
2904
2905               <p>Privoxy will not compress buffered content below a certain
2906               length.</p>
2907             </dd>
2908           </dl>
2909         </div>
2910       </div>
2911
2912       <div class="SECT3">
2913         <h4 class="SECT3"><a name="COMPRESSION-LEVEL" id=
2914         "COMPRESSION-LEVEL">7.6.12. compression-level</a></h4>
2915
2916         <div class="VARIABLELIST">
2917           <dl>
2918             <dt>Specifies:</dt>
2919
2920             <dd>
2921               <p>The compression level that is passed to the zlib library
2922               when compressing buffered content.</p>
2923             </dd>
2924
2925             <dt>Type of value:</dt>
2926
2927             <dd>
2928               <p><tt class="REPLACEABLE"><i>Positive number ranging from 0 to
2929               9.</i></tt></p>
2930             </dd>
2931
2932             <dt>Default value:</dt>
2933
2934             <dd>
2935               <p>1</p>
2936             </dd>
2937
2938             <dt>Notes:</dt>
2939
2940             <dd>
2941               <p>Compressing the data more takes usually longer than
2942               compressing it less or not compressing it at all. Which level
2943               is best depends on the connection between Privoxy and the
2944               client. If you can't be bothered to benchmark it for yourself,
2945               you should stick with the default and keep compression
2946               disabled.</p>
2947
2948               <p>If compression is disabled, the compression level is
2949               irrelevant.</p>
2950             </dd>
2951
2952             <dt>Examples:</dt>
2953
2954             <dd>
2955               <table border="0" bgcolor="#E0E0E0" width="90%">
2956                 <tr>
2957                   <td>
2958                     <pre class="SCREEN">
2959     # Best speed (compared to the other levels)
2960     compression-level 1
2961     # Best compression
2962     compression-level 9
2963     # No compression. Only useful for testing as the added header
2964     # slightly increases the amount of data that has to be sent.
2965     # If your benchmark shows that using this compression level
2966     # is superior to using no compression at all, the benchmark
2967     # is likely to be flawed.
2968     compression-level 0
2969
2970 </pre>
2971                   </td>
2972                 </tr>
2973               </table>
2974             </dd>
2975           </dl>
2976         </div>
2977       </div>
2978
2979       <div class="SECT3">
2980         <h4 class="SECT3"><a name="CLIENT-HEADER-ORDER" id=
2981         "CLIENT-HEADER-ORDER">7.6.13. client-header-order</a></h4>
2982
2983         <div class="VARIABLELIST">
2984           <dl>
2985             <dt>Specifies:</dt>
2986
2987             <dd>
2988               <p>The order in which client headers are sorted before
2989               forwarding them.</p>
2990             </dd>
2991
2992             <dt>Type of value:</dt>
2993
2994             <dd>
2995               <p><tt class="REPLACEABLE"><i>Client header names delimited by
2996               spaces or tabs</i></tt></p>
2997             </dd>
2998
2999             <dt>Default value:</dt>
3000
3001             <dd>
3002               <p>None</p>
3003             </dd>
3004
3005             <dt>Notes:</dt>
3006
3007             <dd>
3008               <p>By default <span class="APPLICATION">Privoxy</span> leaves
3009               the client headers in the order they were sent by the client.
3010               Headers are modified in-place, new headers are added at the end
3011               of the already existing headers.</p>
3012
3013               <p>The header order can be used to fingerprint client requests
3014               independently of other headers like the User-Agent.</p>
3015
3016               <p>This directive allows to sort the headers differently to
3017               better mimic a different User-Agent. Client headers will be
3018               emitted in the order given, headers whose name isn't explicitly
3019               specified are added at the end.</p>
3020
3021               <p>Note that sorting headers in an uncommon way will make
3022               fingerprinting actually easier. Encrypted headers are not
3023               affected by this directive.</p>
3024             </dd>
3025           </dl>
3026         </div>
3027       </div>
3028     </div>
3029
3030     <div class="SECT2">
3031       <h2 class="SECT2"><a name="WINDOWS-GUI" id="WINDOWS-GUI">7.7. Windows
3032       GUI Options</a></h2>
3033
3034       <p><span class="APPLICATION">Privoxy</span> has a number of options
3035       specific to the Windows GUI interface:</p><a name="ACTIVITY-ANIMATION"
3036       id="ACTIVITY-ANIMATION"></a>
3037
3038       <p>If <span class="QUOTE">"activity-animation"</span> is set to 1, the
3039       <span class="APPLICATION">Privoxy</span> icon will animate when
3040       <span class="QUOTE">"Privoxy"</span> is active. To turn off, set to
3041       0.</p>
3042
3043       <p class="LITERALLAYOUT"><tt class="LITERAL">&nbsp;&nbsp;<span class=
3044       "emphasis"><i class="EMPHASIS">activity-animation 1</i></span><br>
3045       &nbsp;&nbsp;&nbsp;</tt></p><a name="LOG-MESSAGES" id=
3046       "LOG-MESSAGES"></a>
3047
3048       <p>If <span class="QUOTE">"log-messages"</span> is set to 1,
3049       <span class="APPLICATION">Privoxy</span> copy log messages to the
3050       console window. The log detail depends on the <a href=
3051       "config.html#DEBUG">debug</a> directive.</p>
3052
3053       <p class="LITERALLAYOUT"><tt class="LITERAL">&nbsp;&nbsp;<span class=
3054       "emphasis"><i class="EMPHASIS">log-messages 1</i></span><br>
3055       &nbsp;&nbsp;&nbsp;</tt></p><a name="LOG-BUFFER-SIZE" id=
3056       "LOG-BUFFER-SIZE"></a>
3057
3058       <p>If <span class="QUOTE">"log-buffer-size"</span> is set to 1, the
3059       size of the log buffer, i.e. the amount of memory used for the log
3060       messages displayed in the console window, will be limited to
3061       <span class="QUOTE">"log-max-lines"</span> (see below).</p>
3062
3063       <p>Warning: Setting this to 0 will result in the buffer to grow
3064       infinitely and eat up all your memory!</p>
3065
3066       <p class="LITERALLAYOUT"><tt class="LITERAL">&nbsp;&nbsp;<span class=
3067       "emphasis"><i class="EMPHASIS">log-buffer-size 1</i></span><br>
3068       &nbsp;&nbsp;&nbsp;</tt></p><a name="LOG-MAX-LINES" id=
3069       "LOG-MAX-LINES"></a>
3070
3071       <p><span class="APPLICATION">log-max-lines</span> is the maximum number
3072       of lines held in the log buffer. See above.</p>
3073
3074       <p class="LITERALLAYOUT"><tt class="LITERAL">&nbsp;&nbsp;<span class=
3075       "emphasis"><i class="EMPHASIS">log-max-lines 200</i></span><br>
3076       &nbsp;&nbsp;&nbsp;</tt></p><a name="LOG-HIGHLIGHT-MESSAGES" id=
3077       "LOG-HIGHLIGHT-MESSAGES"></a>
3078
3079       <p>If <span class="QUOTE">"log-highlight-messages"</span> is set to 1,
3080       <span class="APPLICATION">Privoxy</span> will highlight portions of the
3081       log messages with a bold-faced font:</p>
3082
3083       <p class="LITERALLAYOUT"><tt class="LITERAL">&nbsp;&nbsp;<span class=
3084       "emphasis"><i class="EMPHASIS">log-highlight-messages 1</i></span><br>
3085       &nbsp;&nbsp;&nbsp;</tt></p><a name="LOG-FONT-NAME" id=
3086       "LOG-FONT-NAME"></a>
3087
3088       <p>The font used in the console window:</p>
3089
3090       <p class="LITERALLAYOUT"><tt class="LITERAL">&nbsp;&nbsp;<span class=
3091       "emphasis"><i class="EMPHASIS">log-font-name Comic Sans
3092       MS</i></span><br>
3093       &nbsp;&nbsp;&nbsp;</tt></p><a name="LOG-FONT-SIZE" id=
3094       "LOG-FONT-SIZE"></a>
3095
3096       <p>Font size used in the console window:</p>
3097
3098       <p class="LITERALLAYOUT"><tt class="LITERAL">&nbsp;&nbsp;<span class=
3099       "emphasis"><i class="EMPHASIS">log-font-size 8</i></span><br>
3100       &nbsp;&nbsp;&nbsp;</tt></p><a name="SHOW-ON-TASK-BAR" id=
3101       "SHOW-ON-TASK-BAR"></a>
3102
3103       <p><span class="QUOTE">"show-on-task-bar"</span> controls whether or
3104       not <span class="APPLICATION">Privoxy</span> will appear as a button on
3105       the Task bar when minimized:</p>
3106
3107       <p class="LITERALLAYOUT"><tt class="LITERAL">&nbsp;&nbsp;<span class=
3108       "emphasis"><i class="EMPHASIS">show-on-task-bar 0</i></span><br>
3109       &nbsp;&nbsp;&nbsp;</tt></p><a name="CLOSE-BUTTON-MINIMIZES" id=
3110       "CLOSE-BUTTON-MINIMIZES"></a>
3111
3112       <p>If <span class="QUOTE">"close-button-minimizes"</span> is set to 1,
3113       the Windows close button will minimize <span class=
3114       "APPLICATION">Privoxy</span> instead of closing the program (close with
3115       the exit option on the File menu).</p>
3116
3117       <p class="LITERALLAYOUT"><tt class="LITERAL">&nbsp;&nbsp;<span class=
3118       "emphasis"><i class="EMPHASIS">close-button-minimizes 1</i></span><br>
3119       &nbsp;&nbsp;&nbsp;</tt></p><a name="HIDE-CONSOLE" id=
3120       "HIDE-CONSOLE"></a>
3121
3122       <p>The <span class="QUOTE">"hide-console"</span> option is specific to
3123       the MS-Win console version of <span class="APPLICATION">Privoxy</span>.
3124       If this option is used, <span class="APPLICATION">Privoxy</span> will
3125       disconnect from and hide the command console.</p>
3126
3127       <p class="LITERALLAYOUT"><tt class="LITERAL">&nbsp;&nbsp;#<span class=
3128       "emphasis"><i class="EMPHASIS">hide-console</i></span><br>
3129       &nbsp;&nbsp;&nbsp;</tt></p>
3130     </div>
3131   </div>
3132
3133   <div class="NAVFOOTER">
3134     <hr align="left" width="100%">
3135
3136     <table summary="Footer navigation table" width="100%" border="0"
3137     cellpadding="0" cellspacing="0">
3138       <tr>
3139         <td width="33%" align="left" valign="top"><a href=
3140         "configuration.html" accesskey="P">Prev</a></td>
3141
3142         <td width="34%" align="center" valign="top"><a href="index.html"
3143         accesskey="H">Home</a></td>
3144
3145         <td width="33%" align="right" valign="top"><a href=
3146         "actions-file.html" accesskey="N">Next</a></td>
3147       </tr>
3148
3149       <tr>
3150         <td width="33%" align="left" valign="top">Privoxy Configuration</td>
3151
3152         <td width="34%" align="center" valign="top">&nbsp;</td>
3153
3154         <td width="33%" align="right" valign="top">Actions Files</td>
3155       </tr>
3156     </table>
3157   </div>
3158 </body>
3159 </html>