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.111 2014/11/14 11:31:24 fabiankeil Exp $
8 Copyright (C) 2001-2014 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 By default, the main configuration file is named <filename>config</filename>,
54 with the exception of Windows, where it is named <filename>config.txt</filename>.
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). Like the filter and action files, the config file is
85 a plain text file and can be modified with a text editor like emacs, vim or
93 <!-- This part only goes into the config file -->
96 @@TITLE<!-- between the @@ is stripped by Makefile -->@@
97 Sample Configuration File for Privoxy &p-version;
100 $Id: p-config.sgml,v 2.111 2014/11/14 11:31:24 fabiankeil Exp $
103 Copyright (C) 2001-2014 Privoxy Developers http://www.privoxy.org/
108 #################################################################
113 II. FORMAT OF THE CONFIGURATION FILE #
115 1. LOCAL SET-UP DOCUMENTATION #
116 2. CONFIGURATION AND LOG FILE LOCATIONS #
118 4. ACCESS CONTROL AND SECURITY #
121 7. WINDOWS GUI OPTIONS #
123 #################################################################
127 <literallayout>I. INTRODUCTION
128 =============== <!-- fuck this madness --></literallayout>
131 This file holds Privoxy's main configuration. Privoxy detects
132 configuration changes automatically, so you don't have to restart it
133 unless you want to load a different configuration file.
136 The configuration will be reloaded with the first request after the
137 change was done, this request itself will still use the old configuration,
138 though. In other words: it takes two requests before you see the result of
139 your changes. Requests that are dropped due to ACL don't trigger reloads.
142 When starting Privoxy on Unix systems, give the location of this
143 file as last argument. On Windows systems, Privoxy will look for
144 this file with the name 'config.txt' in the current working directory
145 of the Privoxy process.
149 <literallayout><!-- funky spacing -->
151 II. FORMAT OF THE CONFIGURATION FILE
152 ====================================</literallayout>
155 Configuration lines consist of an initial keyword followed by a list
156 of values, all separated by whitespace (any number of spaces or
160 actionsfile default.action
163 Indicates that the actionsfile is named 'default.action'.
166 The '#' indicates a comment. Any part of a line following a '#' is
167 ignored, except if the '#' is preceded by a '\'.
170 Thus, by placing a # at the start of an existing configuration line,
171 you can make it a comment and it will be treated as if it weren't there.
172 This is called "commenting out" an option and can be useful. Removing
173 the # again is called "uncommenting".
176 Note that commenting out an option and leaving it at its default
177 are two completely different things! Most options behave very
178 differently when unset. See the "Effect if unset" explanation
179 in each option's description for details.
182 Long lines can be continued on the next line by using a `\' as
188 <!-- ************************************************ -->
189 <!-- The following is common to both outputs (mostly) -->
190 <!-- ************************************************ -->
194 <!-- ~~~~~ New section ~~~~~ -->
195 <sect2 id="local-set-up">
196 <title>Local Set-up Documentation</title>
199 If you intend to operate <application>Privoxy</application> for more users
200 than just yourself, it might be a good idea to let them know how to reach
201 you, what you block and why you do that, your policies, etc.
205 <!-- ~~~~~ New section ~~~~~ -->
206 <sect3 renderas="sect4" id="user-manual"><title>user-manual</title>
209 <term>Specifies:</term>
212 Location of the <application>Privoxy</application> User Manual.
217 <term>Type of value:</term>
219 <para>A fully qualified URI</para>
223 <term>Default value:</term>
225 <para><emphasis>Unset</emphasis></para>
229 <term>Effect if unset:</term>
232 <ulink url="http://www.privoxy.org/user-manual/">http://www.privoxy.org/<replaceable class="parameter">version</replaceable>/user-manual/</ulink>
233 will be used, where <replaceable class="parameter">version</replaceable> is the <application>Privoxy</application> version.
241 The User Manual URI is the single best source of information on
242 <application>Privoxy</application>, and is used for help links from some
243 of the internal CGI pages. The manual itself is normally packaged with the
244 binary distributions, so you probably want to set this to a locally
252 Unix, in local filesystem (may not work with all browsers):
255 <screen> user-manual file:///usr/share/doc/privoxy-&p-version;/user-manual/</screen>
258 Windows, in local filesystem, <emphasis>must</emphasis> use forward slash notation:
261 <screen> user-manual file:/c:/some-dir/privoxy-&p-version;/user-manual/</screen>
264 Windows, UNC notation (with forward slashes):
267 <screen> user-manual file://///some-server/some-path/privoxy-&p-version;/user-manual/</screen>
271 The best all purpose solution is simply to put the full local
272 <literal>PATH</literal> to where the <citetitle>User Manual</citetitle> is
276 <screen> user-manual /usr/share/doc/privoxy/user-manual</screen>
279 The User Manual is then available to anyone with access to
280 <application>Privoxy</application>, by following the built-in URL:
281 <literal>http://config.privoxy.org/user-manual/</literal>
282 (or the shortcut: <literal>http://p.p/user-manual/</literal>).
285 If the documentation is not on the local system, it can be accessed
286 from a remote server, as:
289 <screen> user-manual http://example.com/privoxy/user-manual/</screen>
292 <!-- this gets hammered in conversion to config. Text repeated below. -->
295 If set, this option should be <emphasis>the first option in the config
296 file</emphasis>, because it is used while the config file is being read
309 If set, this option should be the first option in the config
310 file, because it is used while the config file is being read.
319 <![%config-file;[<literallayout>@@#user-manual http://www.privoxy.org/user-manual/</literallayout>]]>
323 <!-- ~~~~~ New section ~~~~~ -->
324 <sect3 renderas="sect4" id="trust-info-url"><title>trust-info-url</title>
328 <term>Specifies:</term>
331 A URL to be displayed in the error page that users will see if access to an untrusted page is denied.
336 <term>Type of value:</term>
342 <term>Default value:</term>
344 <para><emphasis>Unset</emphasis></para>
348 <term>Effect if unset:</term>
351 No links are displayed on the "untrusted" error page.
359 The value of this option only matters if the experimental trust mechanism has been
360 activated. (See <link linkend="trustfile"><emphasis>trustfile</emphasis></link> below.)
363 If you use the trust mechanism, it is a good idea to write up some on-line
364 documentation about your trust policy and to specify the URL(s) here.
365 Use multiple times for multiple URLs.
368 The URL(s) should be added to the trustfile as well, so users don't end up
369 locked out from the information on why they were locked out in the first place!
375 <![%config-file;[<literallayout>@@#trust-info-url http://www.example.com/why_we_block.html</literallayout>]]>
376 <![%config-file;[<literallayout>@@#trust-info-url http://www.example.com/what_we_allow.html</literallayout>]]>
380 <!-- ~~~~~ New section ~~~~~ -->
381 <sect3 renderas="sect4" id="admin-address"><title>admin-address</title>
385 <term>Specifies:</term>
388 An email address to reach the <application>Privoxy</application> administrator.
393 <term>Type of value:</term>
395 <para>Email address</para>
399 <term>Default value:</term>
401 <para><emphasis>Unset</emphasis></para>
405 <term>Effect if unset:</term>
408 No email address is displayed on error pages and the CGI user interface.
416 If both <literal>admin-address</literal> and <literal>proxy-info-url</literal>
417 are unset, the whole "Local Privoxy Support" box on all generated pages will
424 <![%config-file;[<literallayout>@@#admin-address privoxy-admin@example.com</literallayout>]]>
428 <!-- ~~~~~ New section ~~~~~ -->
429 <sect3 renderas="sect4" id="proxy-info-url"><title>proxy-info-url</title>
433 <term>Specifies:</term>
436 A URL to documentation about the local <application>Privoxy</application> setup,
437 configuration or policies.
442 <term>Type of value:</term>
448 <term>Default value:</term>
450 <para><emphasis>Unset</emphasis></para>
454 <term>Effect if unset:</term>
457 No link to local documentation is displayed on error pages and the CGI user interface.
465 If both <literal>admin-address</literal> and <literal>proxy-info-url</literal>
466 are unset, the whole "Local Privoxy Support" box on all generated pages will
470 This URL shouldn't be blocked ;-)
476 <![%config-file;[<literallayout>@@#proxy-info-url http://www.example.com/proxy-service.html</literallayout>]]>
480 <!-- ~ End section ~ -->
484 <!-- ~~~~~ New section ~~~~~ -->
486 <sect2 id="conf-log-loc">
487 <title>Configuration and Log File Locations</title>
490 <application>Privoxy</application> can (and normally does) use a number of
491 other files for additional configuration, help and logging.
492 This section of the configuration file tells <application>Privoxy</application>
493 where to find those other files.
497 The user running <application>Privoxy</application>, must have read
498 permission for all configuration files, and write permission to any files
499 that would be modified, such as log files and actions files.
503 <!-- ~~~~~ New section ~~~~~ -->
504 <sect3 renderas="sect4" id="confdir"><title>confdir</title>
508 <term>Specifies:</term>
510 <para>The directory where the other configuration files are located.</para>
514 <term>Type of value:</term>
516 <para>Path name</para>
520 <term>Default value:</term>
522 <para>/etc/privoxy (Unix) <emphasis>or</emphasis> <application>Privoxy</application> installation dir (Windows) </para>
526 <term>Effect if unset:</term>
528 <para><emphasis>Mandatory</emphasis></para>
535 No trailing <quote><literal>/</literal></quote>, please.
541 <![%config-file;[<literallayout>@@confdir .</literallayout>]]>
544 <!-- ~~~~~ New section ~~~~~ -->
545 <sect3 renderas="sect4" id="templdir"><title>templdir</title>
549 <term>Specifies:</term>
551 <para>An alternative directory where the templates are loaded from.</para>
555 <term>Type of value:</term>
557 <para>Path name</para>
561 <term>Default value:</term>
567 <term>Effect if unset:</term>
569 <para>The templates are assumed to be located in confdir/template.</para>
576 <application>Privoxy's</application> original templates are usually
577 overwritten with each update. Use this option to relocate customized
578 templates that should be kept. As template variables might change
579 between updates, you shouldn't expect templates to work with
580 <application>Privoxy</application> releases other than the one
581 they were part of, though.
587 <![%config-file;[<literallayout>@@#templdir .</literallayout>]]>
591 <!-- ~~~~~ New section ~~~~~ -->
592 <sect3 renderas="sect4" id="temporary-directory"><title>temporary-directory</title>
596 <term>Specifies:</term>
598 <para>A directory where Privoxy can create temporary files.</para>
602 <term>Type of value:</term>
604 <para>Path name</para>
608 <term>Default value:</term>
614 <term>Effect if unset:</term>
616 <para>No temporary files are created, external filters don't work.</para>
623 To execute <literal><ulink url="actions-file.html#EXTERNAL-FILTER">external filters</ulink></literal>,
624 <application>Privoxy</application> has to create temporary files.
625 This directive specifies the directory the temporary files should
629 It should be a directory only <application>Privoxy</application>
630 (and trusted users) can access.
636 <![%config-file;[<literallayout>@@#temporary-directory .</literallayout>]]>
640 <!-- ~~~~~ New section ~~~~~ -->
641 <sect3 renderas="sect4" id="logdir"><title>logdir</title>
645 <term>Specifies:</term>
648 The directory where all logging takes place
649 (i.e. where the <filename>logfile</filename> is located).
654 <term>Type of value:</term>
656 <para>Path name</para>
660 <term>Default value:</term>
662 <para>/var/log/privoxy (Unix) <emphasis>or</emphasis> <application>Privoxy</application> installation dir (Windows) </para>
666 <term>Effect if unset:</term>
668 <para><emphasis>Mandatory</emphasis></para>
675 No trailing <quote><literal>/</literal></quote>, please.
681 <![%config-file;[<literallayout>@@logdir .</literallayout>]]>
685 <!-- ~~~~~ New section ~~~~~ -->
686 <sect3 renderas="sect4" id="actionsfile"><title>
689 <anchor id="default.action">
690 <anchor id="standard.action">
691 <anchor id="user.action">
692 <!-- Note: slightly modified this section 04/28/02, hal. See NOTE. -->
695 <term>Specifies:</term>
698 The <link linkend="actions-file">actions file(s)</link> to use
703 <term>Type of value:</term>
705 <para>Complete file name, relative to <literal>confdir</literal></para>
709 <term>Default values:</term>
713 <msgtext><literallayout> match-all.action # Actions that are applied to all sites and maybe overruled later on.</literallayout></msgtext>
716 <msgtext><literallayout> default.action # Main actions file</literallayout></msgtext>
719 <msgtext><literallayout> user.action # User customizations</literallayout></msgtext>
725 <term>Effect if unset:</term>
728 No actions are taken at all. More or less neutral proxying.
736 Multiple <literal>actionsfile</literal> lines are permitted, and are in fact recommended!
739 The default values are <filename>default.action</filename>, which is the
740 <quote>main</quote> actions file maintained by the developers, and
741 <filename>user.action</filename>, where you can make your personal additions.
744 Actions files contain all the per site and per URL configuration for
745 ad blocking, cookie management, privacy considerations, etc.
751 <!-- NOTE: alternate markup to make a simpler list doesn't work due to -->
752 <!-- html -> text conversion, blah -->
753 <![%config-file;[<literallayout>@@actionsfile match-all.action # Actions that are applied to all sites and maybe overruled later on.</literallayout>]]>
754 <![%config-file;[<literallayout>@@actionsfile default.action # Main actions file</literallayout>]]>
756 XXX: Like user.filter, user.action should probably be commented out
757 by default as not all packages install it into the default directory.
760 <![%config-file;[<literallayout>@@actionsfile user.action # User customizations</literallayout>]]>
763 <!-- ~~~~~ New section ~~~~~ -->
764 <sect3 renderas="sect4" id="filterfile"><title>filterfile</title>
765 <anchor id="default.filter">
768 <term>Specifies:</term>
771 The <link linkend="filter-file">filter file(s)</link> to use
776 <term>Type of value:</term>
778 <para>File name, relative to <literal>confdir</literal></para>
782 <term>Default value:</term>
784 <para>default.filter (Unix) <emphasis>or</emphasis> default.filter.txt (Windows)</para>
788 <term>Effect if unset:</term>
791 No textual content filtering takes place, i.e. all
792 <literal>+<link linkend="filter">filter</link>{<replaceable class="parameter">name</replaceable>}</literal>
793 actions in the actions files are turned neutral.
801 Multiple <literal>filterfile</literal> lines are permitted.
804 The <link linkend="filter-file">filter files</link> contain content modification
805 rules that use <link linkend="regex">regular expressions</link>. These rules permit
806 powerful changes on the content of Web pages, and optionally the headers
807 as well, e.g., you could try to disable your favorite JavaScript annoyances,
808 re-write the actual displayed text, or just have some fun
809 playing buzzword bingo with web pages.
813 <literal>+<link linkend="filter">filter</link>{<replaceable class="parameter">name</replaceable>}</literal>
814 actions rely on the relevant filter (<replaceable class="parameter">name</replaceable>)
815 to be defined in a filter file!
818 A pre-defined filter file called <filename>default.filter</filename> that contains
819 a number of useful filters for common problems is included in the distribution.
820 See the section on the <literal><link linkend="filter">filter</link></literal>
824 It is recommended to place any locally adapted filters into a separate
825 file, such as <filename>user.filter</filename>.
831 <![%config-file;[<literallayout>@@filterfile default.filter</literallayout>]]>
832 <![%config-file;[<literallayout>@@filterfile user.filter # User customizations</literallayout>]]>
836 <!-- ~~~~~ New section ~~~~~ -->
837 <sect3 renderas="sect4" id="logfile"><title>logfile</title>
841 <term>Specifies:</term>
849 <term>Type of value:</term>
851 <para>File name, relative to <literal>logdir</literal></para>
855 <term>Default value:</term>
857 <para><emphasis>Unset (commented out)</emphasis>. When activated: logfile (Unix) <emphasis>or</emphasis> privoxy.log (Windows).</para>
861 <term>Effect if unset:</term>
864 No logfile is written.
872 The logfile is where all logging and error messages are written. The level
873 of detail and number of messages are set with the <literal>debug</literal>
874 option (see below). The logfile can be useful for tracking down a problem with
875 <application>Privoxy</application> (e.g., it's not blocking an ad you
876 think it should block) and it can help you to monitor what your browser
880 Depending on the debug options below, the logfile may be a privacy risk
881 if third parties can get access to it. As most users will never look
882 at it, <application>Privoxy</application> only logs fatal errors by default.
885 For most troubleshooting purposes, you will have to change that,
886 please refer to the debugging section for details.
889 Any log files must be writable by whatever user <application>Privoxy</application>
890 is being run as (on Unix, default user id is <quote>privoxy</quote>).
893 To prevent the logfile from growing indefinitely, it is recommended to
894 periodically rotate or shorten it. Many operating systems support log
895 rotation out of the box, some require additional software to do it.
896 For details, please refer to the documentation for your operating system.
902 <![%config-file;[<literallayout>@@logfile logfile</literallayout>]]>
906 <!-- ~~~~~ New section ~~~~~ -->
907 <sect3 renderas="sect4" id="trustfile"><title>trustfile</title>
910 <term>Specifies:</term>
913 The name of the trust file to use
918 <term>Type of value:</term>
920 <para>File name, relative to <literal>confdir</literal></para>
924 <term>Default value:</term>
926 <para><emphasis>Unset (commented out)</emphasis>. When activated: trust (Unix) <emphasis>or</emphasis> trust.txt (Windows)</para>
930 <term>Effect if unset:</term>
933 The entire trust mechanism is disabled.
941 The trust mechanism is an experimental feature for building white-lists and should
942 be used with care. It is <emphasis>NOT</emphasis> recommended for the casual user.
945 If you specify a trust file, <application>Privoxy</application> will only allow
946 access to sites that are specified in the trustfile. Sites can be listed
950 Prepending a <literal>~</literal> character limits access to this site
951 only (and any sub-paths within this site), e.g.
952 <literal>~www.example.com</literal> allows access to
953 <literal>~www.example.com/features/news.html</literal>, etc.
956 Or, you can designate sites as <emphasis>trusted referrers</emphasis>, by
957 prepending the name with a <literal>+</literal> character. The effect is that
958 access to untrusted sites will be granted -- but only if a link from this
959 trusted referrer was used to get there. The link target will then be added
960 to the <quote>trustfile</quote> so that future, direct accesses will be
961 granted. Sites added via this mechanism do not become trusted referrers
962 themselves (i.e. they are added with a <literal>~</literal> designation).
963 There is a limit of 512 such entries, after which new entries will not be
967 If you use the <literal>+</literal> operator in the trust file, it may grow
968 considerably over time.
971 It is recommended that <application>Privoxy</application> be compiled with
972 the <literal>--disable-force</literal>, <literal>--disable-toggle</literal> and
973 <literal> --disable-editor</literal> options, if this feature is to be
977 Possible applications include limiting Internet access for children.
984 <![%config-file;[<literallayout>@@#trustfile trust</literallayout>]]>
988 <!-- ~ End section ~ -->
990 <!-- ~~~~~ New section ~~~~~ -->
991 <sect2 id="debugging">
992 <title>Debugging</title>
995 These options are mainly useful when tracing a problem.
996 Note that you might also want to invoke
997 <application>Privoxy</application> with the <literal>--no-daemon</literal>
998 command line option when debugging.
1001 <sect3 renderas="sect4" id="debug"><title>debug</title>
1005 <term>Specifies:</term>
1008 Key values that determine what information gets logged.
1013 <term>Type of value:</term>
1015 <para>Integer values</para>
1019 <term>Default value:</term>
1021 <para>0 (i.e.: only fatal errors (that cause Privoxy to exit) are logged)</para>
1025 <term>Effect if unset:</term>
1028 Default value is used (see above).
1036 The available debug levels are:
1040 debug 1 # Log the destination for each request &my-app; let through. See also debug 1024.
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 written to the network
1045 debug 32 # debug force feature
1046 debug 64 # debug regular expression filters
1047 debug 128 # debug redirects
1048 debug 256 # debug GIF de-animation
1049 debug 512 # Common Log Format
1050 debug 1024 # Log the destination for requests &my-app; didn't let through, and the reason why.
1051 debug 2048 # CGI user interface
1052 debug 4096 # Startup banner and warnings.
1053 debug 8192 # Non-fatal errors
1054 debug 32768 # log all data read from the network
1055 debug 65536 # Log the applying actions
1059 To select multiple debug levels, you can either add them or use
1060 multiple <literal>debug</literal> lines.
1063 A debug level of 1 is informative because it will show you each request
1064 as it happens. <emphasis>1, 1024, 4096 and 8192 are recommended</emphasis>
1065 so that you will notice when things go wrong. The other levels are
1066 probably only of interest if you are hunting down a specific problem.
1067 They can produce a hell of an output (especially 16).
1071 If you are used to the more verbose settings, simply enable the debug lines
1075 If you want to use pure CLF (Common Log Format), you should set <quote>debug
1076 512</quote> <emphasis>ONLY</emphasis> and not enable anything else.
1079 <application>Privoxy</application> has a hard-coded limit for the
1080 length of log messages. If it's reached, messages are logged truncated
1081 and marked with <quote>... [too long, truncated]</quote>.
1084 Please don't file any support requests without trying to reproduce
1085 the problem with increased debug level first. Once you read the log
1086 messages, you may even be able to solve the problem on your own.
1092 <![%config-file;[<literallayout>@@#debug 1 # Log the destination for each request &my-app; let through.</literallayout>]]>
1093 <![%config-file;[<literallayout>@@#debug 1024 # Log the destination for requests &my-app; didn't let through, and the reason why.</literallayout>]]>
1094 <![%config-file;[<literallayout>@@#debug 4096 # Startup banner and warnings</literallayout>]]>
1095 <![%config-file;[<literallayout>@@#debug 8192 # Non-fatal errors</literallayout>]]>
1099 <!-- ~~~~~ New section ~~~~~ -->
1100 <sect3 renderas="sect4" id="single-threaded"><title>single-threaded</title>
1104 <term>Specifies:</term>
1107 Whether to run only one server thread.
1112 <term>Type of value:</term>
1114 <para><emphasis>1 or 0</emphasis></para>
1118 <term>Default value:</term>
1120 <para><emphasis>0</emphasis></para>
1124 <term>Effect if unset:</term>
1127 Multi-threaded (or, where unavailable: forked) operation, i.e. the ability to
1128 serve multiple requests simultaneously.
1136 This option is only there for debugging purposes.
1137 <emphasis>It will drastically reduce performance.</emphasis>
1143 <![%config-file;[<literallayout>@@#single-threaded 1</literallayout>]]>
1146 <!-- ~~~~~ New section ~~~~~ -->
1147 <sect3 renderas="sect4" id="hostname"><title>hostname</title>
1151 <term>Specifies:</term>
1154 The hostname shown on the CGI pages.
1159 <term>Type of value:</term>
1165 <term>Default value:</term>
1167 <para><emphasis>Unset</emphasis></para>
1171 <term>Effect if unset:</term>
1174 The hostname provided by the operating system is used.
1182 On some misconfigured systems resolving the hostname fails or
1183 takes too much time and slows Privoxy down. Setting a fixed hostname
1184 works around the problem.
1187 In other circumstances it might be desirable to show a hostname
1188 other than the one returned by the operating system. For example
1189 if the system has several different hostnames and you don't want
1190 to use the first one.
1193 Note that Privoxy does not validate the specified hostname value.
1199 <![%config-file;[<literallayout>@@#hostname hostname.example.org</literallayout>]]>
1204 <!-- ~ End section ~ -->
1207 <!-- ~~~~~ New section ~~~~~ -->
1208 <sect2 id="access-control">
1209 <title>Access Control and Security</title>
1212 This section of the config file controls the security-relevant aspects
1213 of <application>Privoxy</application>'s configuration.
1217 <!-- ~~~~~ New section ~~~~~ -->
1218 <sect3 renderas="sect4" id="listen-address"><title>listen-address</title>
1222 <term>Specifies:</term>
1225 The address and TCP port on which <application>Privoxy</application> will
1226 listen for client requests.
1231 <term>Type of value:</term>
1233 <para>[<replaceable class="parameter">IP-Address</replaceable>]:<replaceable class="parameter">Port</replaceable></para>
1234 <para>[<replaceable class="parameter">Hostname</replaceable>]:<replaceable class="parameter">Port</replaceable></para>
1239 <term>Default value:</term>
1241 <para>127.0.0.1:8118</para>
1245 <term>Effect if unset:</term>
1248 Bind to 127.0.0.1 (IPv4 localhost), port 8118. This is suitable and
1249 recommended for home users who run <application>Privoxy</application> on
1250 the same machine as their browser.
1258 You will need to configure your browser(s) to this proxy address and port.
1261 If you already have another service running on port 8118, or if you want to
1262 serve requests from other machines (e.g. on your local network) as well, you
1263 will need to override the default.
1266 You can use this statement multiple times to make
1267 <application>Privoxy</application> listen on more ports or more
1268 <abbrev>IP</abbrev> addresses. Suitable if your operating system does not
1269 support sharing <abbrev>IPv6</abbrev> and <abbrev>IPv4</abbrev> protocols
1273 If a hostname is used instead of an IP address, <application>Privoxy</application>
1274 will try to resolve it to an IP address and if there are multiple, use the first
1278 If the address for the hostname isn't already known on the system
1279 (for example because it's in /etc/hostname), this may result in DNS
1283 If the specified address isn't available on the system, or if the
1284 hostname can't be resolved, <application>Privoxy</application>
1288 IPv6 addresses containing colons have to be quoted by brackets.
1289 They can only be used if <application>Privoxy</application> has
1290 been compiled with IPv6 support. If you aren't sure if your version
1291 supports it, have a look at
1292 <literal>http://config.privoxy.org/show-status</literal>.
1295 Some operating systems will prefer IPv6 to IPv4 addresses even if the
1296 system has no IPv6 connectivity which is usually not expected by the user.
1297 Some even rely on DNS to resolve localhost which mean the "localhost" address
1298 used may not actually be local.
1301 It is therefore recommended to explicitly configure the intended IP address
1302 instead of relying on the operating system, unless there's a strong reason not to.
1305 If you leave out the address, <application>Privoxy</application> will bind to all
1306 IPv4 interfaces (addresses) on your machine and may become reachable from the
1307 Internet and/or the local network. Be aware that some GNU/Linux distributions
1308 modify that behaviour without updating the documentation. Check for non-standard
1309 patches if your <application>Privoxy</application> version behaves differently.
1312 If you configure <application>Privoxy</application> to be reachable from the
1313 network, consider using <link linkend="acls">access control lists</link>
1314 (ACL's, see below), and/or a firewall.
1317 If you open <application>Privoxy</application> to untrusted users, you will
1318 also want to make sure that the following actions are disabled: <literal><link
1319 linkend="enable-edit-actions">enable-edit-actions</link></literal> and
1320 <literal><link linkend="enable-remote-toggle">enable-remote-toggle</link></literal>
1325 <term>Example:</term>
1328 Suppose you are running <application>Privoxy</application> on
1329 a machine which has the address 192.168.0.1 on your local private network
1330 (192.168.0.0) and has another outside connection with a different address.
1331 You want it to serve requests from inside only:
1335 listen-address 192.168.0.1:8118
1339 Suppose you are running <application>Privoxy</application> on an
1340 IPv6-capable machine and you want it to listen on the IPv6 address
1341 of the loopback device:
1345 listen-address [::1]:8118
1352 <![%config-file;[<literallayout>@@listen-address 127.0.0.1:8118</literallayout>]]>
1356 <!-- ~~~~~ New section ~~~~~ -->
1357 <sect3 renderas="sect4" id="toggle"><title>toggle</title>
1361 <term>Specifies:</term>
1364 Initial state of "toggle" status
1369 <term>Type of value:</term>
1375 <term>Default value:</term>
1381 <term>Effect if unset:</term>
1384 Act as if toggled on
1392 If set to 0, <application>Privoxy</application> will start in
1393 <quote>toggled off</quote> mode, i.e. mostly behave like a normal,
1394 content-neutral proxy with both ad blocking and content filtering
1395 disabled. See <literal>enable-remote-toggle</literal> below.
1401 <![%config-file;[<literallayout>@@toggle 1</literallayout>]]>
1405 <!-- ~~~~~ New section ~~~~~ -->
1406 <sect3 renderas="sect4" id="enable-remote-toggle"><title>enable-remote-toggle</title>
1409 <term>Specifies:</term>
1412 Whether or not the <ulink url="http://config.privoxy.org/toggle">web-based toggle
1413 feature</ulink> may be used
1418 <term>Type of value:</term>
1424 <term>Default value:</term>
1430 <term>Effect if unset:</term>
1433 The web-based toggle feature is disabled.
1441 When toggled off, <application>Privoxy</application> mostly acts like a normal,
1442 content-neutral proxy, i.e. doesn't block ads or filter content.
1445 Access to the toggle feature can <emphasis>not</emphasis> be
1446 controlled separately by <quote>ACLs</quote> or HTTP authentication,
1447 so that everybody who can access <application>Privoxy</application> (see
1448 <quote>ACLs</quote> and <literal>listen-address</literal> above) can
1449 toggle it for all users. So this option is <emphasis>not recommended</emphasis>
1450 for multi-user environments with untrusted users.
1453 Note that malicious client side code (e.g Java) is also
1454 capable of using this option.
1457 As a lot of <application>Privoxy</application> users don't read
1458 documentation, this feature is disabled by default.
1461 Note that you must have compiled <application>Privoxy</application> with
1462 support for this feature, otherwise this option has no effect.
1468 <![%config-file;[<literallayout>@@enable-remote-toggle 0</literallayout>]]>
1472 <!-- ~~~~~ New section ~~~~~ -->
1473 <sect3 renderas="sect4" id="enable-remote-http-toggle"><title>enable-remote-http-toggle</title>
1476 <term>Specifies:</term>
1479 Whether or not Privoxy recognizes special HTTP headers to change its behaviour.
1484 <term>Type of value:</term>
1490 <term>Default value:</term>
1496 <term>Effect if unset:</term>
1499 Privoxy ignores special HTTP headers.
1507 When toggled on, the client can change <application>Privoxy's</application>
1508 behaviour by setting special HTTP headers. Currently the only supported
1509 special header is <quote>X-Filter: No</quote>, to disable filtering for
1510 the ongoing request, even if it is enabled in one of the action files.
1513 This feature is disabled by default. If you are using
1514 <application>Privoxy</application> in a environment with trusted clients,
1515 you may enable this feature at your discretion. Note that malicious client
1516 side code (e.g Java) is also capable of using this feature.
1519 This option will be removed in future releases as it has been obsoleted
1520 by the more general header taggers.
1526 <![%config-file;[<literallayout>@@enable-remote-http-toggle 0</literallayout>]]>
1530 <!-- ~~~~~ New section ~~~~~ -->
1531 <sect3 renderas="sect4" id="enable-edit-actions"><title>enable-edit-actions</title>
1534 <term>Specifies:</term>
1537 Whether or not the <ulink url="http://config.privoxy.org/show-status">web-based actions
1538 file editor</ulink> may be used
1543 <term>Type of value:</term>
1549 <term>Default value:</term>
1555 <term>Effect if unset:</term>
1558 The web-based actions file editor is disabled.
1566 Access to the editor can <emphasis>not</emphasis> be
1567 controlled separately by <quote>ACLs</quote> or HTTP authentication,
1568 so that everybody who can access <application>Privoxy</application> (see
1569 <quote>ACLs</quote> and <literal>listen-address</literal> above) can
1570 modify its configuration for all users.
1573 This option is <emphasis>not recommended</emphasis> for environments
1574 with untrusted users and as a lot of <application>Privoxy</application>
1575 users don't read documentation, this feature is disabled by default.
1578 Note that malicious client side code (e.g Java) is also
1579 capable of using the actions editor and you shouldn't enable
1580 this options unless you understand the consequences and are
1581 sure your browser is configured correctly.
1584 Note that you must have compiled <application>Privoxy</application> with
1585 support for this feature, otherwise this option has no effect.
1591 <![%config-file;[<literallayout>@@enable-edit-actions 0</literallayout>]]>
1595 <sect3 renderas="sect4" id="enforce-blocks"><title>enforce-blocks</title>
1598 <term>Specifies:</term>
1601 Whether the user is allowed to ignore blocks and can <quote>go there anyway</quote>.
1606 <term>Type of value:</term>
1609 <replaceable>0 or 1</replaceable>
1614 <term>Default value:</term>
1616 <para><emphasis>0</emphasis></para>
1620 <term>Effect if unset:</term>
1623 Blocks are not enforced.
1631 <application>Privoxy</application> is mainly used to block and filter
1632 requests as a service to the user, for example to block ads and other
1633 junk that clogs the pipes. <application>Privoxy's</application> configuration
1634 isn't perfect and sometimes innocent pages are blocked. In this situation it
1635 makes sense to allow the user to enforce the request and have
1636 <application>Privoxy</application> ignore the block.
1639 In the default configuration <application>Privoxy's</application>
1640 <quote>Blocked</quote> page contains a <quote>go there anyway</quote>
1641 link to adds a special string (the force prefix) to the request URL.
1642 If that link is used, <application>Privoxy</application> will
1643 detect the force prefix, remove it again and let the request pass.
1646 Of course <application>Privoxy</application> can also be used to enforce
1647 a network policy. In that case the user obviously should not be able to
1648 bypass any blocks, and that's what the <quote>enforce-blocks</quote>
1649 option is for. If it's enabled, <application>Privoxy</application> hides
1650 the <quote>go there anyway</quote> link. If the user adds the force
1651 prefix by hand, it will not be accepted and the circumvention attempt
1657 <term>Examples:</term>
1665 <![%config-file;[<literallayout>@@enforce-blocks 0</literallayout>]]>
1669 <!-- ~~~~~ New section ~~~~~ -->
1670 <sect3 renderas="sect4" id="acls"><title>
1671 ACLs: permit-access and deny-access</title>
1672 <anchor id="permit-access">
1673 <anchor id="deny-access">
1677 <term>Specifies:</term>
1680 Who can access what.
1685 <term>Type of value:</term>
1688 <replaceable class="parameter">src_addr</replaceable>[:<replaceable class="parameter">port</replaceable>][/<replaceable class="parameter">src_masklen</replaceable>]
1689 [<replaceable class="parameter">dst_addr</replaceable>[:<replaceable class="parameter">port</replaceable>][/<replaceable class="parameter">dst_masklen</replaceable>]]
1692 Where <replaceable class="parameter">src_addr</replaceable> and
1693 <replaceable class="parameter">dst_addr</replaceable> are IPv4 addresses in dotted decimal notation or valid
1694 DNS names, <replaceable class="parameter">port</replaceable> is a port
1695 number, and <replaceable class="parameter">src_masklen</replaceable> and
1696 <replaceable class="parameter">dst_masklen</replaceable> are subnet masks in CIDR notation, i.e. integer
1697 values from 2 to 30 representing the length (in bits) of the network address. The masks and the whole
1698 destination part are optional.
1701 If your system implements
1702 <ulink url="http://tools.ietf.org/html/rfc3493">RFC 3493</ulink>, then
1703 <replaceable class="parameter">src_addr</replaceable> and <replaceable
1704 class="parameter">dst_addr</replaceable> can be IPv6 addresses delimeted by
1705 brackets, <replaceable class="parameter">port</replaceable> can be a number
1706 or a service name, and
1707 <replaceable class="parameter">src_masklen</replaceable> and
1708 <replaceable class="parameter">dst_masklen</replaceable> can be a number
1714 <term>Default value:</term>
1716 <para><emphasis>Unset</emphasis></para>
1718 If no <replaceable class="parameter">port</replaceable> is specified,
1719 any port will match. If no <replaceable class="parameter">src_masklen</replaceable> or
1720 <replaceable class="parameter">src_masklen</replaceable> is given, the complete IP
1721 address has to match (i.e. 32 bits for IPv4 and 128 bits for IPv6).
1726 <term>Effect if unset:</term>
1729 Don't restrict access further than implied by <literal>listen-address</literal>
1737 Access controls are included at the request of ISPs and systems
1738 administrators, and <emphasis>are not usually needed by individual users</emphasis>.
1739 For a typical home user, it will normally suffice to ensure that
1740 <application>Privoxy</application> only listens on the localhost
1741 (127.0.0.1) or internal (home) network address by means of the
1742 <link linkend="listen-address"><emphasis>listen-address</emphasis></link>
1746 Please see the warnings in the FAQ that <application>Privoxy</application>
1747 is not intended to be a substitute for a firewall or to encourage anyone
1748 to defer addressing basic security weaknesses.
1751 Multiple ACL lines are OK.
1752 If any ACLs are specified, <application>Privoxy</application> only talks
1753 to IP addresses that match at least one <literal>permit-access</literal> line
1754 and don't match any subsequent <literal>deny-access</literal> line. In other words, the
1755 last match wins, with the default being <literal>deny-access</literal>.
1758 If <application>Privoxy</application> is using a forwarder (see <literal>forward</literal> below)
1759 for a particular destination URL, the <replaceable class="parameter">dst_addr</replaceable>
1760 that is examined is the address of the forwarder and <emphasis>NOT</emphasis> the address
1761 of the ultimate target. This is necessary because it may be impossible for the local
1762 <application>Privoxy</application> to determine the IP address of the
1763 ultimate target (that's often what gateways are used for).
1766 You should prefer using IP addresses over DNS names, because the address lookups take
1767 time. All DNS names must resolve! You can <emphasis>not</emphasis> use domain patterns
1768 like <quote>*.org</quote> or partial domain names. If a DNS name resolves to multiple
1769 IP addresses, only the first one is used.
1772 Some systems allow IPv4 clients to connect to IPv6 server sockets.
1773 Then the client's IPv4 address will be translated by the system into
1774 IPv6 address space with special prefix ::ffff:0:0/96 (so called IPv4
1775 mapped IPv6 address). <application>Privoxy</application> can handle it
1776 and maps such ACL addresses automatically.
1779 Denying access to particular sites by ACL may have undesired side effects
1780 if the site in question is hosted on a machine which also hosts other sites
1786 <term>Examples:</term>
1789 Explicitly define the default behavior if no ACL and
1790 <literal>listen-address</literal> are set: <quote>localhost</quote>
1791 is OK. The absence of a <replaceable class="parameter">dst_addr</replaceable> implies that
1792 <emphasis>all</emphasis> destination addresses are OK:
1796 permit-access localhost
1800 Allow any host on the same class C subnet as www.privoxy.org access to
1801 nothing but www.example.com (or other domains hosted on the same system):
1805 permit-access www.privoxy.org/24 www.example.com/32
1809 Allow access from any host on the 26-bit subnet 192.168.45.64 to anywhere,
1810 with the exception that 192.168.45.73 may not access the IP address behind
1811 www.dirty-stuff.example.com:
1815 permit-access 192.168.45.64/26
1816 deny-access 192.168.45.73 www.dirty-stuff.example.com
1820 Allow access from the IPv4 network 192.0.2.0/24 even if listening on
1821 an IPv6 wild card address (not supported on all platforms):
1825 permit-access 192.0.2.0/24
1829 This is equivalent to the following line even if listening on an
1830 IPv4 address (not supported on all platforms):
1834 permit-access [::ffff:192.0.2.0]/120
1843 <!-- ~~~~~ New section ~~~~~ -->
1844 <sect3 renderas="sect4" id="buffer-limit"><title>buffer-limit</title>
1848 <term>Specifies:</term>
1851 Maximum size of the buffer for content filtering.
1856 <term>Type of value:</term>
1858 <para>Size in Kbytes</para>
1862 <term>Default value:</term>
1868 <term>Effect if unset:</term>
1871 Use a 4MB (4096 KB) limit.
1879 For content filtering, i.e. the <literal>+filter</literal> and
1880 <literal>+deanimate-gif</literal> actions, it is necessary that
1881 <application>Privoxy</application> buffers the entire document body.
1882 This can be potentially dangerous, since a server could just keep sending
1883 data indefinitely and wait for your RAM to exhaust -- with nasty consequences.
1887 When a document buffer size reaches the <literal>buffer-limit</literal>, it is
1888 flushed to the client unfiltered and no further attempt to
1889 filter the rest of the document is made. Remember that there may be multiple threads
1890 running, which might require up to <literal>buffer-limit</literal> Kbytes
1891 <emphasis>each</emphasis>, unless you have enabled <quote>single-threaded</quote>
1898 <![%config-file;[<literallayout>@@buffer-limit 4096</literallayout>]]>
1901 <!-- ~~~~~ New section ~~~~~ -->
1902 <sect3 renderas="sect4" id="enable-proxy-authentication-forwarding"><title>enable-proxy-authentication-forwarding</title>
1905 <term>Specifies:</term>
1908 Whether or not proxy authentication through &my-app; should work.
1913 <term>Type of value:</term>
1919 <term>Default value:</term>
1925 <term>Effect if unset:</term>
1928 Proxy authentication headers are removed.
1936 Privoxy itself does not support proxy authentication, but can
1937 allow clients to authenticate against Privoxy's parent proxy.
1940 By default Privoxy (3.0.21 and later) don't do that and remove
1941 Proxy-Authorization headers in requests and Proxy-Authenticate
1942 headers in responses to make it harder for malicious sites to
1943 trick inexperienced users into providing login information.
1946 If this option is enabled the headers are forwarded.
1949 Enabling this option is <emphasis>not recommended</emphasis> if there is
1950 no parent proxy that requires authentication or if the local network between
1951 Privoxy and the parent proxy isn't trustworthy. If proxy authentication is
1952 only required for some requests, it is recommended to use a client header filter
1953 to remove the authentication headers for requests where they aren't needed.
1959 <![%config-file;[<literallayout>@@enable-proxy-authentication-forwarding 0</literallayout>]]>
1964 <!-- ~ End section ~ -->
1967 <!-- ~~~~~ New section ~~~~~ -->
1969 <sect2 id="forwarding">
1970 <title>Forwarding</title>
1973 This feature allows routing of HTTP requests through a chain of
1977 Forwarding can be used to chain Privoxy with a caching proxy to speed
1978 up browsing. Using a parent proxy may also be necessary if the machine
1979 that <application>Privoxy</application> runs on has no direct Internet access.
1982 Note that parent proxies can severely decrease your privacy level.
1983 For example a parent proxy could add your IP address to the request
1984 headers and if it's a caching proxy it may add the <quote>Etag</quote>
1985 header to revalidation requests again, even though you configured Privoxy
1986 to remove it. It may also ignore Privoxy's header time randomization and use the
1987 original values which could be used by the server as cookie replacement
1988 to track your steps between visits.
1992 Also specified here are SOCKS proxies. <application>Privoxy</application>
1993 supports the SOCKS 4 and SOCKS 4A protocols.
1996 <sect3 renderas="sect4" id="forward"><title>forward</title>
1999 <term>Specifies:</term>
2002 To which parent HTTP proxy specific requests should be routed.
2007 <term>Type of value:</term>
2010 <replaceable class="parameter">target_pattern</replaceable>
2011 <replaceable class="parameter">http_parent</replaceable>[:<replaceable class="parameter">port</replaceable>]
2014 where <replaceable class="parameter">target_pattern</replaceable> is a <link linkend="af-patterns">URL pattern</link>
2015 that specifies to which requests (i.e. URLs) this forward rule shall apply. Use <literal>/</literal> to
2016 denote <quote>all URLs</quote>.
2017 <replaceable class="parameter">http_parent</replaceable>[:<replaceable class="parameter">port</replaceable>]
2018 is the DNS name or IP address of the parent HTTP proxy through which the requests should be forwarded,
2019 optionally followed by its listening port (default: 8000).
2020 Use a single dot (<literal>.</literal>) to denote <quote>no forwarding</quote>.
2025 <term>Default value:</term>
2027 <para><emphasis>Unset</emphasis></para>
2031 <term>Effect if unset:</term>
2034 Don't use parent HTTP proxies.
2042 If <replaceable class="parameter">http_parent</replaceable> is <quote>.</quote>, then requests are not
2043 forwarded to another HTTP proxy but are made directly to the web servers.
2046 <replaceable class="parameter">http_parent</replaceable> can be a
2047 numerical IPv6 address (if
2048 <ulink url="http://tools.ietf.org/html/rfc3493">RFC 3493</ulink> is
2049 implemented). To prevent clashes with the port delimiter, the whole IP
2050 address has to be put into brackets. On the other hand a <replaceable
2051 class="parameter">target_pattern</replaceable> containing an IPv6 address
2052 has to be put into angle brackets (normal brackets are reserved for
2053 regular expressions already).
2056 Multiple lines are OK, they are checked in sequence, and the last match wins.
2061 <term>Examples:</term>
2064 Everything goes to an example parent proxy, except SSL on port 443 (which it doesn't handle):
2068 forward / parent-proxy.example.org:8080
2073 Everything goes to our example ISP's caching proxy, except for requests
2074 to that ISP's sites:
2078 forward / caching-proxy.isp.example.net:8000
2079 forward .isp.example.net .
2083 Parent proxy specified by an IPv6 address:
2087 forward / [2001:DB8::1]:8000
2091 Suppose your parent proxy doesn't support IPv6:
2095 forward / parent-proxy.example.org:8000
2096 forward ipv6-server.example.org .
2097 forward <[2-3][0-9a-f][0-9a-f][0-9a-f]:*> .
2106 <!-- ~~~~~ New section ~~~~~ -->
2107 <sect3 renderas="sect4" id="socks"><title>
2108 forward-socks4, forward-socks4a, forward-socks5 and forward-socks5t</title>
2109 <anchor id="forward-socks4">
2110 <anchor id="forward-socks4a">
2114 <term>Specifies:</term>
2117 Through which SOCKS proxy (and optionally to which parent HTTP proxy) specific requests should be routed.
2122 <term>Type of value:</term>
2125 <replaceable class="parameter">target_pattern</replaceable>
2126 <replaceable class="parameter">socks_proxy</replaceable>[:<replaceable class="parameter">port</replaceable>]
2127 <replaceable class="parameter">http_parent</replaceable>[:<replaceable class="parameter">port</replaceable>]
2130 where <replaceable class="parameter">target_pattern</replaceable> is a
2131 <link linkend="af-patterns">URL pattern</link> that specifies to which
2132 requests (i.e. URLs) this forward rule shall apply. Use <literal>/</literal> to
2133 denote <quote>all URLs</quote>. <replaceable class="parameter">http_parent</replaceable>
2134 and <replaceable class="parameter">socks_proxy</replaceable>
2135 are IP addresses in dotted decimal notation or valid DNS names
2136 (<replaceable class="parameter">http_parent</replaceable>
2137 may be <quote>.</quote> to denote <quote>no HTTP forwarding</quote>), and the optional
2138 <replaceable class="parameter">port</replaceable> parameters are TCP ports,
2139 i.e. integer values from 1 to 65535
2144 <term>Default value:</term>
2146 <para><emphasis>Unset</emphasis></para>
2150 <term>Effect if unset:</term>
2153 Don't use SOCKS proxies.
2161 Multiple lines are OK, they are checked in sequence, and the last match wins.
2164 The difference between <literal>forward-socks4</literal> and <literal>forward-socks4a</literal>
2165 is that in the SOCKS 4A protocol, the DNS resolution of the target hostname happens on the SOCKS
2166 server, while in SOCKS 4 it happens locally.
2169 With <literal>forward-socks5</literal> the DNS resolution will happen on the remote server as well.
2172 <literal>forward-socks5t</literal> works like vanilla <literal>forward-socks5</literal> but
2173 lets &my-app; additionally use Tor-specific SOCKS extensions. Currently the only supported
2174 SOCKS extension is optimistic data which can reduce the latency for the first request made
2175 on a newly created connection.
2178 <replaceable class="parameter">socks_proxy</replaceable> and
2179 <replaceable class="parameter">http_parent</replaceable> can be a
2180 numerical IPv6 address (if
2181 <ulink url="http://tools.ietf.org/html/rfc3493">RFC 3493</ulink> is
2182 implemented). To prevent clashes with the port delimiter, the whole IP
2183 address has to be put into brackets. On the other hand a <replaceable
2184 class="parameter">target_pattern</replaceable> containing an IPv6 address
2185 has to be put into angle brackets (normal brackets are reserved for
2186 regular expressions already).
2189 If <replaceable class="parameter">http_parent</replaceable> is <quote>.</quote>, then requests are not
2190 forwarded to another HTTP proxy but are made (HTTP-wise) directly to the web servers, albeit through
2196 <term>Examples:</term>
2199 From the company example.com, direct connections are made to all
2200 <quote>internal</quote> domains, but everything outbound goes through
2201 their ISP's proxy by way of example.com's corporate SOCKS 4A gateway to
2206 forward-socks4a / socks-gw.example.com:1080 www-cache.isp.example.net:8080
2207 forward .example.com .
2211 A rule that uses a SOCKS 4 gateway for all destinations but no HTTP parent looks like this:
2215 forward-socks4 / socks-gw.example.com:1080 .
2220 To chain Privoxy and Tor, both running on the same system, you would use
2225 forward-socks5t / 127.0.0.1:9050 .
2229 Note that if you got Tor through one of the bundles, you may
2230 have to change the port from 9050 to 9150 (or even another one).
2231 For details, please check the documentation on the
2232 <ulink url="https://torproject.org/">Tor website</ulink>.
2235 The public <application>Tor</application> network can't be used to
2236 reach your local network, if you need to access local servers you
2237 therefore might want to make some exceptions:
2241 forward 192.168.*.*/ .
2243 forward 127.*.*.*/ .
2247 Unencrypted connections to systems in these address ranges will
2248 be as (un)secure as the local network is, but the alternative is that you
2249 can't reach the local network through <application>Privoxy</application>
2250 at all. Of course this may actually be desired and there is no reason
2251 to make these exceptions if you aren't sure you need them.
2254 If you also want to be able to reach servers in your local network by
2255 using their names, you will need additional exceptions that look like
2260 forward localhost/ .
2269 <![%user-man;[ <!-- not included in config due to length -->
2270 <!-- ~~~~~ New section ~~~~~ -->
2271 <sect3 renderas="sect4" id="advanced-forwarding-examples"><title>Advanced Forwarding Examples</title>
2274 If you have links to multiple ISPs that provide various special content
2275 only to their subscribers, you can configure multiple <application>Privoxies</application>
2276 which have connections to the respective ISPs to act as forwarders to each other, so that
2277 <emphasis>your</emphasis> users can see the internal content of all ISPs.
2281 Assume that host-a has a PPP connection to isp-a.example.net. And host-b has a PPP connection to
2282 isp-b.example.org. Both run <application>Privoxy</application>. Their forwarding
2283 configuration can look like this:
2293 forward .isp-b.example.net host-b:8118
2304 forward .isp-a.example.org host-a:8118
2309 Now, your users can set their browser's proxy to use either
2310 host-a or host-b and be able to browse the internal content
2311 of both isp-a and isp-b.
2315 If you intend to chain <application>Privoxy</application> and
2316 <application>squid</application> locally, then chaining as
2317 <literal>browser -> squid -> privoxy</literal> is the recommended way.
2321 Assuming that <application>Privoxy</application> and <application>squid</application>
2322 run on the same box, your <application>squid</application> configuration could then look like this:
2327 # Define Privoxy as parent proxy (without ICP)
2328 cache_peer 127.0.0.1 parent 8118 7 no-query
2330 # Define ACL for protocol FTP
2333 # Do not forward FTP requests to Privoxy
2334 always_direct allow ftp
2336 # Forward all the rest to Privoxy
2337 never_direct allow all</screen>
2341 You would then need to change your browser's proxy settings to <application>squid</application>'s address and port.
2342 Squid normally uses port 3128. If unsure consult <literal>http_port</literal> in <filename>squid.conf</filename>.
2346 You could just as well decide to only forward requests you suspect
2347 of leading to Windows executables through a virus-scanning parent proxy,
2348 say, on <literal>antivir.example.com</literal>, port 8010:
2354 forward /.*\.(exe|com|dll|zip)$ antivir.example.com:8010</screen>
2360 <sect3 renderas="sect4" id="forwarded-connect-retries"><title>forwarded-connect-retries</title>
2363 <term>Specifies:</term>
2366 How often Privoxy retries if a forwarded connection request fails.
2371 <term>Type of value:</term>
2374 <replaceable class="parameter">Number of retries.</replaceable>
2379 <term>Default value:</term>
2381 <para><emphasis>0</emphasis></para>
2385 <term>Effect if unset:</term>
2388 Connections forwarded through other proxies are treated like direct connections and no retry attempts are made.
2396 <replaceable class="parameter">forwarded-connect-retries</replaceable> is mainly interesting
2397 for socks4a connections, where <application>Privoxy</application> can't detect why the connections failed.
2398 The connection might have failed because of a DNS timeout in which case a retry makes sense,
2399 but it might also have failed because the server doesn't exist or isn't reachable. In this
2400 case the retry will just delay the appearance of Privoxy's error message.
2403 Note that in the context of this option, <quote>forwarded connections</quote> includes all connections
2404 that Privoxy forwards through other proxies. This option is not limited to the HTTP CONNECT method.
2407 Only use this option, if you are getting lots of forwarding-related error messages
2408 that go away when you try again manually. Start with a small value and check Privoxy's
2409 logfile from time to time, to see how many retries are usually needed.
2414 <term>Examples:</term>
2417 forwarded-connect-retries 1
2422 <![%config-file;[<literallayout>@@forwarded-connect-retries 0</literallayout>]]>
2428 <title>Miscellaneous</title>
2430 <sect3 renderas="sect4" id="accept-intercepted-requests"><title>accept-intercepted-requests</title>
2433 <term>Specifies:</term>
2436 Whether intercepted requests should be treated as valid.
2441 <term>Type of value:</term>
2444 <replaceable>0 or 1</replaceable>
2449 <term>Default value:</term>
2451 <para><emphasis>0</emphasis></para>
2455 <term>Effect if unset:</term>
2458 Only proxy requests are accepted, intercepted requests are treated as invalid.
2466 If you don't trust your clients and want to force them
2467 to use <application>Privoxy</application>, enable this
2468 option and configure your packet filter to redirect outgoing
2469 HTTP connections into <application>Privoxy</application>.
2472 Note that intercepting encrypted connections (HTTPS) isn't supported.
2475 Make sure that <application>Privoxy's</application> own requests
2476 aren't redirected as well. Additionally take care that
2477 <application>Privoxy</application> can't intentionally connect
2478 to itself, otherwise you could run into redirection loops if
2479 <application>Privoxy's</application> listening port is reachable
2480 by the outside or an attacker has access to the pages you visit.
2485 <term>Examples:</term>
2488 accept-intercepted-requests 1
2493 <![%config-file;[<literallayout>@@accept-intercepted-requests 0</literallayout>]]>
2496 <sect3 renderas="sect4" id="allow-cgi-request-crunching"><title>allow-cgi-request-crunching</title>
2499 <term>Specifies:</term>
2502 Whether requests to <application>Privoxy's</application> CGI pages can be blocked or redirected.
2507 <term>Type of value:</term>
2510 <replaceable>0 or 1</replaceable>
2515 <term>Default value:</term>
2517 <para><emphasis>0</emphasis></para>
2521 <term>Effect if unset:</term>
2524 <application>Privoxy</application> ignores block and redirect actions for its CGI pages.
2532 By default <application>Privoxy</application> ignores block or redirect actions
2533 for its CGI pages. Intercepting these requests can be useful in multi-user
2534 setups to implement fine-grained access control, but it can also render the complete
2535 web interface useless and make debugging problems painful if done without care.
2538 Don't enable this option unless you're sure that you really need it.
2543 <term>Examples:</term>
2546 allow-cgi-request-crunching 1
2551 <![%config-file;[<literallayout>@@allow-cgi-request-crunching 0</literallayout>]]>
2554 <sect3 renderas="sect4" id="split-large-forms"><title>split-large-forms</title>
2557 <term>Specifies:</term>
2560 Whether the CGI interface should stay compatible with broken HTTP clients.
2565 <term>Type of value:</term>
2568 <replaceable>0 or 1</replaceable>
2573 <term>Default value:</term>
2575 <para><emphasis>0</emphasis></para>
2579 <term>Effect if unset:</term>
2582 The CGI form generate long GET URLs.
2590 <application>Privoxy's</application> CGI forms can lead to
2591 rather long URLs. This isn't a problem as far as the HTTP
2592 standard is concerned, but it can confuse clients with arbitrary
2593 URL length limitations.
2596 Enabling split-large-forms causes <application>Privoxy</application>
2597 to divide big forms into smaller ones to keep the URL length down.
2598 It makes editing a lot less convenient and you can no longer
2599 submit all changes at once, but at least it works around this
2603 If you don't notice any editing problems, there is no reason
2604 to enable this option, but if one of the submit buttons appears
2605 to be broken, you should give it a try.
2610 <term>Examples:</term>
2618 <![%config-file;[<literallayout>@@split-large-forms 0</literallayout>]]>
2621 <sect3 renderas="sect4" id="keep-alive-timeout"><title>keep-alive-timeout</title>
2624 <term>Specifies:</term>
2627 Number of seconds after which an open connection will no longer be reused.
2632 <term>Type of value:</term>
2635 <replaceable>Time in seconds.</replaceable>
2640 <term>Default value:</term>
2646 <term>Effect if unset:</term>
2649 Connections are not kept alive.
2657 This option allows clients to keep the connection to &my-app;
2658 alive. If the server supports it, &my-app; will keep
2659 the connection to the server alive as well. Under certain
2660 circumstances this may result in speed-ups.
2663 By default, &my-app; will close the connection to the server if
2664 the client connection gets closed, or if the specified timeout
2665 has been reached without a new request coming in. This behaviour
2666 can be changed with the <ulink
2667 url="#CONNECTION-SHARING">connection-sharing</ulink> option.
2670 This option has no effect if <application>Privoxy</application>
2671 has been compiled without keep-alive support.
2674 Note that a timeout of five seconds as used in the default
2675 configuration file significantly decreases the number of
2676 connections that will be reused. The value is used because
2677 some browsers limit the number of connections they open to
2678 a single host and apply the same limit to proxies. This can
2679 result in a single website <quote>grabbing</quote> all the
2680 connections the browser allows, which means connections to
2681 other websites can't be opened until the connections currently
2685 Several users have reported this as a Privoxy bug, so the
2686 default value has been reduced. Consider increasing it to
2687 300 seconds or even more if you think your browser can handle
2688 it. If your browser appears to be hanging, it probably can't.
2693 <term>Examples:</term>
2696 keep-alive-timeout 300
2701 <![%config-file;[<literallayout>@@keep-alive-timeout 5</literallayout>]]>
2705 <sect3 renderas="sect4" id="tolerate-pipelining"><title>tolerate-pipelining</title>
2708 <term>Specifies:</term>
2711 Whether or not pipelined requests should be served.
2716 <term>Type of value:</term>
2719 <replaceable>0 or 1.</replaceable>
2724 <term>Default value:</term>
2730 <term>Effect if unset:</term>
2733 If Privoxy receives more than one request at once, it terminates the
2734 client connection after serving the first one.
2742 &my-app; currently doesn't pipeline outgoing requests,
2743 thus allowing pipelining on the client connection is not
2744 guaranteed to improve the performance.
2747 By default &my-app; tries to discourage clients from pipelining
2748 by discarding aggressively pipelined requests, which forces the
2749 client to resend them through a new connection.
2752 This option lets &my-app; tolerate pipelining. Whether or not
2753 that improves performance mainly depends on the client configuration.
2756 If you are seeing problems with pages not properly loading,
2757 disabling this option could work around the problem.
2762 <term>Examples:</term>
2765 tolerate-pipelining 1
2770 <![%config-file;[<literallayout>@@tolerate-pipelining 1</literallayout>]]>
2774 <sect3 renderas="sect4" id="default-server-timeout"><title>default-server-timeout</title>
2777 <term>Specifies:</term>
2780 Assumed server-side keep-alive timeout if not specified by the server.
2785 <term>Type of value:</term>
2788 <replaceable>Time in seconds.</replaceable>
2793 <term>Default value:</term>
2799 <term>Effect if unset:</term>
2802 Connections for which the server didn't specify the keep-alive
2803 timeout are not reused.
2811 Enabling this option significantly increases the number of connections
2812 that are reused, provided the <ulink
2813 url="#KEEP-ALIVE-TIMEOUT">keep-alive-timeout</ulink> option
2817 While it also increases the number of connections problems
2818 when &my-app; tries to reuse a connection that already has
2819 been closed on the server side, or is closed while &my-app;
2820 is trying to reuse it, this should only be a problem if it
2821 happens for the first request sent by the client. If it happens
2822 for requests on reused client connections, &my-app; will simply
2823 close the connection and the client is supposed to retry the
2824 request without bothering the user.
2827 Enabling this option is therefore only recommended if the
2829 url="#CONNECTION-SHARING">connection-sharing</ulink> option
2833 It is an error to specify a value larger than the <ulink
2834 url="#KEEP-ALIVE-TIMEOUT">keep-alive-timeout</ulink> value.
2837 This option has no effect if <application>Privoxy</application>
2838 has been compiled without keep-alive support.
2843 <term>Examples:</term>
2846 default-server-timeout 60
2851 <![%config-file;[<literallayout>@@#default-server-timeout 60</literallayout>]]>
2855 <sect3 renderas="sect4" id="connection-sharing"><title>connection-sharing</title>
2858 <term>Specifies:</term>
2861 Whether or not outgoing connections that have been kept alive
2862 should be shared between different incoming connections.
2867 <term>Type of value:</term>
2870 <replaceable>0 or 1</replaceable>
2875 <term>Default value:</term>
2881 <term>Effect if unset:</term>
2884 Connections are not shared.
2892 This option has no effect if <application>Privoxy</application>
2893 has been compiled without keep-alive support, or if it's disabled.
2901 Note that reusing connections doesn't necessary cause speedups.
2902 There are also a few privacy implications you should be aware of.
2905 If this option is effective, outgoing connections are shared between
2906 clients (if there are more than one) and closing the browser that initiated
2907 the outgoing connection does no longer affect the connection between &my-app;
2908 and the server unless the client's request hasn't been completed yet.
2911 If the outgoing connection is idle, it will not be closed until either
2912 <application>Privoxy's</application> or the server's timeout is reached.
2913 While it's open, the server knows that the system running &my-app; is still
2917 If there are more than one client (maybe even belonging to multiple users),
2918 they will be able to reuse each others connections. This is potentially
2919 dangerous in case of authentication schemes like NTLM where only the
2920 connection is authenticated, instead of requiring authentication for
2924 If there is only a single client, and if said client can keep connections
2925 alive on its own, enabling this option has next to no effect. If the client
2926 doesn't support connection keep-alive, enabling this option may make sense
2927 as it allows &my-app; to keep outgoing connections alive even if the client
2928 itself doesn't support it.
2931 You should also be aware that enabling this option increases the likelihood
2932 of getting the "No server or forwarder data" error message, especially if you
2933 are using a slow connection to the Internet.
2936 This option should only be used by experienced users who
2937 understand the risks and can weight them against the benefits.
2942 <term>Examples:</term>
2945 connection-sharing 1
2950 <![%config-file;[<literallayout>@@#connection-sharing 1</literallayout>]]>
2954 <sect3 renderas="sect4" id="socket-timeout"><title>socket-timeout</title>
2957 <term>Specifies:</term>
2960 Number of seconds after which a socket times out if
2961 no data is received.
2966 <term>Type of value:</term>
2969 <replaceable>Time in seconds.</replaceable>
2974 <term>Default value:</term>
2980 <term>Effect if unset:</term>
2983 A default value of 300 seconds is used.
2991 The default is quite high and you probably want to reduce it.
2992 If you aren't using an occasionally slow proxy like Tor, reducing
2993 it to a few seconds should be fine.
2998 <term>Examples:</term>
3006 <![%config-file;[<literallayout>@@socket-timeout 300</literallayout>]]>
3010 <sect3 renderas="sect4" id="max-client-connections"><title>max-client-connections</title>
3013 <term>Specifies:</term>
3016 Maximum number of client connections that will be served.
3021 <term>Type of value:</term>
3024 <replaceable>Positive number.</replaceable>
3029 <term>Default value:</term>
3035 <term>Effect if unset:</term>
3038 Connections are served until a resource limit is reached.
3046 &my-app; creates one thread (or process) for every incoming client
3047 connection that isn't rejected based on the access control settings.
3050 If the system is powerful enough, &my-app; can theoretically deal with
3051 several hundred (or thousand) connections at the same time, but some
3052 operating systems enforce resource limits by shutting down offending
3053 processes and their default limits may be below the ones &my-app; would
3054 require under heavy load.
3057 Configuring &my-app; to enforce a connection limit below the thread
3058 or process limit used by the operating system makes sure this doesn't
3059 happen. Simply increasing the operating system's limit would work too,
3060 but if &my-app; isn't the only application running on the system,
3061 you may actually want to limit the resources used by &my-app;.
3064 If &my-app; is only used by a single trusted user, limiting the
3065 number of client connections is probably unnecessary. If there
3066 are multiple possibly untrusted users you probably still want to
3067 additionally use a packet filter to limit the maximal number of
3068 incoming connections per client. Otherwise a malicious user could
3069 intentionally create a high number of connections to prevent other
3070 users from using &my-app;.
3073 Obviously using this option only makes sense if you choose a limit
3074 below the one enforced by the operating system.
3077 One most POSIX-compliant systems &my-app; can't properly deal with
3078 more than FD_SETSIZE file descriptors at the same time and has to reject
3079 connections if the limit is reached. This will likely change in a
3080 future version, but currently this limit can't be increased without
3081 recompiling &my-app; with a different FD_SETSIZE limit.
3086 <term>Examples:</term>
3089 max-client-connections 256
3094 <![%config-file;[<literallayout>@@#max-client-connections 256</literallayout>]]>
3098 <sect3 renderas="sect4" id="handle-as-empty-doc-returns-ok"><title>handle-as-empty-doc-returns-ok</title>
3101 <term>Specifies:</term>
3104 The status code Privoxy returns for pages blocked with
3105 <!-- URL will only end up in the user manual so the relative link should work. -->
3106 <literal><ulink url="actions-file.html#HANDLE-AS-EMPTY-DOCUMENT">+handle-as-empty-document</ulink></literal>.
3111 <term>Type of value:</term>
3114 <replaceable>0 or 1</replaceable>
3119 <term>Default value:</term>
3125 <term>Effect if unset:</term>
3128 Privoxy returns a status 403(forbidden) for all blocked pages.
3133 <term>Effect if set:</term>
3136 Privoxy returns a status 200(OK) for pages blocked with +handle-as-empty-document
3137 and a status 403(Forbidden) for all other blocked pages.
3145 This directive was added as a work-around for Firefox bug 492459:
3146 <quote>Websites are no longer rendered if SSL requests for JavaScripts are blocked by a proxy.</quote>
3147 (<ulink url="https://bugzilla.mozilla.org/show_bug.cgi?id=492459"
3148 >https://bugzilla.mozilla.org/show_bug.cgi?id=492459</ulink>),
3149 the bug has been fixed for quite some time, but this directive is also useful
3150 to make it harder for websites to detect whether or not resources are being
3156 <![%config-file;[<literallayout>@@#handle-as-empty-doc-returns-ok 1</literallayout>]]>
3160 <sect3 renderas="sect4" id="enable-compression"><title>enable-compression</title>
3163 <term>Specifies:</term>
3166 Whether or not buffered content is compressed before delivery.
3171 <term>Type of value:</term>
3174 <replaceable>0 or 1</replaceable>
3179 <term>Default value:</term>
3185 <term>Effect if unset:</term>
3188 Privoxy does not compress buffered content.
3193 <term>Effect if set:</term>
3196 Privoxy compresses buffered content before delivering it to the client,
3197 provided the client supports it.
3205 This directive is only supported if Privoxy has been compiled with
3206 FEATURE_COMPRESSION, which should not to be confused with FEATURE_ZLIB.
3209 Compressing buffered content is mainly useful if Privoxy and the
3210 client are running on different systems. If they are running on the
3211 same system, enabling compression is likely to slow things down.
3212 If you didn't measure otherwise, you should assume that it does
3213 and keep this option disabled.
3216 Privoxy will not compress buffered content below a certain length.
3221 <![%config-file;[<literallayout>@@#enable-compression 1</literallayout>]]>
3225 <sect3 renderas="sect4" id="compression-level"><title>compression-level</title>
3228 <term>Specifies:</term>
3231 The compression level that is passed to the zlib library when compressing buffered content.
3236 <term>Type of value:</term>
3239 <replaceable>Positive number ranging from 0 to 9.</replaceable>
3244 <term>Default value:</term>
3253 Compressing the data more takes usually longer than compressing
3254 it less or not compressing it at all. Which level is best depends
3255 on the connection between Privoxy and the client. If you can't
3256 be bothered to benchmark it for yourself, you should stick with
3257 the default and keep compression disabled.
3260 If compression is disabled, the compression level is irrelevant.
3265 <term>Examples:</term>
3269 # Best speed (compared to the other levels)
3273 # No compression. Only useful for testing as the added header
3274 # slightly increases the amount of data that has to be sent.
3275 # If your benchmark shows that using this compression level
3276 # is superior to using no compression at all, the benchmark
3277 # is likely to be flawed.
3284 <![%config-file;[<literallayout>@@#compression-level 1</literallayout>]]>
3288 <sect3 renderas="sect4" id="client-header-order"><title>client-header-order</title>
3291 <term>Specifies:</term>
3294 The order in which client headers are sorted before forwarding them.
3299 <term>Type of value:</term>
3302 <replaceable>Client header names delimited by spaces or tabs</replaceable>
3307 <term>Default value:</term>
3316 By default &my-app; leaves the client headers in the order they
3317 were sent by the client. Headers are modified in-place, new headers
3318 are added at the end of the already existing headers.
3321 The header order can be used to fingerprint client requests
3322 independently of other headers like the User-Agent.
3325 This directive allows to sort the headers differently to better
3326 mimic a different User-Agent. Client headers will be emitted
3327 in the order given, headers whose name isn't explicitly specified
3328 are added at the end.
3331 Note that sorting headers in an uncommon way will make fingerprinting
3332 actually easier. Encrypted headers are not affected by this directive.
3337 <![%config-file;[<literallayout>@@#client-header-order Host \
3356 <!-- ~ End section ~ -->
3359 <!-- ~~~~~ New section ~~~~~ -->
3361 <sect2 id="windows-gui">
3362 <title>Windows GUI Options</title>
3364 <application>Privoxy</application> has a number of options specific to the
3365 Windows GUI interface:
3368 <anchor id="activity-animation">
3369 <![%config-file;[<para>@@</para>]]> <!-- for spacing -->
3371 If <quote>activity-animation</quote> is set to 1, the
3372 <application>Privoxy</application> icon will animate when
3373 <quote>Privoxy</quote> is active. To turn off, set to 0.
3376 <![%config-file;[<literallayout>@@#activity-animation 1</literallayout>]]>
3382 <emphasis>activity-animation 1</emphasis>
3389 <anchor id="log-messages">
3390 <![%config-file;[<para>@@</para>]]> <!-- for spacing -->
3392 If <quote>log-messages</quote> is set to 1,
3393 <application>Privoxy</application> copies log messages to the console
3395 The log detail depends on the <link linkend="debug">debug</link> directive.
3398 <![%config-file;[<literallayout>@@#log-messages 1</literallayout>]]>
3404 <emphasis>log-messages 1</emphasis>
3411 <anchor id="log-buffer-size">
3412 <![%config-file;[<para>@@</para>]]> <!-- for spacing -->
3414 If <quote>log-buffer-size</quote> is set to 1, the size of the log buffer,
3415 i.e. the amount of memory used for the log messages displayed in the
3416 console window, will be limited to <quote>log-max-lines</quote> (see below).
3420 Warning: Setting this to 0 will result in the buffer to grow infinitely and
3421 eat up all your memory!
3424 <![%config-file;[<literallayout>@@#log-buffer-size 1</literallayout>]]>
3430 <emphasis>log-buffer-size 1</emphasis>
3437 <anchor id="log-max-lines">
3438 <![%config-file;[<para>@@</para>]]> <!-- for spacing -->
3440 <application>log-max-lines</application> is the maximum number of lines held
3441 in the log buffer. See above.
3444 <![%config-file;[<literallayout>@@#log-max-lines 200</literallayout>]]>
3450 <emphasis>log-max-lines 200</emphasis>
3457 <anchor id="log-highlight-messages">
3458 <![%config-file;[<para>@@</para>]]> <!-- for spacing -->
3460 If <quote>log-highlight-messages</quote> is set to 1,
3461 <application>Privoxy</application> will highlight portions of the log
3462 messages with a bold-faced font:
3465 <![%config-file;[<literallayout>@@#log-highlight-messages 1</literallayout>]]>
3471 <emphasis>log-highlight-messages 1</emphasis>
3478 <anchor id="log-font-name">
3479 <![%config-file;[<para>@@</para>]]> <!-- for spacing -->
3481 The font used in the console window:
3484 <![%config-file;[<literallayout>@@#log-font-name Comic Sans MS</literallayout>]]>
3490 <emphasis>log-font-name Comic Sans MS</emphasis>
3497 <anchor id="log-font-size">
3498 <![%config-file;[<para>@@</para>]]> <!-- for spacing -->
3500 Font size used in the console window:
3503 <![%config-file;[<literallayout>@@#log-font-size 8</literallayout>]]>
3509 <emphasis>log-font-size 8</emphasis>
3516 <anchor id="show-on-task-bar">
3517 <![%config-file;[<para>@@</para>]]> <!-- for spacing -->
3519 <quote>show-on-task-bar</quote> controls whether or not
3520 <application>Privoxy</application> will appear as a button on the Task bar
3524 <![%config-file;[<literallayout>@@#show-on-task-bar 0</literallayout>]]>
3530 <emphasis>show-on-task-bar 0</emphasis>
3537 <anchor id="close-button-minimizes">
3538 <![%config-file;[<para>@@</para>]]> <!-- for spacing -->
3540 If <quote>close-button-minimizes</quote> is set to 1, the Windows close
3541 button will minimize <application>Privoxy</application> instead of closing
3542 the program (close with the exit option on the File menu).
3545 <![%config-file;[<literallayout>@@#close-button-minimizes 1</literallayout>]]>
3551 <emphasis>close-button-minimizes 1</emphasis>
3558 <anchor id="hide-console">
3559 <![%config-file;[<para>@@</para>]]> <!-- for spacing -->
3561 The <quote>hide-console</quote> option is specific to the MS-Win console
3562 version of <application>Privoxy</application>. If this option is used,
3563 <application>Privoxy</application> will disconnect from and hide the
3567 <![%config-file;[<literallayout>@@#hide-console</literallayout>]]>
3573 #<emphasis>hide-console</emphasis>
3583 <!-- end config content common to both outputs -->
3586 <!-- These are dummy anchors to keep the processor quiet -->
3587 <!-- when building config-file only (ie. they are used in u-m only) -->
3590 <anchor id="filter">
3591 <anchor id="filter-file">
3593 <anchor id="actions-file">
3594 <anchor id="af-patterns">
3598 <!-- eof p-config.sgml -->
projects / privoxy.git / blob