1 # Sample Configuration File for Privoxy 3.0.21
3 # $Id: config,v 1.103 2013/03/02 14:47:05 fabiankeil Exp $
5 # Copyright (C) 2001-2013 Privoxy Developers http://www.privoxy.org/
7 ####################################################################
12 # II. FORMAT OF THE CONFIGURATION FILE #
14 # 1. LOCAL SET-UP DOCUMENTATION #
15 # 2. CONFIGURATION AND LOG FILE LOCATIONS #
17 # 4. ACCESS CONTROL AND SECURITY #
20 # 7. WINDOWS GUI OPTIONS #
22 ####################################################################
28 # This file holds Privoxy's main configuration. Privoxy detects
29 # configuration changes automatically, so you don't have to restart
30 # it unless you want to load a different configuration file.
32 # The configuration will be reloaded with the first request after
33 # the change was done, this request itself will still use the old
34 # configuration, though. In other words: it takes two requests
35 # before you see the result of your changes. Requests that are
36 # dropped due to ACL don't trigger reloads.
38 # When starting Privoxy on Unix systems, give the location of this
39 # file as last argument. On Windows systems, Privoxy will look for
40 # this file with the name 'config.txt' in the current working
41 # directory of the Privoxy process.
44 # II. FORMAT OF THE CONFIGURATION FILE
45 # ====================================
47 # Configuration lines consist of an initial keyword followed by a
48 # list of values, all separated by whitespace (any number of spaces
49 # or tabs). For example,
51 # actionsfile default.action
53 # Indicates that the actionsfile is named 'default.action'.
55 # The '#' indicates a comment. Any part of a line following a '#' is
56 # ignored, except if the '#' is preceded by a '\'.
58 # Thus, by placing a # at the start of an existing configuration
59 # line, you can make it a comment and it will be treated as if it
60 # weren't there. This is called "commenting out" an option and can
61 # be useful. Removing the # again is called "uncommenting".
63 # Note that commenting out an option and leaving it at its default
64 # are two completely different things! Most options behave very
65 # differently when unset. See the "Effect if unset" explanation in
66 # each option's description for details.
68 # Long lines can be continued on the next line by using a `\' as the
72 # 1. LOCAL SET-UP DOCUMENTATION
73 # ==============================
75 # If you intend to operate Privoxy for more users than just
76 # yourself, it might be a good idea to let them know how to reach
77 # you, what you block and why you do that, your policies, etc.
85 # Location of the Privoxy User Manual.
89 # A fully qualified URI
97 # http://www.privoxy.org/version/user-manual/ will be used,
98 # where version is the Privoxy version.
102 # The User Manual URI is the single best source of information
103 # on Privoxy, and is used for help links from some of the
104 # internal CGI pages. The manual itself is normally packaged
105 # with the binary distributions, so you probably want to set
106 # this to a locally installed copy.
110 # The best all purpose solution is simply to put the full local
111 # PATH to where the User Manual is located:
113 # user-manual /usr/share/doc/privoxy/user-manual
115 # The User Manual is then available to anyone with access to
116 # Privoxy, by following the built-in URL: http://
117 # config.privoxy.org/user-manual/ (or the shortcut: http://p.p/
120 # If the documentation is not on the local system, it can be
121 # accessed from a remote server, as:
123 # user-manual http://example.com/privoxy/user-manual/
127 # If set, this option should be the first option in the
128 # config file, because it is used while the config file is
131 #user-manual http://www.privoxy.org/user-manual/
133 # 1.2. trust-info-url
134 # ====================
138 # A URL to be displayed in the error page that users will see if
139 # access to an untrusted page is denied.
151 # No links are displayed on the "untrusted" error page.
155 # The value of this option only matters if the experimental
156 # trust mechanism has been activated. (See trustfile below.)
158 # If you use the trust mechanism, it is a good idea to write up
159 # some on-line documentation about your trust policy and to
160 # specify the URL(s) here. Use multiple times for multiple URLs.
162 # The URL(s) should be added to the trustfile as well, so users
163 # don't end up locked out from the information on why they were
164 # locked out in the first place!
166 #trust-info-url http://www.example.com/why_we_block.html
167 #trust-info-url http://www.example.com/what_we_allow.html
170 # ===================
174 # An email address to reach the Privoxy administrator.
186 # No email address is displayed on error pages and the CGI user
191 # If both admin-address and proxy-info-url are unset, the whole
192 # "Local Privoxy Support" box on all generated pages will not be
195 #admin-address privoxy-admin@example.com
197 # 1.4. proxy-info-url
198 # ====================
202 # A URL to documentation about the local Privoxy setup,
203 # configuration or policies.
215 # No link to local documentation is displayed on error pages and
216 # the CGI user interface.
220 # If both admin-address and proxy-info-url are unset, the whole
221 # "Local Privoxy Support" box on all generated pages will not be
224 # This URL shouldn't be blocked ;-)
226 #proxy-info-url http://www.example.com/proxy-service.html
228 # 2. CONFIGURATION AND LOG FILE LOCATIONS
229 # ========================================
231 # Privoxy can (and normally does) use a number of other files for
232 # additional configuration, help and logging. This section of the
233 # configuration file tells Privoxy where to find those other files.
235 # The user running Privoxy, must have read permission for all
236 # configuration files, and write permission to any files that would
237 # be modified, such as log files and actions files.
245 # The directory where the other configuration files are located.
253 # /etc/privoxy (Unix) or Privoxy installation dir (Windows)
261 # No trailing "/", please.
270 # An alternative directory where the templates are loaded from.
282 # The templates are assumed to be located in confdir/template.
286 # Privoxy's original templates are usually overwritten with each
287 # update. Use this option to relocate customized templates that
288 # should be kept. As template variables might change between
289 # updates, you shouldn't expect templates to work with Privoxy
290 # releases other than the one they were part of, though.
299 # The directory where all logging takes place (i.e. where the
300 # logfile is located).
308 # /var/log/privoxy (Unix) or Privoxy installation dir (Windows)
316 # No trailing "/", please.
325 # The actions file(s) to use
329 # Complete file name, relative to confdir
333 # match-all.action # Actions that are applied to all sites and maybe overruled later on.
335 # default.action # Main actions file
337 # user.action # User customizations
341 # No actions are taken at all. More or less neutral proxying.
345 # Multiple actionsfile lines are permitted, and are in fact
348 # The default values are default.action, which is the "main"
349 # actions file maintained by the developers, and user.action,
350 # where you can make your personal additions.
352 # Actions files contain all the per site and per URL
353 # configuration for ad blocking, cookie management, privacy
354 # considerations, etc. There is no point in using Privoxy
355 # without at least one actions file.
357 # Note that since Privoxy 3.0.7, the complete filename,
358 # including the ".action" extension has to be specified. The
359 # syntax change was necessary to be consistent with the other
360 # file options and to allow previously forbidden characters.
362 actionsfile match-all.action # Actions that are applied to all sites and maybe overruled later on.
363 actionsfile default.action # Main actions file
364 actionsfile user.action # User customizations
371 # The filter file(s) to use
375 # File name, relative to confdir
379 # default.filter (Unix) or default.filter.txt (Windows)
383 # No textual content filtering takes place, i.e. all +filter{name}
384 # actions in the actions files are turned neutral.
388 # Multiple filterfile lines are permitted.
390 # The filter files contain content modification rules that use
391 # regular expressions. These rules permit powerful changes on
392 # the content of Web pages, and optionally the headers as well,
393 # e.g., you could try to disable your favorite JavaScript
394 # annoyances, re-write the actual displayed text, or just have
395 # some fun playing buzzword bingo with web pages.
397 # The +filter{name} actions rely on the relevant filter (name)
398 # to be defined in a filter file!
400 # A pre-defined filter file called default.filter that contains
401 # a number of useful filters for common problems is included in
402 # the distribution. See the section on the filter action for a
405 # It is recommended to place any locally adapted filters into a
406 # separate file, such as user.filter.
408 filterfile default.filter
409 filterfile user.filter # User customizations
416 # The log file to use
420 # File name, relative to logdir
424 # Unset (commented out). When activated: logfile (Unix) or
425 # privoxy.log (Windows).
429 # No logfile is written.
433 # The logfile is where all logging and error messages are
434 # written. The level of detail and number of messages are set
435 # with the debug option (see below). The logfile can be useful
436 # for tracking down a problem with Privoxy (e.g., it's not
437 # blocking an ad you think it should block) and it can help you
438 # to monitor what your browser is doing.
440 # Depending on the debug options below, the logfile may be a
441 # privacy risk if third parties can get access to it. As most
442 # users will never look at it, Privoxy 3.0.7 and later only log
443 # fatal errors by default.
445 # For most troubleshooting purposes, you will have to change
446 # that, please refer to the debugging section for details.
448 # Your logfile will grow indefinitely, and you will probably
449 # want to periodically remove it. On Unix systems, you can do
450 # this with a cron job (see "man cron").
452 # Any log files must be writable by whatever user Privoxy is
453 # being run as (on Unix, default user id is "privoxy").
462 # The name of the trust file to use
466 # File name, relative to confdir
470 # Unset (commented out). When activated: trust (Unix) or
471 # trust.txt (Windows)
475 # The entire trust mechanism is disabled.
479 # The trust mechanism is an experimental feature for building
480 # white-lists and should be used with care. It is NOT
481 # recommended for the casual user.
483 # If you specify a trust file, Privoxy will only allow access to
484 # sites that are specified in the trustfile. Sites can be listed
485 # in one of two ways:
487 # Prepending a ~ character limits access to this site only (and
488 # any sub-paths within this site), e.g. ~www.example.com allows
489 # access to ~www.example.com/features/news.html, etc.
491 # Or, you can designate sites as trusted referrers, by
492 # prepending the name with a + character. The effect is that
493 # access to untrusted sites will be granted -- but only if a
494 # link from this trusted referrer was used to get there. The
495 # link target will then be added to the "trustfile" so that
496 # future, direct accesses will be granted. Sites added via this
497 # mechanism do not become trusted referrers themselves (i.e.
498 # they are added with a ~ designation). There is a limit of 512
499 # such entries, after which new entries will not be made.
501 # If you use the + operator in the trust file, it may grow
502 # considerably over time.
504 # It is recommended that Privoxy be compiled with the
505 # --disable-force, --disable-toggle and --disable-editor
506 # options, if this feature is to be used.
508 # Possible applications include limiting Internet access for
516 # These options are mainly useful when tracing a problem. Note that
517 # you might also want to invoke Privoxy with the --no-daemon command
518 # line option when debugging.
526 # Key values that determine what information gets logged.
534 # 0 (i.e.: only fatal errors (that cause Privoxy to exit) are
539 # Default value is used (see above).
543 # The available debug levels are:
545 # debug 1 # Log the destination for each request Privoxy let through. See also debug 1024.
546 # debug 2 # show each connection status
547 # debug 4 # show I/O status
548 # debug 8 # show header parsing
549 # debug 16 # log all data written to the network
550 # debug 32 # debug force feature
551 # debug 64 # debug regular expression filters
552 # debug 128 # debug redirects
553 # debug 256 # debug GIF de-animation
554 # debug 512 # Common Log Format
555 # debug 1024 # Log the destination for requests Privoxy didn't let through, and the reason why.
556 # debug 2048 # CGI user interface
557 # debug 4096 # Startup banner and warnings.
558 # debug 8192 # Non-fatal errors
559 # debug 32768 # log all data read from the network
560 # debug 65536 # Log the applying actions
562 # To select multiple debug levels, you can either add them or
563 # use multiple debug lines.
565 # A debug level of 1 is informative because it will show you
566 # each request as it happens. 1, 1024, 4096 and 8192 are
567 # recommended so that you will notice when things go wrong. The
568 # other levels are probably only of interest if you are hunting
569 # down a specific problem. They can produce a hell of an output
572 # Privoxy used to ship with the debug levels recommended above
573 # enabled by default, but due to privacy concerns 3.0.7 and
574 # later are configured to only log fatal errors.
576 # If you are used to the more verbose settings, simply enable
577 # the debug lines below again.
579 # If you want to use pure CLF (Common Log Format), you should
580 # set "debug 512" ONLY and not enable anything else.
582 # Privoxy has a hard-coded limit for the length of log messages.
583 # If it's reached, messages are logged truncated and marked with
584 # "... [too long, truncated]".
586 # Please don't file any support requests without trying to
587 # reproduce the problem with increased debug level first. Once
588 # you read the log messages, you may even be able to solve the
589 # problem on your own.
591 #debug 1 # Log the destination for each request Privoxy let through. See also debug 1024.
592 #debug 1024 # Actions that are applied to all sites and maybe overruled later on.
593 #debug 4096 # Startup banner and warnings
594 #debug 8192 # Non-fatal errors
596 # 3.2. single-threaded
597 # =====================
601 # Whether to run only one server thread.
613 # Multi-threaded (or, where unavailable: forked) operation, i.e.
614 # the ability to serve multiple requests simultaneously.
618 # This option is only there for debugging purposes. It will
619 # drastically reduce performance.
628 # The hostname shown on the CGI pages.
640 # The hostname provided by the operating system is used.
644 # On some misconfigured systems resolving the hostname fails or
645 # takes too much time and slows Privoxy down. Setting a fixed
646 # hostname works around the problem.
648 # In other circumstances it might be desirable to show a
649 # hostname other than the one returned by the operating system.
650 # For example if the system has several different hostnames and
651 # you don't want to use the first one.
653 # Note that Privoxy does not validate the specified hostname
656 #hostname hostname.example.org
658 # 4. ACCESS CONTROL AND SECURITY
659 # ===============================
661 # This section of the config file controls the security-relevant
662 # aspects of Privoxy's configuration.
665 # 4.1. listen-address
666 # ====================
670 # The address and TCP port on which Privoxy will listen for
685 # Bind to 127.0.0.1 (IPv4 localhost), port 8118. This is
686 # suitable and recommended for home users who run Privoxy on the
687 # same machine as their browser.
691 # You will need to configure your browser(s) to this proxy
694 # If you already have another service running on port 8118, or
695 # if you want to serve requests from other machines (e.g. on
696 # your local network) as well, you will need to override the
699 # You can use this statement multiple times to make Privoxy
700 # listen on more ports or more IP addresses. Suitable if your
701 # operating system does not support sharing IPv6 and IPv4
702 # protocols on the same socket.
704 # If a hostname is used instead of an IP address, Privoxy will
705 # try to resolve it to an IP address and if there are multiple,
706 # use the first one returned.
708 # If the address for the hostname isn't already known on the
709 # system (for example because it's in /etc/hostname), this may
710 # result in DNS traffic.
712 # If the specified address isn't available on the system, or if
713 # the hostname can't be resolved, Privoxy will fail to start.
715 # IPv6 addresses containing colons have to be quoted by
716 # brackets. They can only be used if Privoxy has been compiled
717 # with IPv6 support. If you aren't sure if your version supports
718 # it, have a look at http://config.privoxy.org/show-status.
720 # Some operating systems will prefer IPv6 to IPv4 addresses even
721 # if the system has no IPv6 connectivity which is usually not
722 # expected by the user. Some even rely on DNS to resolve
723 # localhost which mean the "localhost" address used may not
726 # It is therefore recommended to explicitly configure the
727 # intended IP address instead of relying on the operating
728 # system, unless there's a strong reason not to.
730 # If you leave out the address, Privoxy will bind to all IPv4
731 # interfaces (addresses) on your machine and may become
732 # reachable from the Internet and/or the local network. Be aware
733 # that some GNU/Linux distributions modify that behaviour
734 # without updating the documentation. Check for non-standard
735 # patches if your Privoxy version behaves differently.
737 # If you configure Privoxy to be reachable from the network,
738 # consider using access control lists (ACL's, see below), and/or
741 # If you open Privoxy to untrusted users, you will also want to
742 # make sure that the following actions are disabled:
743 # enable-edit-actions and enable-remote-toggle
747 # Suppose you are running Privoxy on a machine which has the
748 # address 192.168.0.1 on your local private network
749 # (192.168.0.0) and has another outside connection with a
750 # different address. You want it to serve requests from inside
753 # listen-address 192.168.0.1:8118
755 # Suppose you are running Privoxy on an IPv6-capable machine and
756 # you want it to listen on the IPv6 address of the loopback
759 # listen-address [::1]:8118
761 listen-address 127.0.0.1:8118
768 # Initial state of "toggle" status
780 # Act as if toggled on
784 # If set to 0, Privoxy will start in "toggled off" mode, i.e.
785 # mostly behave like a normal, content-neutral proxy with both
786 # ad blocking and content filtering disabled. See
787 # enable-remote-toggle below.
791 # 4.3. enable-remote-toggle
792 # ==========================
796 # Whether or not the web-based toggle feature may be used
808 # The web-based toggle feature is disabled.
812 # When toggled off, Privoxy mostly acts like a normal,
813 # content-neutral proxy, i.e. doesn't block ads or filter
816 # Access to the toggle feature can not be controlled separately
817 # by "ACLs" or HTTP authentication, so that everybody who can
818 # access Privoxy (see "ACLs" and listen-address above) can
819 # toggle it for all users. So this option is not recommended for
820 # multi-user environments with untrusted users.
822 # Note that malicious client side code (e.g Java) is also
823 # capable of using this option.
825 # As a lot of Privoxy users don't read documentation, this
826 # feature is disabled by default.
828 # Note that you must have compiled Privoxy with support for this
829 # feature, otherwise this option has no effect.
831 enable-remote-toggle 0
833 # 4.4. enable-remote-http-toggle
834 # ===============================
838 # Whether or not Privoxy recognizes special HTTP headers to
839 # change its behaviour.
851 # Privoxy ignores special HTTP headers.
855 # When toggled on, the client can change Privoxy's behaviour by
856 # setting special HTTP headers. Currently the only supported
857 # special header is "X-Filter: No", to disable filtering for the
858 # ongoing request, even if it is enabled in one of the action
861 # This feature is disabled by default. If you are using Privoxy
862 # in a environment with trusted clients, you may enable this
863 # feature at your discretion. Note that malicious client side
864 # code (e.g Java) is also capable of using this feature.
866 # This option will be removed in future releases as it has been
867 # obsoleted by the more general header taggers.
869 enable-remote-http-toggle 0
871 # 4.5. enable-edit-actions
872 # =========================
876 # Whether or not the web-based actions file editor may be used
888 # The web-based actions file editor is disabled.
892 # Access to the editor can not be controlled separately by
893 # "ACLs" or HTTP authentication, so that everybody who can
894 # access Privoxy (see "ACLs" and listen-address above) can
895 # modify its configuration for all users.
897 # This option is not recommended for environments with untrusted
898 # users and as a lot of Privoxy users don't read documentation,
899 # this feature is disabled by default.
901 # Note that malicious client side code (e.g Java) is also
902 # capable of using the actions editor and you shouldn't enable
903 # this options unless you understand the consequences and are
904 # sure your browser is configured correctly.
906 # Note that you must have compiled Privoxy with support for this
907 # feature, otherwise this option has no effect.
909 enable-edit-actions 0
911 # 4.6. enforce-blocks
912 # ====================
916 # Whether the user is allowed to ignore blocks and can "go there
929 # Blocks are not enforced.
933 # Privoxy is mainly used to block and filter requests as a
934 # service to the user, for example to block ads and other junk
935 # that clogs the pipes. Privoxy's configuration isn't perfect
936 # and sometimes innocent pages are blocked. In this situation it
937 # makes sense to allow the user to enforce the request and have
938 # Privoxy ignore the block.
940 # In the default configuration Privoxy's "Blocked" page contains
941 # a "go there anyway" link to adds a special string (the force
942 # prefix) to the request URL. If that link is used, Privoxy will
943 # detect the force prefix, remove it again and let the request
946 # Of course Privoxy can also be used to enforce a network
947 # policy. In that case the user obviously should not be able to
948 # bypass any blocks, and that's what the "enforce-blocks" option
949 # is for. If it's enabled, Privoxy hides the "go there anyway"
950 # link. If the user adds the force prefix by hand, it will not
951 # be accepted and the circumvention attempt is logged.
959 # 4.7. ACLs: permit-access and deny-access
960 # =========================================
964 # Who can access what.
968 # src_addr[:port][/src_masklen] [dst_addr[:port][/dst_masklen]]
970 # Where src_addr and dst_addr are IPv4 addresses in dotted
971 # decimal notation or valid DNS names, port is a port number,
972 # and src_masklen and dst_masklen are subnet masks in CIDR
973 # notation, i.e. integer values from 2 to 30 representing the
974 # length (in bits) of the network address. The masks and the
975 # whole destination part are optional.
977 # If your system implements RFC 3493, then src_addr and dst_addr
978 # can be IPv6 addresses delimeted by brackets, port can be a
979 # number or a service name, and src_masklen and dst_masklen can
980 # be a number from 0 to 128.
986 # If no port is specified, any port will match. If no
987 # src_masklen or src_masklen is given, the complete IP address
988 # has to match (i.e. 32 bits for IPv4 and 128 bits for IPv6).
992 # Don't restrict access further than implied by listen-address
996 # Access controls are included at the request of ISPs and
997 # systems administrators, and are not usually needed by
998 # individual users. For a typical home user, it will normally
999 # suffice to ensure that Privoxy only listens on the localhost
1000 # (127.0.0.1) or internal (home) network address by means of the
1001 # listen-address option.
1003 # Please see the warnings in the FAQ that Privoxy is not
1004 # intended to be a substitute for a firewall or to encourage
1005 # anyone to defer addressing basic security weaknesses.
1007 # Multiple ACL lines are OK. If any ACLs are specified, Privoxy
1008 # only talks to IP addresses that match at least one
1009 # permit-access line and don't match any subsequent deny-access
1010 # line. In other words, the last match wins, with the default
1011 # being deny-access.
1013 # If Privoxy is using a forwarder (see forward below) for a
1014 # particular destination URL, the dst_addr that is examined is
1015 # the address of the forwarder and NOT the address of the
1016 # ultimate target. This is necessary because it may be
1017 # impossible for the local Privoxy to determine the IP address
1018 # of the ultimate target (that's often what gateways are used
1021 # You should prefer using IP addresses over DNS names, because
1022 # the address lookups take time. All DNS names must resolve! You
1023 # can not use domain patterns like "*.org" or partial domain
1024 # names. If a DNS name resolves to multiple IP addresses, only
1025 # the first one is used.
1027 # Some systems allow IPv4 clients to connect to IPv6 server
1028 # sockets. Then the client's IPv4 address will be translated by
1029 # the system into IPv6 address space with special prefix
1030 # ::ffff:0:0/96 (so called IPv4 mapped IPv6 address). Privoxy
1031 # can handle it and maps such ACL addresses automatically.
1033 # Denying access to particular sites by ACL may have undesired
1034 # side effects if the site in question is hosted on a machine
1035 # which also hosts other sites (most sites are).
1039 # Explicitly define the default behavior if no ACL and
1040 # listen-address are set: "localhost" is OK. The absence of a
1041 # dst_addr implies that all destination addresses are OK:
1043 # permit-access localhost
1045 # Allow any host on the same class C subnet as www.privoxy.org
1046 # access to nothing but www.example.com (or other domains hosted
1047 # on the same system):
1049 # permit-access www.privoxy.org/24 www.example.com/32
1051 # Allow access from any host on the 26-bit subnet 192.168.45.64
1052 # to anywhere, with the exception that 192.168.45.73 may not
1053 # access the IP address behind www.dirty-stuff.example.com:
1055 # permit-access 192.168.45.64/26
1056 # deny-access 192.168.45.73 www.dirty-stuff.example.com
1058 # Allow access from the IPv4 network 192.0.2.0/24 even if
1059 # listening on an IPv6 wild card address (not supported on all
1062 # permit-access 192.0.2.0/24
1064 # This is equivalent to the following line even if listening on
1065 # an IPv4 address (not supported on all platforms):
1067 # permit-access [::ffff:192.0.2.0]/120
1071 # ==================
1075 # Maximum size of the buffer for content filtering.
1087 # Use a 4MB (4096 KB) limit.
1091 # For content filtering, i.e. the +filter and +deanimate-gif
1092 # actions, it is necessary that Privoxy buffers the entire
1093 # document body. This can be potentially dangerous, since a
1094 # server could just keep sending data indefinitely and wait for
1095 # your RAM to exhaust -- with nasty consequences. Hence this
1098 # When a document buffer size reaches the buffer-limit, it is
1099 # flushed to the client unfiltered and no further attempt to
1100 # filter the rest of the document is made. Remember that there
1101 # may be multiple threads running, which might require up to
1102 # buffer-limit Kbytes each, unless you have enabled
1103 # "single-threaded" above.
1107 # 4.9. enable-proxy-authentication-forwarding
1108 # ============================================
1112 # Whether or not proxy authentication through Privoxy should
1125 # Proxy authentication headers are removed.
1129 # Privoxy itself does not support proxy authentication, but can
1130 # allow clients to authenticate against Privoxy's parent proxy.
1132 # By default Privoxy (3.0.21 and later) don't do that and remove
1133 # Proxy-Authorization headers in requests and Proxy-Authenticate
1134 # headers in responses to make it harder for malicious sites to
1135 # trick inexperienced users into providing login information.
1137 # If this option is enabled the headers are forwarded.
1139 # Enabling this option is not recommended if there is no parent
1140 # proxy that requires authentication or if the local network
1141 # between Privoxy and the parent proxy isn't trustworthy. If
1142 # proxy authentication is only required for some requests, it is
1143 # recommended to use a client header filter to remove the
1144 # authentication headers for requests where they aren't needed.
1146 enable-proxy-authentication-forwarding 0
1151 # This feature allows routing of HTTP requests through a chain of
1154 # Forwarding can be used to chain Privoxy with a caching proxy to
1155 # speed up browsing. Using a parent proxy may also be necessary if
1156 # the machine that Privoxy runs on has no direct Internet access.
1158 # Note that parent proxies can severely decrease your privacy level.
1159 # For example a parent proxy could add your IP address to the
1160 # request headers and if it's a caching proxy it may add the "Etag"
1161 # header to revalidation requests again, even though you configured
1162 # Privoxy to remove it. It may also ignore Privoxy's header time
1163 # randomization and use the original values which could be used by
1164 # the server as cookie replacement to track your steps between
1167 # Also specified here are SOCKS proxies. Privoxy supports the SOCKS
1168 # 4 and SOCKS 4A protocols.
1176 # To which parent HTTP proxy specific requests should be routed.
1180 # target_pattern http_parent[:port]
1182 # where target_pattern is a URL pattern that specifies to which
1183 # requests (i.e. URLs) this forward rule shall apply. Use / to
1184 # denote "all URLs". http_parent[:port] is the DNS name or IP
1185 # address of the parent HTTP proxy through which the requests
1186 # should be forwarded, optionally followed by its listening port
1187 # (default: 8000). Use a single dot (.) to denote "no
1196 # Don't use parent HTTP proxies.
1200 # If http_parent is ".", then requests are not forwarded to
1201 # another HTTP proxy but are made directly to the web servers.
1203 # http_parent can be a numerical IPv6 address (if RFC 3493 is
1204 # implemented). To prevent clashes with the port delimiter, the
1205 # whole IP address has to be put into brackets. On the other
1206 # hand a target_pattern containing an IPv6 address has to be put
1207 # into angle brackets (normal brackets are reserved for regular
1208 # expressions already).
1210 # Multiple lines are OK, they are checked in sequence, and the
1215 # Everything goes to an example parent proxy, except SSL on port
1216 # 443 (which it doesn't handle):
1218 # forward / parent-proxy.example.org:8080
1221 # Everything goes to our example ISP's caching proxy, except for
1222 # requests to that ISP's sites:
1224 # forward / caching-proxy.isp.example.net:8000
1225 # forward .isp.example.net .
1227 # Parent proxy specified by an IPv6 address:
1229 # forward / [2001:DB8::1]:8000
1231 # Suppose your parent proxy doesn't support IPv6:
1233 # forward / parent-proxy.example.org:8000
1234 # forward ipv6-server.example.org .
1235 # forward <[2-3][0-9a-f][0-9a-f][0-9a-f]:*> .
1238 # 5.2. forward-socks4, forward-socks4a, forward-socks5 and forward-socks5t
1239 # =========================================================================
1243 # Through which SOCKS proxy (and optionally to which parent HTTP
1244 # proxy) specific requests should be routed.
1248 # target_pattern socks_proxy[:port] http_parent[:port]
1250 # where target_pattern is a URL pattern that specifies to which
1251 # requests (i.e. URLs) this forward rule shall apply. Use / to
1252 # denote "all URLs". http_parent and socks_proxy are IP
1253 # addresses in dotted decimal notation or valid DNS names (
1254 # http_parent may be "." to denote "no HTTP forwarding"), and
1255 # the optional port parameters are TCP ports, i.e. integer
1256 # values from 1 to 65535
1264 # Don't use SOCKS proxies.
1268 # Multiple lines are OK, they are checked in sequence, and the
1271 # The difference between forward-socks4 and forward-socks4a is
1272 # that in the SOCKS 4A protocol, the DNS resolution of the
1273 # target hostname happens on the SOCKS server, while in SOCKS 4
1274 # it happens locally.
1276 # With forward-socks5 the DNS resolution will happen on the
1277 # remote server as well.
1279 # forward-socks5t works like vanilla forward-socks5 but lets
1280 # Privoxy additionally use Tor-specific SOCKS extensions.
1281 # Currently the only supported SOCKS extension is optimistic
1282 # data which can reduce the latency for the first request made
1283 # on a newly created connection.
1285 # socks_proxy and http_parent can be a numerical IPv6 address
1286 # (if RFC 3493 is implemented). To prevent clashes with the port
1287 # delimiter, the whole IP address has to be put into brackets.
1288 # On the other hand a target_pattern containing an IPv6 address
1289 # has to be put into angle brackets (normal brackets are
1290 # reserved for regular expressions already).
1292 # If http_parent is ".", then requests are not forwarded to
1293 # another HTTP proxy but are made (HTTP-wise) directly to the
1294 # web servers, albeit through a SOCKS proxy.
1298 # From the company example.com, direct connections are made to
1299 # all "internal" domains, but everything outbound goes through
1300 # their ISP's proxy by way of example.com's corporate SOCKS 4A
1301 # gateway to the Internet.
1303 # forward-socks4a / socks-gw.example.com:1080 www-cache.isp.example.net:8080
1304 # forward .example.com .
1306 # A rule that uses a SOCKS 4 gateway for all destinations but no
1307 # HTTP parent looks like this:
1309 # forward-socks4 / socks-gw.example.com:1080 .
1311 # To chain Privoxy and Tor, both running on the same system, you
1312 # would use something like:
1314 # forward-socks5 / 127.0.0.1:9050 .
1316 # The public Tor network can't be used to reach your local
1317 # network, if you need to access local servers you therefore
1318 # might want to make some exceptions:
1320 # forward 192.168.*.*/ .
1321 # forward 10.*.*.*/ .
1322 # forward 127.*.*.*/ .
1324 # Unencrypted connections to systems in these address ranges
1325 # will be as (un)secure as the local network is, but the
1326 # alternative is that you can't reach the local network through
1327 # Privoxy at all. Of course this may actually be desired and
1328 # there is no reason to make these exceptions if you aren't sure
1331 # If you also want to be able to reach servers in your local
1332 # network by using their names, you will need additional
1333 # exceptions that look like this:
1335 # forward localhost/ .
1338 # 5.3. forwarded-connect-retries
1339 # ===============================
1343 # How often Privoxy retries if a forwarded connection request
1348 # Number of retries.
1356 # Connections forwarded through other proxies are treated like
1357 # direct connections and no retry attempts are made.
1361 # forwarded-connect-retries is mainly interesting for socks4a
1362 # connections, where Privoxy can't detect why the connections
1363 # failed. The connection might have failed because of a DNS
1364 # timeout in which case a retry makes sense, but it might also
1365 # have failed because the server doesn't exist or isn't
1366 # reachable. In this case the retry will just delay the
1367 # appearance of Privoxy's error message.
1369 # Note that in the context of this option, "forwarded
1370 # connections" includes all connections that Privoxy forwards
1371 # through other proxies. This option is not limited to the HTTP
1374 # Only use this option, if you are getting lots of
1375 # forwarding-related error messages that go away when you try
1376 # again manually. Start with a small value and check Privoxy's
1377 # logfile from time to time, to see how many retries are usually
1382 # forwarded-connect-retries 1
1384 forwarded-connect-retries 0
1389 # 6.1. accept-intercepted-requests
1390 # =================================
1394 # Whether intercepted requests should be treated as valid.
1406 # Only proxy requests are accepted, intercepted requests are
1407 # treated as invalid.
1411 # If you don't trust your clients and want to force them to use
1412 # Privoxy, enable this option and configure your packet filter
1413 # to redirect outgoing HTTP connections into Privoxy.
1415 # Make sure that Privoxy's own requests aren't redirected as
1416 # well. Additionally take care that Privoxy can't intentionally
1417 # connect to itself, otherwise you could run into redirection
1418 # loops if Privoxy's listening port is reachable by the outside
1419 # or an attacker has access to the pages you visit.
1423 # accept-intercepted-requests 1
1425 accept-intercepted-requests 0
1427 # 6.2. allow-cgi-request-crunching
1428 # =================================
1432 # Whether requests to Privoxy's CGI pages can be blocked or
1445 # Privoxy ignores block and redirect actions for its CGI pages.
1449 # By default Privoxy ignores block or redirect actions for its
1450 # CGI pages. Intercepting these requests can be useful in
1451 # multi-user setups to implement fine-grained access control,
1452 # but it can also render the complete web interface useless and
1453 # make debugging problems painful if done without care.
1455 # Don't enable this option unless you're sure that you really
1460 # allow-cgi-request-crunching 1
1462 allow-cgi-request-crunching 0
1464 # 6.3. split-large-forms
1465 # =======================
1469 # Whether the CGI interface should stay compatible with broken
1482 # The CGI form generate long GET URLs.
1486 # Privoxy's CGI forms can lead to rather long URLs. This isn't a
1487 # problem as far as the HTTP standard is concerned, but it can
1488 # confuse clients with arbitrary URL length limitations.
1490 # Enabling split-large-forms causes Privoxy to divide big forms
1491 # into smaller ones to keep the URL length down. It makes
1492 # editing a lot less convenient and you can no longer submit all
1493 # changes at once, but at least it works around this browser
1496 # If you don't notice any editing problems, there is no reason
1497 # to enable this option, but if one of the submit buttons
1498 # appears to be broken, you should give it a try.
1502 # split-large-forms 1
1506 # 6.4. keep-alive-timeout
1507 # ========================
1511 # Number of seconds after which an open connection will no
1524 # Connections are not kept alive.
1528 # This option allows clients to keep the connection to Privoxy
1529 # alive. If the server supports it, Privoxy will keep the
1530 # connection to the server alive as well. Under certain
1531 # circumstances this may result in speed-ups.
1533 # By default, Privoxy will close the connection to the server if
1534 # the client connection gets closed, or if the specified timeout
1535 # has been reached without a new request coming in. This
1536 # behaviour can be changed with the connection-sharing option.
1538 # This option has no effect if Privoxy has been compiled without
1539 # keep-alive support.
1541 # Note that a timeout of five seconds as used in the default
1542 # configuration file significantly decreases the number of
1543 # connections that will be reused. The value is used because
1544 # some browsers limit the number of connections they open to a
1545 # single host and apply the same limit to proxies. This can
1546 # result in a single website "grabbing" all the connections the
1547 # browser allows, which means connections to other websites
1548 # can't be opened until the connections currently in use time
1551 # Several users have reported this as a Privoxy bug, so the
1552 # default value has been reduced. Consider increasing it to 300
1553 # seconds or even more if you think your browser can handle it.
1554 # If your browser appears to be hanging, it probably can't.
1558 # keep-alive-timeout 300
1560 keep-alive-timeout 5
1562 # 6.5. tolerate-pipelining
1563 # =========================
1567 # Whether or not pipelined requests should be served.
1579 # If Privoxy receives more than one request at once, it
1580 # terminates the client connection after serving the first one.
1584 # Privoxy currently doesn't pipeline outgoing requests, thus
1585 # allowing pipelining on the client connection is not guaranteed
1586 # to improve the performance.
1588 # By default Privoxy tries to discourage clients from pipelining
1589 # by discarding aggressively pipelined requests, which forces
1590 # the client to resend them through a new connection.
1592 # This option lets Privoxy tolerate pipelining. Whether or not
1593 # that improves performance mainly depends on the client
1596 # If you are seeing problems with pages not properly loading,
1597 # disabling this option could work around the problem.
1601 # tolerate-pipelining 1
1603 tolerate-pipelining 1
1605 # 6.6. default-server-timeout
1606 # ============================
1610 # Assumed server-side keep-alive timeout if not specified by the
1623 # Connections for which the server didn't specify the keep-alive
1624 # timeout are not reused.
1628 # Enabling this option significantly increases the number of
1629 # connections that are reused, provided the keep-alive-timeout
1630 # option is also enabled.
1632 # While it also increases the number of connections problems
1633 # when Privoxy tries to reuse a connection that already has been
1634 # closed on the server side, or is closed while Privoxy is
1635 # trying to reuse it, this should only be a problem if it
1636 # happens for the first request sent by the client. If it
1637 # happens for requests on reused client connections, Privoxy
1638 # will simply close the connection and the client is supposed to
1639 # retry the request without bothering the user.
1641 # Enabling this option is therefore only recommended if the
1642 # connection-sharing option is disabled.
1644 # It is an error to specify a value larger than the
1645 # keep-alive-timeout value.
1647 # This option has no effect if Privoxy has been compiled without
1648 # keep-alive support.
1652 # default-server-timeout 60
1654 #default-server-timeout 60
1656 # 6.7. connection-sharing
1657 # ========================
1661 # Whether or not outgoing connections that have been kept alive
1662 # should be shared between different incoming connections.
1674 # Connections are not shared.
1678 # This option has no effect if Privoxy has been compiled without
1679 # keep-alive support, or if it's disabled.
1683 # Note that reusing connections doesn't necessary cause
1684 # speedups. There are also a few privacy implications you should
1687 # If this option is effective, outgoing connections are shared
1688 # between clients (if there are more than one) and closing the
1689 # browser that initiated the outgoing connection does no longer
1690 # affect the connection between Privoxy and the server unless
1691 # the client's request hasn't been completed yet.
1693 # If the outgoing connection is idle, it will not be closed
1694 # until either Privoxy's or the server's timeout is reached.
1695 # While it's open, the server knows that the system running
1696 # Privoxy is still there.
1698 # If there are more than one client (maybe even belonging to
1699 # multiple users), they will be able to reuse each others
1700 # connections. This is potentially dangerous in case of
1701 # authentication schemes like NTLM where only the connection is
1702 # authenticated, instead of requiring authentication for each
1705 # If there is only a single client, and if said client can keep
1706 # connections alive on its own, enabling this option has next to
1707 # no effect. If the client doesn't support connection
1708 # keep-alive, enabling this option may make sense as it allows
1709 # Privoxy to keep outgoing connections alive even if the client
1710 # itself doesn't support it.
1712 # You should also be aware that enabling this option increases
1713 # the likelihood of getting the "No server or forwarder data"
1714 # error message, especially if you are using a slow connection
1717 # This option should only be used by experienced users who
1718 # understand the risks and can weight them against the benefits.
1722 # connection-sharing 1
1724 #connection-sharing 1
1726 # 6.8. socket-timeout
1727 # ====================
1731 # Number of seconds after which a socket times out if no data is
1744 # A default value of 300 seconds is used.
1748 # The default is quite high and you probably want to reduce it.
1749 # If you aren't using an occasionally slow proxy like Tor,
1750 # reducing it to a few seconds should be fine.
1754 # socket-timeout 300
1758 # 6.9. max-client-connections
1759 # ============================
1763 # Maximum number of client connections that will be served.
1775 # Connections are served until a resource limit is reached.
1779 # Privoxy creates one thread (or process) for every incoming
1780 # client connection that isn't rejected based on the access
1783 # If the system is powerful enough, Privoxy can theoretically
1784 # deal with several hundred (or thousand) connections at the
1785 # same time, but some operating systems enforce resource limits
1786 # by shutting down offending processes and their default limits
1787 # may be below the ones Privoxy would require under heavy load.
1789 # Configuring Privoxy to enforce a connection limit below the
1790 # thread or process limit used by the operating system makes
1791 # sure this doesn't happen. Simply increasing the operating
1792 # system's limit would work too, but if Privoxy isn't the only
1793 # application running on the system, you may actually want to
1794 # limit the resources used by Privoxy.
1796 # If Privoxy is only used by a single trusted user, limiting the
1797 # number of client connections is probably unnecessary. If there
1798 # are multiple possibly untrusted users you probably still want
1799 # to additionally use a packet filter to limit the maximal
1800 # number of incoming connections per client. Otherwise a
1801 # malicious user could intentionally create a high number of
1802 # connections to prevent other users from using Privoxy.
1804 # Obviously using this option only makes sense if you choose a
1805 # limit below the one enforced by the operating system.
1807 # One most POSIX-compliant systems Privoxy can't properly deal
1808 # with more than FD_SETSIZE file descriptors at the same time
1809 # and has to reject connections if the limit is reached. This
1810 # will likely change in a future version, but currently this
1811 # limit can't be increased without recompiling Privoxy with a
1812 # different FD_SETSIZE limit.
1816 # max-client-connections 256
1818 #max-client-connections 256
1820 # 6.10. handle-as-empty-doc-returns-ok
1821 # =====================================
1825 # The status code Privoxy returns for pages blocked with
1826 # +handle-as-empty-document.
1838 # Privoxy returns a status 403(forbidden) for all blocked pages.
1842 # Privoxy returns a status 200(OK) for pages blocked with
1843 # +handle-as-empty-document and a status 403(Forbidden) for all
1844 # other blocked pages.
1848 # This is a work-around for Firefox bug 492459: " Websites are
1849 # no longer rendered if SSL requests for JavaScripts are blocked
1850 # by a proxy. " (https://bugzilla.mozilla.org/show_bug.cgi?id=
1851 # 492459) As the bug has been fixed for quite some time this
1852 # option should no longer be needed and will be removed in a
1853 # future release. Please speak up if you have a reason why the
1854 # option should be kept around.
1856 #handle-as-empty-doc-returns-ok 1
1858 # 6.11. enable-compression
1859 # =========================
1863 # Whether or not buffered content is compressed before delivery.
1875 # Privoxy does not compress buffered content.
1879 # Privoxy compresses buffered content before delivering it to
1880 # the client, provided the client supports it.
1884 # This directive is only supported if Privoxy has been compiled
1885 # with FEATURE_COMPRESSION, which should not to be confused with
1888 # Compressing buffered content is mainly useful if Privoxy and
1889 # the client are running on different systems. If they are
1890 # running on the same system, enabling compression is likely to
1891 # slow things down. If you didn't measure otherwise, you should
1892 # assume that it does and keep this option disabled.
1894 # Privoxy will not compress buffered content below a certain
1897 #enable-compression 1
1899 # 6.12. compression-level
1900 # ========================
1904 # The compression level that is passed to the zlib library when
1905 # compressing buffered content.
1909 # Positive number ranging from 0 to 9.
1917 # Compressing the data more takes usually longer than
1918 # compressing it less or not compressing it at all. Which level
1919 # is best depends on the connection between Privoxy and the
1920 # client. If you can't be bothered to benchmark it for yourself,
1921 # you should stick with the default and keep compression
1924 # If compression is disabled, the compression level is
1929 # # Best speed (compared to the other levels)
1930 # compression-level 1
1932 # # Best compression
1933 # compression-level 9
1935 # # No compression. Only useful for testing as the added header
1936 # # slightly increases the amount of data that has to be sent.
1937 # # If your benchmark shows that using this compression level
1938 # # is superior to using no compression at all, the benchmark
1939 # # is likely to be flawed.
1940 # compression-level 0
1943 #compression-level 1
1945 # 6.13. client-header-order
1946 # ==========================
1950 # The order in which client headers are sorted before forwarding
1955 # Client header names delimited by spaces or tabs
1963 # By default Privoxy leaves the client headers in the order they
1964 # were sent by the client. Headers are modified in-place, new
1965 # headers are added at the end of the already existing headers.
1967 # The header order can be used to fingerprint client requests
1968 # independently of other headers like the User-Agent.
1970 # This directive allows to sort the headers differently to
1971 # better mimic a different User-Agent. Client headers will be
1972 # emitted in the order given, headers whose name isn't
1973 # explicitly specified are added at the end.
1975 # Note that sorting headers in an uncommon way will make
1976 # fingerprinting actually easier. Encrypted headers are not
1977 # affected by this directive.
1979 #client-header-order Host \
1983 # Proxy-Connection \
1987 # If-Modified-Since \
1993 # 7. WINDOWS GUI OPTIONS
1994 # =======================
1996 # Privoxy has a number of options specific to the Windows GUI
2001 # If "activity-animation" is set to 1, the Privoxy icon will animate
2002 # when "Privoxy" is active. To turn off, set to 0.
2004 #activity-animation 1
2008 # If "log-messages" is set to 1, Privoxy copies log messages to the
2009 # console window. The log detail depends on the debug directive.
2015 # If "log-buffer-size" is set to 1, the size of the log buffer, i.e.
2016 # the amount of memory used for the log messages displayed in the
2017 # console window, will be limited to "log-max-lines" (see below).
2019 # Warning: Setting this to 0 will result in the buffer to grow
2020 # infinitely and eat up all your memory!
2026 # log-max-lines is the maximum number of lines held in the log
2027 # buffer. See above.
2033 # If "log-highlight-messages" is set to 1, Privoxy will highlight
2034 # portions of the log messages with a bold-faced font:
2036 #log-highlight-messages 1
2040 # The font used in the console window:
2042 #log-font-name Comic Sans MS
2046 # Font size used in the console window:
2052 # "show-on-task-bar" controls whether or not Privoxy will appear as
2053 # a button on the Task bar when minimized:
2059 # If "close-button-minimizes" is set to 1, the Windows close button
2060 # will minimize Privoxy instead of closing the program (close with
2061 # the exit option on the File menu).
2063 #close-button-minimizes 1
2067 # The "hide-console" option is specific to the MS-Win console
2068 # version of Privoxy. If this option is used, Privoxy will
2069 # disconnect from and hide the command console.