2 File : $Source: /cvsroot/ijbswa/current/doc/source/p-config.sgml,v $
4 Purpose : Used with other docs and files only.
6 $Id: p-config.sgml,v 2.32 2008/08/30 12:03:09 fabiankeil Exp $
8 Copyright (C) 2001-2008 Privoxy Developers http://www.privoxy.org/
11 ========================================================================
12 NOTE: Please read developer-manual/documentation.html before touching
13 anything in this, or other Privoxy documentation.
14 ========================================================================
17 This file contains all the config file comments and options. It used to
18 build both the user-manual config sections, and all of config (yes, the main
21 Rationale: This is broken up into two files since a file with a prolog
22 (DTD, etc) cannot be sourced as a secondary file. config.sgml is basically
23 a wrapper for this file.
27 OPTIONS: The actual options are included in this file and prefixed with
28 '@@', and processed by the Makefile to strip the '@@'. Default options
29 that should appear commented out should be listed as: '@@#OPTION'.
30 Otherwise, as '@@OPTION'. Example:
32 @@listen-address 127.0.0.1:8118
34 The Makefile does significant other processing too. The final results
35 should be checked to make sure that the perl processing does not
36 fubar something!!! Makefile processing requires w3m, fmt (shell line
40 This file is included into:
43 config (the actual Privoxy config file)
48 <!-- This part only goes into user-manual -->
50 <title>The Main Configuration File</title>
53 Again, the main configuration file is named <filename>config</filename> on
54 Linux/Unix/BSD and OS/2, and <filename>config.txt</filename> on Windows.
55 Configuration lines consist of an initial keyword followed by a list of
56 values, all separated by whitespace (any number of spaces or tabs). For
64 <emphasis>confdir /etc/privoxy</emphasis></literallayout>
70 Assigns the value <literal>/etc/privoxy</literal> to the option
71 <literal>confdir</literal> and thus indicates that the configuration
72 directory is named <quote>/etc/privoxy/</quote>.
76 All options in the config file except for <literal>confdir</literal> and
77 <literal>logdir</literal> are optional. Watch out in the below description
78 for what happens if you leave them unset.
82 The main config file controls all aspects of <application>Privoxy</application>'s
83 operation that are not location dependent (i.e. they apply universally, no matter
84 where you may be surfing).
91 <!-- This part only goes into the config file -->
94 @@TITLE<!-- between the @@ is stripped by Makefile -->@@
95 Sample Configuration File for Privoxy v&p-version;
98 $Id: p-config.sgml,v 2.32 2008/08/30 12:03:09 fabiankeil Exp $
101 Copyright (C) 2001-2008 Privoxy Developers http://www.privoxy.org/
106 #################################################################
111 II. FORMAT OF THE CONFIGURATION FILE #
113 1. LOCAL SET-UP DOCUMENTATION #
114 2. CONFIGURATION AND LOG FILE LOCATIONS #
116 4. ACCESS CONTROL AND SECURITY #
118 6. WINDOWS GUI OPTIONS #
120 #################################################################
124 <literallayout>I. INTRODUCTION
125 =============== <!-- fuck this madness --></literallayout>
128 This file holds Privoxy's main configuration. Privoxy detects
129 configuration changes automatically, so you don't have to restart it
130 unless you want to load a different configuration file.
133 The configuration will be reloaded with the first request after the
134 change was done, this request itself will still use the old configuration,
135 though. In other words: it takes two requests before you see the result of
136 your changes. Requests that are dropped due to ACL don't trigger reloads.
139 When starting Privoxy on Unix systems, give the location of this
140 file as last argument. On Windows systems, Privoxy will look for
141 this file with the name 'config.txt' in the current working directory
142 of the Privoxy process.
146 <literallayout><!-- funky spacing -->
148 II. FORMAT OF THE CONFIGURATION FILE
149 ====================================</literallayout>
152 Configuration lines consist of an initial keyword followed by a list
153 of values, all separated by whitespace (any number of spaces or
157 actionsfile default.action
160 Indicates that the actionsfile is named 'default.action'.
163 The '#' indicates a comment. Any part of a line following a '#' is
164 ignored, except if the '#' is preceded by a '\'.
167 Thus, by placing a # at the start of an existing configuration line,
168 you can make it a comment and it will be treated as if it weren't there.
169 This is called "commenting out" an option and can be useful. Removing
170 the # again is called "uncommenting".
173 Note that commenting out an option and leaving it at its default
174 are two completely different things! Most options behave very
175 differently when unset. See the "Effect if unset" explanation
176 in each option's description for details.
179 Long lines can be continued on the next line by using a `\' as
185 <!-- ************************************************ -->
186 <!-- The following is common to both outputs (mostly) -->
187 <!-- ************************************************ -->
191 <!-- ~~~~~ New section ~~~~~ -->
192 <sect2 id="local-set-up">
193 <title>Local Set-up Documentation</title>
196 If you intend to operate <application>Privoxy</application> for more users
197 than just yourself, it might be a good idea to let them know how to reach
198 you, what you block and why you do that, your policies, etc.
202 <!-- ~~~~~ New section ~~~~~ -->
203 <sect3 renderas="sect4" id="user-manual"><title>user-manual</title>
206 <term>Specifies:</term>
209 Location of the <application>Privoxy</application> User Manual.
214 <term>Type of value:</term>
216 <para>A fully qualified URI</para>
220 <term>Default value:</term>
222 <para><emphasis>Unset</emphasis></para>
226 <term>Effect if unset:</term>
229 <ulink url="http://www.privoxy.org/user-manual/">http://www.privoxy.org/<replaceable class="parameter">version</replaceable>/user-manual/</ulink>
230 will be used, where <replaceable class="parameter">version</replaceable> is the <application>Privoxy</application> version.
238 The User Manual URI is the single best source of information on
239 <application>Privoxy</application>, and is used for help links from some
240 of the internal CGI pages. The manual itself is normally packaged with the
241 binary distributions, so you probably want to set this to a locally
249 Unix, in local filesystem (may not work with all browsers):
252 <screen> user-manual file:///usr/share/doc/privoxy-&p-version;/user-manual/</screen>
255 Windows, in local filesystem, <emphasis>must</emphasis> use forward slash notation:
258 <screen> user-manual file:/c:/some-dir/privoxy-&p-version;/user-manual/</screen>
261 Windows, UNC notation (with forward slashes):
264 <screen> user-manual file://///some-server/some-path/privoxy-&p-version;/user-manual/</screen>
268 The best all purpose solution is simply to put the full local
269 <literal>PATH</literal> to where the <citetitle>User Manual</citetitle> is
273 <screen> user-manual /usr/share/doc/privoxy/user-manual</screen>
276 The User Manual is then available to anyone with access to
277 <application>Privoxy</application>, by following the built-in URL:
278 <literal>http://config.privoxy.org/user-manual/</literal>
279 (or the shortcut: <literal>http://p.p/user-manual/</literal>).
282 If the documentation is not on the local system, it can be accessed
283 from a remote server, as:
286 <screen> user-manual http://example.com/privoxy/user-manual/</screen>
289 <!-- this gets hammered in conversion to config. Text repeated below. -->
292 If set, this option should be <emphasis>the first option in the config
293 file</emphasis>, because it is used while the config file is being read
306 If set, this option should be the first option in the config
307 file, because it is used while the config file is being read.
316 <![%config-file;[<literallayout>@@#user-manual http://www.privoxy.org/user-manual/</literallayout>]]>
320 <!-- ~~~~~ New section ~~~~~ -->
321 <sect3 renderas="sect4" id="trust-info-url"><title>trust-info-url</title>
325 <term>Specifies:</term>
328 A URL to be displayed in the error page that users will see if access to an untrusted page is denied.
333 <term>Type of value:</term>
339 <term>Default value:</term>
341 <para>Two example URLs are provided</para>
345 <term>Effect if unset:</term>
348 No links are displayed on the "untrusted" error page.
356 The value of this option only matters if the experimental trust mechanism has been
357 activated. (See <link linkend="trustfile"><emphasis>trustfile</emphasis></link> below.)
360 If you use the trust mechanism, it is a good idea to write up some on-line
361 documentation about your trust policy and to specify the URL(s) here.
362 Use multiple times for multiple URLs.
365 The URL(s) should be added to the trustfile as well, so users don't end up
366 locked out from the information on why they were locked out in the first place!
372 <![%config-file;[<literallayout>@@trust-info-url http://www.example.com/why_we_block.html</literallayout>]]>
373 <![%config-file;[<literallayout>@@trust-info-url http://www.example.com/what_we_allow.html</literallayout>]]>
377 <!-- ~~~~~ New section ~~~~~ -->
378 <sect3 renderas="sect4" id="admin-address"><title>admin-address</title>
382 <term>Specifies:</term>
385 An email address to reach the <application>Privoxy</application> administrator.
390 <term>Type of value:</term>
392 <para>Email address</para>
396 <term>Default value:</term>
398 <para><emphasis>Unset</emphasis></para>
402 <term>Effect if unset:</term>
405 No email address is displayed on error pages and the CGI user interface.
413 If both <literal>admin-address</literal> and <literal>proxy-info-url</literal>
414 are unset, the whole "Local Privoxy Support" box on all generated pages will
421 <![%config-file;[<literallayout>@@#admin-address privoxy-admin@example.com</literallayout>]]>
425 <!-- ~~~~~ New section ~~~~~ -->
426 <sect3 renderas="sect4" id="proxy-info-url"><title>proxy-info-url</title>
430 <term>Specifies:</term>
433 A URL to documentation about the local <application>Privoxy</application> setup,
434 configuration or policies.
439 <term>Type of value:</term>
445 <term>Default value:</term>
447 <para><emphasis>Unset</emphasis></para>
451 <term>Effect if unset:</term>
454 No link to local documentation is displayed on error pages and the CGI user interface.
462 If both <literal>admin-address</literal> and <literal>proxy-info-url</literal>
463 are unset, the whole "Local Privoxy Support" box on all generated pages will
467 This URL shouldn't be blocked ;-)
473 <![%config-file;[<literallayout>@@#proxy-info-url http://www.example.com/proxy-service.html</literallayout>]]>
477 <!-- ~ End section ~ -->
481 <!-- ~~~~~ New section ~~~~~ -->
483 <sect2 id="conf-log-loc">
484 <title>Configuration and Log File Locations</title>
487 <application>Privoxy</application> can (and normally does) use a number of
488 other files for additional configuration, help and logging.
489 This section of the configuration file tells <application>Privoxy</application>
490 where to find those other files.
494 The user running <application>Privoxy</application>, must have read
495 permission for all configuration files, and write permission to any files
496 that would be modified, such as log files and actions files.
500 <!-- ~~~~~ New section ~~~~~ -->
501 <sect3 renderas="sect4" id="confdir"><title>confdir</title>
505 <term>Specifies:</term>
507 <para>The directory where the other configuration files are located.</para>
511 <term>Type of value:</term>
513 <para>Path name</para>
517 <term>Default value:</term>
519 <para>/etc/privoxy (Unix) <emphasis>or</emphasis> <application>Privoxy</application> installation dir (Windows) </para>
523 <term>Effect if unset:</term>
525 <para><emphasis>Mandatory</emphasis></para>
532 No trailing <quote><literal>/</literal></quote>, please.
535 This is really outdated and not likely to happen. HB 09/20/06
537 When development goes modular and multi-user, the blocker, filter, and
538 per-user config will be stored in subdirectories of <quote>confdir</quote>.
539 For now, the configuration directory structure is flat, except for
540 <filename>confdir/templates</filename>, where the HTML templates for CGI
541 output reside (e.g. <application>Privoxy's</application> 404 error page).
548 <![%config-file;[<literallayout>@@confdir .</literallayout>]]>
551 <!-- ~~~~~ New section ~~~~~ -->
552 <sect3 renderas="sect4" id="templdir"><title>templdir</title>
556 <term>Specifies:</term>
558 <para>An alternative directory where the templates are loaded from.</para>
562 <term>Type of value:</term>
564 <para>Path name</para>
568 <term>Default value:</term>
574 <term>Effect if unset:</term>
576 <para>The templates are assumed to be located in confdir/template.</para>
583 <application>Privoxy's</application> original templates are usually
584 overwritten with each update. Use this option to relocate customized
585 templates that should be kept. As template variables might change
586 between updates, you shouldn't expect templates to work with
587 <application>Privoxy</application> releases other than the one
588 they were part of, though.
594 <![%config-file;[<literallayout>@@#templdir .</literallayout>]]>
598 <!-- ~~~~~ New section ~~~~~ -->
599 <sect3 renderas="sect4" id="logdir"><title>logdir</title>
603 <term>Specifies:</term>
606 The directory where all logging takes place
607 (i.e. where the <filename>logfile</filename> is located).
612 <term>Type of value:</term>
614 <para>Path name</para>
618 <term>Default value:</term>
620 <para>/var/log/privoxy (Unix) <emphasis>or</emphasis> <application>Privoxy</application> installation dir (Windows) </para>
624 <term>Effect if unset:</term>
626 <para><emphasis>Mandatory</emphasis></para>
633 No trailing <quote><literal>/</literal></quote>, please.
639 <![%config-file;[<literallayout>@@logdir .</literallayout>]]>
643 <!-- ~~~~~ New section ~~~~~ -->
644 <sect3 renderas="sect4" id="actionsfile"><title>
647 <anchor id="default.action">
648 <anchor id="standard.action">
649 <anchor id="user.action">
650 <!-- Note: slightly modified this section 04/28/02, hal. See NOTE. -->
653 <term>Specifies:</term>
656 The <link linkend="actions-file">actions file(s)</link> to use
661 <term>Type of value:</term>
663 <para>Complete file name, relative to <literal>confdir</literal></para>
667 <term>Default values:</term>
671 <msgtext><literallayout> standard.action # Internal purposes, no editing recommended</literallayout></msgtext>
674 <msgtext><literallayout> default.action # Main actions file</literallayout></msgtext>
677 <msgtext><literallayout> user.action # User customizations</literallayout></msgtext>
683 <term>Effect if unset:</term>
686 No actions are taken at all. More or less neutral proxying.
694 Multiple <literal>actionsfile</literal> lines are permitted, and are in fact recommended!
697 The default values include <filename>standard.action</filename>, which is used
698 for internal purposes and should be loaded, <filename>default.action</filename>,
699 which is the <quote>main</quote> actions file maintained by the developers, and
700 <filename>user.action</filename>, where you can make your personal additions.
703 Actions files contain all the per site and per URL configuration for
704 ad blocking, cookie management, privacy considerations, etc.
705 There is no point in using <application>Privoxy</application> without at
706 least one actions file.
709 Note that since Privoxy 3.0.7, the complete filename, including the <quote>.action</quote>
710 extension has to be specified. The syntax change was necessary to be consistent
711 with the other file options and to allow previously forbidden characters.
717 <!-- NOTE: alternate markup to make a simpler list doesn't work due to -->
718 <!-- html -> text conversion, blah -->
719 <![%config-file;[<literallayout>@@actionsfile standard.action # Internal purpose, recommended</literallayout>]]>
720 <![%config-file;[<literallayout>@@actionsfile default.action # Main actions file</literallayout>]]>
722 XXX: Like user.filter, user.action should probably be commented out
723 by default as not all packages install it into the default directory.
726 <![%config-file;[<literallayout>@@actionsfile user.action # User customizations</literallayout>]]>
729 <!-- ~~~~~ New section ~~~~~ -->
730 <sect3 renderas="sect4" id="filterfile"><title>filterfile</title>
731 <anchor id="default.filter">
734 <term>Specifies:</term>
737 The <link linkend="filter-file">filter file(s)</link> to use
742 <term>Type of value:</term>
744 <para>File name, relative to <literal>confdir</literal></para>
748 <term>Default value:</term>
750 <para>default.filter (Unix) <emphasis>or</emphasis> default.filter.txt (Windows)</para>
754 <term>Effect if unset:</term>
757 No textual content filtering takes place, i.e. all
758 <literal>+<link linkend="filter">filter</link>{<replaceable class="parameter">name</replaceable>}</literal>
759 actions in the actions files are turned neutral.
767 Multiple <literal>filterfile</literal> lines are permitted.
770 The <link linkend="filter-file">filter files</link> contain content modification
771 rules that use <link linkend="regex">regular expressions</link>. These rules permit
772 powerful changes on the content of Web pages, and optionally the headers
773 as well, e.g., you could try to disable your favorite JavaScript annoyances,
774 re-write the actual displayed text, or just have some fun
775 playing buzzword bingo with web pages.
779 <literal>+<link linkend="filter">filter</link>{<replaceable class="parameter">name</replaceable>}</literal>
780 actions rely on the relevant filter (<replaceable class="parameter">name</replaceable>)
781 to be defined in a filter file!
784 A pre-defined filter file called <filename>default.filter</filename> that contains
785 a number of useful filters for common problems is included in the distribution.
786 See the section on the <literal><link linkend="filter">filter</link></literal>
790 It is recommended to place any locally adapted filters into a separate
791 file, such as <filename>user.filter</filename>.
797 <![%config-file;[<literallayout>@@filterfile default.filter</literallayout>]]>
798 <![%config-file;[<literallayout>@@#filterfile user.filter # User customizations</literallayout>]]>
802 <!-- ~~~~~ New section ~~~~~ -->
803 <sect3 renderas="sect4" id="logfile"><title>logfile</title>
807 <term>Specifies:</term>
815 <term>Type of value:</term>
817 <para>File name, relative to <literal>logdir</literal></para>
821 <term>Default value:</term>
823 <para><emphasis>Unset (commented out)</emphasis>. When activated: logfile (Unix) <emphasis>or</emphasis> privoxy.log (Windows).</para>
827 <term>Effect if unset:</term>
830 No logfile is written.
838 The logfile is where all logging and error messages are written. The level
839 of detail and number of messages are set with the <literal>debug</literal>
840 option (see below). The logfile can be useful for tracking down a problem with
841 <application>Privoxy</application> (e.g., it's not blocking an ad you
842 think it should block) and it can help you to monitor what your browser
846 Depending on the debug options below, the logfile may be a privacy risk
847 if third parties can get access to it. As most users will never look
848 at it, <application>Privoxy</application> 3.0.7 and later only log fatal
852 For most troubleshooting purposes, you will have to change that,
853 please refer to the debugging section for details.
856 Your logfile will grow indefinitely, and you will probably want to
857 periodically remove it. On Unix systems, you can do this with a cron job
858 (see <quote>man cron</quote>). For Red Hat based Linux distributions, a
859 <command>logrotate</command> script has been included.
862 Any log files must be writable by whatever user <application>Privoxy</application>
863 is being run as (on Unix, default user id is <quote>privoxy</quote>).
869 <![%config-file;[<literallayout>@@logfile logfile</literallayout>]]>
873 <!-- ~~~~~ New section ~~~~~ -->
874 <sect3 renderas="sect4" id="trustfile"><title>trustfile</title>
877 <term>Specifies:</term>
880 The name of the trust file to use
885 <term>Type of value:</term>
887 <para>File name, relative to <literal>confdir</literal></para>
891 <term>Default value:</term>
893 <para><emphasis>Unset (commented out)</emphasis>. When activated: trust (Unix) <emphasis>or</emphasis> trust.txt (Windows)</para>
897 <term>Effect if unset:</term>
900 The entire trust mechanism is disabled.
908 The trust mechanism is an experimental feature for building white-lists and should
909 be used with care. It is <emphasis>NOT</emphasis> recommended for the casual user.
912 If you specify a trust file, <application>Privoxy</application> will only allow
913 access to sites that are specified in the trustfile. Sites can be listed
917 Prepending a <literal>~</literal> character limits access to this site
918 only (and any sub-paths within this site), e.g.
919 <literal>~www.example.com</literal> allows access to
920 <literal>~www.example.com/features/news.html</literal>, etc.
923 Or, you can designate sites as <emphasis>trusted referrers</emphasis>, by
924 prepending the name with a <literal>+</literal> character. The effect is that
925 access to untrusted sites will be granted -- but only if a link from this
926 trusted referrer was used to get there. The link target will then be added
927 to the <quote>trustfile</quote> so that future, direct accesses will be
928 granted. Sites added via this mechanism do not become trusted referrers
929 themselves (i.e. they are added with a <literal>~</literal> designation).
930 There is a limit of 512 such entries, after which new entries will not be
934 If you use the <literal>+</literal> operator in the trust file, it may grow
935 considerably over time.
938 It is recommended that <application>Privoxy</application> be compiled with
939 the <literal>--disable-force</literal>, <literal>--disable-toggle</literal> and
940 <literal> --disable-editor</literal> options, if this feature is to be
944 Possible applications include limiting Internet access for children.
951 <![%config-file;[<literallayout>@@#trustfile trust</literallayout>]]>
955 <!-- ~ End section ~ -->
957 <!-- ~~~~~ New section ~~~~~ -->
958 <sect2 id="debugging">
959 <title>Debugging</title>
962 These options are mainly useful when tracing a problem.
963 Note that you might also want to invoke
964 <application>Privoxy</application> with the <literal>--no-daemon</literal>
965 command line option when debugging.
968 <sect3 renderas="sect4" id="debug"><title>debug</title>
972 <term>Specifies:</term>
975 Key values that determine what information gets logged.
980 <term>Type of value:</term>
982 <para>Integer values</para>
986 <term>Default value:</term>
988 <para>0 (i.e.: only fatal errors (that cause Privoxy to exit) are logged)</para>
992 <term>Effect if unset:</term>
995 Default value is used (see above).
1003 The available debug levels are:
1007 debug 1 # log each request destination (and the crunch reason if &my-app; intercepted the request)
1008 debug 2 # show each connection status
1009 debug 4 # show I/O status
1010 debug 8 # show header parsing
1011 debug 16 # log all data written to the network into the logfile
1012 debug 32 # debug force feature
1013 debug 64 # debug regular expression filters
1014 debug 128 # debug redirects
1015 debug 256 # debug GIF de-animation
1016 debug 512 # Common Log Format
1017 debug 2048 # CGI user interface
1018 debug 4096 # Startup banner and warnings.
1019 debug 8192 # Non-fatal errors
1023 To select multiple debug levels, you can either add them or use
1024 multiple <literal>debug</literal> lines.
1027 A debug level of 1 is informative because it will show you each request
1028 as it happens. <emphasis>1, 4096 and 8192 are recommended</emphasis>
1029 so that you will notice when things go wrong. The other levels are
1030 probably only of interest if you are hunting down a specific problem.
1031 They can produce a hell of an output (especially 16).
1035 &my-app; used to ship with the debug levels recommended above enabled by
1036 default, but due to privacy concerns 3.0.7 and later are configured to
1037 only log fatal errors.
1040 If you are used to the more verbose settings, simply enable the debug lines
1044 If you want to use pure CLF (Common Log Format), you should set <quote>debug
1045 512</quote> <emphasis>ONLY</emphasis> and not enable anything else.
1048 <application>Privoxy</application> has a hard-coded limit for the
1049 length of log messages. If it's reached, messages are logged truncated
1050 and marked with <quote>... [too long, truncated]</quote>.
1053 Please don't file any support requests without trying to reproduce
1054 the problem with increased debug level first. Once you read the log
1055 messages, you may even be able to solve the problem on your own.
1061 <![%config-file;[<literallayout>@@#debug 1 # log each request destination (and the crunch reason if &my-app; intercepted the request)</literallayout>]]>
1062 <![%config-file;[<literallayout>@@#debug 4096 # Startup banner and warnings</literallayout>]]>
1063 <![%config-file;[<literallayout>@@#debug 8192 # Non-fatal errors</literallayout>]]>
1067 <!-- ~~~~~ New section ~~~~~ -->
1068 <sect3 renderas="sect4" id="single-threaded"><title>single-threaded</title>
1072 <term>Specifies:</term>
1075 Whether to run only one server thread.
1080 <term>Type of value:</term>
1082 <para><emphasis>None</emphasis></para>
1086 <term>Default value:</term>
1088 <para><emphasis>Unset</emphasis></para>
1092 <term>Effect if unset:</term>
1095 Multi-threaded (or, where unavailable: forked) operation, i.e. the ability to
1096 serve multiple requests simultaneously.
1104 This option is only there for debugging purposes.
1105 <emphasis>It will drastically reduce performance.</emphasis>
1111 <![%config-file;[<literallayout>@@#single-threaded</literallayout>]]>
1114 <!-- ~~~~~ New section ~~~~~ -->
1115 <sect3 renderas="sect4" id="hostname"><title>hostname</title>
1119 <term>Specifies:</term>
1122 The hostname shown on the CGI pages.
1127 <term>Type of value:</term>
1133 <term>Default value:</term>
1135 <para><emphasis>Unset</emphasis></para>
1139 <term>Effect if unset:</term>
1142 The hostname provided by the operating system is used.
1150 On some misconfigured systems resolving the hostname fails or
1151 takes too much time and slows Privoxy down. Setting a fixed hostname
1152 works around the problem.
1155 In other circumstances it might be desirable to show a hostname
1156 other than the one returned by the operating system. For example
1157 if the system has several different hostnames and you don't want
1158 to use the first one.
1161 Note that Privoxy does not validate the specified hostname value.
1167 <![%config-file;[<literallayout>@@#hostname hostname.example.org</literallayout>]]>
1172 <!-- ~ End section ~ -->
1175 <!-- ~~~~~ New section ~~~~~ -->
1176 <sect2 id="access-control">
1177 <title>Access Control and Security</title>
1180 This section of the config file controls the security-relevant aspects
1181 of <application>Privoxy</application>'s configuration.
1185 <!-- ~~~~~ New section ~~~~~ -->
1186 <sect3 renderas="sect4" id="listen-address"><title>listen-address</title>
1190 <term>Specifies:</term>
1193 The IP address and TCP port on which <application>Privoxy</application> will
1194 listen for client requests.
1199 <term>Type of value:</term>
1201 <para>[<replaceable class="parameter">IP-Address</replaceable>]:<replaceable class="parameter">Port</replaceable></para>
1206 <term>Default value:</term>
1208 <para>127.0.0.1:8118</para>
1212 <term>Effect if unset:</term>
1215 Bind to 127.0.0.1 (localhost), port 8118. This is suitable and recommended for
1216 home users who run <application>Privoxy</application> on the same machine as
1225 You will need to configure your browser(s) to this proxy address and port.
1228 If you already have another service running on port 8118, or if you want to
1229 serve requests from other machines (e.g. on your local network) as well, you
1230 will need to override the default.
1233 If you leave out the IP address, <application>Privoxy</application> will
1234 bind to all interfaces (addresses) on your machine and may become reachable
1235 from the Internet. In that case, consider using <link
1236 linkend="acls">access control lists</link> (ACL's, see below), and/or
1240 If you open <application>Privoxy</application> to untrusted users, you will
1241 also want to make sure that the following actions are disabled: <literal><link
1242 linkend="enable-edit-actions">enable-edit-actions</link></literal> and
1243 <literal><link linkend="enable-remote-toggle">enable-remote-toggle</link></literal>
1248 <term>Example:</term>
1251 Suppose you are running <application>Privoxy</application> on
1252 a machine which has the address 192.168.0.1 on your local private network
1253 (192.168.0.0) and has another outside connection with a different address.
1254 You want it to serve requests from inside only:
1258 listen-address 192.168.0.1:8118
1265 <![%config-file;[<literallayout>@@listen-address 127.0.0.1:8118</literallayout>]]>
1269 <!-- ~~~~~ New section ~~~~~ -->
1270 <sect3 renderas="sect4" id="toggle"><title>toggle</title>
1274 <term>Specifies:</term>
1277 Initial state of "toggle" status
1282 <term>Type of value:</term>
1288 <term>Default value:</term>
1294 <term>Effect if unset:</term>
1297 Act as if toggled on
1305 If set to 0, <application>Privoxy</application> will start in
1306 <quote>toggled off</quote> mode, i.e. mostly behave like a normal,
1307 content-neutral proxy with both ad blocking and content filtering
1308 disabled. See <literal>enable-remote-toggle</literal> below.
1310 This is not really useful
1311 anymore, since toggling is much easier via <ulink
1312 url="http://config.privoxy.org/toggle">the web interface</ulink> than via
1313 editing the <filename>conf</filename> file.
1315 Remote toggling is now disabled by default. fk 2007-11-07)
1319 The windows version will only display the toggle icon in the system tray
1320 if this option is present.
1326 <![%config-file;[<literallayout>@@toggle 1</literallayout>]]>
1330 <!-- ~~~~~ New section ~~~~~ -->
1331 <sect3 renderas="sect4" id="enable-remote-toggle"><title>enable-remote-toggle</title>
1334 <term>Specifies:</term>
1337 Whether or not the <ulink url="http://config.privoxy.org/toggle">web-based toggle
1338 feature</ulink> may be used
1343 <term>Type of value:</term>
1349 <term>Default value:</term>
1355 <term>Effect if unset:</term>
1358 The web-based toggle feature is disabled.
1366 When toggled off, <application>Privoxy</application> mostly acts like a normal,
1367 content-neutral proxy, i.e. doesn't block ads or filter content.
1370 Access to the toggle feature can <emphasis>not</emphasis> be
1371 controlled separately by <quote>ACLs</quote> or HTTP authentication,
1372 so that everybody who can access <application>Privoxy</application> (see
1373 <quote>ACLs</quote> and <literal>listen-address</literal> above) can
1374 toggle it for all users. So this option is <emphasis>not recommended</emphasis>
1375 for multi-user environments with untrusted users.
1378 Note that malicious client side code (e.g Java) is also
1379 capable of using this option.
1382 As a lot of <application>Privoxy</application> users don't read
1383 documentation, this feature is disabled by default.
1386 Note that you must have compiled <application>Privoxy</application> with
1387 support for this feature, otherwise this option has no effect.
1393 <![%config-file;[<literallayout>@@enable-remote-toggle 0</literallayout>]]>
1397 <!-- ~~~~~ New section ~~~~~ -->
1398 <sect3 renderas="sect4" id="enable-remote-http-toggle"><title>enable-remote-http-toggle</title>
1401 <term>Specifies:</term>
1404 Whether or not Privoxy recognizes special HTTP headers to change its behaviour.
1409 <term>Type of value:</term>
1415 <term>Default value:</term>
1421 <term>Effect if unset:</term>
1424 Privoxy ignores special HTTP headers.
1432 When toggled on, the client can change <application>Privoxy's</application>
1433 behaviour by setting special HTTP headers. Currently the only supported
1434 special header is <quote>X-Filter: No</quote>, to disable filtering for
1435 the ongoing request, even if it is enabled in one of the action files.
1438 This feature is disabled by default. If you are using
1439 <application>Privoxy</application> in a environment with trusted clients,
1440 you may enable this feature at your discretion. Note that malicious client
1441 side code (e.g Java) is also capable of using this feature.
1444 This option will be removed in future releases as it has been obsoleted
1445 by the more general header taggers.
1451 <![%config-file;[<literallayout>@@enable-remote-http-toggle 0</literallayout>]]>
1455 <!-- ~~~~~ New section ~~~~~ -->
1456 <sect3 renderas="sect4" id="enable-edit-actions"><title>enable-edit-actions</title>
1459 <term>Specifies:</term>
1462 Whether or not the <ulink url="http://config.privoxy.org/show-status">web-based actions
1463 file editor</ulink> may be used
1468 <term>Type of value:</term>
1474 <term>Default value:</term>
1480 <term>Effect if unset:</term>
1483 The web-based actions file editor is disabled.
1491 Access to the editor can <emphasis>not</emphasis> be
1492 controlled separately by <quote>ACLs</quote> or HTTP authentication,
1493 so that everybody who can access <application>Privoxy</application> (see
1494 <quote>ACLs</quote> and <literal>listen-address</literal> above) can
1495 modify its configuration for all users.
1498 This option is <emphasis>not recommended</emphasis> for environments
1499 with untrusted users and as a lot of <application>Privoxy</application>
1500 users don't read documentation, this feature is disabled by default.
1503 Note that malicious client side code (e.g Java) is also
1504 capable of using the actions editor and you shouldn't enable
1505 this options unless you understand the consequences and are
1506 sure your browser is configured correctly.
1509 Note that you must have compiled <application>Privoxy</application> with
1510 support for this feature, otherwise this option has no effect.
1516 <![%config-file;[<literallayout>@@enable-edit-actions 0</literallayout>]]>
1520 <sect3 renderas="sect4" id="enforce-blocks"><title>enforce-blocks</title>
1523 <term>Specifies:</term>
1526 Whether the user is allowed to ignore blocks and can <quote>go there anyway</quote>.
1531 <term>Type of value:</term>
1534 <replaceable>0 or 1</replaceable>
1539 <term>Default value:</term>
1541 <para><emphasis>0</emphasis></para>
1545 <term>Effect if unset:</term>
1548 Blocks are not enforced.
1556 <application>Privoxy</application> is mainly used to block and filter
1557 requests as a service to the user, for example to block ads and other
1558 junk that clogs the pipes. <application>Privoxy's</application> configuration
1559 isn't perfect and sometimes innocent pages are blocked. In this situation it
1560 makes sense to allow the user to enforce the request and have
1561 <application>Privoxy</application> ignore the block.
1564 In the default configuration <application>Privoxy's</application>
1565 <quote>Blocked</quote> page contains a <quote>go there anyway</quote>
1566 link to adds a special string (the force prefix) to the request URL.
1567 If that link is used, <application>Privoxy</application> will
1568 detect the force prefix, remove it again and let the request pass.
1571 Of course <application>Privoxy</application> can also be used to enforce
1572 a network policy. In that case the user obviously should not be able to
1573 bypass any blocks, and that's what the <quote>enforce-blocks</quote>
1574 option is for. If it's enabled, <application>Privoxy</application> hides
1575 the <quote>go there anyway</quote> link. If the user adds the force
1576 prefix by hand, it will not be accepted and the circumvention attempt
1582 <term>Examples:</term>
1590 <![%config-file;[<literallayout>@@enforce-blocks 0</literallayout>]]>
1594 <!-- ~~~~~ New section ~~~~~ -->
1595 <sect3 renderas="sect4" id="acls"><title>
1596 ACLs: permit-access and deny-access</title>
1597 <anchor id="permit-access">
1598 <anchor id="deny-access">
1602 <term>Specifies:</term>
1605 Who can access what.
1610 <term>Type of value:</term>
1613 <replaceable class="parameter">src_addr</replaceable>[/<replaceable class="parameter">src_masklen</replaceable>]
1614 [<replaceable class="parameter">dst_addr</replaceable>[/<replaceable class="parameter">dst_masklen</replaceable>]]
1617 Where <replaceable class="parameter">src_addr</replaceable> and
1618 <replaceable class="parameter">dst_addr</replaceable> are IP addresses in dotted decimal notation or valid
1619 DNS names, and <replaceable class="parameter">src_masklen</replaceable> and
1620 <replaceable class="parameter">dst_masklen</replaceable> are subnet masks in CIDR notation, i.e. integer
1621 values from 2 to 30 representing the length (in bits) of the network address. The masks and the whole
1622 destination part are optional.
1627 <term>Default value:</term>
1629 <para><emphasis>Unset</emphasis></para>
1633 <term>Effect if unset:</term>
1636 Don't restrict access further than implied by <literal>listen-address</literal>
1644 Access controls are included at the request of ISPs and systems
1645 administrators, and <emphasis>are not usually needed by individual users</emphasis>.
1646 For a typical home user, it will normally suffice to ensure that
1647 <application>Privoxy</application> only listens on the localhost
1648 (127.0.0.1) or internal (home) network address by means of the
1649 <link linkend="listen-address"><emphasis>listen-address</emphasis></link>
1653 Please see the warnings in the FAQ that <application>Privoxy</application>
1654 is not intended to be a substitute for a firewall or to encourage anyone
1655 to defer addressing basic security weaknesses.
1658 Multiple ACL lines are OK.
1659 If any ACLs are specified, <application>Privoxy</application> only talks
1660 to IP addresses that match at least one <literal>permit-access</literal> line
1661 and don't match any subsequent <literal>deny-access</literal> line. In other words, the
1662 last match wins, with the default being <literal>deny-access</literal>.
1665 If <application>Privoxy</application> is using a forwarder (see <literal>forward</literal> below)
1666 for a particular destination URL, the <replaceable class="parameter">dst_addr</replaceable>
1667 that is examined is the address of the forwarder and <emphasis>NOT</emphasis> the address
1668 of the ultimate target. This is necessary because it may be impossible for the local
1669 <application>Privoxy</application> to determine the IP address of the
1670 ultimate target (that's often what gateways are used for).
1673 You should prefer using IP addresses over DNS names, because the address lookups take
1674 time. All DNS names must resolve! You can <emphasis>not</emphasis> use domain patterns
1675 like <quote>*.org</quote> or partial domain names. If a DNS name resolves to multiple
1676 IP addresses, only the first one is used.
1679 Denying access to particular sites by ACL may have undesired side effects
1680 if the site in question is hosted on a machine which also hosts other sites
1686 <term>Examples:</term>
1689 Explicitly define the default behavior if no ACL and
1690 <literal>listen-address</literal> are set: <quote>localhost</quote>
1691 is OK. The absence of a <replaceable class="parameter">dst_addr</replaceable> implies that
1692 <emphasis>all</emphasis> destination addresses are OK:
1696 permit-access localhost
1700 Allow any host on the same class C subnet as www.privoxy.org access to
1701 nothing but www.example.com (or other domains hosted on the same system):
1705 permit-access www.privoxy.org/24 www.example.com/32
1709 Allow access from any host on the 26-bit subnet 192.168.45.64 to anywhere,
1710 with the exception that 192.168.45.73 may not access the IP address behind
1711 www.dirty-stuff.example.com:
1715 permit-access 192.168.45.64/26
1716 deny-access 192.168.45.73 www.dirty-stuff.example.com
1725 <!-- ~~~~~ New section ~~~~~ -->
1726 <sect3 renderas="sect4" id="buffer-limit"><title>buffer-limit</title>
1730 <term>Specifies:</term>
1733 Maximum size of the buffer for content filtering.
1738 <term>Type of value:</term>
1740 <para>Size in Kbytes</para>
1744 <term>Default value:</term>
1750 <term>Effect if unset:</term>
1753 Use a 4MB (4096 KB) limit.
1761 For content filtering, i.e. the <literal>+filter</literal> and
1762 <literal>+deanimate-gif</literal> actions, it is necessary that
1763 <application>Privoxy</application> buffers the entire document body.
1764 This can be potentially dangerous, since a server could just keep sending
1765 data indefinitely and wait for your RAM to exhaust -- with nasty consequences.
1769 When a document buffer size reaches the <literal>buffer-limit</literal>, it is
1770 flushed to the client unfiltered and no further attempt to
1771 filter the rest of the document is made. Remember that there may be multiple threads
1772 running, which might require up to <literal>buffer-limit</literal> Kbytes
1773 <emphasis>each</emphasis>, unless you have enabled <quote>single-threaded</quote>
1780 <![%config-file;[<literallayout>@@buffer-limit 4096</literallayout>]]>
1785 <!-- ~ End section ~ -->
1788 <!-- ~~~~~ New section ~~~~~ -->
1790 <sect2 id="forwarding">
1791 <title>Forwarding</title>
1794 This feature allows routing of HTTP requests through a chain of
1798 Forwarding can be used to chain Privoxy with a caching proxy to speed
1799 up browsing. Using a parent proxy may also be necessary if the machine
1800 that <application>Privoxy</application> runs on has no direct Internet access.
1803 Note that parent proxies can severely decrease your privacy level.
1804 For example a parent proxy could add your IP address to the request
1805 headers and if it's a caching proxy it may add the <quote>Etag</quote>
1806 header to revalidation requests again, even though you configured Privoxy
1807 to remove it. It may also ignore Privoxy's header time randomization and use the
1808 original values which could be used by the server as cookie replacement
1809 to track your steps between visits.
1813 Also specified here are SOCKS proxies. <application>Privoxy</application>
1814 supports the SOCKS 4 and SOCKS 4A protocols.
1817 <sect3 renderas="sect4" id="forward"><title>forward</title>
1820 <term>Specifies:</term>
1823 To which parent HTTP proxy specific requests should be routed.
1828 <term>Type of value:</term>
1831 <replaceable class="parameter">target_pattern</replaceable>
1832 <replaceable class="parameter">http_parent</replaceable>[:<replaceable class="parameter">port</replaceable>]
1835 where <replaceable class="parameter">target_pattern</replaceable> is a <link linkend="af-patterns">URL pattern</link>
1836 that specifies to which requests (i.e. URLs) this forward rule shall apply. Use <literal>/</literal> to
1837 denote <quote>all URLs</quote>.
1838 <replaceable class="parameter">http_parent</replaceable>[:<replaceable class="parameter">port</replaceable>]
1839 is the DNS name or IP address of the parent HTTP proxy through which the requests should be forwarded,
1840 optionally followed by its listening port (default: 8080).
1841 Use a single dot (<literal>.</literal>) to denote <quote>no forwarding</quote>.
1846 <term>Default value:</term>
1848 <para><emphasis>Unset</emphasis></para>
1852 <term>Effect if unset:</term>
1855 Don't use parent HTTP proxies.
1863 If <replaceable class="parameter">http_parent</replaceable> is <quote>.</quote>, then requests are not
1864 forwarded to another HTTP proxy but are made directly to the web servers.
1867 Multiple lines are OK, they are checked in sequence, and the last match wins.
1872 <term>Examples:</term>
1875 Everything goes to an example parent proxy, except SSL on port 443 (which it doesn't handle):
1879 forward / parent-proxy.example.org:8080
1884 Everything goes to our example ISP's caching proxy, except for requests
1885 to that ISP's sites:
1889 forward / caching-proxy.isp.example.net:8000
1890 forward .isp.example.net .
1899 <!-- ~~~~~ New section ~~~~~ -->
1900 <sect3 renderas="sect4" id="socks"><title>
1901 forward-socks4, forward-socks4a and forward-socks5</title>
1902 <anchor id="forward-socks4">
1903 <anchor id="forward-socks4a">
1907 <term>Specifies:</term>
1910 Through which SOCKS proxy (and optionally to which parent HTTP proxy) specific requests should be routed.
1915 <term>Type of value:</term>
1918 <replaceable class="parameter">target_pattern</replaceable>
1919 <replaceable class="parameter">socks_proxy</replaceable>[:<replaceable class="parameter">port</replaceable>]
1920 <replaceable class="parameter">http_parent</replaceable>[:<replaceable class="parameter">port</replaceable>]
1923 where <replaceable class="parameter">target_pattern</replaceable> is a
1924 <link linkend="af-patterns">URL pattern</link> that specifies to which
1925 requests (i.e. URLs) this forward rule shall apply. Use <literal>/</literal> to
1926 denote <quote>all URLs</quote>. <replaceable class="parameter">http_parent</replaceable>
1927 and <replaceable class="parameter">socks_proxy</replaceable>
1928 are IP addresses in dotted decimal notation or valid DNS names
1929 (<replaceable class="parameter">http_parent</replaceable>
1930 may be <quote>.</quote> to denote <quote>no HTTP forwarding</quote>), and the optional
1931 <replaceable class="parameter">port</replaceable> parameters are TCP ports,
1932 i.e. integer values from 1 to 65535
1937 <term>Default value:</term>
1939 <para><emphasis>Unset</emphasis></para>
1943 <term>Effect if unset:</term>
1946 Don't use SOCKS proxies.
1954 Multiple lines are OK, they are checked in sequence, and the last match wins.
1957 The difference between <literal>forward-socks4</literal> and <literal>forward-socks4a</literal>
1958 is that in the SOCKS 4A protocol, the DNS resolution of the target hostname happens on the SOCKS
1959 server, while in SOCKS 4 it happens locally.
1962 With <literal>forward-socks5</literal> the DNS resolution will happen on the remote server as well.
1965 If <replaceable class="parameter">http_parent</replaceable> is <quote>.</quote>, then requests are not
1966 forwarded to another HTTP proxy but are made (HTTP-wise) directly to the web servers, albeit through
1972 <term>Examples:</term>
1975 From the company example.com, direct connections are made to all
1976 <quote>internal</quote> domains, but everything outbound goes through
1977 their ISP's proxy by way of example.com's corporate SOCKS 4A gateway to
1982 forward-socks4a / socks-gw.example.com:1080 www-cache.isp.example.net:8080
1983 forward .example.com .
1987 A rule that uses a SOCKS 4 gateway for all destinations but no HTTP parent looks like this:
1991 forward-socks4 / socks-gw.example.com:1080 .
1996 To chain Privoxy and Tor, both running on the same system, you would use
2001 forward-socks4a / 127.0.0.1:9050 .
2006 The public <application>Tor</application> network can't be used to
2007 reach your local network, if you need to access local servers you
2008 therefore might want to make some exceptions:
2012 forward 192.168.*.*/ .
2014 forward 127.*.*.*/ .
2018 Unencrypted connections to systems in these address ranges will
2019 be as (un)secure as the local network is, but the alternative is that you
2020 can't reach the local network through <application>Privoxy</application>
2021 at all. Of course this may actually be desired and there is no reason
2022 to make these exceptions if you aren't sure you need them.
2025 If you also want to be able to reach servers in your local network by
2026 using their names, you will need additional exceptions that look like
2031 forward localhost/ .
2040 <![%user-man;[ <!-- not included in config due to length -->
2041 <!-- ~~~~~ New section ~~~~~ -->
2042 <sect3 renderas="sect4" id="advanced-forwarding-examples"><title>Advanced Forwarding Examples</title>
2045 If you have links to multiple ISPs that provide various special content
2046 only to their subscribers, you can configure multiple <application>Privoxies</application>
2047 which have connections to the respective ISPs to act as forwarders to each other, so that
2048 <emphasis>your</emphasis> users can see the internal content of all ISPs.
2052 Assume that host-a has a PPP connection to isp-a.example.net. And host-b has a PPP connection to
2053 isp-b.example.org. Both run <application>Privoxy</application>. Their forwarding
2054 configuration can look like this:
2064 forward .isp-b.example.net host-b:8118
2075 forward .isp-a.example.org host-a:8118
2080 Now, your users can set their browser's proxy to use either
2081 host-a or host-b and be able to browse the internal content
2082 of both isp-a and isp-b.
2086 If you intend to chain <application>Privoxy</application> and
2087 <application>squid</application> locally, then chaining as
2088 <literal>browser -> squid -> privoxy</literal> is the recommended way.
2092 Assuming that <application>Privoxy</application> and <application>squid</application>
2093 run on the same box, your <application>squid</application> configuration could then look like this:
2098 # Define Privoxy as parent proxy (without ICP)
2099 cache_peer 127.0.0.1 parent 8118 7 no-query
2101 # Define ACL for protocol FTP
2104 # Do not forward FTP requests to Privoxy
2105 always_direct allow ftp
2107 # Forward all the rest to Privoxy
2108 never_direct allow all</screen>
2112 You would then need to change your browser's proxy settings to <application>squid</application>'s address and port.
2113 Squid normally uses port 3128. If unsure consult <literal>http_port</literal> in <filename>squid.conf</filename>.
2117 You could just as well decide to only forward requests you suspect
2118 of leading to Windows executables through a virus-scanning parent proxy,
2119 say, on <literal>antivir.example.com</literal>, port 8010:
2125 forward /.*\.(exe|com|dll|zip)$ antivir.example.com:8010</screen>
2131 <sect3 renderas="sect4" id="forwarded-connect-retries"><title>forwarded-connect-retries</title>
2134 <term>Specifies:</term>
2137 How often Privoxy retries if a forwarded connection request fails.
2142 <term>Type of value:</term>
2145 <replaceable class="parameter">Number of retries.</replaceable>
2150 <term>Default value:</term>
2152 <para><emphasis>0</emphasis></para>
2156 <term>Effect if unset:</term>
2159 Connections forwarded through other proxies are treated like direct connections and no retry attempts are made.
2167 <replaceable class="parameter">forwarded-connect-retries</replaceable> is mainly interesting
2168 for socks4a connections, where <application>Privoxy</application> can't detect why the connections failed.
2169 The connection might have failed because of a DNS timeout in which case a retry makes sense,
2170 but it might also have failed because the server doesn't exist or isn't reachable. In this
2171 case the retry will just delay the appearance of Privoxy's error message.
2174 Note that in the context of this option, <quote>forwarded connections</quote> includes all connections
2175 that Privoxy forwards through other proxies. This option is not limited to the HTTP CONNECT method.
2178 Only use this option, if you are getting lots of forwarding-related error messages
2179 that go away when you try again manually. Start with a small value and check Privoxy's
2180 logfile from time to time, to see how many retries are usually needed.
2185 <term>Examples:</term>
2188 forwarded-connect-retries 1
2193 <![%config-file;[<literallayout>@@forwarded-connect-retries 0</literallayout>]]>
2196 <sect3 renderas="sect4" id="accept-intercepted-requests"><title>accept-intercepted-requests</title>
2199 <term>Specifies:</term>
2202 Whether intercepted requests should be treated as valid.
2207 <term>Type of value:</term>
2210 <replaceable>0 or 1</replaceable>
2215 <term>Default value:</term>
2217 <para><emphasis>0</emphasis></para>
2221 <term>Effect if unset:</term>
2224 Only proxy requests are accepted, intercepted requests are treated as invalid.
2232 If you don't trust your clients and want to force them
2233 to use <application>Privoxy</application>, enable this
2234 option and configure your packet filter to redirect outgoing
2235 HTTP connections into <application>Privoxy</application>.
2238 Make sure that <application>Privoxy's</application> own requests
2239 aren't redirected as well. Additionally take care that
2240 <application>Privoxy</application> can't intentionally connect
2241 to itself, otherwise you could run into redirection loops if
2242 <application>Privoxy's</application> listening port is reachable
2243 by the outside or an attacker has access to the pages you visit.
2248 <term>Examples:</term>
2251 accept-intercepted-requests 1
2256 <![%config-file;[<literallayout>@@accept-intercepted-requests 0</literallayout>]]>
2259 <sect3 renderas="sect4" id="allow-cgi-request-crunching"><title>allow-cgi-request-crunching</title>
2262 <term>Specifies:</term>
2265 Whether requests to <application>Privoxy's</application> CGI pages can be blocked or redirected.
2270 <term>Type of value:</term>
2273 <replaceable>0 or 1</replaceable>
2278 <term>Default value:</term>
2280 <para><emphasis>0</emphasis></para>
2284 <term>Effect if unset:</term>
2287 <application>Privoxy</application> ignores block and redirect actions for its CGI pages.
2295 By default <application>Privoxy</application> ignores block or redirect actions
2296 for its CGI pages. Intercepting these requests can be useful in multi-user
2297 setups to implement fine-grained access control, but it can also render the complete
2298 web interface useless and make debugging problems painful if done without care.
2301 Don't enable this option unless you're sure that you really need it.
2306 <term>Examples:</term>
2309 allow-cgi-request-crunching 1
2314 <![%config-file;[<literallayout>@@allow-cgi-request-crunching 0</literallayout>]]>
2317 <sect3 renderas="sect4" id="split-large-forms"><title>split-large-forms</title>
2320 <term>Specifies:</term>
2323 Whether the CGI interface should stay compatible with broken HTTP clients.
2328 <term>Type of value:</term>
2331 <replaceable>0 or 1</replaceable>
2336 <term>Default value:</term>
2338 <para><emphasis>0</emphasis></para>
2342 <term>Effect if unset:</term>
2345 The CGI form generate long GET URLs.
2353 <application>Privoxy's</application> CGI forms can lead to
2354 rather long URLs. This isn't a problem as far as the HTTP
2355 standard is concerned, but it can confuse clients with arbitrary
2356 URL length limitations.
2359 Enabling split-large-forms causes <application>Privoxy</application>
2360 to divide big forms into smaller ones to keep the URL length down.
2361 It makes editing a lot less convenient and you can no longer
2362 submit all changes at once, but at least it works around this
2366 If you don't notice any editing problems, there is no reason
2367 to enable this option, but if one of the submit buttons appears
2368 to be broken, you should give it a try.
2373 <term>Examples:</term>
2381 <![%config-file;[<literallayout>@@split-large-forms 0</literallayout>]]>
2384 <sect3 renderas="sect4" id="keep-alive-timeout"><title>keep-alive-timeout</title>
2387 <term>Specifies:</term>
2390 Number of seconds after which an open connection will no longer be reused.
2395 <term>Type of value:</term>
2398 <replaceable>Time in seconds.</replaceable>
2403 <term>Default value:</term>
2409 <term>Effect if unset:</term>
2412 Connections are not reused.
2420 This option has no effect if <application>Privoxy</application>
2421 has been compiled without keep-alive support.
2426 <term>Examples:</term>
2429 keep-alive-timeout 300
2434 <![%config-file;[<literallayout>@@keep-alive-timeout 300</literallayout>]]>
2440 <!-- ~ End section ~ -->
2443 <!-- ~~~~~ New section ~~~~~ -->
2445 <sect2 id="windows-gui">
2446 <title>Windows GUI Options</title>
2448 <application>Privoxy</application> has a number of options specific to the
2449 Windows GUI interface:
2452 <anchor id="activity-animation">
2453 <![%config-file;[<para>@@</para>]]> <!-- for spacing -->
2455 If <quote>activity-animation</quote> is set to 1, the
2456 <application>Privoxy</application> icon will animate when
2457 <quote>Privoxy</quote> is active. To turn off, set to 0.
2460 <![%config-file;[<literallayout>@@#activity-animation 1</literallayout>]]>
2466 <emphasis>activity-animation 1</emphasis>
2473 <anchor id="log-messages">
2474 <![%config-file;[<para>@@</para>]]> <!-- for spacing -->
2476 If <quote>log-messages</quote> is set to 1,
2477 <application>Privoxy</application> will log messages to the console
2481 <![%config-file;[<literallayout>@@#log-messages 1</literallayout>]]>
2487 <emphasis>log-messages 1</emphasis>
2494 <anchor id="log-buffer-size">
2495 <![%config-file;[<para>@@</para>]]> <!-- for spacing -->
2497 If <quote>log-buffer-size</quote> is set to 1, the size of the log buffer,
2498 i.e. the amount of memory used for the log messages displayed in the
2499 console window, will be limited to <quote>log-max-lines</quote> (see below).
2503 Warning: Setting this to 0 will result in the buffer to grow infinitely and
2504 eat up all your memory!
2507 <![%config-file;[<literallayout>@@#log-buffer-size 1</literallayout>]]>
2513 <emphasis>log-buffer-size 1</emphasis>
2520 <anchor id="log-max-lines">
2521 <![%config-file;[<para>@@</para>]]> <!-- for spacing -->
2523 <application>log-max-lines</application> is the maximum number of lines held
2524 in the log buffer. See above.
2527 <![%config-file;[<literallayout>@@#log-max-lines 200</literallayout>]]>
2533 <emphasis>log-max-lines 200</emphasis>
2540 <anchor id="log-highlight-messages">
2541 <![%config-file;[<para>@@</para>]]> <!-- for spacing -->
2543 If <quote>log-highlight-messages</quote> is set to 1,
2544 <application>Privoxy</application> will highlight portions of the log
2545 messages with a bold-faced font:
2548 <![%config-file;[<literallayout>@@#log-highlight-messages 1</literallayout>]]>
2554 <emphasis>log-highlight-messages 1</emphasis>
2561 <anchor id="log-font-name">
2562 <![%config-file;[<para>@@</para>]]> <!-- for spacing -->
2564 The font used in the console window:
2567 <![%config-file;[<literallayout>@@#log-font-name Comic Sans MS</literallayout>]]>
2573 <emphasis>log-font-name Comic Sans MS</emphasis>
2580 <anchor id="log-font-size">
2581 <![%config-file;[<para>@@</para>]]> <!-- for spacing -->
2583 Font size used in the console window:
2586 <![%config-file;[<literallayout>@@#log-font-size 8</literallayout>]]>
2592 <emphasis>log-font-size 8</emphasis>
2599 <anchor id="show-on-task-bar">
2600 <![%config-file;[<para>@@</para>]]> <!-- for spacing -->
2602 <quote>show-on-task-bar</quote> controls whether or not
2603 <application>Privoxy</application> will appear as a button on the Task bar
2607 <![%config-file;[<literallayout>@@#show-on-task-bar 0</literallayout>]]>
2613 <emphasis>show-on-task-bar 0</emphasis>
2620 <anchor id="close-button-minimizes">
2621 <![%config-file;[<para>@@</para>]]> <!-- for spacing -->
2623 If <quote>close-button-minimizes</quote> is set to 1, the Windows close
2624 button will minimize <application>Privoxy</application> instead of closing
2625 the program (close with the exit option on the File menu).
2628 <![%config-file;[<literallayout>@@#close-button-minimizes 1</literallayout>]]>
2634 <emphasis>close-button-minimizes 1</emphasis>
2641 <anchor id="hide-console">
2642 <![%config-file;[<para>@@</para>]]> <!-- for spacing -->
2644 The <quote>hide-console</quote> option is specific to the MS-Win console
2645 version of <application>Privoxy</application>. If this option is used,
2646 <application>Privoxy</application> will disconnect from and hide the
2650 <![%config-file;[<literallayout>@@#hide-console</literallayout>]]>
2656 #<emphasis>hide-console</emphasis>
2666 <!-- end config content common to both outputs -->
2669 <!-- These are dummy anchors to keep the processor quiet -->
2670 <!-- when building config-file only (ie. they are used in u-m only) -->
2673 <anchor id="filter">
2674 <anchor id="filter-file">
2676 <anchor id="actions-file">
2677 <anchor id="af-patterns">
2681 <!-- eof p-config.sgml -->