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.20 2007/11/07 11:36:53 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.20 2007/11/07 11:36:53 hal9 Exp $
101 Copyright (C) 2001-2007 Privoxy Developers http://www.privoxy.org/
106 #################################################################
111 II. FORMAT OF THE CONFIGURATION FILE #
113 1. LOCAL SET-UP DOCUMENTATION #
114 2. CONFIGURATION AND LOG FILE LOCATIONS #
116 4. ACCESS CONTROL AND SECURITY #
118 6. WINDOWS GUI OPTIONS #
120 #################################################################
124 <literallayout>I. INTRODUCTION
125 =============== <!-- fuck this madness --></literallayout>
128 This file holds Privoxy's main configuration. Privoxy detects
129 configuration changes automatically, so you don't have to restart it
130 unless you want to load a different configuration file.
133 The configuration will be reloaded with the first request after the
134 change was done, this request itself will still use the old configuration,
135 though. In other words: it takes two requests before you see the result of
136 your changes. Requests that are dropped due to ACL don't trigger reloads.
139 When starting Privoxy on Unix systems, give the location of this
140 file as last argument. On Windows systems, Privoxy will look for
141 this file with the name 'config.txt' in the current working directory
142 of the Privoxy process.
146 <literallayout><!-- funky spacing -->
148 II. FORMAT OF THE CONFIGURATION FILE
149 ====================================</literallayout>
152 Configuration lines consist of an initial keyword followed by a list
153 of values, all separated by whitespace (any number of spaces or
157 actionsfile default.action
160 Indicates that the actionsfile is named 'default.action'.
163 The '#' indicates a comment. Any part of a line following a '#' is
164 ignored, except if the '#' is preceded by a '\'.
167 Thus, by placing a # at the start of an existing configuration line,
168 you can make it a comment and it will be treated as if it weren't there.
169 This is called "commenting out" an option and can be useful. Removing
170 the # again is called "uncommenting".
173 Note that commenting out an option and leaving it at its default
174 are two completely different things! Most options behave very
175 differently when unset. See the "Effect if unset" explanation
176 in each option's description for details.
179 Long lines can be continued on the next line by using a `\' as
185 <!-- ************************************************ -->
186 <!-- The following is common to both outputs (mostly) -->
187 <!-- ************************************************ -->
191 <!-- ~~~~~ New section ~~~~~ -->
192 <sect2 id="local-set-up">
193 <title>Local Set-up Documentation</title>
196 If you intend to operate <application>Privoxy</application> for more users
197 than just yourself, it might be a good idea to let them know how to reach
198 you, what you block and why you do that, your policies, etc.
202 <!-- ~~~~~ New section ~~~~~ -->
203 <sect3 renderas="sect4" id="user-manual"><title>user-manual</title>
206 <term>Specifies:</term>
209 Location of the <application>Privoxy</application> User Manual.
214 <term>Type of value:</term>
216 <para>A fully qualified URI</para>
220 <term>Default value:</term>
222 <para><emphasis>Unset</emphasis></para>
226 <term>Effect if unset:</term>
229 <ulink url="http://www.privoxy.org/user-manual/">http://www.privoxy.org/<replaceable class="parameter">version</replaceable>/user-manual/</ulink>
230 will be used, where <replaceable class="parameter">version</replaceable> is the <application>Privoxy</application> version.
238 The User Manual URI is the single best source of information on
239 <application>Privoxy</application>, and is used for help links from some
240 of the internal CGI pages. The manual itself is normally packaged with the
241 binary distributions, so you probably want to set this to a locally
249 Unix, in local filesystem (may not work with all browsers):
252 <screen> user-manual file:///usr/share/doc/privoxy-&p-version;/user-manual/</screen>
255 Windows, in local filesystem, <emphasis>must</emphasis> use forward slash notation:
258 <screen> user-manual file:/c:/some-dir/privoxy-&p-version;/user-manual/</screen>
261 Windows, UNC notation (with forward slashes):
264 <screen> user-manual file://///some-server/some-path/privoxy-&p-version;/user-manual/</screen>
268 The best all purpose solution is simply to put the full local
269 <literal>PATH</literal> to where the <citetitle>User Manual</citetitle> is
273 <screen> user-manual /usr/share/doc/privoxy/user-manual</screen>
276 The User Manual is then available to anyone with access to
277 <application>Privoxy</application>, by following the built-in URL:
278 <literal>http://config.privoxy.org/user-manual/</literal>
279 (or the shortcut: <literal>http://p.p/user-manual/</literal>).
282 If the documentation is not on the local system, it can be accessed
283 from a remote server, as:
286 <screen> user-manual http://example.com/privoxy/user-manual/</screen>
289 <!-- this gets hammered in conversion to config. Text repeated below. -->
292 If set, this option should be <emphasis>the first option in the config
293 file</emphasis>, because it is used while the config file is being read
306 If set, this option should be the first option in the config
307 file, because it is used while the config file is being read.
316 <![%config-file;[<literallayout>@@#user-manual http://www.privoxy.org/user-manual/</literallayout>]]>
320 <!-- ~~~~~ New section ~~~~~ -->
321 <sect3 renderas="sect4" id="trust-info-url"><title>trust-info-url</title>
325 <term>Specifies:</term>
328 A URL to be displayed in the error page that users will see if access to an untrusted page is denied.
333 <term>Type of value:</term>
339 <term>Default value:</term>
341 <para>Two example URLs are provided</para>
345 <term>Effect if unset:</term>
348 No links are displayed on the "untrusted" error page.
356 The value of this option only matters if the experimental trust mechanism has been
357 activated. (See <link linkend="trustfile"><emphasis>trustfile</emphasis></link> above.)
360 If you use the trust mechanism, it is a good idea to write up some on-line
361 documentation about your trust policy and to specify the URL(s) here.
362 Use multiple times for multiple URLs.
365 The URL(s) should be added to the trustfile as well, so users don't end up
366 locked out from the information on why they were locked out in the first place!
372 <![%config-file;[<literallayout>@@trust-info-url http://www.example.com/why_we_block.html</literallayout>]]>
373 <![%config-file;[<literallayout>@@trust-info-url http://www.example.com/what_we_allow.html</literallayout>]]>
377 <!-- ~~~~~ New section ~~~~~ -->
378 <sect3 renderas="sect4" id="admin-address"><title>admin-address</title>
382 <term>Specifies:</term>
385 An email address to reach the <application>Privoxy</application> administrator.
390 <term>Type of value:</term>
392 <para>Email address</para>
396 <term>Default value:</term>
398 <para><emphasis>Unset</emphasis></para>
402 <term>Effect if unset:</term>
405 No email address is displayed on error pages and the CGI user interface.
413 If both <literal>admin-address</literal> and <literal>proxy-info-url</literal>
414 are unset, the whole "Local Privoxy Support" box on all generated pages will
421 <![%config-file;[<literallayout>@@#admin-address privoxy-admin@example.com</literallayout>]]>
425 <!-- ~~~~~ New section ~~~~~ -->
426 <sect3 renderas="sect4" id="proxy-info-url"><title>proxy-info-url</title>
430 <term>Specifies:</term>
433 A URL to documentation about the local <application>Privoxy</application> setup,
434 configuration or policies.
439 <term>Type of value:</term>
445 <term>Default value:</term>
447 <para><emphasis>Unset</emphasis></para>
451 <term>Effect if unset:</term>
454 No link to local documentation is displayed on error pages and the CGI user interface.
462 If both <literal>admin-address</literal> and <literal>proxy-info-url</literal>
463 are unset, the whole "Local Privoxy Support" box on all generated pages will
467 This URL shouldn't be blocked ;-)
473 <![%config-file;[<literallayout>@@#proxy-info-url http://www.example.com/proxy-service.html</literallayout>]]>
477 <!-- ~ End section ~ -->
481 <!-- ~~~~~ New section ~~~~~ -->
483 <sect2 id="conf-log-loc">
484 <title>Configuration and Log File Locations</title>
487 <application>Privoxy</application> can (and normally does) use a number of
488 other files for additional configuration, help and logging.
489 This section of the configuration file tells <application>Privoxy</application>
490 where to find those other files.
494 The user running <application>Privoxy</application>, must have read
495 permission for all configuration files, and write permission to any files
496 that would be modified, such as log files and actions files.
500 <!-- ~~~~~ New section ~~~~~ -->
501 <sect3 renderas="sect4" id="confdir"><title>confdir</title>
505 <term>Specifies:</term>
507 <para>The directory where the other configuration files are located</para>
511 <term>Type of value:</term>
513 <para>Path name</para>
517 <term>Default value:</term>
519 <para>/etc/privoxy (Unix) <emphasis>or</emphasis> <application>Privoxy</application> installation dir (Windows) </para>
523 <term>Effect if unset:</term>
525 <para><emphasis>Mandatory</emphasis></para>
532 No trailing <quote><literal>/</literal></quote>, please
535 This is really outdated and not likely to happen. HB 09/20/06
537 When development goes modular and multi-user, the blocker, filter, and
538 per-user config will be stored in subdirectories of <quote>confdir</quote>.
539 For now, the configuration directory structure is flat, except for
540 <filename>confdir/templates</filename>, where the HTML templates for CGI
541 output reside (e.g. <application>Privoxy's</application> 404 error page).
548 <![%config-file;[<literallayout>@@confdir .</literallayout>]]>
551 <!-- ~~~~~ New section ~~~~~ -->
552 <sect3 renderas="sect4" id="templdir"><title>templdir</title>
556 <term>Specifies:</term>
558 <para>An alternative directory where the templates are loaded from</para>
562 <term>Type of value:</term>
564 <para>Path name</para>
568 <term>Default value:</term>
574 <term>Effect if unset:</term>
576 <para>The templates are assumed to be located in confdir/template.</para>
583 Privoxy's original templates are usually overwritten
584 with each update. Use this option to relocate customized templates
585 that should be kept. Note that template variables might change
586 between updates and templates are not guaranteed to work with
587 <application>Privoxy</application> releases other than the one
594 <![%config-file;[<literallayout>@@#templdir .</literallayout>]]>
598 <!-- ~~~~~ New section ~~~~~ -->
599 <sect3 renderas="sect4" id="logdir"><title>logdir</title>
603 <term>Specifies:</term>
606 The directory where all logging takes place (i.e. where <filename>logfile</filename> and
607 <filename>jarfile</filename> are located)
612 <term>Type of value:</term>
614 <para>Path name</para>
618 <term>Default value:</term>
620 <para>/var/log/privoxy (Unix) <emphasis>or</emphasis> <application>Privoxy</application> installation dir (Windows) </para>
624 <term>Effect if unset:</term>
626 <para><emphasis>Mandatory</emphasis></para>
633 No trailing <quote><literal>/</literal></quote>, please
639 <![%config-file;[<literallayout>@@logdir .</literallayout>]]>
643 <!-- ~~~~~ New section ~~~~~ -->
644 <sect3 renderas="sect4" id="actionsfile"><title>
647 <anchor id="default.action">
648 <anchor id="standard.action">
649 <anchor id="user.action">
650 <!-- Note: slightly modified this section 04/28/02, hal. See NOTE. -->
653 <term>Specifies:</term>
656 The <link linkend="actions-file">actions file(s)</link> to use
661 <term>Type of value:</term>
663 <para>Complete file name, relative to <literal>confdir</literal></para>
667 <term>Default values:</term>
671 <msgtext><literallayout> standard.action # Internal purposes, no editing recommended</literallayout></msgtext>
674 <msgtext><literallayout> default.action # Main actions file</literallayout></msgtext>
677 <msgtext><literallayout> user.action # User customizations</literallayout></msgtext>
683 <term>Effect if unset:</term>
686 No actions are taken at all. More or less neutral proxying.
694 Multiple <literal>actionsfile</literal> lines are permitted, and are in fact recommended!
697 The default values include standard.action, which is used for internal
698 purposes and should be loaded, default.action, which is the
699 <quote>main</quote> actions file maintained by the developers, and
700 <filename>user.action</filename>, where you can make your personal additions.
703 Actions files are where all the per site and per URL configuration is done for
704 ad blocking, cookie management, privacy considerations, etc.
705 There is no point in using <application>Privoxy</application> without at
706 least one actions file.
709 Note that since Privoxy 3.0.7, the complete filename, including the <quote>.action</quote>
710 extension has to be specified. The syntax change was necessary to be consistent
711 with the other file options and to allow previously forbidden characters.
717 <!-- NOTE: alternate markup to make a simpler list doesn't work due to -->
718 <!-- html -> text conversion, blah -->
719 <![%config-file;[<literallayout>@@actionsfile standard.action # Internal purpose, recommended</literallayout>]]>
720 <![%config-file;[<literallayout>@@actionsfile default.action # Main actions file</literallayout>]]>
722 XXX: Like user.filter, user.action should probably be commented out
723 by default as not all packages install it into the default directory.
726 <![%config-file;[<literallayout>@@actionsfile user.action # User customizations</literallayout>]]>
729 <!-- ~~~~~ New section ~~~~~ -->
730 <sect3 renderas="sect4" id="filterfile"><title>filterfile</title>
731 <anchor id="default.filter">
734 <term>Specifies:</term>
737 The <link linkend="filter-file">filter file(s)</link> to use
742 <term>Type of value:</term>
744 <para>File name, relative to <literal>confdir</literal></para>
748 <term>Default value:</term>
750 <para>default.filter (Unix) <emphasis>or</emphasis> default.filter.txt (Windows)</para>
754 <term>Effect if unset:</term>
757 No textual content filtering takes place, i.e. all
758 <literal>+<link linkend="filter">filter</link>{<replaceable class="parameter">name</replaceable>}</literal>
759 actions in the actions files are turned neutral.
767 Multiple <literal>filterfile</literal> lines are permitted.
770 The <link linkend="filter-file">filter files</link> contain content modification
771 rules that use <link linkend="regex">regular expressions</link>. These rules permit
772 powerful changes on the content of Web pages, and optionally the headers
773 as well, e.g., you could try to disable your favorite JavaScript annoyances,
774 re-write the actual displayed text, or just have some fun
775 playing buzzword bingo with web pages.
779 <literal>+<link linkend="filter">filter</link>{<replaceable class="parameter">name</replaceable>}</literal>
780 actions rely on the relevant filter (<replaceable class="parameter">name</replaceable>)
781 to be defined in a filter file!
784 A pre-defined filter file called <filename>default.filter</filename> that contains
785 a number of useful filters for common problems is included in the distribution.
786 See the section on the <literal><link linkend="filter">filter</link></literal>
790 It is recommended to place any locally adapted filters into a separate
791 file, such as <filename>user.filter</filename>.
797 <![%config-file;[<literallayout>@@filterfile default.filter</literallayout>]]>
798 <![%config-file;[<literallayout>@@#filterfile user.filter # User customizations</literallayout>]]>
802 <!-- ~~~~~ New section ~~~~~ -->
803 <sect3 renderas="sect4" id="logfile"><title>logfile</title>
807 <term>Specifies:</term>
815 <term>Type of value:</term>
817 <para>File name, relative to <literal>logdir</literal></para>
821 <term>Default value:</term>
823 <para><emphasis>Unset (commented out)</emphasis>. When activated: logfile (Unix) <emphasis>or</emphasis> privoxy.log (Windows)</para>
827 <term>Effect if unset:</term>
830 Logging is disabled unless <literal>--no-daemon</literal> mode is used.
838 removed per bug report 688728 02/20/03 HB
841 The windows version will additionally log to the console.
845 The logfile is where all logging and error messages are written. The level
846 of detail and number of messages are set with the <literal>debug</literal>
847 option (see below). The logfile can be useful for tracking down a problem with
848 <application>Privoxy</application> (e.g., it's not blocking an ad you
849 think it should block) and it can help you to monitor what your browser
853 Many users will never look at it, however, and it's a privacy risk
854 if third parties can get access to it. It is therefore disabled by
855 default in <application>Privoxy</application> 3.0.7 and later.
858 For troubleshooting purposes, you will have to explicitly enable it.
859 Please don't file any support requests without trying to reproduce
860 the problem with logging enabled first. Once you read the log messages,
861 you may even be able to solve the problem on your own.
864 Your logfile will grow indefinitely, and you will probably want to
865 periodically remove it. On Unix systems, you can do this with a cron job
866 (see <quote>man cron</quote>). For Red Hat based Linux distributions, a
867 <command>logrotate</command> script has been included.
870 No one cares enough about SuSE to build privoxy packages,
871 so most Privoxy users seem to use different platforms and
872 are thus unlikely to care about these instructions.
873 It's also questionable if they still work.
876 On SuSE Linux systems, you can place a line like <quote>/var/log/privoxy.*
877 +1024k 644 nobody.nogroup</quote> in <filename>/etc/logfiles</filename>, with
878 the effect that cron.daily will automatically archive, gzip, and empty the
879 log, when it exceeds 1M size.
883 Any log files must be writable by whatever user <application>Privoxy</application>
884 is being run as (on Unix, default user id is <quote>privoxy</quote>).
890 <![%config-file;[<literallayout>@@#logfile logfile</literallayout>]]>
894 <!-- ~~~~~ New section ~~~~~ -->
895 <sect3 renderas="sect4" id="jarfile"><title>jarfile</title>
899 <term>Specifies:</term>
902 The file to store intercepted cookies in
907 <term>Type of value:</term>
909 <para>File name, relative to <literal>logdir</literal></para>
913 <term>Default value:</term>
915 <para><emphasis>Unset (commented out)</emphasis>. When activated: jarfile (Unix) <emphasis>or</emphasis> privoxy.jar (Windows)</para>
919 <term>Effect if unset:</term>
922 Intercepted cookies are not stored in a dedicated log file.
930 The jarfile may grow to ridiculous sizes over time.
933 If debug 8 (show header parsing) is enabled, cookies are
934 also written to the logfile with the rest of the headers.
935 Therefore this option isn't very useful and may be removed
936 in future releases. Please report to the developers if you
943 <![%config-file;[<literallayout>@@#jarfile jarfile</literallayout>]]>
947 <!-- ~~~~~ New section ~~~~~ -->
948 <sect3 renderas="sect4" id="trustfile"><title>trustfile</title>
951 <term>Specifies:</term>
954 The name of the trust file to use
959 <term>Type of value:</term>
961 <para>File name, relative to <literal>confdir</literal></para>
965 <term>Default value:</term>
967 <para><emphasis>Unset (commented out)</emphasis>. When activated: trust (Unix) <emphasis>or</emphasis> trust.txt (Windows)</para>
971 <term>Effect if unset:</term>
974 The entire trust mechanism is disabled.
982 The trust mechanism is an experimental feature for building white-lists and should
983 be used with care. It is <emphasis>NOT</emphasis> recommended for the casual user.
986 If you specify a trust file, <application>Privoxy</application> will only allow
987 access to sites that are specified in the trustfile. Sites can be listed
991 Prepending a <literal>~</literal> character limits access to this site
992 only (and any sub-paths within this site), e.g.
993 <literal>~www.example.com</literal> allows access to
994 <literal>~www.example.com/features/news.html</literal>, etc.
997 Or, you can designate sites as <emphasis>trusted referrers</emphasis>, by
998 prepending the name with a <literal>+</literal> character. The effect is that
999 access to untrusted sites will be granted -- but only if a link from this
1000 trusted referrer was used to get there. The link target will then be added
1001 to the <quote>trustfile</quote> so that future, direct accesses will be
1002 granted. Sites added via this mechanism do not become trusted referrers
1003 themselves (i.e. they are added with a <literal>~</literal> designation).
1004 There is a limit of 512 such entries, after which new entries will not be
1008 If you use the <literal>+</literal> operator in the trust file, it may grow
1009 considerably over time.
1012 It is recommended that <application>Privoxy</application> be compiled with
1013 the <literal>--disable-force</literal>, <literal>--disable-toggle</literal> and
1014 <literal> --disable-editor</literal> options, if this feature is to be
1018 Possible applications include limiting Internet access for children.
1025 <![%config-file;[<literallayout>@@#trustfile trust</literallayout>]]>
1029 <!-- ~ End section ~ -->
1031 <!-- ~~~~~ New section ~~~~~ -->
1032 <sect2 id="debugging">
1033 <title>Debugging</title>
1036 These options are mainly useful when tracing a problem.
1037 Note that you might also want to invoke
1038 <application>Privoxy</application> with the <literal>--no-daemon</literal>
1039 command line option when debugging.
1042 <sect3 renderas="sect4" id="debug"><title>debug</title>
1046 <term>Specifies:</term>
1049 Key values that determine what information gets logged to the
1050 <link linkend="logfile"><emphasis>logfile</emphasis></link>.
1055 <term>Type of value:</term>
1057 <para>Integer values</para>
1061 <term>Default value:</term>
1063 <para>12289 (i.e.: URLs plus informational and warning messages)</para>
1067 <term>Effect if unset:</term>
1070 Nothing gets logged.
1078 The available debug levels are:
1082 debug 1 # show each GET/POST/CONNECT request
1083 debug 2 # show each connection status
1084 debug 4 # show I/O status
1085 debug 8 # show header parsing
1086 debug 16 # log all data written to the network into the logfile
1087 debug 32 # debug force feature
1088 debug 64 # debug regular expression filters
1089 debug 128 # debug redirects
1090 debug 256 # debug GIF de-animation
1091 debug 512 # Common Log Format
1092 debug 1024 # debug kill pop-ups
1093 debug 2048 # CGI user interface
1094 debug 4096 # Startup banner and warnings.
1095 debug 8192 # Non-fatal errors
1099 To select multiple debug levels, you can either add them or use
1100 multiple <literal>debug</literal> lines.
1103 A debug level of 1 is informative because it will show you each request
1104 as it happens. <emphasis>1, 4096 and 8192 are highly recommended</emphasis>
1105 so that you will notice when things go wrong. The other levels are probably
1106 only of interest if you are hunting down a specific problem. They can produce
1107 a hell of an output (especially 16).
1111 The reporting of <emphasis>fatal</emphasis> errors (i.e. ones which causes
1112 <application>Privoxy</application> to exit) is always on and cannot be disabled.
1115 If you want to use CLF (Common Log Format), you should set <quote>debug
1116 512</quote> <emphasis>ONLY</emphasis> and not enable anything else.
1119 <application>Privoxy</application> has a hard-coded limit for the
1120 length of log messages. If it's reached, messages are logged truncated
1121 and marked with <quote>... [too long, truncated]</quote>.
1127 <![%config-file;[<literallayout>@@debug 1 # show each GET/POST/CONNECT request</literallayout>]]>
1128 <![%config-file;[<literallayout>@@debug 4096 # Startup banner and warnings</literallayout>]]>
1129 <![%config-file;[<literallayout>@@debug 8192 # Errors - *we highly recommended enabling this*</literallayout>]]>
1133 <!-- ~~~~~ New section ~~~~~ -->
1134 <sect3 renderas="sect4" id="single-threaded"><title>single-threaded</title>
1138 <term>Specifies:</term>
1141 Whether to run only one server thread
1146 <term>Type of value:</term>
1148 <para><emphasis>None</emphasis></para>
1152 <term>Default value:</term>
1154 <para><emphasis>Unset</emphasis></para>
1158 <term>Effect if unset:</term>
1161 Multi-threaded (or, where unavailable: forked) operation, i.e. the ability to
1162 serve multiple requests simultaneously.
1170 This option is only there for debugging purposes and you should never
1171 need to use it. <emphasis>It will drastically reduce performance.</emphasis>
1177 <![%config-file;[<literallayout>@@#single-threaded</literallayout>]]>
1182 <!-- ~ End section ~ -->
1185 <!-- ~~~~~ New section ~~~~~ -->
1186 <sect2 id="access-control">
1187 <title>Access Control and Security</title>
1190 This section of the config file controls the security-relevant aspects
1191 of <application>Privoxy</application>'s configuration.
1195 <!-- ~~~~~ New section ~~~~~ -->
1196 <sect3 renderas="sect4" id="listen-address"><title>listen-address</title>
1200 <term>Specifies:</term>
1203 The IP address and TCP port on which <application>Privoxy</application> will
1204 listen for client requests.
1209 <term>Type of value:</term>
1211 <para>[<replaceable class="parameter">IP-Address</replaceable>]:<replaceable class="parameter">Port</replaceable></para>
1216 <term>Default value:</term>
1218 <para>127.0.0.1:8118</para>
1222 <term>Effect if unset:</term>
1225 Bind to 127.0.0.1 (localhost), port 8118. This is suitable and recommended for
1226 home users who run <application>Privoxy</application> on the same machine as
1235 You will need to configure your browser(s) to this proxy address and port.
1238 If you already have another service running on port 8118, or if you want to
1239 serve requests from other machines (e.g. on your local network) as well, you
1240 will need to override the default.
1243 If you leave out the IP address, <application>Privoxy</application> will
1244 bind to all interfaces (addresses) on your machine and may become reachable
1245 from the Internet. In that case, consider using <link
1246 linkend="acls">access control lists</link> (ACL's, see below), and/or
1250 If you open <application>Privoxy</application> to untrusted users, you will
1251 also want to make sure that the following actions are disabled: <literal><link
1252 linkend="enable-edit-actions">enable-edit-actions</link></literal> and
1253 <literal><link linkend="enable-remote-toggle">enable-remote-toggle</link></literal>
1258 <term>Example:</term>
1261 Suppose you are running <application>Privoxy</application> on
1262 a machine which has the address 192.168.0.1 on your local private network
1263 (192.168.0.0) and has another outside connection with a different address.
1264 You want it to serve requests from inside only:
1268 listen-address 192.168.0.1:8118
1275 <![%config-file;[<literallayout>@@listen-address 127.0.0.1:8118</literallayout>]]>
1279 <!-- ~~~~~ New section ~~~~~ -->
1280 <sect3 renderas="sect4" id="toggle"><title>toggle</title>
1284 <term>Specifies:</term>
1287 Initial state of "toggle" status
1292 <term>Type of value:</term>
1298 <term>Default value:</term>
1304 <term>Effect if unset:</term>
1307 Act as if toggled on
1315 If set to 0, <application>Privoxy</application> will start in
1316 <quote>toggled off</quote> mode, i.e. mostly behave like a normal,
1317 content-neutral proxy with both ad blocking and content filtering
1318 disabled. See <literal>enable-remote-toggle</literal> below.
1320 This is not really useful
1321 anymore, since toggling is much easier via <ulink
1322 url="http://config.privoxy.org/toggle">the web interface</ulink> than via
1323 editing the <filename>conf</filename> file.
1325 Remote toggling is now disabled by default. fk 2007-11-07)
1329 The windows version will only display the toggle icon in the system tray
1330 if this option is present.
1336 <![%config-file;[<literallayout>@@toggle 1</literallayout>]]>
1340 <!-- ~~~~~ New section ~~~~~ -->
1341 <sect3 renderas="sect4" id="enable-remote-toggle"><title>enable-remote-toggle</title>
1344 <term>Specifies:</term>
1347 Whether or not the <ulink url="http://config.privoxy.org/toggle">web-based toggle
1348 feature</ulink> may be used
1353 <term>Type of value:</term>
1359 <term>Default value:</term>
1365 <term>Effect if unset:</term>
1368 The web-based toggle feature is disabled.
1376 When toggled off, <application>Privoxy</application> mostly acts like a normal,
1377 content-neutral proxy, i.e. doesn't block ads or filter content.
1380 Access to the toggle feature can <emphasis>not</emphasis> be
1381 controlled separately by <quote>ACLs</quote> or HTTP authentication,
1382 so that everybody who can access <application>Privoxy</application> (see
1383 <quote>ACLs</quote> and <literal>listen-address</literal> above) can
1384 toggle it for all users. So this option is <emphasis>not recommended</emphasis>
1385 for multi-user environments with untrusted users.
1388 Note that malicious client side code (e.g Java) is also
1389 capable of using this option.
1392 As a lot of <application>Privoxy</application> users don't read
1393 documentation, this feature has been disabled by default.
1396 Note that you must have compiled <application>Privoxy</application> with
1397 support for this feature, otherwise this option has no effect.
1403 <![%config-file;[<literallayout>@@enable-remote-toggle 0</literallayout>]]>
1407 <!-- ~~~~~ New section ~~~~~ -->
1408 <sect3 renderas="sect4" id="enable-remote-http-toggle"><title>enable-remote-http-toggle</title>
1411 <term>Specifies:</term>
1414 Whether or not Privoxy recognizes special HTTP headers to change its behaviour.
1419 <term>Type of value:</term>
1425 <term>Default value:</term>
1431 <term>Effect if unset:</term>
1434 Privoxy ignores special HTTP headers.
1442 When toggled on, the client can change <application>Privoxy's</application>
1443 behaviour by setting special HTTP headers. Currently the only supported
1444 special header is <quote>X-Filter: No</quote>, to disable filtering for
1445 the ongoing request, even if it is enabled in one of the action files.
1448 This feature is disabled by default. If you are using
1449 <application>Privoxy</application> in a environment with trusted clients,
1450 you may enable this feature at your discretion. Note that malicious client
1451 side code (e.g Java) is also capable of using this feature.
1454 This option may be removed in future releases as it has been obsoleted
1455 by the more general header taggers.
1461 <![%config-file;[<literallayout>@@enable-remote-http-toggle 0</literallayout>]]>
1465 <!-- ~~~~~ New section ~~~~~ -->
1466 <sect3 renderas="sect4" id="enable-edit-actions"><title>enable-edit-actions</title>
1469 <term>Specifies:</term>
1472 Whether or not the <ulink url="http://config.privoxy.org/show-status">web-based actions
1473 file editor</ulink> may be used
1478 <term>Type of value:</term>
1484 <term>Default value:</term>
1490 <term>Effect if unset:</term>
1493 The web-based actions file editor is disabled.
1501 Access to the editor can <emphasis>not</emphasis> be
1502 controlled separately by <quote>ACLs</quote> or HTTP authentication,
1503 so that everybody who can access <application>Privoxy</application> (see
1504 <quote>ACLs</quote> and <literal>listen-address</literal> above) can
1505 modify its configuration for all users.
1508 This option is <emphasis>not recommended</emphasis> for environments
1509 with untrusted users and is therefore disabled by default.
1512 Note that malicious client side code (e.g Java) is also
1513 capable of using the actions editor and you shouldn't enable
1514 this options unless you understand the consequences and are
1515 sure your browser is configured correctly.
1518 As a lot of <application>Privoxy</application> users don't read
1519 documentation, this feature has been disabled by default.
1522 Note that you must have compiled <application>Privoxy</application> with
1523 support for this feature, otherwise this option has no effect.
1529 <![%config-file;[<literallayout>@@enable-edit-actions 0</literallayout>]]>
1533 <sect3 renderas="sect4" id="enforce-blocks"><title>enforce-blocks</title>
1536 <term>Specifies:</term>
1539 Whether the user is allowed to ignore blocks and can <quote>go there anyway</quote>.
1544 <term>Type of value:</term>
1547 <replaceable>0 or 1</replaceable>
1552 <term>Default value:</term>
1554 <para><emphasis>0</emphasis></para>
1558 <term>Effect if unset:</term>
1561 Blocks are not enforced.
1569 <application>Privoxy</application> is mainly used to block and filter
1570 requests as a service to the user, for example to block ads and other
1571 junk that clogs the pipes. <application>Privoxy's</application> configuration
1572 isn't perfect and sometimes innocent pages are blocked. In this situation it
1573 makes sense to allow the user to enforce the request and have
1574 <application>Privoxy</application> ignore the block.
1577 In the default configuration <application>Privoxy's</application>
1578 <quote>Blocked</quote> page contains a <quote>go there anyway</quote>
1579 link to adds a special string (the force prefix) to the request URL.
1580 If that link is used, <application>Privoxy</application> will
1581 detect the force prefix, remove it again and let the request pass.
1584 Of course <application>Privoxy</application> can also be used to enforce
1585 a network policy. In that case the user obviously should not be able to
1586 bypass any blocks, and that's what the <quote>enforce-blocks</quote>
1587 option is for. If it's enabled, <application>Privoxy</application> hides
1588 the <quote>go there anyway</quote> link. If the user adds the force
1589 prefix by hand, it will not be accepted and the circumvention attempt
1595 <term>Examples:</term>
1603 <![%config-file;[<literallayout>@@enforce-blocks 0</literallayout>]]>
1607 <!-- ~~~~~ New section ~~~~~ -->
1608 <sect3 renderas="sect4" id="acls"><title>
1609 ACLs: permit-access and deny-access</title>
1610 <anchor id="permit-access">
1611 <anchor id="deny-access">
1615 <term>Specifies:</term>
1618 Who can access what.
1623 <term>Type of value:</term>
1626 <replaceable class="parameter">src_addr</replaceable>[/<replaceable class="parameter">src_masklen</replaceable>]
1627 [<replaceable class="parameter">dst_addr</replaceable>[/<replaceable class="parameter">dst_masklen</replaceable>]]
1630 Where <replaceable class="parameter">src_addr</replaceable> and
1631 <replaceable class="parameter">dst_addr</replaceable> are IP addresses in dotted decimal notation or valid
1632 DNS names, and <replaceable class="parameter">src_masklen</replaceable> and
1633 <replaceable class="parameter">dst_masklen</replaceable> are subnet masks in CIDR notation, i.e. integer
1634 values from 2 to 30 representing the length (in bits) of the network address. The masks and the whole
1635 destination part are optional.
1640 <term>Default value:</term>
1642 <para><emphasis>Unset</emphasis></para>
1646 <term>Effect if unset:</term>
1649 Don't restrict access further than implied by <literal>listen-address</literal>
1657 Access controls are included at the request of ISPs and systems
1658 administrators, and <emphasis>are not usually needed by individual users</emphasis>.
1659 For a typical home user, it will normally suffice to ensure that
1660 <application>Privoxy</application> only listens on the localhost
1661 (127.0.0.1) or internal (home) network address by means of the
1662 <link linkend="listen-address"><emphasis>listen-address</emphasis></link>
1666 Please see the warnings in the FAQ that this proxy is not intended to be a substitute
1667 for a firewall or to encourage anyone to defer addressing basic security
1671 Multiple ACL lines are OK.
1672 If any ACLs are specified, <application>Privoxy</application> only talks
1673 to IP addresses that match at least one <literal>permit-access</literal> line
1674 and don't match any subsequent <literal>deny-access</literal> line. In other words, the
1675 last match wins, with the default being <literal>deny-access</literal>.
1678 If <application>Privoxy</application> is using a forwarder (see <literal>forward</literal> below)
1679 for a particular destination URL, the <replaceable class="parameter">dst_addr</replaceable>
1680 that is examined is the address of the forwarder and <emphasis>NOT</emphasis> the address
1681 of the ultimate target. This is necessary because it may be impossible for the local
1682 <application>Privoxy</application> to determine the IP address of the
1683 ultimate target (that's often what gateways are used for).
1686 You should prefer using IP addresses over DNS names, because the address lookups take
1687 time. All DNS names must resolve! You can <emphasis>not</emphasis> use domain patterns
1688 like <quote>*.org</quote> or partial domain names. If a DNS name resolves to multiple
1689 IP addresses, only the first one is used.
1692 Denying access to particular sites by ACL may have undesired side effects
1693 if the site in question is hosted on a machine which also hosts other sites
1699 <term>Examples:</term>
1702 Explicitly define the default behavior if no ACL and
1703 <literal>listen-address</literal> are set: <quote>localhost</quote>
1704 is OK. The absence of a <replaceable class="parameter">dst_addr</replaceable> implies that
1705 <emphasis>all</emphasis> destination addresses are OK:
1709 permit-access localhost
1713 Allow any host on the same class C subnet as www.privoxy.org access to
1714 nothing but www.example.com (or other domains hosted on the same system):
1718 permit-access www.privoxy.org/24 www.example.com/32
1722 Allow access from any host on the 26-bit subnet 192.168.45.64 to anywhere,
1723 with the exception that 192.168.45.73 may not access the IP address behind
1724 www.dirty-stuff.example.com:
1728 permit-access 192.168.45.64/26
1729 deny-access 192.168.45.73 www.dirty-stuff.example.com
1738 <!-- ~~~~~ New section ~~~~~ -->
1739 <sect3 renderas="sect4" id="buffer-limit"><title>buffer-limit</title>
1743 <term>Specifies:</term>
1746 Maximum size of the buffer for content filtering.
1751 <term>Type of value:</term>
1753 <para>Size in Kbytes</para>
1757 <term>Default value:</term>
1763 <term>Effect if unset:</term>
1766 Use a 4MB (4096 KB) limit.
1774 For content filtering, i.e. the <literal>+filter</literal> and
1775 <literal>+deanimate-gif</literal> actions, it is necessary that
1776 <application>Privoxy</application> buffers the entire document body.
1777 This can be potentially dangerous, since a server could just keep sending
1778 data indefinitely and wait for your RAM to exhaust -- with nasty consequences.
1782 When a document buffer size reaches the <literal>buffer-limit</literal>, it is
1783 flushed to the client unfiltered and no further attempt to
1784 filter the rest of the document is made. Remember that there may be multiple threads
1785 running, which might require up to <literal>buffer-limit</literal> Kbytes
1786 <emphasis>each</emphasis>, unless you have enabled <quote>single-threaded</quote>
1793 <![%config-file;[<literallayout>@@buffer-limit 4096</literallayout>]]>
1798 <!-- ~ End section ~ -->
1801 <!-- ~~~~~ New section ~~~~~ -->
1803 <sect2 id="forwarding">
1804 <title>Forwarding</title>
1807 This feature allows routing of HTTP requests through a chain of
1811 Forwarding can be used to chain Privoxy with a caching proxy to speed
1812 up browsing. Using a parent proxy may also be necessary if the machine
1813 that <application>Privoxy</application> runs on has no direct Internet access.
1816 Note that parent proxies can severely decrease your privacy level.
1817 For example a parent proxy could add your IP address to the request
1818 headers and if it's a caching proxy it may add the <quote>Etag</quote>
1819 header to revalidation requests again, even though you configured Privoxy
1820 to remove it. It may also ignore Privoxy's header time randomization and use the
1821 original values which could be used by the server as cookie replacement
1822 to track your steps between visits.
1826 Also specified here are SOCKS proxies. <application>Privoxy</application>
1827 supports the SOCKS 4 and SOCKS 4A protocols.
1830 <sect3 renderas="sect4" id="forward"><title>forward</title>
1833 <term>Specifies:</term>
1836 To which parent HTTP proxy specific requests should be routed.
1841 <term>Type of value:</term>
1844 <replaceable class="parameter">target_pattern</replaceable>
1845 <replaceable class="parameter">http_parent</replaceable>[:<replaceable class="parameter">port</replaceable>]
1848 where <replaceable class="parameter">target_pattern</replaceable> is a <link linkend="af-patterns">URL pattern</link>
1849 that specifies to which requests (i.e. URLs) this forward rule shall apply. Use <literal>/</literal> to
1850 denote <quote>all URLs</quote>.
1851 <replaceable class="parameter">http_parent</replaceable>[:<replaceable class="parameter">port</replaceable>]
1852 is the DNS name or IP address of the parent HTTP proxy through which the requests should be forwarded,
1853 optionally followed by its listening port (default: 8080).
1854 Use a single dot (<literal>.</literal>) to denote <quote>no forwarding</quote>.
1859 <term>Default value:</term>
1861 <para><emphasis>Unset</emphasis></para>
1865 <term>Effect if unset:</term>
1868 Don't use parent HTTP proxies.
1876 If <replaceable class="parameter">http_parent</replaceable> is <quote>.</quote>, then requests are not
1877 forwarded to another HTTP proxy but are made directly to the web servers.
1880 Multiple lines are OK, they are checked in sequence, and the last match wins.
1885 <term>Examples:</term>
1888 Everything goes to an example parent proxy, except SSL on port 443 (which it doesn't handle):
1892 forward / parent-proxy.example.org:8080
1897 Everything goes to our example ISP's caching proxy, except for requests
1898 to that ISP's sites:
1902 forward / caching-proxy.example-isp.net:8000
1903 forward .example-isp.net .
1912 <!-- ~~~~~ New section ~~~~~ -->
1913 <sect3 renderas="sect4" id="socks"><title>
1914 forward-socks4 and forward-socks4a</title>
1915 <anchor id="forward-socks4">
1916 <anchor id="forward-socks4a">
1920 <term>Specifies:</term>
1923 Through which SOCKS proxy (and optionally to which parent HTTP proxy) specific requests should be routed.
1928 <term>Type of value:</term>
1931 <replaceable class="parameter">target_pattern</replaceable>
1932 <replaceable class="parameter">socks_proxy</replaceable>[:<replaceable class="parameter">port</replaceable>]
1933 <replaceable class="parameter">http_parent</replaceable>[:<replaceable class="parameter">port</replaceable>]
1936 where <replaceable class="parameter">target_pattern</replaceable> is a <link linkend="af-patterns">URL pattern</link>
1937 that specifies to which requests (i.e. URLs) this forward rule shall apply. Use <literal>/</literal> to
1938 denote <quote>all URLs</quote>.
1939 <replaceable class="parameter">http_parent</replaceable> and <replaceable class="parameter">socks_proxy</replaceable>
1940 are IP addresses in dotted decimal notation or valid DNS names (<replaceable class="parameter">http_parent</replaceable>
1941 may be <quote>.</quote> to denote <quote>no HTTP forwarding</quote>), and the optional
1942 <replaceable class="parameter">port</replaceable> parameters are TCP ports, i.e. integer values from 1 to 64535
1947 <term>Default value:</term>
1949 <para><emphasis>Unset</emphasis></para>
1953 <term>Effect if unset:</term>
1956 Don't use SOCKS proxies.
1964 Multiple lines are OK, they are checked in sequence, and the last match wins.
1967 The difference between <literal>forward-socks4</literal> and <literal>forward-socks4a</literal>
1968 is that in the SOCKS 4A protocol, the DNS resolution of the target hostname happens on the SOCKS
1969 server, while in SOCKS 4 it happens locally.
1972 If <replaceable class="parameter">http_parent</replaceable> is <quote>.</quote>, then requests are not
1973 forwarded to another HTTP proxy but are made (HTTP-wise) directly to the web servers, albeit through
1979 <term>Examples:</term>
1982 From the company example.com, direct connections are made to all
1983 <quote>internal</quote> domains, but everything outbound goes through
1984 their ISP's proxy by way of example.com's corporate SOCKS 4A gateway to
1989 forward-socks4a / socks-gw.example.com:1080 www-cache.example-isp.net:8080
1990 forward .example.com .
1994 A rule that uses a SOCKS 4 gateway for all destinations but no HTTP parent looks like this:
1998 forward-socks4 / socks-gw.example.com:1080 .
2003 To chain Privoxy and Tor, both running on the same system, you should use
2008 forward-socks4a / 127.0.0.1:9050 .
2013 The public <application>Tor</application> network can't be used to
2014 reach your local network, if you need to access local servers you
2015 therefore might want to make some exceptions:
2019 forward 192.168.*.*/ .
2021 forward 127.*.*.*/ .
2025 Unencrypted connections to systems in these address ranges will
2026 be as (un)secure as the local network is, but the alternative is that you
2027 can't reach the local network through <application>Privoxy</application>
2031 If you also want to be able to reach servers in your local network by
2032 using their names, you will need additional exceptions that look like
2037 forward localhost/ .
2046 <![%user-man;[ <!-- not included in config due to length -->
2047 <!-- ~~~~~ New section ~~~~~ -->
2048 <sect3 renderas="sect4" id="advanced-forwarding-examples"><title>Advanced Forwarding Examples</title>
2051 If you have links to multiple ISPs that provide various special content
2052 only to their subscribers, you can configure multiple <application>Privoxies</application>
2053 which have connections to the respective ISPs to act as forwarders to each other, so that
2054 <emphasis>your</emphasis> users can see the internal content of all ISPs.
2058 Assume that host-a has a PPP connection to isp-a.net. And host-b has a PPP connection to
2059 isp-b.net. Both run <application>Privoxy</application>. Their forwarding
2060 configuration can look like this:
2070 forward .isp-b.net host-b:8118
2081 forward .isp-a.net host-a:8118
2086 Now, your users can set their browser's proxy to use either
2087 host-a or host-b and be able to browse the internal content
2088 of both isp-a and isp-b.
2092 If you intend to chain <application>Privoxy</application> and
2093 <application>squid</application> locally, then chain as
2094 <literal>browser -> squid -> privoxy</literal> is the recommended way.
2098 Assuming that <application>Privoxy</application> and <application>squid</application>
2099 run on the same box, your <application>squid</application> configuration could then look like this:
2104 # Define Privoxy as parent proxy (without ICP)
2105 cache_peer 127.0.0.1 parent 8118 7 no-query
2107 # Define ACL for protocol FTP
2110 # Do not forward FTP requests to Privoxy
2111 always_direct allow ftp
2113 # Forward all the rest to Privoxy
2114 never_direct allow all</screen>
2118 You would then need to change your browser's proxy settings to <application>squid</application>'s address and port.
2119 Squid normally uses port 3128. If unsure consult <literal>http_port</literal> in <filename>squid.conf</filename>.
2123 You could just as well decide to only forward requests for Windows executables through
2124 a virus-scanning parent proxy, say, on <literal>antivir.example.com</literal>, port 8010:
2130 forward /.*\.(exe|com|dll|zip)$ antivir.example.com:8010</screen>
2136 <sect3 renderas="sect4" id="forwarded-connect-retries"><title>forwarded-connect-retries</title>
2139 <term>Specifies:</term>
2142 How often Privoxy retries if a forwarded connection request fails.
2147 <term>Type of value:</term>
2150 <replaceable class="parameter">Number of retries.</replaceable>
2155 <term>Default value:</term>
2157 <para><emphasis>0</emphasis></para>
2161 <term>Effect if unset:</term>
2164 Connections forwarded through other proxies are treated like direct connections and no retry attempts are made.
2172 <replaceable class="parameter">forwarded-connect-retries</replaceable> is mainly interesting
2173 for socks4a connections, where <application>Privoxy</application> can't detect why the connections failed.
2174 The connection might have failed because of a DNS timeout in which case a retry makes sense,
2175 but it might also have failed because the server doesn't exist or isn't reachable. In this
2176 case the retry will just delay the appearance of Privoxy's error message.
2179 Note that in the context of this option, <quote>forwarded connections</quote> includes all connections
2180 that Privoxy forwards through other proxies. This option is not limited to the HTTP CONNECT method.
2183 Only use this option, if you are getting lots of forwarding-related error messages
2184 that go away when you try again manually. Start with a small value and check Privoxy's
2185 logfile from time to time, to see how many retries are usually needed.
2190 <term>Examples:</term>
2193 forwarded-connect-retries 1
2198 <![%config-file;[<literallayout>@@forwarded-connect-retries 0</literallayout>]]>
2201 <sect3 renderas="sect4" id="accept-intercepted-requests"><title>accept-intercepted-requests</title>
2204 <term>Specifies:</term>
2207 Whether intercepted requests should be treated as valid.
2212 <term>Type of value:</term>
2215 <replaceable>0 or 1</replaceable>
2220 <term>Default value:</term>
2222 <para><emphasis>0</emphasis></para>
2226 <term>Effect if unset:</term>
2229 Only proxy requests are accepted, intercepted requests are treated as invalid.
2237 If you don't trust your clients and want to force them
2238 to use <application>Privoxy</application>, enable this
2239 option and configure your packet filter to redirect outgoing
2240 HTTP connections into <application>Privoxy</application>.
2243 Make sure that <application>Privoxy's</application> own requests
2244 aren't redirected as well. Additionally take care that
2245 <application>Privoxy</application> can't intentionally connect
2246 to itself, otherwise you could run into redirection loops if
2247 <application>Privoxy's</application> listening port is reachable
2248 by the outside or an attacker has access to the pages you visit.
2253 <term>Examples:</term>
2256 accept-intercepted-requests 1
2261 <![%config-file;[<literallayout>@@accept-intercepted-requests 0</literallayout>]]>
2264 <sect3 renderas="sect4" id="allow-cgi-request-crunching"><title>allow-cgi-request-crunching</title>
2267 <term>Specifies:</term>
2270 Whether requests to <application>Privoxy's</application> CGI pages can be blocked or redirected.
2275 <term>Type of value:</term>
2278 <replaceable>0 or 1</replaceable>
2283 <term>Default value:</term>
2285 <para><emphasis>0</emphasis></para>
2289 <term>Effect if unset:</term>
2292 <application>Privoxy</application> ignores block and redirect actions for its CGI pages.
2300 By default <application>Privoxy</application> ignores block or redirect actions
2301 for its CGI pages. Intercepting these requests can be useful in multi-user
2302 setups to implement fine-grained access control, but it can also render the complete
2303 web interface useless and make debugging problems painful if done without care.
2306 Don't enable this option unless you're sure that you really need it.
2311 <term>Examples:</term>
2314 allow-cgi-request-crunching 1
2319 <![%config-file;[<literallayout>@@allow-cgi-request-crunching 0</literallayout>]]>
2322 <sect3 renderas="sect4" id="split-large-forms"><title>split-large-forms</title>
2325 <term>Specifies:</term>
2328 Whether the CGI interface should stay compatible with broken HTTP clients.
2333 <term>Type of value:</term>
2336 <replaceable>0 or 1</replaceable>
2341 <term>Default value:</term>
2343 <para><emphasis>0</emphasis></para>
2347 <term>Effect if unset:</term>
2350 The CGI form generate long GET URLs.
2358 <application>Privoxy's</application> CGI forms can lead to
2359 rather long URLs. This isn't a problem as far as the HTTP
2360 standard is concerned, but it can confuse clients with arbitrary
2361 URL lenght limitations.
2364 Enabling split-large-forms causes <application>Privoxy</application>
2365 to devide big forms into smaller ones to keep the URL length down.
2366 It makes editing a lot less convenient and you can no longer
2367 submit all changes at once, but at least it works around this
2371 If you don't notice any editing problems, there is no reason
2372 to enable this option, but if one of the submit buttons appears
2373 to be broken, you should give it a try.
2378 <term>Examples:</term>
2386 <![%config-file;[<literallayout>@@split-large-forms 0</literallayout>]]>
2391 <!-- ~ End section ~ -->
2394 <!-- ~~~~~ New section ~~~~~ -->
2396 <sect2 id="windows-gui">
2397 <title>Windows GUI Options</title>
2399 <application>Privoxy</application> has a number of options specific to the
2400 Windows GUI interface:
2403 <anchor id="activity-animation">
2404 <![%config-file;[<para>@@</para>]]> <!-- for spacing -->
2406 If <quote>activity-animation</quote> is set to 1, the
2407 <application>Privoxy</application> icon will animate when
2408 <quote>Privoxy</quote> is active. To turn off, set to 0.
2411 <![%config-file;[<literallayout>@@#activity-animation 1</literallayout>]]>
2417 <emphasis>activity-animation 1</emphasis>
2424 <anchor id="log-messages">
2425 <![%config-file;[<para>@@</para>]]> <!-- for spacing -->
2427 If <quote>log-messages</quote> is set to 1,
2428 <application>Privoxy</application> will log messages to the console
2432 <![%config-file;[<literallayout>@@#log-messages 1</literallayout>]]>
2438 <emphasis>log-messages 1</emphasis>
2445 <anchor id="log-buffer-size">
2446 <![%config-file;[<para>@@</para>]]> <!-- for spacing -->
2448 If <quote>log-buffer-size</quote> is set to 1, the size of the log buffer,
2449 i.e. the amount of memory used for the log messages displayed in the
2450 console window, will be limited to <quote>log-max-lines</quote> (see below).
2454 Warning: Setting this to 0 will result in the buffer to grow infinitely and
2455 eat up all your memory!
2458 <![%config-file;[<literallayout>@@#log-buffer-size 1</literallayout>]]>
2464 <emphasis>log-buffer-size 1</emphasis>
2471 <anchor id="log-max-lines">
2472 <![%config-file;[<para>@@</para>]]> <!-- for spacing -->
2474 <application>log-max-lines</application> is the maximum number of lines held
2475 in the log buffer. See above.
2478 <![%config-file;[<literallayout>@@#log-max-lines 200</literallayout>]]>
2484 <emphasis>log-max-lines 200</emphasis>
2491 <anchor id="log-highlight-messages">
2492 <![%config-file;[<para>@@</para>]]> <!-- for spacing -->
2494 If <quote>log-highlight-messages</quote> is set to 1,
2495 <application>Privoxy</application> will highlight portions of the log
2496 messages with a bold-faced font:
2499 <![%config-file;[<literallayout>@@#log-highlight-messages 1</literallayout>]]>
2505 <emphasis>log-highlight-messages 1</emphasis>
2512 <anchor id="log-font-name">
2513 <![%config-file;[<para>@@</para>]]> <!-- for spacing -->
2515 The font used in the console window:
2518 <![%config-file;[<literallayout>@@#log-font-name Comic Sans MS</literallayout>]]>
2524 <emphasis>log-font-name Comic Sans MS</emphasis>
2531 <anchor id="log-font-size">
2532 <![%config-file;[<para>@@</para>]]> <!-- for spacing -->
2534 Font size used in the console window:
2537 <![%config-file;[<literallayout>@@#log-font-size 8</literallayout>]]>
2543 <emphasis>log-font-size 8</emphasis>
2550 <anchor id="show-on-task-bar">
2551 <![%config-file;[<para>@@</para>]]> <!-- for spacing -->
2553 <quote>show-on-task-bar</quote> controls whether or not
2554 <application>Privoxy</application> will appear as a button on the Task bar
2558 <![%config-file;[<literallayout>@@#show-on-task-bar 0</literallayout>]]>
2564 <emphasis>show-on-task-bar 0</emphasis>
2571 <anchor id="close-button-minimizes">
2572 <![%config-file;[<para>@@</para>]]> <!-- for spacing -->
2574 If <quote>close-button-minimizes</quote> is set to 1, the Windows close
2575 button will minimize <application>Privoxy</application> instead of closing
2576 the program (close with the exit option on the File menu).
2579 <![%config-file;[<literallayout>@@#close-button-minimizes 1</literallayout>]]>
2585 <emphasis>close-button-minimizes 1</emphasis>
2592 <anchor id="hide-console">
2593 <![%config-file;[<para>@@</para>]]> <!-- for spacing -->
2595 The <quote>hide-console</quote> option is specific to the MS-Win console
2596 version of <application>Privoxy</application>. If this option is used,
2597 <application>Privoxy</application> will disconnect from and hide the
2601 <![%config-file;[<literallayout>@@#hide-console</literallayout>]]>
2607 #<emphasis>hide-console</emphasis>
2617 <!-- end config content common to both outputs -->
2620 <!-- These are dummy anchors to keep the processor quiet -->
2621 <!-- when building config-file only (ie. they are used in u-m only) -->
2624 <anchor id="filter">
2625 <anchor id="filter-file">
2627 <anchor id="actions-file">
2628 <anchor id="af-patterns">
2632 <!-- eof p-config.sgml -->