1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
2 "http://www.w3.org/TR/html4/loose.dtd">
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=
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">
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">
24 <th colspan="3" align="center">Privoxy 3.0.20 User Manual</th>
28 <td width="10%" align="left" valign="bottom"><a href=
29 "configuration.html" accesskey="P">Prev</a></td>
31 <td width="80%" align="center" valign="bottom"></td>
33 <td width="10%" align="right" valign="bottom"><a href=
34 "actions-file.html" accesskey="N">Next</a></td>
37 <hr align="left" width="100%">
41 <h1 class="SECT1"><a name="CONFIG" id="CONFIG">7. The Main Configuration
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>
50 <p class="LITERALLAYOUT"><tt class="LITERAL"> <span class=
51 "emphasis"><i class="EMPHASIS">confdir /etc/privoxy</i></span></tt></p>
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>
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
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>
70 <h2 class="SECT2"><a name="LOCAL-SET-UP" id="LOCAL-SET-UP">7.1. Local
71 Set-up Documentation</a></h2>
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
79 <h4 class="SECT3"><a name="USER-MANUAL" id="USER-MANUAL">7.1.1.
82 <div class="VARIABLELIST">
87 <p>Location of the <span class="APPLICATION">Privoxy</span>
91 <dt>Type of value:</dt>
94 <p>A fully qualified URI</p>
97 <dt>Default value:</dt>
100 <p><span class="emphasis"><i class=
101 "EMPHASIS">Unset</i></span></p>
104 <dt>Effect if unset:</dt>
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>
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>
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>
129 <table border="0" bgcolor="#E0E0E0" width="90%">
133 user-manual /usr/share/doc/privoxy/user-manual
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
144 "LITERAL">http://p.p/user-manual/</tt>).</p>
146 <p>If the documentation is not on the local system, it can be
147 accessed from a remote server, as:</p>
149 <table border="0" bgcolor="#E0E0E0" width="90%">
153 user-manual http://example.com/privoxy/user-manual/
159 <div class="WARNING">
160 <table class="WARNING" border="1" width="90%">
162 <td align="center"><b>Warning</b></td>
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>
181 <h4 class="SECT3"><a name="TRUST-INFO-URL" id="TRUST-INFO-URL">7.1.2.
182 trust-info-url</a></h4>
184 <div class="VARIABLELIST">
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>
193 <dt>Type of value:</dt>
199 <dt>Default value:</dt>
202 <p><span class="emphasis"><i class=
203 "EMPHASIS">Unset</i></span></p>
206 <dt>Effect if unset:</dt>
209 <p>No links are displayed on the "untrusted" error page.</p>
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>
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
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>
234 <h4 class="SECT3"><a name="ADMIN-ADDRESS" id="ADMIN-ADDRESS">7.1.3.
235 admin-address</a></h4>
237 <div class="VARIABLELIST">
242 <p>An email address to reach the <span class=
243 "APPLICATION">Privoxy</span> administrator.</p>
246 <dt>Type of value:</dt>
252 <dt>Default value:</dt>
255 <p><span class="emphasis"><i class=
256 "EMPHASIS">Unset</i></span></p>
259 <dt>Effect if unset:</dt>
262 <p>No email address is displayed on error pages and the CGI
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
279 <h4 class="SECT3"><a name="PROXY-INFO-URL" id="PROXY-INFO-URL">7.1.4.
280 proxy-info-url</a></h4>
282 <div class="VARIABLELIST">
287 <p>A URL to documentation about the local <span class=
288 "APPLICATION">Privoxy</span> setup, configuration or
292 <dt>Type of value:</dt>
298 <dt>Default value:</dt>
301 <p><span class="emphasis"><i class=
302 "EMPHASIS">Unset</i></span></p>
305 <dt>Effect if unset:</dt>
308 <p>No link to local documentation is displayed on error pages
309 and the CGI user interface.</p>
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
320 <p>This URL shouldn't be blocked ;-)</p>
328 <h2 class="SECT2"><a name="CONF-LOG-LOC" id="CONF-LOG-LOC">7.2.
329 Configuration and Log File Locations</a></h2>
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>
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
342 <h4 class="SECT3"><a name="CONFDIR" id="CONFDIR">7.2.1.
345 <div class="VARIABLELIST">
350 <p>The directory where the other configuration files are
354 <dt>Type of value:</dt>
360 <dt>Default value:</dt>
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>
368 <dt>Effect if unset:</dt>
371 <p><span class="emphasis"><i class=
372 "EMPHASIS">Mandatory</i></span></p>
378 <p>No trailing <span class="QUOTE">"<tt class=
379 "LITERAL">/</tt>"</span>, please.</p>
386 <h4 class="SECT3"><a name="TEMPLDIR" id="TEMPLDIR">7.2.2.
389 <div class="VARIABLELIST">
394 <p>An alternative directory where the templates are loaded
398 <dt>Type of value:</dt>
404 <dt>Default value:</dt>
410 <dt>Effect if unset:</dt>
413 <p>The templates are assumed to be located in
414 confdir/template.</p>
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>
433 <h4 class="SECT3"><a name="LOGDIR" id="LOGDIR">7.2.3. logdir</a></h4>
435 <div class="VARIABLELIST">
440 <p>The directory where all logging takes place (i.e. where the
441 <tt class="FILENAME">logfile</tt> is located).</p>
444 <dt>Type of value:</dt>
450 <dt>Default value:</dt>
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>
458 <dt>Effect if unset:</dt>
461 <p><span class="emphasis"><i class=
462 "EMPHASIS">Mandatory</i></span></p>
468 <p>No trailing <span class="QUOTE">"<tt class=
469 "LITERAL">/</tt>"</span>, please.</p>
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>
481 <div class="VARIABLELIST">
486 <p>The <a href="actions-file.html">actions file(s)</a> to
490 <dt>Type of value:</dt>
493 <p>Complete file name, relative to <tt class=
494 "LITERAL">confdir</tt></p>
497 <dt>Default values:</dt>
504 <p class="LITERALLAYOUT">
505 match-all.action # Actions that are applied to all sites and maybe overruled later on.</p>
511 <p class="LITERALLAYOUT">
512 default.action # Main actions file</p>
518 <p class="LITERALLAYOUT">
519 user.action # User customizations</p>
526 <dt>Effect if unset:</dt>
529 <p>No actions are taken at all. More or less neutral
536 <p>Multiple <tt class="LITERAL">actionsfile</tt> lines are
537 permitted, and are in fact recommended!</p>
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>
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
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>
562 <h4 class="SECT3"><a name="FILTERFILE" id="FILTERFILE">7.2.5.
563 filterfile</a></h4><a name="DEFAULT.FILTER" id="DEFAULT.FILTER"></a>
565 <div class="VARIABLELIST">
570 <p>The <a href="filter-file.html">filter file(s)</a> to use</p>
573 <dt>Type of value:</dt>
576 <p>File name, relative to <tt class="LITERAL">confdir</tt></p>
579 <dt>Default value:</dt>
582 <p>default.filter (Unix) <span class="emphasis"><i class=
583 "EMPHASIS">or</i></span> default.filter.txt (Windows)</p>
586 <dt>Effect if unset:</dt>
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>
599 <p>Multiple <tt class="LITERAL">filterfile</tt> lines are
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
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>
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
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>
633 <h4 class="SECT3"><a name="LOGFILE" id="LOGFILE">7.2.6.
636 <div class="VARIABLELIST">
641 <p>The log file to use</p>
644 <dt>Type of value:</dt>
647 <p>File name, relative to <tt class="LITERAL">logdir</tt></p>
650 <dt>Default value:</dt>
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
659 <dt>Effect if unset:</dt>
662 <p>No logfile is written.</p>
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>
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>
682 <p>For most troubleshooting purposes, you will have to change
683 that, please refer to the debugging section for details.</p>
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
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>
699 <h4 class="SECT3"><a name="TRUSTFILE" id="TRUSTFILE">7.2.7.
702 <div class="VARIABLELIST">
707 <p>The name of the trust file to use</p>
710 <dt>Type of value:</dt>
713 <p>File name, relative to <tt class="LITERAL">confdir</tt></p>
716 <dt>Default value:</dt>
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
725 <dt>Effect if unset:</dt>
728 <p>The entire trust mechanism is disabled.</p>
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
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
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>,
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>
762 <p>If you use the <tt class="LITERAL">+</tt> operator in the
763 trust file, it may grow considerably over time.</p>
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
772 <p>Possible applications include limiting Internet access for
781 <h2 class="SECT2"><a name="DEBUGGING" id="DEBUGGING">7.3.
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
790 <h4 class="SECT3"><a name="DEBUG" id="DEBUG">7.3.1. debug</a></h4>
792 <div class="VARIABLELIST">
797 <p>Key values that determine what information gets logged.</p>
800 <dt>Type of value:</dt>
803 <p>Integer values</p>
806 <dt>Default value:</dt>
809 <p>0 (i.e.: only fatal errors (that cause Privoxy to exit) are
813 <dt>Effect if unset:</dt>
816 <p>Default value is used (see above).</p>
822 <p>The available debug levels are:</p>
824 <table border="0" bgcolor="#E0E0E0" width="90%">
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
851 <p>To select multiple debug levels, you can either add them or
852 use multiple <tt class="LITERAL">debug</tt> lines.</p>
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
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
867 <p>If you are used to the more verbose settings, simply enable
868 the debug lines below again.</p>
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
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>
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>
890 <h4 class="SECT3"><a name="SINGLE-THREADED" id=
891 "SINGLE-THREADED">7.3.2. single-threaded</a></h4>
893 <div class="VARIABLELIST">
898 <p>Whether to run only one server thread.</p>
901 <dt>Type of value:</dt>
904 <p><span class="emphasis"><i class=
905 "EMPHASIS">None</i></span></p>
908 <dt>Default value:</dt>
911 <p><span class="emphasis"><i class=
912 "EMPHASIS">Unset</i></span></p>
915 <dt>Effect if unset:</dt>
918 <p>Multi-threaded (or, where unavailable: forked) operation,
919 i.e. the ability to serve multiple requests simultaneously.</p>
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>
934 <h4 class="SECT3"><a name="HOSTNAME" id="HOSTNAME">7.3.3.
937 <div class="VARIABLELIST">
942 <p>The hostname shown on the CGI pages.</p>
945 <dt>Type of value:</dt>
951 <dt>Default value:</dt>
954 <p><span class="emphasis"><i class=
955 "EMPHASIS">Unset</i></span></p>
958 <dt>Effect if unset:</dt>
961 <p>The hostname provided by the operating system is used.</p>
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>
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>
976 <p>Note that Privoxy does not validate the specified hostname
985 <h2 class="SECT2"><a name="ACCESS-CONTROL" id="ACCESS-CONTROL">7.4.
986 Access Control and Security</a></h2>
988 <p>This section of the config file controls the security-relevant
989 aspects of <span class="APPLICATION">Privoxy</span>'s
993 <h4 class="SECT3"><a name="LISTEN-ADDRESS" id="LISTEN-ADDRESS">7.4.1.
994 listen-address</a></h4>
996 <div class="VARIABLELIST">
1001 <p>The address and TCP port on which <span class=
1002 "APPLICATION">Privoxy</span> will listen for client
1006 <dt>Type of value:</dt>
1009 <p>[<tt class="REPLACEABLE"><i>IP-Address</i></tt>]:<tt class=
1010 "REPLACEABLE"><i>Port</i></tt></p>
1012 <p>[<tt class="REPLACEABLE"><i>Hostname</i></tt>]:<tt class=
1013 "REPLACEABLE"><i>Port</i></tt></p>
1016 <dt>Default value:</dt>
1019 <p>127.0.0.1:8118</p>
1022 <dt>Effect if unset:</dt>
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
1034 <p>You will need to configure your browser(s) to this proxy
1035 address and port.</p>
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
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>
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
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>
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>
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
1067 "LITERAL">http://config.privoxy.org/show-status</tt>.</p>
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>
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>
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
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>
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>
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>
1110 <table border="0" bgcolor="#E0E0E0" width="90%">
1113 <pre class="PROGRAMLISTING">
1114 listen-address 192.168.0.1:8118
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
1125 <table border="0" bgcolor="#E0E0E0" width="90%">
1128 <pre class="PROGRAMLISTING">
1129 listen-address [::1]:8118
1140 <h4 class="SECT3"><a name="TOGGLE" id="TOGGLE">7.4.2. toggle</a></h4>
1142 <div class="VARIABLELIST">
1147 <p>Initial state of "toggle" status</p>
1150 <dt>Type of value:</dt>
1156 <dt>Default value:</dt>
1162 <dt>Effect if unset:</dt>
1165 <p>Act as if toggled on</p>
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>
1182 <h4 class="SECT3"><a name="ENABLE-REMOTE-TOGGLE" id=
1183 "ENABLE-REMOTE-TOGGLE">7.4.3. enable-remote-toggle</a></h4>
1185 <div class="VARIABLELIST">
1190 <p>Whether or not the <a href=
1191 "http://config.privoxy.org/toggle" target="_top">web-based
1192 toggle feature</a> may be used</p>
1195 <dt>Type of value:</dt>
1201 <dt>Default value:</dt>
1207 <dt>Effect if unset:</dt>
1210 <p>The web-based toggle feature is disabled.</p>
1216 <p>When toggled off, <span class="APPLICATION">Privoxy</span>
1217 mostly acts like a normal, content-neutral proxy, i.e. doesn't
1218 block ads or filter content.</p>
1220 <p>Access to the toggle feature can <span class=
1221 "emphasis"><i class="EMPHASIS">not</i></span> be controlled
1222 separately by <span class="QUOTE">"ACLs"</span> or HTTP
1223 authentication, so that everybody who can access <span class=
1224 "APPLICATION">Privoxy</span> (see <span class=
1225 "QUOTE">"ACLs"</span> and <tt class=
1226 "LITERAL">listen-address</tt> above) can toggle it for all
1227 users. So this option is <span class="emphasis"><i class=
1228 "EMPHASIS">not recommended</i></span> for multi-user
1229 environments with untrusted users.</p>
1231 <p>Note that malicious client side code (e.g Java) is also
1232 capable of using this option.</p>
1234 <p>As a lot of <span class="APPLICATION">Privoxy</span> users
1235 don't read documentation, this feature is disabled by
1238 <p>Note that you must have compiled <span class=
1239 "APPLICATION">Privoxy</span> with support for this feature,
1240 otherwise this option has no effect.</p>
1247 <h4 class="SECT3"><a name="ENABLE-REMOTE-HTTP-TOGGLE" id=
1248 "ENABLE-REMOTE-HTTP-TOGGLE">7.4.4. enable-remote-http-toggle</a></h4>
1250 <div class="VARIABLELIST">
1255 <p>Whether or not Privoxy recognizes special HTTP headers to
1256 change its behaviour.</p>
1259 <dt>Type of value:</dt>
1265 <dt>Default value:</dt>
1271 <dt>Effect if unset:</dt>
1274 <p>Privoxy ignores special HTTP headers.</p>
1280 <p>When toggled on, the client can change <span class=
1281 "APPLICATION">Privoxy's</span> behaviour by setting special
1282 HTTP headers. Currently the only supported special header is
1283 <span class="QUOTE">"X-Filter: No"</span>, to disable filtering
1284 for the ongoing request, even if it is enabled in one of the
1287 <p>This feature is disabled by default. If you are using
1288 <span class="APPLICATION">Privoxy</span> in a environment with
1289 trusted clients, you may enable this feature at your
1290 discretion. Note that malicious client side code (e.g Java) is
1291 also capable of using this feature.</p>
1293 <p>This option will be removed in future releases as it has
1294 been obsoleted by the more general header taggers.</p>
1301 <h4 class="SECT3"><a name="ENABLE-EDIT-ACTIONS" id=
1302 "ENABLE-EDIT-ACTIONS">7.4.5. enable-edit-actions</a></h4>
1304 <div class="VARIABLELIST">
1309 <p>Whether or not the <a href=
1310 "http://config.privoxy.org/show-status" target="_top">web-based
1311 actions file editor</a> may be used</p>
1314 <dt>Type of value:</dt>
1320 <dt>Default value:</dt>
1326 <dt>Effect if unset:</dt>
1329 <p>The web-based actions file editor is disabled.</p>
1335 <p>Access to the editor can <span class="emphasis"><i class=
1336 "EMPHASIS">not</i></span> be controlled separately by
1337 <span class="QUOTE">"ACLs"</span> or HTTP authentication, so
1338 that everybody who can access <span class=
1339 "APPLICATION">Privoxy</span> (see <span class=
1340 "QUOTE">"ACLs"</span> and <tt class=
1341 "LITERAL">listen-address</tt> above) can modify its
1342 configuration for all users.</p>
1344 <p>This option is <span class="emphasis"><i class=
1345 "EMPHASIS">not recommended</i></span> for environments with
1346 untrusted users and as a lot of <span class=
1347 "APPLICATION">Privoxy</span> users don't read documentation,
1348 this feature is disabled by default.</p>
1350 <p>Note that malicious client side code (e.g Java) is also
1351 capable of using the actions editor and you shouldn't enable
1352 this options unless you understand the consequences and are
1353 sure your browser is configured correctly.</p>
1355 <p>Note that you must have compiled <span class=
1356 "APPLICATION">Privoxy</span> with support for this feature,
1357 otherwise this option has no effect.</p>
1364 <h4 class="SECT3"><a name="ENFORCE-BLOCKS" id="ENFORCE-BLOCKS">7.4.6.
1365 enforce-blocks</a></h4>
1367 <div class="VARIABLELIST">
1372 <p>Whether the user is allowed to ignore blocks and can
1373 <span class="QUOTE">"go there anyway"</span>.</p>
1376 <dt>Type of value:</dt>
1379 <p><tt class="REPLACEABLE"><i>0 or 1</i></tt></p>
1382 <dt>Default value:</dt>
1385 <p><span class="emphasis"><i class="EMPHASIS">0</i></span></p>
1388 <dt>Effect if unset:</dt>
1391 <p>Blocks are not enforced.</p>
1397 <p><span class="APPLICATION">Privoxy</span> is mainly used to
1398 block and filter requests as a service to the user, for example
1399 to block ads and other junk that clogs the pipes. <span class=
1400 "APPLICATION">Privoxy's</span> configuration isn't perfect and
1401 sometimes innocent pages are blocked. In this situation it
1402 makes sense to allow the user to enforce the request and have
1403 <span class="APPLICATION">Privoxy</span> ignore the block.</p>
1405 <p>In the default configuration <span class=
1406 "APPLICATION">Privoxy's</span> <span class=
1407 "QUOTE">"Blocked"</span> page contains a <span class=
1408 "QUOTE">"go there anyway"</span> link to adds a special string
1409 (the force prefix) to the request URL. If that link is used,
1410 <span class="APPLICATION">Privoxy</span> will detect the force
1411 prefix, remove it again and let the request pass.</p>
1413 <p>Of course <span class="APPLICATION">Privoxy</span> can also
1414 be used to enforce a network policy. In that case the user
1415 obviously should not be able to bypass any blocks, and that's
1416 what the <span class="QUOTE">"enforce-blocks"</span> option is
1417 for. If it's enabled, <span class="APPLICATION">Privoxy</span>
1418 hides the <span class="QUOTE">"go there anyway"</span> link. If
1419 the user adds the force prefix by hand, it will not be accepted
1420 and the circumvention attempt is logged.</p>
1426 <p>enforce-blocks 1</p>
1433 <h4 class="SECT3"><a name="ACLS" id="ACLS">7.4.7. ACLs: permit-access
1434 and deny-access</a></h4><a name="PERMIT-ACCESS" id=
1435 "PERMIT-ACCESS"></a><a name="DENY-ACCESS" id="DENY-ACCESS"></a>
1437 <div class="VARIABLELIST">
1442 <p>Who can access what.</p>
1445 <dt>Type of value:</dt>
1448 <p><tt class="REPLACEABLE"><i>src_addr</i></tt>[:<tt class=
1449 "REPLACEABLE"><i>port</i></tt>][/<tt class=
1450 "REPLACEABLE"><i>src_masklen</i></tt>] [<tt class=
1451 "REPLACEABLE"><i>dst_addr</i></tt>[:<tt class=
1452 "REPLACEABLE"><i>port</i></tt>][/<tt class=
1453 "REPLACEABLE"><i>dst_masklen</i></tt>]]</p>
1455 <p>Where <tt class="REPLACEABLE"><i>src_addr</i></tt> and
1456 <tt class="REPLACEABLE"><i>dst_addr</i></tt> are IPv4 addresses
1457 in dotted decimal notation or valid DNS names, <tt class=
1458 "REPLACEABLE"><i>port</i></tt> is a port number, and <tt class=
1459 "REPLACEABLE"><i>src_masklen</i></tt> and <tt class=
1460 "REPLACEABLE"><i>dst_masklen</i></tt> are subnet masks in CIDR
1461 notation, i.e. integer values from 2 to 30 representing the
1462 length (in bits) of the network address. The masks and the
1463 whole destination part are optional.</p>
1465 <p>If your system implements <a href=
1466 "http://tools.ietf.org/html/rfc3493" target="_top">RFC
1467 3493</a>, then <tt class="REPLACEABLE"><i>src_addr</i></tt> and
1468 <tt class="REPLACEABLE"><i>dst_addr</i></tt> can be IPv6
1469 addresses delimeted by brackets, <tt class=
1470 "REPLACEABLE"><i>port</i></tt> can be a number or a service
1471 name, and <tt class="REPLACEABLE"><i>src_masklen</i></tt> and
1472 <tt class="REPLACEABLE"><i>dst_masklen</i></tt> can be a number
1476 <dt>Default value:</dt>
1479 <p><span class="emphasis"><i class=
1480 "EMPHASIS">Unset</i></span></p>
1482 <p>If no <tt class="REPLACEABLE"><i>port</i></tt> is specified,
1483 any port will match. If no <tt class=
1484 "REPLACEABLE"><i>src_masklen</i></tt> or <tt class=
1485 "REPLACEABLE"><i>src_masklen</i></tt> is given, the complete IP
1486 address has to match (i.e. 32 bits for IPv4 and 128 bits for
1490 <dt>Effect if unset:</dt>
1493 <p>Don't restrict access further than implied by <tt class=
1494 "LITERAL">listen-address</tt></p>
1500 <p>Access controls are included at the request of ISPs and
1501 systems administrators, and <span class="emphasis"><i class=
1502 "EMPHASIS">are not usually needed by individual
1503 users</i></span>. For a typical home user, it will normally
1504 suffice to ensure that <span class="APPLICATION">Privoxy</span>
1505 only listens on the localhost (127.0.0.1) or internal (home)
1506 network address by means of the <a href=
1507 "config.html#LISTEN-ADDRESS"><span class="emphasis"><i class=
1508 "EMPHASIS">listen-address</i></span></a> option.</p>
1510 <p>Please see the warnings in the FAQ that <span class=
1511 "APPLICATION">Privoxy</span> is not intended to be a substitute
1512 for a firewall or to encourage anyone to defer addressing basic
1513 security weaknesses.</p>
1515 <p>Multiple ACL lines are OK. If any ACLs are specified,
1516 <span class="APPLICATION">Privoxy</span> only talks to IP
1517 addresses that match at least one <tt class=
1518 "LITERAL">permit-access</tt> line and don't match any
1519 subsequent <tt class="LITERAL">deny-access</tt> line. In other
1520 words, the last match wins, with the default being <tt class=
1521 "LITERAL">deny-access</tt>.</p>
1523 <p>If <span class="APPLICATION">Privoxy</span> is using a
1524 forwarder (see <tt class="LITERAL">forward</tt> below) for a
1525 particular destination URL, the <tt class=
1526 "REPLACEABLE"><i>dst_addr</i></tt> that is examined is the
1527 address of the forwarder and <span class="emphasis"><i class=
1528 "EMPHASIS">NOT</i></span> the address of the ultimate target.
1529 This is necessary because it may be impossible for the local
1530 <span class="APPLICATION">Privoxy</span> to determine the IP
1531 address of the ultimate target (that's often what gateways are
1534 <p>You should prefer using IP addresses over DNS names, because
1535 the address lookups take time. All DNS names must resolve! You
1536 can <span class="emphasis"><i class="EMPHASIS">not</i></span>
1537 use domain patterns like <span class="QUOTE">"*.org"</span> or
1538 partial domain names. If a DNS name resolves to multiple IP
1539 addresses, only the first one is used.</p>
1541 <p>Some systems allow IPv4 clients to connect to IPv6 server
1542 sockets. Then the client's IPv4 address will be translated by
1543 the system into IPv6 address space with special prefix
1544 ::ffff:0:0/96 (so called IPv4 mapped IPv6 address).
1545 <span class="APPLICATION">Privoxy</span> can handle it and maps
1546 such ACL addresses automatically.</p>
1548 <p>Denying access to particular sites by ACL may have undesired
1549 side effects if the site in question is hosted on a machine
1550 which also hosts other sites (most sites are).</p>
1556 <p>Explicitly define the default behavior if no ACL and
1557 <tt class="LITERAL">listen-address</tt> are set: <span class=
1558 "QUOTE">"localhost"</span> is OK. The absence of a <tt class=
1559 "REPLACEABLE"><i>dst_addr</i></tt> implies that <span class=
1560 "emphasis"><i class="EMPHASIS">all</i></span> destination
1561 addresses are OK:</p>
1563 <table border="0" bgcolor="#E0E0E0" width="90%">
1566 <pre class="SCREEN">
1567 permit-access localhost
1573 <p>Allow any host on the same class C subnet as www.privoxy.org
1574 access to nothing but www.example.com (or other domains hosted
1575 on the same system):</p>
1577 <table border="0" bgcolor="#E0E0E0" width="90%">
1580 <pre class="SCREEN">
1581 permit-access www.privoxy.org/24 www.example.com/32
1587 <p>Allow access from any host on the 26-bit subnet
1588 192.168.45.64 to anywhere, with the exception that
1589 192.168.45.73 may not access the IP address behind
1590 www.dirty-stuff.example.com:</p>
1592 <table border="0" bgcolor="#E0E0E0" width="90%">
1595 <pre class="SCREEN">
1596 permit-access 192.168.45.64/26
1597 deny-access 192.168.45.73 www.dirty-stuff.example.com
1603 <p>Allow access from the IPv4 network 192.0.2.0/24 even if
1604 listening on an IPv6 wild card address (not supported on all
1607 <table border="0" bgcolor="#E0E0E0" width="90%">
1610 <pre class="PROGRAMLISTING">
1611 permit-access 192.0.2.0/24
1617 <p>This is equivalent to the following line even if listening
1618 on an IPv4 address (not supported on all platforms):</p>
1620 <table border="0" bgcolor="#E0E0E0" width="90%">
1623 <pre class="PROGRAMLISTING">
1624 permit-access [::ffff:192.0.2.0]/120
1635 <h4 class="SECT3"><a name="BUFFER-LIMIT" id="BUFFER-LIMIT">7.4.8.
1636 buffer-limit</a></h4>
1638 <div class="VARIABLELIST">
1643 <p>Maximum size of the buffer for content filtering.</p>
1646 <dt>Type of value:</dt>
1649 <p>Size in Kbytes</p>
1652 <dt>Default value:</dt>
1658 <dt>Effect if unset:</dt>
1661 <p>Use a 4MB (4096 KB) limit.</p>
1667 <p>For content filtering, i.e. the <tt class=
1668 "LITERAL">+filter</tt> and <tt class=
1669 "LITERAL">+deanimate-gif</tt> actions, it is necessary that
1670 <span class="APPLICATION">Privoxy</span> buffers the entire
1671 document body. This can be potentially dangerous, since a
1672 server could just keep sending data indefinitely and wait for
1673 your RAM to exhaust -- with nasty consequences. Hence this
1676 <p>When a document buffer size reaches the <tt class=
1677 "LITERAL">buffer-limit</tt>, it is flushed to the client
1678 unfiltered and no further attempt to filter the rest of the
1679 document is made. Remember that there may be multiple threads
1680 running, which might require up to <tt class=
1681 "LITERAL">buffer-limit</tt> Kbytes <span class=
1682 "emphasis"><i class="EMPHASIS">each</i></span>, unless you have
1683 enabled <span class="QUOTE">"single-threaded"</span> above.</p>
1691 <h2 class="SECT2"><a name="FORWARDING" id="FORWARDING">7.5.
1694 <p>This feature allows routing of HTTP requests through a chain of
1695 multiple proxies.</p>
1697 <p>Forwarding can be used to chain Privoxy with a caching proxy to
1698 speed up browsing. Using a parent proxy may also be necessary if the
1699 machine that <span class="APPLICATION">Privoxy</span> runs on has no
1700 direct Internet access.</p>
1702 <p>Note that parent proxies can severely decrease your privacy level.
1703 For example a parent proxy could add your IP address to the request
1704 headers and if it's a caching proxy it may add the <span class=
1705 "QUOTE">"Etag"</span> header to revalidation requests again, even
1706 though you configured Privoxy to remove it. It may also ignore
1707 Privoxy's header time randomization and use the original values which
1708 could be used by the server as cookie replacement to track your steps
1711 <p>Also specified here are SOCKS proxies. <span class=
1712 "APPLICATION">Privoxy</span> supports the SOCKS 4 and SOCKS 4A
1716 <h4 class="SECT3"><a name="FORWARD" id="FORWARD">7.5.1.
1719 <div class="VARIABLELIST">
1724 <p>To which parent HTTP proxy specific requests should be
1728 <dt>Type of value:</dt>
1731 <p><tt class="REPLACEABLE"><i>target_pattern</i></tt>
1732 <tt class="REPLACEABLE"><i>http_parent</i></tt>[:<tt class=
1733 "REPLACEABLE"><i>port</i></tt>]</p>
1735 <p>where <tt class="REPLACEABLE"><i>target_pattern</i></tt> is
1736 a <a href="actions-file.html#AF-PATTERNS">URL pattern</a> that
1737 specifies to which requests (i.e. URLs) this forward rule shall
1738 apply. Use <tt class="LITERAL">/</tt> to denote <span class=
1739 "QUOTE">"all URLs"</span>. <tt class=
1740 "REPLACEABLE"><i>http_parent</i></tt>[:<tt class=
1741 "REPLACEABLE"><i>port</i></tt>] is the DNS name or IP address
1742 of the parent HTTP proxy through which the requests should be
1743 forwarded, optionally followed by its listening port (default:
1744 8000). Use a single dot (<tt class="LITERAL">.</tt>) to denote
1745 <span class="QUOTE">"no forwarding"</span>.</p>
1748 <dt>Default value:</dt>
1751 <p><span class="emphasis"><i class=
1752 "EMPHASIS">Unset</i></span></p>
1755 <dt>Effect if unset:</dt>
1758 <p>Don't use parent HTTP proxies.</p>
1764 <p>If <tt class="REPLACEABLE"><i>http_parent</i></tt> is
1765 <span class="QUOTE">"."</span>, then requests are not forwarded
1766 to another HTTP proxy but are made directly to the web
1769 <p><tt class="REPLACEABLE"><i>http_parent</i></tt> can be a
1770 numerical IPv6 address (if <a href=
1771 "http://tools.ietf.org/html/rfc3493" target="_top">RFC 3493</a>
1772 is implemented). To prevent clashes with the port delimiter,
1773 the whole IP address has to be put into brackets. On the other
1774 hand a <tt class="REPLACEABLE"><i>target_pattern</i></tt>
1775 containing an IPv6 address has to be put into angle brackets
1776 (normal brackets are reserved for regular expressions
1779 <p>Multiple lines are OK, they are checked in sequence, and the
1780 last match wins.</p>
1786 <p>Everything goes to an example parent proxy, except SSL on
1787 port 443 (which it doesn't handle):</p>
1789 <table border="0" bgcolor="#E0E0E0" width="90%">
1792 <pre class="SCREEN">
1793 forward / parent-proxy.example.org:8080
1800 <p>Everything goes to our example ISP's caching proxy, except
1801 for requests to that ISP's sites:</p>
1803 <table border="0" bgcolor="#E0E0E0" width="90%">
1806 <pre class="SCREEN">
1807 forward / caching-proxy.isp.example.net:8000
1808 forward .isp.example.net .
1814 <p>Parent proxy specified by an IPv6 address:</p>
1816 <table border="0" bgcolor="#E0E0E0" width="90%">
1819 <pre class="PROGRAMLISTING">
1820 forward / [2001:DB8::1]:8000
1826 <p>Suppose your parent proxy doesn't support IPv6:</p>
1828 <table border="0" bgcolor="#E0E0E0" width="90%">
1831 <pre class="PROGRAMLISTING">
1832 forward / parent-proxy.example.org:8000
1833 forward ipv6-server.example.org .
1834 forward <[2-3][0-9a-f][0-9a-f][0-9a-f]:*> .
1845 <h4 class="SECT3"><a name="SOCKS" id="SOCKS">7.5.2. forward-socks4,
1846 forward-socks4a, forward-socks5 and forward-socks5t</a></h4><a name=
1847 "FORWARD-SOCKS4" id="FORWARD-SOCKS4"></a><a name="FORWARD-SOCKS4A"
1848 id="FORWARD-SOCKS4A"></a>
1850 <div class="VARIABLELIST">
1855 <p>Through which SOCKS proxy (and optionally to which parent
1856 HTTP proxy) specific requests should be routed.</p>
1859 <dt>Type of value:</dt>
1862 <p><tt class="REPLACEABLE"><i>target_pattern</i></tt>
1863 <tt class="REPLACEABLE"><i>socks_proxy</i></tt>[:<tt class=
1864 "REPLACEABLE"><i>port</i></tt>] <tt class=
1865 "REPLACEABLE"><i>http_parent</i></tt>[:<tt class=
1866 "REPLACEABLE"><i>port</i></tt>]</p>
1868 <p>where <tt class="REPLACEABLE"><i>target_pattern</i></tt> is
1869 a <a href="actions-file.html#AF-PATTERNS">URL pattern</a> that
1870 specifies to which requests (i.e. URLs) this forward rule shall
1871 apply. Use <tt class="LITERAL">/</tt> to denote <span class=
1872 "QUOTE">"all URLs"</span>. <tt class=
1873 "REPLACEABLE"><i>http_parent</i></tt> and <tt class=
1874 "REPLACEABLE"><i>socks_proxy</i></tt> are IP addresses in
1875 dotted decimal notation or valid DNS names (<tt class=
1876 "REPLACEABLE"><i>http_parent</i></tt> may be <span class=
1877 "QUOTE">"."</span> to denote <span class="QUOTE">"no HTTP
1878 forwarding"</span>), and the optional <tt class=
1879 "REPLACEABLE"><i>port</i></tt> parameters are TCP ports, i.e.
1880 integer values from 1 to 65535</p>
1883 <dt>Default value:</dt>
1886 <p><span class="emphasis"><i class=
1887 "EMPHASIS">Unset</i></span></p>
1890 <dt>Effect if unset:</dt>
1893 <p>Don't use SOCKS proxies.</p>
1899 <p>Multiple lines are OK, they are checked in sequence, and the
1900 last match wins.</p>
1902 <p>The difference between <tt class=
1903 "LITERAL">forward-socks4</tt> and <tt class=
1904 "LITERAL">forward-socks4a</tt> is that in the SOCKS 4A
1905 protocol, the DNS resolution of the target hostname happens on
1906 the SOCKS server, while in SOCKS 4 it happens locally.</p>
1908 <p>With <tt class="LITERAL">forward-socks5</tt> the DNS
1909 resolution will happen on the remote server as well.</p>
1911 <p><tt class="LITERAL">forward-socks5t</tt> works like vanilla
1912 <tt class="LITERAL">forward-socks5</tt> but lets <span class=
1913 "APPLICATION">Privoxy</span> additionally use Tor-specific
1914 SOCKS extensions. Currently the only supported SOCKS extension
1915 is optimistic data which can reduce the latency for the first
1916 request made on a newly created connection.</p>
1918 <p><tt class="REPLACEABLE"><i>socks_proxy</i></tt> and
1919 <tt class="REPLACEABLE"><i>http_parent</i></tt> can be a
1920 numerical IPv6 address (if <a href=
1921 "http://tools.ietf.org/html/rfc3493" target="_top">RFC 3493</a>
1922 is implemented). To prevent clashes with the port delimiter,
1923 the whole IP address has to be put into brackets. On the other
1924 hand a <tt class="REPLACEABLE"><i>target_pattern</i></tt>
1925 containing an IPv6 address has to be put into angle brackets
1926 (normal brackets are reserved for regular expressions
1929 <p>If <tt class="REPLACEABLE"><i>http_parent</i></tt> is
1930 <span class="QUOTE">"."</span>, then requests are not forwarded
1931 to another HTTP proxy but are made (HTTP-wise) directly to the
1932 web servers, albeit through a SOCKS proxy.</p>
1938 <p>From the company example.com, direct connections are made to
1939 all <span class="QUOTE">"internal"</span> domains, but
1940 everything outbound goes through their ISP's proxy by way of
1941 example.com's corporate SOCKS 4A gateway to the Internet.</p>
1943 <table border="0" bgcolor="#E0E0E0" width="90%">
1946 <pre class="SCREEN">
1947 forward-socks4a / socks-gw.example.com:1080 www-cache.isp.example.net:8080
1948 forward .example.com .
1954 <p>A rule that uses a SOCKS 4 gateway for all destinations but
1955 no HTTP parent looks like this:</p>
1957 <table border="0" bgcolor="#E0E0E0" width="90%">
1960 <pre class="SCREEN">
1961 forward-socks4 / socks-gw.example.com:1080 .
1967 <p>To chain Privoxy and Tor, both running on the same system,
1968 you would use something like:</p>
1970 <table border="0" bgcolor="#E0E0E0" width="90%">
1973 <pre class="SCREEN">
1974 forward-socks5 / 127.0.0.1:9050 .
1980 <p>The public <span class="APPLICATION">Tor</span> network
1981 can't be used to reach your local network, if you need to
1982 access local servers you therefore might want to make some
1985 <table border="0" bgcolor="#E0E0E0" width="90%">
1988 <pre class="SCREEN">
1989 forward 192.168.*.*/ .
1991 forward 127.*.*.*/ .
1997 <p>Unencrypted connections to systems in these address ranges
1998 will be as (un)secure as the local network is, but the
1999 alternative is that you can't reach the local network through
2000 <span class="APPLICATION">Privoxy</span> at all. Of course this
2001 may actually be desired and there is no reason to make these
2002 exceptions if you aren't sure you need them.</p>
2004 <p>If you also want to be able to reach servers in your local
2005 network by using their names, you will need additional
2006 exceptions that look like this:</p>
2008 <table border="0" bgcolor="#E0E0E0" width="90%">
2011 <pre class="SCREEN">
2012 forward localhost/ .
2023 <h4 class="SECT3"><a name="ADVANCED-FORWARDING-EXAMPLES" id=
2024 "ADVANCED-FORWARDING-EXAMPLES">7.5.3. Advanced Forwarding
2027 <p>If you have links to multiple ISPs that provide various special
2028 content only to their subscribers, you can configure multiple
2029 <span class="APPLICATION">Privoxies</span> which have connections to
2030 the respective ISPs to act as forwarders to each other, so that
2031 <span class="emphasis"><i class="EMPHASIS">your</i></span> users can
2032 see the internal content of all ISPs.</p>
2034 <p>Assume that host-a has a PPP connection to isp-a.example.net. And
2035 host-b has a PPP connection to isp-b.example.org. Both run
2036 <span class="APPLICATION">Privoxy</span>. Their forwarding
2037 configuration can look like this:</p>
2041 <table border="0" bgcolor="#E0E0E0" width="100%">
2044 <pre class="SCREEN">
2046 forward .isp-b.example.net host-b:8118
2054 <table border="0" bgcolor="#E0E0E0" width="100%">
2057 <pre class="SCREEN">
2059 forward .isp-a.example.org host-a:8118
2065 <p>Now, your users can set their browser's proxy to use either host-a
2066 or host-b and be able to browse the internal content of both isp-a
2069 <p>If you intend to chain <span class="APPLICATION">Privoxy</span>
2070 and <span class="APPLICATION">squid</span> locally, then chaining as
2071 <tt class="LITERAL">browser -> squid -> privoxy</tt> is the
2072 recommended way.</p>
2074 <p>Assuming that <span class="APPLICATION">Privoxy</span> and
2075 <span class="APPLICATION">squid</span> run on the same box, your
2076 <span class="APPLICATION">squid</span> configuration could then look
2079 <table border="0" bgcolor="#E0E0E0" width="100%">
2082 <pre class="SCREEN">
2083 # Define Privoxy as parent proxy (without ICP)
2084 cache_peer 127.0.0.1 parent 8118 7 no-query
2086 # Define ACL for protocol FTP
2089 # Do not forward FTP requests to Privoxy
2090 always_direct allow ftp
2092 # Forward all the rest to Privoxy
2093 never_direct allow all
2099 <p>You would then need to change your browser's proxy settings to
2100 <span class="APPLICATION">squid</span>'s address and port. Squid
2101 normally uses port 3128. If unsure consult <tt class=
2102 "LITERAL">http_port</tt> in <tt class="FILENAME">squid.conf</tt>.</p>
2104 <p>You could just as well decide to only forward requests you suspect
2105 of leading to Windows executables through a virus-scanning parent
2106 proxy, say, on <tt class="LITERAL">antivir.example.com</tt>, port
2109 <table border="0" bgcolor="#E0E0E0" width="100%">
2112 <pre class="SCREEN">
2114 forward /.*\.(exe|com|dll|zip)$ antivir.example.com:8010
2122 <h4 class="SECT3"><a name="FORWARDED-CONNECT-RETRIES" id=
2123 "FORWARDED-CONNECT-RETRIES">7.5.4. forwarded-connect-retries</a></h4>
2125 <div class="VARIABLELIST">
2130 <p>How often Privoxy retries if a forwarded connection request
2134 <dt>Type of value:</dt>
2137 <p><tt class="REPLACEABLE"><i>Number of retries.</i></tt></p>
2140 <dt>Default value:</dt>
2143 <p><span class="emphasis"><i class="EMPHASIS">0</i></span></p>
2146 <dt>Effect if unset:</dt>
2149 <p>Connections forwarded through other proxies are treated like
2150 direct connections and no retry attempts are made.</p>
2157 "REPLACEABLE"><i>forwarded-connect-retries</i></tt> is mainly
2158 interesting for socks4a connections, where <span class=
2159 "APPLICATION">Privoxy</span> can't detect why the connections
2160 failed. The connection might have failed because of a DNS
2161 timeout in which case a retry makes sense, but it might also
2162 have failed because the server doesn't exist or isn't
2163 reachable. In this case the retry will just delay the
2164 appearance of Privoxy's error message.</p>
2166 <p>Note that in the context of this option, <span class=
2167 "QUOTE">"forwarded connections"</span> includes all connections
2168 that Privoxy forwards through other proxies. This option is not
2169 limited to the HTTP CONNECT method.</p>
2171 <p>Only use this option, if you are getting lots of
2172 forwarding-related error messages that go away when you try
2173 again manually. Start with a small value and check Privoxy's
2174 logfile from time to time, to see how many retries are usually
2181 <p>forwarded-connect-retries 1</p>
2189 <h2 class="SECT2"><a name="MISC" id="MISC">7.6. Miscellaneous</a></h2>
2192 <h4 class="SECT3"><a name="ACCEPT-INTERCEPTED-REQUESTS" id=
2193 "ACCEPT-INTERCEPTED-REQUESTS">7.6.1.
2194 accept-intercepted-requests</a></h4>
2196 <div class="VARIABLELIST">
2201 <p>Whether intercepted requests should be treated as valid.</p>
2204 <dt>Type of value:</dt>
2207 <p><tt class="REPLACEABLE"><i>0 or 1</i></tt></p>
2210 <dt>Default value:</dt>
2213 <p><span class="emphasis"><i class="EMPHASIS">0</i></span></p>
2216 <dt>Effect if unset:</dt>
2219 <p>Only proxy requests are accepted, intercepted requests are
2220 treated as invalid.</p>
2226 <p>If you don't trust your clients and want to force them to
2227 use <span class="APPLICATION">Privoxy</span>, enable this
2228 option and configure your packet filter to redirect outgoing
2229 HTTP connections into <span class=
2230 "APPLICATION">Privoxy</span>.</p>
2232 <p>Make sure that <span class="APPLICATION">Privoxy's</span>
2233 own requests aren't redirected as well. Additionally take care
2234 that <span class="APPLICATION">Privoxy</span> can't
2235 intentionally connect to itself, otherwise you could run into
2236 redirection loops if <span class="APPLICATION">Privoxy's</span>
2237 listening port is reachable by the outside or an attacker has
2238 access to the pages you visit.</p>
2244 <p>accept-intercepted-requests 1</p>
2251 <h4 class="SECT3"><a name="ALLOW-CGI-REQUEST-CRUNCHING" id=
2252 "ALLOW-CGI-REQUEST-CRUNCHING">7.6.2.
2253 allow-cgi-request-crunching</a></h4>
2255 <div class="VARIABLELIST">
2260 <p>Whether requests to <span class=
2261 "APPLICATION">Privoxy's</span> CGI pages can be blocked or
2265 <dt>Type of value:</dt>
2268 <p><tt class="REPLACEABLE"><i>0 or 1</i></tt></p>
2271 <dt>Default value:</dt>
2274 <p><span class="emphasis"><i class="EMPHASIS">0</i></span></p>
2277 <dt>Effect if unset:</dt>
2280 <p><span class="APPLICATION">Privoxy</span> ignores block and
2281 redirect actions for its CGI pages.</p>
2287 <p>By default <span class="APPLICATION">Privoxy</span> ignores
2288 block or redirect actions for its CGI pages. Intercepting these
2289 requests can be useful in multi-user setups to implement
2290 fine-grained access control, but it can also render the
2291 complete web interface useless and make debugging problems
2292 painful if done without care.</p>
2294 <p>Don't enable this option unless you're sure that you really
2301 <p>allow-cgi-request-crunching 1</p>
2308 <h4 class="SECT3"><a name="SPLIT-LARGE-FORMS" id=
2309 "SPLIT-LARGE-FORMS">7.6.3. split-large-forms</a></h4>
2311 <div class="VARIABLELIST">
2316 <p>Whether the CGI interface should stay compatible with broken
2320 <dt>Type of value:</dt>
2323 <p><tt class="REPLACEABLE"><i>0 or 1</i></tt></p>
2326 <dt>Default value:</dt>
2329 <p><span class="emphasis"><i class="EMPHASIS">0</i></span></p>
2332 <dt>Effect if unset:</dt>
2335 <p>The CGI form generate long GET URLs.</p>
2341 <p><span class="APPLICATION">Privoxy's</span> CGI forms can
2342 lead to rather long URLs. This isn't a problem as far as the
2343 HTTP standard is concerned, but it can confuse clients with
2344 arbitrary URL length limitations.</p>
2346 <p>Enabling split-large-forms causes <span class=
2347 "APPLICATION">Privoxy</span> to divide big forms into smaller
2348 ones to keep the URL length down. It makes editing a lot less
2349 convenient and you can no longer submit all changes at once,
2350 but at least it works around this browser bug.</p>
2352 <p>If you don't notice any editing problems, there is no reason
2353 to enable this option, but if one of the submit buttons appears
2354 to be broken, you should give it a try.</p>
2360 <p>split-large-forms 1</p>
2367 <h4 class="SECT3"><a name="KEEP-ALIVE-TIMEOUT" id=
2368 "KEEP-ALIVE-TIMEOUT">7.6.4. keep-alive-timeout</a></h4>
2370 <div class="VARIABLELIST">
2375 <p>Number of seconds after which an open connection will no
2376 longer be reused.</p>
2379 <dt>Type of value:</dt>
2382 <p><tt class="REPLACEABLE"><i>Time in seconds.</i></tt></p>
2385 <dt>Default value:</dt>
2391 <dt>Effect if unset:</dt>
2394 <p>Connections are not kept alive.</p>
2400 <p>This option allows clients to keep the connection to
2401 <span class="APPLICATION">Privoxy</span> alive. If the server
2402 supports it, <span class="APPLICATION">Privoxy</span> will keep
2403 the connection to the server alive as well. Under certain
2404 circumstances this may result in speed-ups.</p>
2406 <p>By default, <span class="APPLICATION">Privoxy</span> will
2407 close the connection to the server if the client connection
2408 gets closed, or if the specified timeout has been reached
2409 without a new request coming in. This behaviour can be changed
2410 with the <a href="#CONNECTION-SHARING" target=
2411 "_top">connection-sharing</a> option.</p>
2413 <p>This option has no effect if <span class=
2414 "APPLICATION">Privoxy</span> has been compiled without
2415 keep-alive support.</p>
2417 <p>Note that a timeout of five seconds as used in the default
2418 configuration file significantly decreases the number of
2419 connections that will be reused. The value is used because some
2420 browsers limit the number of connections they open to a single
2421 host and apply the same limit to proxies. This can result in a
2422 single website <span class="QUOTE">"grabbing"</span> all the
2423 connections the browser allows, which means connections to
2424 other websites can't be opened until the connections currently
2425 in use time out.</p>
2427 <p>Several users have reported this as a Privoxy bug, so the
2428 default value has been reduced. Consider increasing it to 300
2429 seconds or even more if you think your browser can handle it.
2430 If your browser appears to be hanging, it probably can't.</p>
2436 <p>keep-alive-timeout 300</p>
2443 <h4 class="SECT3"><a name="TOLERATE-PIPELINING" id=
2444 "TOLERATE-PIPELINING">7.6.5. tolerate-pipelining</a></h4>
2446 <div class="VARIABLELIST">
2451 <p>Whether or not pipelined requests should be served.</p>
2454 <dt>Type of value:</dt>
2457 <p><tt class="REPLACEABLE"><i>0 or 1.</i></tt></p>
2460 <dt>Default value:</dt>
2466 <dt>Effect if unset:</dt>
2469 <p>If Privoxy receives more than one request at once, it
2470 terminates the client connection after serving the first
2477 <p><span class="APPLICATION">Privoxy</span> currently doesn't
2478 pipeline outgoing requests, thus allowing pipelining on the
2479 client connection is not guaranteed to improve the
2482 <p>By default <span class="APPLICATION">Privoxy</span> tries to
2483 discourage clients from pipelining by discarding aggressively
2484 pipelined requests, which forces the client to resend them
2485 through a new connection.</p>
2487 <p>This option lets <span class="APPLICATION">Privoxy</span>
2488 tolerate pipelining. Whether or not that improves performance
2489 mainly depends on the client configuration.</p>
2491 <p>If you are seeing problems with pages not properly loading,
2492 disabling this option could work around the problem.</p>
2498 <p>tolerate-pipelining 1</p>
2505 <h4 class="SECT3"><a name="DEFAULT-SERVER-TIMEOUT" id=
2506 "DEFAULT-SERVER-TIMEOUT">7.6.6. default-server-timeout</a></h4>
2508 <div class="VARIABLELIST">
2513 <p>Assumed server-side keep-alive timeout if not specified by
2517 <dt>Type of value:</dt>
2520 <p><tt class="REPLACEABLE"><i>Time in seconds.</i></tt></p>
2523 <dt>Default value:</dt>
2529 <dt>Effect if unset:</dt>
2532 <p>Connections for which the server didn't specify the
2533 keep-alive timeout are not reused.</p>
2539 <p>Enabling this option significantly increases the number of
2540 connections that are reused, provided the <a href=
2541 "#KEEP-ALIVE-TIMEOUT" target="_top">keep-alive-timeout</a>
2542 option is also enabled.</p>
2544 <p>While it also increases the number of connections problems
2545 when <span class="APPLICATION">Privoxy</span> tries to reuse a
2546 connection that already has been closed on the server side, or
2547 is closed while <span class="APPLICATION">Privoxy</span> is
2548 trying to reuse it, this should only be a problem if it happens
2549 for the first request sent by the client. If it happens for
2550 requests on reused client connections, <span class=
2551 "APPLICATION">Privoxy</span> will simply close the connection
2552 and the client is supposed to retry the request without
2553 bothering the user.</p>
2555 <p>Enabling this option is therefore only recommended if the
2556 <a href="#CONNECTION-SHARING" target=
2557 "_top">connection-sharing</a> option is disabled.</p>
2559 <p>It is an error to specify a value larger than the <a href=
2560 "#KEEP-ALIVE-TIMEOUT" target="_top">keep-alive-timeout</a>
2563 <p>This option has no effect if <span class=
2564 "APPLICATION">Privoxy</span> has been compiled without
2565 keep-alive support.</p>
2571 <p>default-server-timeout 60</p>
2578 <h4 class="SECT3"><a name="CONNECTION-SHARING" id=
2579 "CONNECTION-SHARING">7.6.7. connection-sharing</a></h4>
2581 <div class="VARIABLELIST">
2586 <p>Whether or not outgoing connections that have been kept
2587 alive should be shared between different incoming
2591 <dt>Type of value:</dt>
2594 <p><tt class="REPLACEABLE"><i>0 or 1</i></tt></p>
2597 <dt>Default value:</dt>
2603 <dt>Effect if unset:</dt>
2606 <p>Connections are not shared.</p>
2612 <p>This option has no effect if <span class=
2613 "APPLICATION">Privoxy</span> has been compiled without
2614 keep-alive support, or if it's disabled.</p>
2620 <p>Note that reusing connections doesn't necessary cause
2621 speedups. There are also a few privacy implications you should
2624 <p>If this option is effective, outgoing connections are shared
2625 between clients (if there are more than one) and closing the
2626 browser that initiated the outgoing connection does no longer
2627 affect the connection between <span class=
2628 "APPLICATION">Privoxy</span> and the server unless the client's
2629 request hasn't been completed yet.</p>
2631 <p>If the outgoing connection is idle, it will not be closed
2632 until either <span class="APPLICATION">Privoxy's</span> or the
2633 server's timeout is reached. While it's open, the server knows
2634 that the system running <span class=
2635 "APPLICATION">Privoxy</span> is still there.</p>
2637 <p>If there are more than one client (maybe even belonging to
2638 multiple users), they will be able to reuse each others
2639 connections. This is potentially dangerous in case of
2640 authentication schemes like NTLM where only the connection is
2641 authenticated, instead of requiring authentication for each
2644 <p>If there is only a single client, and if said client can
2645 keep connections alive on its own, enabling this option has
2646 next to no effect. If the client doesn't support connection
2647 keep-alive, enabling this option may make sense as it allows
2648 <span class="APPLICATION">Privoxy</span> to keep outgoing
2649 connections alive even if the client itself doesn't support
2652 <p>You should also be aware that enabling this option increases
2653 the likelihood of getting the "No server or forwarder data"
2654 error message, especially if you are using a slow connection to
2657 <p>This option should only be used by experienced users who
2658 understand the risks and can weight them against the
2665 <p>connection-sharing 1</p>
2672 <h4 class="SECT3"><a name="SOCKET-TIMEOUT" id="SOCKET-TIMEOUT">7.6.8.
2673 socket-timeout</a></h4>
2675 <div class="VARIABLELIST">
2680 <p>Number of seconds after which a socket times out if no data
2684 <dt>Type of value:</dt>
2687 <p><tt class="REPLACEABLE"><i>Time in seconds.</i></tt></p>
2690 <dt>Default value:</dt>
2696 <dt>Effect if unset:</dt>
2699 <p>A default value of 300 seconds is used.</p>
2705 <p>The default is quite high and you probably want to reduce
2706 it. If you aren't using an occasionally slow proxy like Tor,
2707 reducing it to a few seconds should be fine.</p>
2713 <p>socket-timeout 300</p>
2720 <h4 class="SECT3"><a name="MAX-CLIENT-CONNECTIONS" id=
2721 "MAX-CLIENT-CONNECTIONS">7.6.9. max-client-connections</a></h4>
2723 <div class="VARIABLELIST">
2728 <p>Maximum number of client connections that will be
2732 <dt>Type of value:</dt>
2735 <p><tt class="REPLACEABLE"><i>Positive number.</i></tt></p>
2738 <dt>Default value:</dt>
2744 <dt>Effect if unset:</dt>
2747 <p>Connections are served until a resource limit is
2754 <p><span class="APPLICATION">Privoxy</span> creates one thread
2755 (or process) for every incoming client connection that isn't
2756 rejected based on the access control settings.</p>
2758 <p>If the system is powerful enough, <span class=
2759 "APPLICATION">Privoxy</span> can theoretically deal with
2760 several hundred (or thousand) connections at the same time, but
2761 some operating systems enforce resource limits by shutting down
2762 offending processes and their default limits may be below the
2763 ones <span class="APPLICATION">Privoxy</span> would require
2764 under heavy load.</p>
2766 <p>Configuring <span class="APPLICATION">Privoxy</span> to
2767 enforce a connection limit below the thread or process limit
2768 used by the operating system makes sure this doesn't happen.
2769 Simply increasing the operating system's limit would work too,
2770 but if <span class="APPLICATION">Privoxy</span> isn't the only
2771 application running on the system, you may actually want to
2772 limit the resources used by <span class=
2773 "APPLICATION">Privoxy</span>.</p>
2775 <p>If <span class="APPLICATION">Privoxy</span> is only used by
2776 a single trusted user, limiting the number of client
2777 connections is probably unnecessary. If there are multiple
2778 possibly untrusted users you probably still want to
2779 additionally use a packet filter to limit the maximal number of
2780 incoming connections per client. Otherwise a malicious user
2781 could intentionally create a high number of connections to
2782 prevent other users from using <span class=
2783 "APPLICATION">Privoxy</span>.</p>
2785 <p>Obviously using this option only makes sense if you choose a
2786 limit below the one enforced by the operating system.</p>
2792 <p>max-client-connections 256</p>
2799 <h4 class="SECT3"><a name="HANDLE-AS-EMPTY-DOC-RETURNS-OK" id=
2800 "HANDLE-AS-EMPTY-DOC-RETURNS-OK">7.6.10.
2801 handle-as-empty-doc-returns-ok</a></h4>
2803 <div class="VARIABLELIST">
2808 <p>The status code Privoxy returns for pages blocked with
2809 <tt class="LITERAL"><a href=
2810 "actions-file.html#HANDLE-AS-EMPTY-DOCUMENT" target=
2811 "_top">+handle-as-empty-document</a></tt>.</p>
2814 <dt>Type of value:</dt>
2817 <p><tt class="REPLACEABLE"><i>0 or 1</i></tt></p>
2820 <dt>Default value:</dt>
2826 <dt>Effect if unset:</dt>
2829 <p>Privoxy returns a status 403(forbidden) for all blocked
2833 <dt>Effect if set:</dt>
2836 <p>Privoxy returns a status 200(OK) for pages blocked with
2837 +handle-as-empty-document and a status 403(Forbidden) for all
2838 other blocked pages.</p>
2844 <p>This is a work-around for Firefox bug 492459: <span class=
2845 "QUOTE">" Websites are no longer rendered if SSL requests for
2846 JavaScripts are blocked by a proxy. "</span> (<a href=
2847 "https://bugzilla.mozilla.org/show_bug.cgi?id=492459" target=
2848 "_top">https://bugzilla.mozilla.org/show_bug.cgi?id=492459</a>)
2849 As the bug has been fixed for quite some time this option
2850 should no longer be needed and will be removed in a future
2851 release. Please speak up if you have a reason why the option
2852 should be kept around.</p>
2859 <h4 class="SECT3"><a name="ENABLE-COMPRESSION" id=
2860 "ENABLE-COMPRESSION">7.6.11. enable-compression</a></h4>
2862 <div class="VARIABLELIST">
2867 <p>Whether or not buffered content is compressed before
2871 <dt>Type of value:</dt>
2874 <p><tt class="REPLACEABLE"><i>0 or 1</i></tt></p>
2877 <dt>Default value:</dt>
2883 <dt>Effect if unset:</dt>
2886 <p>Privoxy does not compress buffered content.</p>
2889 <dt>Effect if set:</dt>
2892 <p>Privoxy compresses buffered content before delivering it to
2893 the client, provided the client supports it.</p>
2899 <p>This directive is only supported if Privoxy has been
2900 compiled with FEATURE_COMPRESSION, which should not to be
2901 confused with FEATURE_ZLIB.</p>
2903 <p>Compressing buffered content is mainly useful if Privoxy and
2904 the client are running on different systems. If they are
2905 running on the same system, enabling compression is likely to
2906 slow things down. If you didn't measure otherwise, you should
2907 assume that it does and keep this option disabled.</p>
2909 <p>Privoxy will not compress buffered content below a certain
2917 <h4 class="SECT3"><a name="COMPRESSION-LEVEL" id=
2918 "COMPRESSION-LEVEL">7.6.12. compression-level</a></h4>
2920 <div class="VARIABLELIST">
2925 <p>The compression level that is passed to the zlib library
2926 when compressing buffered content.</p>
2929 <dt>Type of value:</dt>
2932 <p><tt class="REPLACEABLE"><i>Positive number ranging from 0 to
2936 <dt>Default value:</dt>
2945 <p>Compressing the data more takes usually longer than
2946 compressing it less or not compressing it at all. Which level
2947 is best depends on the connection between Privoxy and the
2948 client. If you can't be bothered to benchmark it for yourself,
2949 you should stick with the default and keep compression
2952 <p>If compression is disabled, the compression level is
2959 <table border="0" bgcolor="#E0E0E0" width="90%">
2962 <pre class="SCREEN">
2963 # Best speed (compared to the other levels)
2967 # No compression. Only useful for testing as the added header
2968 # slightly increases the amount of data that has to be sent.
2969 # If your benchmark shows that using this compression level
2970 # is superior to using no compression at all, the benchmark
2971 # is likely to be flawed.
2984 <h4 class="SECT3"><a name="CLIENT-HEADER-ORDER" id=
2985 "CLIENT-HEADER-ORDER">7.6.13. client-header-order</a></h4>
2987 <div class="VARIABLELIST">
2992 <p>The order in which client headers are sorted before
2993 forwarding them.</p>
2996 <dt>Type of value:</dt>
2999 <p><tt class="REPLACEABLE"><i>Client header names delimited by
3000 spaces or tabs</i></tt></p>
3003 <dt>Default value:</dt>
3012 <p>By default <span class="APPLICATION">Privoxy</span> leaves
3013 the client headers in the order they were sent by the client.
3014 Headers are modified in-place, new headers are added at the end
3015 of the already existing headers.</p>
3017 <p>The header order can be used to fingerprint client requests
3018 independently of other headers like the User-Agent.</p>
3020 <p>This directive allows to sort the headers differently to
3021 better mimic a different User-Agent. Client headers will be
3022 emitted in the order given, headers whose name isn't explicitly
3023 specified are added at the end.</p>
3025 <p>Note that sorting headers in an uncommon way will make
3026 fingerprinting actually easier. Encrypted headers are not
3027 affected by this directive.</p>
3035 <h2 class="SECT2"><a name="WINDOWS-GUI" id="WINDOWS-GUI">7.7. Windows
3036 GUI Options</a></h2>
3038 <p><span class="APPLICATION">Privoxy</span> has a number of options
3039 specific to the Windows GUI interface:</p><a name="ACTIVITY-ANIMATION"
3040 id="ACTIVITY-ANIMATION"></a>
3042 <p>If <span class="QUOTE">"activity-animation"</span> is set to 1, the
3043 <span class="APPLICATION">Privoxy</span> icon will animate when
3044 <span class="QUOTE">"Privoxy"</span> is active. To turn off, set to
3047 <p class="LITERALLAYOUT"><tt class="LITERAL"> <span class=
3048 "emphasis"><i class="EMPHASIS">activity-animation 1</i></span><br>
3049 </tt></p><a name="LOG-MESSAGES" id=
3052 <p>If <span class="QUOTE">"log-messages"</span> is set to 1,
3053 <span class="APPLICATION">Privoxy</span> copies log messages to the
3054 console window. The log detail depends on the <a href=
3055 "config.html#DEBUG">debug</a> directive.</p>
3057 <p class="LITERALLAYOUT"><tt class="LITERAL"> <span class=
3058 "emphasis"><i class="EMPHASIS">log-messages 1</i></span><br>
3059 </tt></p><a name="LOG-BUFFER-SIZE" id=
3060 "LOG-BUFFER-SIZE"></a>
3062 <p>If <span class="QUOTE">"log-buffer-size"</span> is set to 1, the
3063 size of the log buffer, i.e. the amount of memory used for the log
3064 messages displayed in the console window, will be limited to
3065 <span class="QUOTE">"log-max-lines"</span> (see below).</p>
3067 <p>Warning: Setting this to 0 will result in the buffer to grow
3068 infinitely and eat up all your memory!</p>
3070 <p class="LITERALLAYOUT"><tt class="LITERAL"> <span class=
3071 "emphasis"><i class="EMPHASIS">log-buffer-size 1</i></span><br>
3072 </tt></p><a name="LOG-MAX-LINES" id=
3073 "LOG-MAX-LINES"></a>
3075 <p><span class="APPLICATION">log-max-lines</span> is the maximum number
3076 of lines held in the log buffer. See above.</p>
3078 <p class="LITERALLAYOUT"><tt class="LITERAL"> <span class=
3079 "emphasis"><i class="EMPHASIS">log-max-lines 200</i></span><br>
3080 </tt></p><a name="LOG-HIGHLIGHT-MESSAGES" id=
3081 "LOG-HIGHLIGHT-MESSAGES"></a>
3083 <p>If <span class="QUOTE">"log-highlight-messages"</span> is set to 1,
3084 <span class="APPLICATION">Privoxy</span> will highlight portions of the
3085 log messages with a bold-faced font:</p>
3087 <p class="LITERALLAYOUT"><tt class="LITERAL"> <span class=
3088 "emphasis"><i class="EMPHASIS">log-highlight-messages 1</i></span><br>
3089 </tt></p><a name="LOG-FONT-NAME" id=
3090 "LOG-FONT-NAME"></a>
3092 <p>The font used in the console window:</p>
3094 <p class="LITERALLAYOUT"><tt class="LITERAL"> <span class=
3095 "emphasis"><i class="EMPHASIS">log-font-name Comic Sans
3097 </tt></p><a name="LOG-FONT-SIZE" id=
3098 "LOG-FONT-SIZE"></a>
3100 <p>Font size used in the console window:</p>
3102 <p class="LITERALLAYOUT"><tt class="LITERAL"> <span class=
3103 "emphasis"><i class="EMPHASIS">log-font-size 8</i></span><br>
3104 </tt></p><a name="SHOW-ON-TASK-BAR" id=
3105 "SHOW-ON-TASK-BAR"></a>
3107 <p><span class="QUOTE">"show-on-task-bar"</span> controls whether or
3108 not <span class="APPLICATION">Privoxy</span> will appear as a button on
3109 the Task bar when minimized:</p>
3111 <p class="LITERALLAYOUT"><tt class="LITERAL"> <span class=
3112 "emphasis"><i class="EMPHASIS">show-on-task-bar 0</i></span><br>
3113 </tt></p><a name="CLOSE-BUTTON-MINIMIZES" id=
3114 "CLOSE-BUTTON-MINIMIZES"></a>
3116 <p>If <span class="QUOTE">"close-button-minimizes"</span> is set to 1,
3117 the Windows close button will minimize <span class=
3118 "APPLICATION">Privoxy</span> instead of closing the program (close with
3119 the exit option on the File menu).</p>
3121 <p class="LITERALLAYOUT"><tt class="LITERAL"> <span class=
3122 "emphasis"><i class="EMPHASIS">close-button-minimizes 1</i></span><br>
3123 </tt></p><a name="HIDE-CONSOLE" id=
3126 <p>The <span class="QUOTE">"hide-console"</span> option is specific to
3127 the MS-Win console version of <span class="APPLICATION">Privoxy</span>.
3128 If this option is used, <span class="APPLICATION">Privoxy</span> will
3129 disconnect from and hide the command console.</p>
3131 <p class="LITERALLAYOUT"><tt class="LITERAL"> #<span class=
3132 "emphasis"><i class="EMPHASIS">hide-console</i></span><br>
3133 </tt></p>
3137 <div class="NAVFOOTER">
3138 <hr align="left" width="100%">
3140 <table summary="Footer navigation table" width="100%" border="0"
3141 cellpadding="0" cellspacing="0">
3143 <td width="33%" align="left" valign="top"><a href=
3144 "configuration.html" accesskey="P">Prev</a></td>
3146 <td width="34%" align="center" valign="top"><a href="index.html"
3147 accesskey="H">Home</a></td>
3149 <td width="33%" align="right" valign="top"><a href=
3150 "actions-file.html" accesskey="N">Next</a></td>
3154 <td width="33%" align="left" valign="top">Privoxy Configuration</td>
3156 <td width="34%" align="center" valign="top"> </td>
3158 <td width="33%" align="right" valign="top">Actions Files</td>
projects / privoxy.git / blob