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.12 2006/09/22 01:27:55 hal9 Exp $
8 Copyright (C) 2001-2007 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.12 2006/09/22 01:27:55 hal9 Exp $
101 Copyright (C) 2001-2006 Privoxy Developers http://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 the Privoxy configuration. If you modify this
129 file, you will need to send a couple of requests (of any kind) to the proxy
130 before any changes take effect.
133 When starting Privoxy on Unix systems, give the name of this
134 file as an argument. On Windows systems, Privoxy will look for
135 this file with the name 'config.txt' in the same directory where
136 Privoxy is installed.
140 <literallayout><!-- funky spacing -->
142 II. FORMAT OF THE CONFIGURATION FILE
143 ====================================</literallayout>
146 Configuration lines consist of an initial keyword followed by a list
147 of values, all separated by whitespace (any number of spaces or
151 actionsfile default.action
154 Indicates that the actionsfile is named 'default.action'.
157 The '#' indicates a comment. Any part of a line following a '#' is
158 ignored, except if the '#' is preceded by a '\'.
161 Thus, by placing a # at the start of an existing configuration line,
162 you can make it a comment and it will be treated as if it weren't there.
163 This is called "commenting out" an option and can be useful.
166 Note that commenting out and option and leaving it at its default
167 are two completely different things! Most options behave very
168 differently when unset. See the the "Effect if unset" explanation
169 in each option's description for details.
172 Long lines can be continued on the next line by using a `\' as
178 <!-- ************************************************ -->
179 <!-- The following is common to both outputs (mostly) -->
180 <!-- ************************************************ -->
184 <!-- ~~~~~ New section ~~~~~ -->
185 <sect2 id="local-set-up">
186 <title>Local Set-up Documentation</title>
189 If you intend to operate <application>Privoxy</application> for more users
190 than just yourself, it might be a good idea to let them know how to reach
191 you, what you block and why you do that, your policies, etc.
195 <!-- ~~~~~ New section ~~~~~ -->
196 <sect3 renderas="sect4" id="user-manual"><title>user-manual</title>
199 <term>Specifies:</term>
202 Location of the <application>Privoxy</application> User Manual.
207 <term>Type of value:</term>
209 <para>A fully qualified URI</para>
213 <term>Default value:</term>
215 <para><emphasis>Unset</emphasis></para>
219 <term>Effect if unset:</term>
222 <ulink url="http://www.privoxy.org/user-manual/">http://www.privoxy.org/<replaceable class="parameter">version</replaceable>/user-manual/</ulink>
223 will be used, where <replaceable class="parameter">version</replaceable> is the <application>Privoxy</application> version.
231 The User Manual URI is the single best source of information on
232 <application>Privoxy</application>, and is used for help links from some
233 of the internal CGI pages. The manual itself is normally packaged with the
234 binary distributions, so you probably want to set this to a locally
242 Unix, in local filesystem (may not work with all browsers):
245 <screen> user-manual file:///usr/share/doc/privoxy-&p-version;/user-manual/</screen>
248 Windows, in local filesystem, <emphasis>must</emphasis> use forward slash notation:
251 <screen> user-manual file:/c:/some-dir/privoxy-&p-version;/user-manual/</screen>
254 Windows, UNC notation (with forward slashes):
257 <screen> user-manual file://///some-server/some-path/privoxy-&p-version;/user-manual/</screen>
261 The best all purpose solution is simply to put the full local
262 <literal>PATH</literal> to where the <citetitle>User Manual</citetitle> is
266 <screen> user-manual /usr/share/doc/privoxy/user-manual</screen>
269 The User Manual is then available to anyone with access to the proxy, by
270 following the built-in URL: <literal>http://config.privoxy.org/user-manual/</literal>
271 (or the shortcut: <literal>http://p.p/user-manual/</literal>).
274 If the documentation is not on the local system, it can be accessed
275 from a remote server, as:
278 <screen> user-manual http://example.com/privoxy/user-manual/</screen>
281 <!-- this gets hammered in conversion to config. Text repeated below. -->
284 If set, this option should be <emphasis>the first option in the config
285 file</emphasis>, because it is used while the config file is being read
298 If set, this option should be the first option in the config
299 file, because it is used while the config file is being read.
308 <![%config-file;[<literallayout>@@#user-manual http://www.privoxy.org/user-manual/</literallayout>]]>
312 <!-- ~~~~~ New section ~~~~~ -->
313 <sect3 renderas="sect4" id="trust-info-url"><title>trust-info-url</title>
317 <term>Specifies:</term>
320 A URL to be displayed in the error page that users will see if access to an untrusted page is denied.
325 <term>Type of value:</term>
331 <term>Default value:</term>
333 <para>Two example URL are provided</para>
337 <term>Effect if unset:</term>
340 No links are displayed on the "untrusted" error page.
348 The value of this option only matters if the experimental trust mechanism has been
349 activated. (See <link linkend="trustfile"><emphasis>trustfile</emphasis></link> above.)
352 If you use the trust mechanism, it is a good idea to write up some on-line
353 documentation about your trust policy and to specify the URL(s) here.
354 Use multiple times for multiple URLs.
357 The URL(s) should be added to the trustfile as well, so users don't end up
358 locked out from the information on why they were locked out in the first place!
364 <![%config-file;[<literallayout>@@trust-info-url http://www.example.com/why_we_block.html</literallayout>]]>
365 <![%config-file;[<literallayout>@@trust-info-url http://www.example.com/what_we_allow.html</literallayout>]]>
369 <!-- ~~~~~ New section ~~~~~ -->
370 <sect3 renderas="sect4" id="admin-address"><title>admin-address</title>
374 <term>Specifies:</term>
377 An email address to reach the proxy administrator.
382 <term>Type of value:</term>
384 <para>Email address</para>
388 <term>Default value:</term>
390 <para><emphasis>Unset</emphasis></para>
394 <term>Effect if unset:</term>
397 No email address is displayed on error pages and the CGI user interface.
405 If both <literal>admin-address</literal> and <literal>proxy-info-url</literal>
406 are unset, the whole "Local Privoxy Support" box on all generated pages will
413 <![%config-file;[<literallayout>@@#admin-address privoxy-admin@example.com</literallayout>]]>
417 <!-- ~~~~~ New section ~~~~~ -->
418 <sect3 renderas="sect4" id="proxy-info-url"><title>proxy-info-url</title>
422 <term>Specifies:</term>
425 A URL to documentation about the local <application>Privoxy</application> setup,
426 configuration or policies.
431 <term>Type of value:</term>
437 <term>Default value:</term>
439 <para><emphasis>Unset</emphasis></para>
443 <term>Effect if unset:</term>
446 No link to local documentation is displayed on error pages and the CGI user interface.
454 If both <literal>admin-address</literal> and <literal>proxy-info-url</literal>
455 are unset, the whole "Local Privoxy Support" box on all generated pages will
459 This URL shouldn't be blocked ;-)
465 <![%config-file;[<literallayout>@@#proxy-info-url http://www.example.com/proxy-service.html</literallayout>]]>
469 <!-- ~ End section ~ -->
473 <!-- ~~~~~ New section ~~~~~ -->
475 <sect2 id="conf-log-loc">
476 <title>Configuration and Log File Locations</title>
479 <application>Privoxy</application> can (and normally does) use a number of
480 other files for additional configuration, help and logging.
481 This section of the configuration file tells <application>Privoxy</application>
482 where to find those other files.
486 The user running <application>Privoxy</application>, must have read
487 permission for all configuration files, and write permission to any files
488 that would be modified, such as log files and actions files.
492 <!-- ~~~~~ New section ~~~~~ -->
493 <sect3 renderas="sect4" id="confdir"><title>confdir</title>
497 <term>Specifies:</term>
499 <para>The directory where the other configuration files are located</para>
503 <term>Type of value:</term>
505 <para>Path name</para>
509 <term>Default value:</term>
511 <para>/etc/privoxy (Unix) <emphasis>or</emphasis> <application>Privoxy</application> installation dir (Windows) </para>
515 <term>Effect if unset:</term>
517 <para><emphasis>Mandatory</emphasis></para>
524 No trailing <quote><literal>/</literal></quote>, please
527 This is really outdated and not likely to happen. HB 09/20/06
529 When development goes modular and multi-user, the blocker, filter, and
530 per-user config will be stored in subdirectories of <quote>confdir</quote>.
531 For now, the configuration directory structure is flat, except for
532 <filename>confdir/templates</filename>, where the HTML templates for CGI
533 output reside (e.g. <application>Privoxy's</application> 404 error page).
540 <![%config-file;[<literallayout>@@confdir .</literallayout>]]>
543 <!-- ~~~~~ New section ~~~~~ -->
544 <sect3 renderas="sect4" id="templdir"><title>templdir</title>
548 <term>Specifies:</term>
550 <para>An alternative directory where the templates are loaded from</para>
554 <term>Type of value:</term>
556 <para>Path name</para>
560 <term>Default value:</term>
566 <term>Effect if unset:</term>
568 <para>The templates are assumed to be located in confdir/template.</para>
575 Privoxy's original templates are usually overwritten
576 with each update. Use this option to relocate customized templates
577 that should be kept. Note that you might be missing new features
578 if you use outdated templates.
584 <![%config-file;[<literallayout>@@#templdir .</literallayout>]]>
588 <!-- ~~~~~ New section ~~~~~ -->
589 <sect3 renderas="sect4" id="logdir"><title>logdir</title>
593 <term>Specifies:</term>
596 The directory where all logging takes place (i.e. where <filename>logfile</filename> and
597 <filename>jarfile</filename> are located)
602 <term>Type of value:</term>
604 <para>Path name</para>
608 <term>Default value:</term>
610 <para>/var/log/privoxy (Unix) <emphasis>or</emphasis> <application>Privoxy</application> installation dir (Windows) </para>
614 <term>Effect if unset:</term>
616 <para><emphasis>Mandatory</emphasis></para>
623 No trailing <quote><literal>/</literal></quote>, please
629 <![%config-file;[<literallayout>@@logdir .</literallayout>]]>
633 <!-- ~~~~~ New section ~~~~~ -->
634 <sect3 renderas="sect4" id="actionsfile"><title>
637 <anchor id="default.action">
638 <anchor id="standard.action">
639 <anchor id="user.action">
640 <!-- Note: slightly modified this section 04/28/02, hal. See NOTE. -->
643 <term>Specifies:</term>
646 The <link linkend="actions-file">actions file(s)</link> to use
651 <term>Type of value:</term>
653 <para>File name, relative to <literal>confdir</literal>, without the <literal>.action</literal> suffix</para>
657 <term>Default values:</term>
661 <msgtext><literallayout> standard # Internal purposes, no editing recommended</literallayout></msgtext>
664 <msgtext><literallayout> default # Main actions file</literallayout></msgtext>
667 <msgtext><literallayout> user # User customizations</literallayout></msgtext>
673 <term>Effect if unset:</term>
676 No actions are taken at all. Simple neutral proxying.
684 Multiple <literal>actionsfile</literal> lines are permitted, and are in fact recommended!
687 The default values include standard.action, which is used for internal
688 purposes and should be loaded, default.action, which is the
689 <quote>main</quote> actions file maintained by the developers, and
690 <filename>user.action</filename>, where you can make your personal additions.
693 Actions files are where all the per site and per URL configuration is done for
694 ad blocking, cookie management, privacy considerations, etc.
695 There is no point in using <application>Privoxy</application> without at
696 least one actions file.
702 <!-- NOTE: alternate markup to make a simpler list doesn't work due to -->
703 <!-- html -> text conversion, blah -->
704 <![%config-file;[<literallayout>@@actionsfile standard # Internal purpose, recommended</literallayout>]]>
705 <![%config-file;[<literallayout>@@actionsfile default # Main actions file</literallayout>]]>
706 <![%config-file;[<literallayout>@@actionsfile user # User customizations</literallayout>]]>
709 <!-- ~~~~~ New section ~~~~~ -->
710 <sect3 renderas="sect4" id="filterfile"><title>filterfile</title>
711 <anchor id="default.filter">
714 <term>Specifies:</term>
717 The <link linkend="filter-file">filter file(s)</link> to use
722 <term>Type of value:</term>
724 <para>File name, relative to <literal>confdir</literal></para>
728 <term>Default value:</term>
730 <para>default.filter (Unix) <emphasis>or</emphasis> default.filter.txt (Windows)</para>
734 <term>Effect if unset:</term>
737 No textual content filtering takes place, i.e. all
738 <literal>+<link linkend="filter">filter</link>{<replaceable class="parameter">name</replaceable>}</literal>
739 actions in the actions files are turned neutral.
747 Multiple <literal>filterfile</literal> lines are permitted.
750 The <link linkend="filter-file">filter files</link> contain content modification
751 rules that use <link linkend="regex">regular expressions</link>. These rules permit
752 powerful changes on the content of Web pages, and optionally the headers
753 as well, e.g., you could disable your favorite JavaScript annoyances,
754 re-write the actual displayed text, or just have some fun
755 playing buzzword bingo with web pages.
759 <literal>+<link linkend="filter">filter</link>{<replaceable class="parameter">name</replaceable>}</literal>
760 actions rely on the relevant filter (<replaceable class="parameter">name</replaceable>)
761 to be defined in a filter file!
764 A pre-defined filter file called <filename>default.filter</filename> that contains
765 a number of useful filters for common problems is included in the distribution.
766 See the section on the <literal><link linkend="filter">filter</link></literal>
770 It is recommended to place any locally adapted filters into a separate
771 file, such as <filename>user.filter</filename>.
777 <![%config-file;[<literallayout>@@filterfile default.filter</literallayout>]]>
778 <![%config-file;[<literallayout>@@#filterfile user.filter # User customizations</literallayout>]]>
782 <!-- ~~~~~ New section ~~~~~ -->
783 <sect3 renderas="sect4" id="logfile"><title>logfile</title>
787 <term>Specifies:</term>
795 <term>Type of value:</term>
797 <para>File name, relative to <literal>logdir</literal></para>
801 <term>Default value:</term>
803 <para>logfile (Unix) <emphasis>or</emphasis> privoxy.log (Windows)</para>
807 <term>Effect if unset:</term>
810 No log file is used, all log messages go to the console (<literal>STDERR</literal>).
818 removed per bug report 688728 02/20/03 HB
821 The windows version will additionally log to the console.
825 The logfile is where all logging and error messages are written. The level
826 of detail and number of messages are set with the <literal>debug</literal>
827 option (see below). The logfile can be useful for tracking down a problem with
828 <application>Privoxy</application> (e.g., it's not blocking an ad you
829 think it should block) but in most cases you probably will never look at it.
832 Your logfile will grow indefinitely, and you will probably want to
833 periodically remove it. On Unix systems, you can do this with a cron job
834 (see <quote>man cron</quote>). For Red Hat, a <command>logrotate</command>
835 script has been included.
838 On SuSE Linux systems, you can place a line like <quote>/var/log/privoxy.*
839 +1024k 644 nobody.nogroup</quote> in <filename>/etc/logfiles</filename>, with
840 the effect that cron.daily will automatically archive, gzip, and empty the
841 log, when it exceeds 1M size.
844 Any log files must be writable by whatever user <application>Privoxy</application>
845 is being run as (default on UNIX, user id is <quote>privoxy</quote>).
851 <![%config-file;[<literallayout>@@logfile logfile</literallayout>]]>
855 <!-- ~~~~~ New section ~~~~~ -->
856 <sect3 renderas="sect4" id="jarfile"><title>jarfile</title>
860 <term>Specifies:</term>
863 The file to store intercepted cookies in
868 <term>Type of value:</term>
870 <para>File name, relative to <literal>logdir</literal></para>
874 <term>Default value:</term>
876 <para>Unset (commented out). When activated: jarfile (Unix) <emphasis>or</emphasis> privoxy.jar (Windows)</para>
880 <term>Effect if unset:</term>
883 Intercepted cookies are not stored in a dedicated log file.
891 The jarfile may grow to ridiculous sizes over time.
894 If debug 8 (show header parsing) is enabled, cookies are
895 written to the logfile with the rest of the headers.
901 <![%config-file;[<literallayout>@@#jarfile jarfile</literallayout>]]>
905 <!-- ~~~~~ New section ~~~~~ -->
906 <sect3 renderas="sect4" id="trustfile"><title>trustfile</title>
909 <term>Specifies:</term>
912 The name of the trust file to use
917 <term>Type of value:</term>
919 <para>File name, relative to <literal>confdir</literal></para>
923 <term>Default value:</term>
925 <para><emphasis>Unset (commented out)</emphasis>. When activated: trust (Unix) <emphasis>or</emphasis> trust.txt (Windows)</para>
929 <term>Effect if unset:</term>
932 The entire trust mechanism is disabled.
940 The trust mechanism is an experimental feature for building white-lists and should
941 be used with care. It is <emphasis>NOT</emphasis> recommended for the casual user.
944 If you specify a trust file, <application>Privoxy</application> will only allow
945 access to sites that are specified in the trustfile. Sites can be listed
949 Prepending a <literal>~</literal> character limits access to this site
950 only (and any sub-paths within this site), e.g.
951 <literal>~www.example.com</literal> allows access to
952 <literal>~www.example.com/features/news.html</literal>, etc.
955 Or, you can designate sites as <emphasis>trusted referrers</emphasis>, by
956 prepending the name with a <literal>+</literal> character. The effect is that
957 access to untrusted sites will be granted -- but only if a link from this
958 trusted referrer was used to get there. The link target will then be added
959 to the <quote>trustfile</quote> so that future, direct accesses will be
960 granted. Sites added via this mechanism do not become trusted referrers
961 themselves (i.e. they are added with a <literal>~</literal> designation).
962 There is a limit of 512 such entries, after which new entries will not be
966 If you use the <literal>+</literal> operator in the trust file, it may grow
967 considerably over time.
970 It is recommended that <application>Privoxy</application> be compiled with
971 the <literal>--disable-force</literal>, <literal>--disable-toggle</literal> and
972 <literal> --disable-editor</literal> options, if this feature is to be
976 Possible applications include limiting Internet access for children.
983 <![%config-file;[<literallayout>@@#trustfile trust</literallayout>]]>
987 <!-- ~ End section ~ -->
989 <!-- ~~~~~ New section ~~~~~ -->
990 <sect2 id="debugging">
991 <title>Debugging</title>
994 These options are mainly useful when tracing a problem.
995 Note that you might also want to invoke
996 <application>Privoxy</application> with the <literal>--no-daemon</literal>
997 command line option when debugging.
1000 <sect3 renderas="sect4" id="debug"><title>debug</title>
1004 <term>Specifies:</term>
1007 Key values that determine what information gets logged to the
1008 <link linkend="logfile"><emphasis>logfile</emphasis></link>.
1013 <term>Type of value:</term>
1015 <para>Integer values</para>
1019 <term>Default value:</term>
1021 <para>12289 (i.e.: URLs plus informational and warning messages)</para>
1025 <term>Effect if unset:</term>
1028 Nothing gets logged.
1036 The available debug levels are:
1040 debug 1 # show each GET/POST/CONNECT request
1041 debug 2 # show each connection status
1042 debug 4 # show I/O status
1043 debug 8 # show header parsing
1044 debug 16 # log all data into the logfile
1045 debug 32 # debug force feature
1046 debug 64 # debug regular expression filter
1047 debug 128 # debug redirects
1048 debug 256 # debug GIF de-animation
1049 debug 512 # Common Log Format
1050 debug 1024 # debug kill pop-ups
1051 debug 2048 # CGI user interface
1052 debug 4096 # Startup banner and warnings.
1053 debug 8192 # Non-fatal errors
1057 To select multiple debug levels, you can either add them or use
1058 multiple <literal>debug</literal> lines.
1061 A debug level of 1 is informative because it will show you each request
1062 as it happens. <emphasis>1, 4096 and 8192 are highly recommended</emphasis>
1063 so that you will notice when things go wrong. The other levels are probably
1064 only of interest if you are hunting down a specific problem. They can produce
1065 a hell of an output (especially 16).
1069 The reporting of <emphasis>fatal</emphasis> errors (i.e. ones which crash
1070 <application>Privoxy</application>) is always on and cannot be disabled.
1073 If you want to use CLF (Common Log Format), you should set <quote>debug
1074 512</quote> <emphasis>ONLY</emphasis> and not enable anything else.
1080 <![%config-file;[<literallayout>@@debug 1 # show each GET/POST/CONNECT request</literallayout>]]>
1081 <![%config-file;[<literallayout>@@debug 4096 # Startup banner and warnings</literallayout>]]>
1082 <![%config-file;[<literallayout>@@debug 8192 # Errors - *we highly recommended enabling this*</literallayout>]]>
1086 <!-- ~~~~~ New section ~~~~~ -->
1087 <sect3 renderas="sect4" id="single-threaded"><title>single-threaded</title>
1091 <term>Specifies:</term>
1094 Whether to run only one server thread
1099 <term>Type of value:</term>
1101 <para><emphasis>None</emphasis></para>
1105 <term>Default value:</term>
1107 <para><emphasis>Unset</emphasis></para>
1111 <term>Effect if unset:</term>
1114 Multi-threaded (or, where unavailable: forked) operation, i.e. the ability to
1115 serve multiple requests simultaneously.
1123 This option is only there for debug purposes and you should never
1124 need to use it. <emphasis>It will drastically reduce performance.</emphasis>
1130 <![%config-file;[<literallayout>@@#single-threaded</literallayout>]]>
1135 <!-- ~ End section ~ -->
1138 <!-- ~~~~~ New section ~~~~~ -->
1139 <sect2 id="access-control">
1140 <title>Access Control and Security</title>
1143 This section of the config file controls the security-relevant aspects
1144 of <application>Privoxy</application>'s configuration.
1148 <!-- ~~~~~ New section ~~~~~ -->
1149 <sect3 renderas="sect4" id="listen-address"><title>listen-address</title>
1153 <term>Specifies:</term>
1156 The IP address and TCP port on which <application>Privoxy</application> will
1157 listen for client requests.
1162 <term>Type of value:</term>
1164 <para>[<replaceable class="parameter">IP-Address</replaceable>]:<replaceable class="parameter">Port</replaceable></para>
1169 <term>Default value:</term>
1171 <para>127.0.0.1:8118</para>
1175 <term>Effect if unset:</term>
1178 Bind to 127.0.0.1 (localhost), port 8118. This is suitable and recommended for
1179 home users who run <application>Privoxy</application> on the same machine as
1188 You will need to configure your browser(s) to this proxy address and port.
1191 If you already have another service running on port 8118, or if you want to
1192 serve requests from other machines (e.g. on your local network) as well, you
1193 will need to override the default.
1196 If you leave out the IP address, <application>Privoxy</application> will
1197 bind to all interfaces (addresses) on your machine and may become reachable
1198 from the Internet. In that case, consider using <link
1199 linkend="acls">access control lists</link> (ACL's, see below), and/or
1203 If you open <application>Privoxy</application> to untrusted users, you will
1204 also want to turn off the <literal><link
1205 linkend="enable-edit-actions">enable-edit-actions</link></literal> and
1206 <literal><link linkend="enable-remote-toggle">enable-remote-toggle</link></literal>
1212 <term>Example:</term>
1215 Suppose you are running <application>Privoxy</application> on
1216 a machine which has the address 192.168.0.1 on your local private network
1217 (192.168.0.0) and has another outside connection with a different address.
1218 You want it to serve requests from inside only:
1222 listen-address 192.168.0.1:8118
1229 <![%config-file;[<literallayout>@@listen-address 127.0.0.1:8118</literallayout>]]>
1233 <!-- ~~~~~ New section ~~~~~ -->
1234 <sect3 renderas="sect4" id="toggle"><title>toggle</title>
1238 <term>Specifies:</term>
1241 Initial state of "toggle" status
1246 <term>Type of value:</term>
1252 <term>Default value:</term>
1258 <term>Effect if unset:</term>
1261 Act as if toggled on
1269 If set to 0, <application>Privoxy</application> will start in
1270 <quote>toggled off</quote> mode, i.e. behave like a normal, content-neutral
1271 proxy where all ad blocking, filtering, etc are disabled. See
1272 <literal>enable-remote-toggle</literal> below. This is not really useful
1273 anymore, since toggling is much easier via <ulink
1274 url="http://config.privoxy.org/toggle">the web interface</ulink> than via
1275 editing the <filename>conf</filename> file.
1278 The windows version will only display the toggle icon in the system tray
1279 if this option is present.
1285 <![%config-file;[<literallayout>@@toggle 1</literallayout>]]>
1289 <!-- ~~~~~ New section ~~~~~ -->
1290 <sect3 renderas="sect4" id="enable-remote-toggle"><title>enable-remote-toggle</title>
1293 <term>Specifies:</term>
1296 Whether or not the <ulink url="http://config.privoxy.org/toggle">web-based toggle
1297 feature</ulink> may be used
1302 <term>Type of value:</term>
1308 <term>Default value:</term>
1314 <term>Effect if unset:</term>
1317 The web-based toggle feature is disabled.
1325 When toggled off, <application>Privoxy</application> acts like a normal,
1326 content-neutral proxy, i.e. it acts as if none of the actions applied to
1330 For the time being, access to the toggle feature can <emphasis>not</emphasis> be
1331 controlled separately by <quote>ACLs</quote> or HTTP authentication,
1332 so that everybody who can access <application>Privoxy</application> (see
1333 <quote>ACLs</quote> and <literal>listen-address</literal> above) can
1334 toggle it for all users. So this option is <emphasis>not recommended</emphasis>
1335 for multi-user environments with untrusted users.
1338 Note that you must have compiled <application>Privoxy</application> with
1339 support for this feature, otherwise this option has no effect.
1345 <![%config-file;[<literallayout>@@enable-remote-toggle 1</literallayout>]]>
1349 <!-- ~~~~~ New section ~~~~~ -->
1350 <sect3 renderas="sect4" id="enable-remote-http-toggle"><title>enable-remote-http-toggle</title>
1353 <term>Specifies:</term>
1356 Whether or not Privoxy recognizes special HTTP headers to change its behaviour.
1361 <term>Type of value:</term>
1367 <term>Default value:</term>
1373 <term>Effect if unset:</term>
1376 Privoxy ignores special HTTP headers.
1384 When toggled on, the client can change <application>Privoxy's</application>
1385 behaviour by setting special HTTP headers. Currently the only supported
1386 special header is <quote>X-Filter: No</quote>, to disable filtering for
1387 the ongoing request, even if it is enabled in one of the action files.
1390 If you are using <application>Privoxy</application> in a
1391 multi-user environment or with untrustworthy clients and want to
1392 enforce filtering, you will have to disable this option,
1393 otherwise you can ignore it.
1399 <![%config-file;[<literallayout>@@enable-remote-http-toggle 1</literallayout>]]>
1403 <!-- ~~~~~ New section ~~~~~ -->
1404 <sect3 renderas="sect4" id="enable-edit-actions"><title>enable-edit-actions</title>
1407 <term>Specifies:</term>
1410 Whether or not the <ulink url="http://config.privoxy.org/show-status">web-based actions
1411 file editor</ulink> may be used
1416 <term>Type of value:</term>
1422 <term>Default value:</term>
1428 <term>Effect if unset:</term>
1431 The web-based actions file editor is disabled.
1439 For the time being, access to the editor can <emphasis>not</emphasis> be
1440 controlled separately by <quote>ACLs</quote> or HTTP authentication,
1441 so that everybody who can access <application>Privoxy</application> (see
1442 <quote>ACLs</quote> and <literal>listen-address</literal> above) can
1443 modify its configuration for all users. So this option is <emphasis>not
1444 recommended</emphasis> for multi-user environments with untrusted users.
1447 Note that you must have compiled <application>Privoxy</application> with
1448 support for this feature, otherwise this option has no effect.
1454 <![%config-file;[<literallayout>@@enable-edit-actions 1</literallayout>]]>
1457 <!-- ~~~~~ New section ~~~~~ -->
1458 <sect3 renderas="sect4" id="acls"><title>
1459 ACLs: permit-access and deny-access</title>
1460 <anchor id="permit-access">
1461 <anchor id="deny-access">
1465 <term>Specifies:</term>
1468 Who can access what.
1473 <term>Type of value:</term>
1476 <replaceable class="parameter">src_addr</replaceable>[/<replaceable class="parameter">src_masklen</replaceable>]
1477 [<replaceable class="parameter">dst_addr</replaceable>[/<replaceable class="parameter">dst_masklen</replaceable>]]
1480 Where <replaceable class="parameter">src_addr</replaceable> and
1481 <replaceable class="parameter">dst_addr</replaceable> are IP addresses in dotted decimal notation or valid
1482 DNS names, and <replaceable class="parameter">src_masklen</replaceable> and
1483 <replaceable class="parameter">dst_masklen</replaceable> are subnet masks in CIDR notation, i.e. integer
1484 values from 2 to 30 representing the length (in bits) of the network address. The masks and the whole
1485 destination part are optional.
1490 <term>Default value:</term>
1492 <para><emphasis>Unset</emphasis></para>
1496 <term>Effect if unset:</term>
1499 Don't restrict access further than implied by <literal>listen-address</literal>
1507 Access controls are included at the request of ISPs and systems
1508 administrators, and <emphasis>are not usually needed by individual users</emphasis>.
1509 For a typical home user, it will normally suffice to ensure that
1510 <application>Privoxy</application> only listens on the localhost
1511 (127.0.0.1) or internal (home) network address by means of the
1512 <link linkend="listen-address"><emphasis>listen-address</emphasis></link>
1516 Please see the warnings in the FAQ that this proxy is not intended to be a substitute
1517 for a firewall or to encourage anyone to defer addressing basic security
1521 Multiple ACL lines are OK.
1522 If any ACLs are specified, then the <application>Privoxy</application>
1523 talks only to IP addresses that match at least one <literal>permit-access</literal> line
1524 and don't match any subsequent <literal>deny-access</literal> line. In other words, the
1525 last match wins, with the default being <literal>deny-access</literal>.
1528 If <application>Privoxy</application> is using a forwarder (see <literal>forward</literal> below)
1529 for a particular destination URL, the <replaceable class="parameter">dst_addr</replaceable>
1530 that is examined is the address of the forwarder and <emphasis>NOT</emphasis> the address
1531 of the ultimate target. This is necessary because it may be impossible for the local
1532 <application>Privoxy</application> to determine the IP address of the
1533 ultimate target (that's often what gateways are used for).
1536 You should prefer using IP addresses over DNS names, because the address lookups take
1537 time. All DNS names must resolve! You can <emphasis>not</emphasis> use domain patterns
1538 like <quote>*.org</quote> or partial domain names. If a DNS name resolves to multiple
1539 IP addresses, only the first one is used.
1542 Denying access to particular sites by ACL may have undesired side effects
1543 if the site in question is hosted on a machine which also hosts other sites.
1548 <term>Examples:</term>
1551 Explicitly define the default behavior if no ACL and
1552 <literal>listen-address</literal> are set: <quote>localhost</quote>
1553 is OK. The absence of a <replaceable class="parameter">dst_addr</replaceable> implies that
1554 <emphasis>all</emphasis> destination addresses are OK:
1558 permit-access localhost
1562 Allow any host on the same class C subnet as www.privoxy.org access to
1563 nothing but www.example.com:
1567 permit-access www.privoxy.org/24 www.example.com/32
1571 Allow access from any host on the 26-bit subnet 192.168.45.64 to anywhere,
1572 with the exception that 192.168.45.73 may not access www.dirty-stuff.example.com:
1576 permit-access 192.168.45.64/26
1577 deny-access 192.168.45.73 www.dirty-stuff.example.com
1586 <!-- ~~~~~ New section ~~~~~ -->
1587 <sect3 renderas="sect4" id="buffer-limit"><title>buffer-limit</title>
1591 <term>Specifies:</term>
1594 Maximum size of the buffer for content filtering.
1599 <term>Type of value:</term>
1601 <para>Size in Kbytes</para>
1605 <term>Default value:</term>
1611 <term>Effect if unset:</term>
1614 Use a 4MB (4096 KB) limit.
1622 For content filtering, i.e. the <literal>+filter</literal> and
1623 <literal>+deanimate-gif</literal> actions, it is necessary that
1624 <application>Privoxy</application> buffers the entire document body.
1625 This can be potentially dangerous, since a server could just keep sending
1626 data indefinitely and wait for your RAM to exhaust -- with nasty consequences.
1630 When a document buffer size reaches the <literal>buffer-limit</literal>, it is
1631 flushed to the client unfiltered and no further attempt to
1632 filter the rest of the document is made. Remember that there may be multiple threads
1633 running, which might require up to <literal>buffer-limit</literal> Kbytes
1634 <emphasis>each</emphasis>, unless you have enabled <quote>single-threaded</quote>
1641 <![%config-file;[<literallayout>@@buffer-limit 4096</literallayout>]]>
1646 <!-- ~ End section ~ -->
1649 <!-- ~~~~~ New section ~~~~~ -->
1651 <sect2 id="forwarding">
1652 <title>Forwarding</title>
1655 This feature allows routing of HTTP requests through a chain of
1657 It can be used to better protect privacy and confidentiality when
1658 accessing specific domains by routing requests to those domains
1659 through an anonymous public proxy. Or to use a caching proxy to speed up browsing. Or chaining to a parent
1660 proxy may be necessary because the machine that <application>Privoxy</application>
1661 runs on has no direct Internet access.
1665 Also specified here are SOCKS proxies. <application>Privoxy</application>
1666 supports the SOCKS 4 and SOCKS 4A protocols.
1669 <sect3 renderas="sect4" id="forward"><title>forward</title>
1672 <term>Specifies:</term>
1675 To which parent HTTP proxy specific requests should be routed.
1680 <term>Type of value:</term>
1683 <replaceable class="parameter">target_pattern</replaceable>
1684 <replaceable class="parameter">http_parent</replaceable>[:<replaceable class="parameter">port</replaceable>]
1687 where <replaceable class="parameter">target_pattern</replaceable> is a <link linkend="af-patterns">URL pattern</link>
1688 that specifies to which requests (i.e. URLs) this forward rule shall apply. Use <literal>/</literal> to
1689 denote <quote>all URLs</quote>.
1690 <replaceable class="parameter">http_parent</replaceable>[:<replaceable class="parameter">port</replaceable>]
1691 is the DNS name or IP address of the parent HTTP proxy through which the requests should be forwarded,
1692 optionally followed by its listening port (default: 8080).
1693 Use a single dot (<literal>.</literal>) to denote <quote>no forwarding</quote>.
1698 <term>Default value:</term>
1700 <para><emphasis>Unset</emphasis></para>
1704 <term>Effect if unset:</term>
1707 Don't use parent HTTP proxies.
1715 If <replaceable class="parameter">http_parent</replaceable> is <quote>.</quote>, then requests are not
1716 forwarded to another HTTP proxy but are made directly to the web servers.
1719 Multiple lines are OK, they are checked in sequence, and the last match wins.
1724 <term>Examples:</term>
1727 Everything goes to an example anonymizing proxy, except SSL on port 443 (which it doesn't handle):
1731 forward / anon-proxy.example.org:8080
1736 Everything goes to our example ISP's caching proxy, except for requests
1737 to that ISP's sites:
1741 forward / caching-proxy.example-isp.net:8000
1742 forward .example-isp.net .
1751 <!-- ~~~~~ New section ~~~~~ -->
1752 <sect3 renderas="sect4" id="socks"><title>
1753 forward-socks4 and forward-socks4a</title>
1754 <anchor id="forward-socks4">
1755 <anchor id="forward-socks4a">
1759 <term>Specifies:</term>
1762 Through which SOCKS proxy (and to which parent HTTP proxy) specific requests should be routed.
1767 <term>Type of value:</term>
1770 <replaceable class="parameter">target_pattern</replaceable>
1771 <replaceable class="parameter">socks_proxy</replaceable>[:<replaceable class="parameter">port</replaceable>]
1772 <replaceable class="parameter">http_parent</replaceable>[:<replaceable class="parameter">port</replaceable>]
1775 where <replaceable class="parameter">target_pattern</replaceable> is a <link linkend="af-patterns">URL pattern</link>
1776 that specifies to which requests (i.e. URLs) this forward rule shall apply. Use <literal>/</literal> to
1777 denote <quote>all URLs</quote>.
1778 <replaceable class="parameter">http_parent</replaceable> and <replaceable class="parameter">socks_proxy</replaceable>
1779 are IP addresses in dotted decimal notation or valid DNS names (<replaceable class="parameter">http_parent</replaceable>
1780 may be <quote>.</quote> to denote <quote>no HTTP forwarding</quote>), and the optional
1781 <replaceable class="parameter">port</replaceable> parameters are TCP ports, i.e. integer values from 1 to 64535
1786 <term>Default value:</term>
1788 <para><emphasis>Unset</emphasis></para>
1792 <term>Effect if unset:</term>
1795 Don't use SOCKS proxies.
1803 Multiple lines are OK, they are checked in sequence, and the last match wins.
1806 The difference between <literal>forward-socks4</literal> and <literal>forward-socks4a</literal>
1807 is that in the SOCKS 4A protocol, the DNS resolution of the target hostname happens on the SOCKS
1808 server, while in SOCKS 4 it happens locally.
1811 If <replaceable class="parameter">http_parent</replaceable> is <quote>.</quote>, then requests are not
1812 forwarded to another HTTP proxy but are made (HTTP-wise) directly to the web servers, albeit through
1818 <term>Examples:</term>
1821 From the company example.com, direct connections are made to all
1822 <quote>internal</quote> domains, but everything outbound goes through
1823 their ISP's proxy by way of example.com's corporate SOCKS 4A gateway to
1828 forward-socks4a / socks-gw.example.com:1080 www-cache.example-isp.net:8080
1829 forward .example.com .
1833 A rule that uses a SOCKS 4 gateway for all destinations but no HTTP parent looks like this:
1837 forward-socks4 / socks-gw.example.com:1080 .
1842 To chain Privoxy and Tor, both running on the same system, you should use
1847 forward-socks4 / 127.0.0.1:9050 .
1852 The public <application>Tor</application> network can't be used to reach your local network,
1853 therefore it's a good idea to make some exceptions:
1857 forward 192.168.*.*/ .
1859 forward 127.*.*.*/ .
1863 Unencrypted connections to systems in these address ranges will
1864 be as (un)secure as the local network is, but the alternative is that you
1865 can't reach the network at all.
1868 If you also want to be able to reach servers in your local network by
1869 using their names, you will need additional exceptions that look like
1874 forward localhost/ .
1883 <![%user-man;[ <!-- not included in config due to length -->
1884 <!-- ~~~~~ New section ~~~~~ -->
1885 <sect3 renderas="sect4" id="advanced-forwarding-examples"><title>Advanced Forwarding Examples</title>
1888 If you have links to multiple ISPs that provide various special content
1889 only to their subscribers, you can configure multiple <application>Privoxies</application>
1890 which have connections to the respective ISPs to act as forwarders to each other, so that
1891 <emphasis>your</emphasis> users can see the internal content of all ISPs.
1895 Assume that host-a has a PPP connection to isp-a.net. And host-b has a PPP connection to
1896 isp-b.net. Both run <application>Privoxy</application>. Their forwarding
1897 configuration can look like this:
1907 forward .isp-b.net host-b:8118
1918 forward .isp-a.net host-a:8118
1923 Now, your users can set their browser's proxy to use either
1924 host-a or host-b and be able to browse the internal content
1925 of both isp-a and isp-b.
1929 If you intend to chain <application>Privoxy</application> and
1930 <application>squid</application> locally, then chain as
1931 <literal>browser -> squid -> privoxy</literal> is the recommended way.
1935 Assuming that <application>Privoxy</application> and <application>squid</application>
1936 run on the same box, your <application>squid</application> configuration could then look like this:
1941 # Define Privoxy as parent proxy (without ICP)
1942 cache_peer 127.0.0.1 parent 8118 7 no-query
1944 # Define ACL for protocol FTP
1947 # Do not forward FTP requests to Privoxy
1948 always_direct allow ftp
1950 # Forward all the rest to Privoxy
1951 never_direct allow all</screen>
1955 You would then need to change your browser's proxy settings to <application>squid</application>'s address and port.
1956 Squid normally uses port 3128. If unsure consult <literal>http_port</literal> in <filename>squid.conf</filename>.
1960 You could just as well decide to only forward requests for Windows executables through
1961 a virus-scanning parent proxy, say, on <literal>antivir.example.com</literal>, port 8010:
1967 forward /.*\.(exe|com|dll|zip)$ antivir.example.com:8010</screen>
1973 <sect3 renderas="sect4" id="forwarded-connect-retries"><title>forwarded-connect-retries</title>
1976 <term>Specifies:</term>
1979 How often Privoxy retries if a forwarded connection request fails.
1984 <term>Type of value:</term>
1987 <replaceable class="parameter">Number of retries.</replaceable>
1992 <term>Default value:</term>
1994 <para><emphasis>0</emphasis></para>
1998 <term>Effect if unset:</term>
2001 Forwarded connections are treated like direct connections and no retry attempts are made.
2009 <replaceable class="parameter">forwarded-connect-retries</replaceable> is mainly interesting
2010 for socks4a connections, where <application>Privoxy</application> can't detect why the connections failed.
2011 The connection might have failed because of a DNS timeout in which case a retry makes sense,
2012 but it might also have failed because the server doesn't exist or isn't reachable. In this
2013 case the retry will just delay the appearance of Privoxy's error message.
2016 Only use this option, if you are getting many forwarding related error messages,
2017 that go away when you try again manually. Start with a small value and check Privoxy's
2018 logfile from time to time, to see how many retries are usually needed.
2023 <term>Examples:</term>
2026 forwarded-connect-retries 1
2031 <![%config-file;[<literallayout>@@forwarded-connect-retries 0</literallayout>]]>
2034 <sect3 renderas="sect4" id="accept-intercepted-requests"><title>accept-intercepted-requests</title>
2037 <term>Specifies:</term>
2040 Whether intercepted requests should be treated as valid.
2045 <term>Type of value:</term>
2048 <replaceable>0 or 1</replaceable>
2053 <term>Default value:</term>
2055 <para><emphasis>0</emphasis></para>
2059 <term>Effect if unset:</term>
2062 Only proxy requests are accepted, intercepted requests are treated as invalid.
2070 If you don't trust your clients and want to force them
2071 to use <application>Privoxy</application>, enable this
2072 option and configure your packet filter to redirect outgoing
2073 HTTP connections into <application>Privoxy</application>.
2076 Make sure that <application>Privoxy's</application> own requests
2077 aren't redirected as well. Additionally take care that
2078 <application>Privoxy</application> can't intentionally connect
2079 to itself, otherwise you could run into redirection loops if
2080 <application>Privoxy's</application> listening port is reachable
2081 by the outside or an attacker has access to the pages you visit.
2086 <term>Examples:</term>
2089 accept-intercepted-requests 1
2094 <![%config-file;[<literallayout>@@accept-intercepted-requests 0</literallayout>]]>
2097 <sect3 renderas="sect4" id="split-large-forms"><title>split-large-forms</title>
2100 <term>Specifies:</term>
2103 Whether the CGI interface should stay compatible with broken HTTP clients.
2108 <term>Type of value:</term>
2111 <replaceable>0 or 1</replaceable>
2116 <term>Default value:</term>
2118 <para><emphasis>0</emphasis></para>
2122 <term>Effect if unset:</term>
2125 The CGI form generate long GET URLs.
2133 <application>Privoxy's</application> CGI forms can lead to
2134 rather long URLs. This isn't a problem as far as the HTTP
2135 standard is concerned, but it can confuse clients with arbitrary
2136 URL lenght limitations.
2139 Enabling split-large-forms causes <application>Privoxy</application>
2140 to devide big forms into smaller ones to keep the URL length down.
2141 It makes editing a lot less convenient and you can no longer
2142 submit all changes at once, but at least it works around this
2146 If you don't notice any editing problems, there is no reason
2147 to enable this option, but if one of the submit buttons appears
2148 to be broken, you should give it a try.
2153 <term>Examples:</term>
2161 <![%config-file;[<literallayout>@@split-large-forms 0</literallayout>]]>
2166 <!-- ~ End section ~ -->
2169 <!-- ~~~~~ New section ~~~~~ -->
2171 <sect2 id="windows-gui">
2172 <title>Windows GUI Options</title>
2174 <application>Privoxy</application> has a number of options specific to the
2175 Windows GUI interface:
2178 <anchor id="activity-animation">
2179 <![%config-file;[<para>@@</para>]]> <!-- for spacing -->
2181 If <quote>activity-animation</quote> is set to 1, the
2182 <application>Privoxy</application> icon will animate when
2183 <quote>Privoxy</quote> is active. To turn off, set to 0.
2186 <![%config-file;[<literallayout>@@#activity-animation 1</literallayout>]]>
2192 <emphasis>activity-animation 1</emphasis>
2199 <anchor id="log-messages">
2200 <![%config-file;[<para>@@</para>]]> <!-- for spacing -->
2202 If <quote>log-messages</quote> is set to 1,
2203 <application>Privoxy</application> will log messages to the console
2207 <![%config-file;[<literallayout>@@#log-messages 1</literallayout>]]>
2213 <emphasis>log-messages 1</emphasis>
2220 <anchor id="log-buffer-size">
2221 <![%config-file;[<para>@@</para>]]> <!-- for spacing -->
2223 If <quote>log-buffer-size</quote> is set to 1, the size of the log buffer,
2224 i.e. the amount of memory used for the log messages displayed in the
2225 console window, will be limited to <quote>log-max-lines</quote> (see below).
2229 Warning: Setting this to 0 will result in the buffer to grow infinitely and
2230 eat up all your memory!
2233 <![%config-file;[<literallayout>@@#log-buffer-size 1</literallayout>]]>
2239 <emphasis>log-buffer-size 1</emphasis>
2246 <anchor id="log-max-lines">
2247 <![%config-file;[<para>@@</para>]]> <!-- for spacing -->
2249 <application>log-max-lines</application> is the maximum number of lines held
2250 in the log buffer. See above.
2253 <![%config-file;[<literallayout>@@#log-max-lines 200</literallayout>]]>
2259 <emphasis>log-max-lines 200</emphasis>
2266 <anchor id="log-highlight-messages">
2267 <![%config-file;[<para>@@</para>]]> <!-- for spacing -->
2269 If <quote>log-highlight-messages</quote> is set to 1,
2270 <application>Privoxy</application> will highlight portions of the log
2271 messages with a bold-faced font:
2274 <![%config-file;[<literallayout>@@#log-highlight-messages 1</literallayout>]]>
2280 <emphasis>log-highlight-messages 1</emphasis>
2287 <anchor id="log-font-name">
2288 <![%config-file;[<para>@@</para>]]> <!-- for spacing -->
2290 The font used in the console window:
2293 <![%config-file;[<literallayout>@@#log-font-name Comic Sans MS</literallayout>]]>
2299 <emphasis>log-font-name Comic Sans MS</emphasis>
2306 <anchor id="log-font-size">
2307 <![%config-file;[<para>@@</para>]]> <!-- for spacing -->
2309 Font size used in the console window:
2312 <![%config-file;[<literallayout>@@#log-font-size 8</literallayout>]]>
2318 <emphasis>log-font-size 8</emphasis>
2325 <anchor id="show-on-task-bar">
2326 <![%config-file;[<para>@@</para>]]> <!-- for spacing -->
2328 <quote>show-on-task-bar</quote> controls whether or not
2329 <application>Privoxy</application> will appear as a button on the Task bar
2333 <![%config-file;[<literallayout>@@#show-on-task-bar 0</literallayout>]]>
2339 <emphasis>show-on-task-bar 0</emphasis>
2346 <anchor id="close-button-minimizes">
2347 <![%config-file;[<para>@@</para>]]> <!-- for spacing -->
2349 If <quote>close-button-minimizes</quote> is set to 1, the Windows close
2350 button will minimize <application>Privoxy</application> instead of closing
2351 the program (close with the exit option on the File menu).
2354 <![%config-file;[<literallayout>@@#close-button-minimizes 1</literallayout>]]>
2360 <emphasis>close-button-minimizes 1</emphasis>
2367 <anchor id="hide-console">
2368 <![%config-file;[<para>@@</para>]]> <!-- for spacing -->
2370 The <quote>hide-console</quote> option is specific to the MS-Win console
2371 version of <application>Privoxy</application>. If this option is used,
2372 <application>Privoxy</application> will disconnect from and hide the
2376 <![%config-file;[<literallayout>@@#hide-console</literallayout>]]>
2382 #<emphasis>hide-console</emphasis>
2392 <!-- end config content common to both outputs -->
2395 <!-- These are dummy anchors to keep the processor quiet -->
2396 <!-- when building config-file only (ie. they are used in u-m only) -->
2399 <anchor id="filter">
2400 <anchor id="filter-file">
2402 <anchor id="actions-file">
2403 <anchor id="af-patterns">
2407 <!-- eof p-config.sgml -->