1 # Sample Configuration File for Privoxy v3.0.16
3 # $Id: config,v 1.85 2010/01/11 13:46:38 fabiankeil Exp $
5 # Copyright (C) 2001-2009 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 #
19 # 6. WINDOWS GUI OPTIONS #
21 ####################################################################
27 # This file holds Privoxy's main configuration. Privoxy detects
28 # configuration changes automatically, so you don't have to restart
29 # it unless you want to load a different configuration file.
31 # The configuration will be reloaded with the first request after
32 # the change was done, this request itself will still use the old
33 # configuration, though. In other words: it takes two requests before
34 # you see the result of your changes. Requests that are dropped due
35 # to ACL don't trigger reloads.
37 # When starting Privoxy on Unix systems, give the location of this
38 # file as last argument. On Windows systems, Privoxy will look for
39 # this file with the name 'config.txt' in the current working directory
40 # of the Privoxy process.
43 # II. FORMAT OF THE CONFIGURATION FILE
44 # ====================================
46 # Configuration lines consist of an initial keyword followed by a
47 # list of values, all separated by whitespace (any number of spaces
48 # or tabs). For example,
50 # actionsfile default.action
52 # Indicates that the actionsfile is named 'default.action'.
54 # The '#' indicates a comment. Any part of a line following a '#'
55 # is ignored, except if the '#' is preceded by a '\'.
57 # Thus, by placing a # at the start of an existing configuration
58 # line, you can make it a comment and it will be treated as if it
59 # weren't there. This is called "commenting out" an option and can
60 # be useful. Removing the # again is called "uncommenting".
62 # Note that commenting out an option and leaving it at its default
63 # are two completely different things! Most options behave very
64 # differently when unset. See the "Effect if unset" explanation in
65 # each option's description for details.
67 # 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 yourself,
76 # it might be a good idea to let them know how to reach you, what
77 # you block and why you do that, your policies, etc.
86 # Location of the Privoxy User Manual.
90 # A fully qualified URI
98 # http://www.privoxy.org/version/user-manual/ will be used,
99 # where version is the Privoxy version.
103 # The User Manual URI is the single best source of information on
104 # Privoxy, and is used for help links from some of the internal
105 # CGI pages. The manual itself is normally packaged with the
106 # binary distributions, so you probably want to set this to a
107 # locally installed copy.
111 # The best all purpose solution is simply to put the full local
112 # PATH to where the User Manual is located:
114 # user-manual /usr/share/doc/privoxy/user-manual
117 # The User Manual is then available to anyone with
118 # access to Privoxy, by following the built-in URL:
119 # http://config.privoxy.org/user-manual/ (or the shortcut:
120 # http://p.p/user-manual/).
122 # If the documentation is not on the local system, it can be
123 # accessed from a remote server, as:
125 # user-manual http://example.com/privoxy/user-manual/
130 # If set, this option should be the first option in the config
131 # file, because it is used while the config file is being read.
133 #user-manual http://www.privoxy.org/user-manual/
136 # 1.2. trust-info-url
137 # ====================
141 # A URL to be displayed in the error page that users will see if
142 # access to an untrusted page is denied.
154 # No links are displayed on the "untrusted" error page.
158 # The value of this option only matters if the experimental trust
159 # mechanism has been activated. (See trustfile below.)
161 # If you use the trust mechanism, it is a good idea to write
162 # up some on-line documentation about your trust policy and to
163 # specify the URL(s) here. Use multiple times for multiple URLs.
165 # The URL(s) should be added to the trustfile as well, so users
166 # don't end up locked out from the information on why they were
167 # locked out in the first place!
169 #trust-info-url http://www.example.com/why_we_block.html
170 #trust-info-url http://www.example.com/what_we_allow.html
174 # ===================
178 # An email address to reach the Privoxy administrator.
190 # No email address is displayed on error pages and the CGI user
195 # If both admin-address and proxy-info-url are unset, the whole
196 # "Local Privoxy Support" box on all generated pages will not
199 #admin-address privoxy-admin@example.com
202 # 1.4. proxy-info-url
203 # ====================
207 # A URL to documentation about the local Privoxy setup,
208 # configuration or policies.
220 # No link to local documentation is displayed on error pages and
221 # the CGI user interface.
225 # If both admin-address and proxy-info-url are unset, the whole
226 # "Local Privoxy Support" box on all generated pages will not
229 # This URL shouldn't be blocked ;-)
231 #proxy-info-url http://www.example.com/proxy-service.html
234 # 2. CONFIGURATION AND LOG FILE LOCATIONS
235 # ========================================
237 # Privoxy can (and normally does) use a number of other files for
238 # additional configuration, help and logging. This section of the
239 # configuration file tells Privoxy where to find those other files.
241 # The user running Privoxy, must have read permission for all
242 # configuration files, and write permission to any files that would
243 # be modified, such as log files and actions files.
252 # The directory where the other configuration files are located.
260 # /etc/privoxy (Unix) or Privoxy installation dir (Windows)
268 # No trailing "/", please.
278 # An alternative directory where the templates are loaded from.
290 # The templates are assumed to be located in confdir/template.
294 # Privoxy's original templates are usually overwritten with each
295 # update. Use this option to relocate customized templates that
296 # should be kept. As template variables might change between
297 # updates, you shouldn't expect templates to work with Privoxy
298 # releases other than the one they were part of, though.
308 # The directory where all logging takes place (i.e. where the
309 # logfile is located).
317 # /var/log/privoxy (Unix) or Privoxy installation dir (Windows)
325 # No trailing "/", please.
335 # The actions file(s) to use
339 # Complete file name, relative to confdir
343 # match-all.action # Actions that are applied to all sites and maybe overruled later on.
345 # default.action # Main actions file
347 # user.action # User customizations
351 # No actions are taken at all. More or less neutral proxying.
355 # Multiple actionsfile lines are permitted, and are in fact
358 # The default values are default.action, which is the "main"
359 # actions file maintained by the developers, and user.action,
360 # where you can make your personal additions.
362 # Actions files contain all the per site and per URL configuration
363 # for ad blocking, cookie management, privacy considerations,
364 # etc. There is no point in using Privoxy without at least one
367 # Note that since Privoxy 3.0.7, the complete filename, including
368 # the ".action" extension has to be specified. The syntax change
369 # was necessary to be consistent with the other file options and
370 # to allow previously forbidden characters.
372 actionsfile match-all.action # Actions that are applied to all sites and maybe overruled later on.
373 actionsfile default.action # Main actions file
374 actionsfile user.action # User customizations
382 # The filter file(s) to use
386 # File name, relative to confdir
390 # default.filter (Unix) or default.filter.txt (Windows)
394 # No textual content filtering takes place, i.e. all +filter{name}
395 # actions in the actions files are turned neutral.
399 # Multiple filterfile lines are permitted.
401 # The filter files contain content modification rules that use
402 # regular expressions. These rules permit powerful changes on the
403 # content of Web pages, and optionally the headers as well, e.g.,
404 # you could try to disable your favorite JavaScript annoyances,
405 # re-write the actual displayed text, or just have some fun
406 # playing buzzword bingo with web pages.
408 # The +filter{name} actions rely on the relevant filter (name)
409 # to be defined in a filter file!
411 # A pre-defined filter file called default.filter that contains a
412 # number of useful filters for common problems is included in the
413 # distribution. See the section on the filter action for a list.
415 # It is recommended to place any locally adapted filters into a
416 # separate file, such as user.filter.
418 filterfile default.filter
419 #filterfile user.filter # User customizations
427 # The log file to use
431 # File name, relative to logdir
435 # Unset (commented out). When activated: logfile (Unix) or
436 # privoxy.log (Windows).
440 # No logfile is written.
444 # The logfile is where all logging and error messages are
445 # written. The level of detail and number of messages are set with
446 # the debug option (see below). The logfile can be useful for
447 # tracking down a problem with Privoxy (e.g., it's not blocking
448 # an ad you think it should block) and it can help you to monitor
449 # what your browser is doing.
451 # Depending on the debug options below, the logfile may be a
452 # privacy risk if third parties can get access to it. As most
453 # users will never look at it, Privoxy 3.0.7 and later only log
454 # fatal errors by default.
456 # For most troubleshooting purposes, you will have to change that,
457 # please refer to the debugging section for details.
459 # Your logfile will grow indefinitely, and you will probably
460 # want to periodically remove it. On Unix systems, you can do
461 # this with a cron job (see "man cron"). For Red Hat based Linux
462 # distributions, a logrotate script has been included.
464 # Any log files must be writable by whatever user Privoxy is
465 # being run as (on Unix, default user id is "privoxy").
475 # The name of the trust file to use
479 # File name, relative to confdir
483 # Unset (commented out). When activated: trust (Unix) or trust.txt
488 # The entire trust mechanism is disabled.
492 # The trust mechanism is an experimental feature for building
493 # white-lists and should be used with care. It is NOT recommended
494 # for the casual user.
496 # If you specify a trust file, Privoxy will only allow access to
497 # sites that are specified in the trustfile. Sites can be listed
498 # in one of two ways:
500 # Prepending a ~ character limits access to this site only (and
501 # any sub-paths within this site), e.g. ~www.example.com allows
502 # access to ~www.example.com/ features/news.html, etc.
504 # Or, you can designate sites as trusted referrers, by prepending
505 # the name with a + character. The effect is that access to
506 # untrusted sites will be granted -- but only if a link from
507 # this trusted referrer was used to get there. The link target
508 # will then be added to the "trustfile" so that future, direct
509 # accesses will be granted. Sites added via this mechanism do
510 # not become trusted referrers themselves (i.e. they are added
511 # with a ~ designation). There is a limit of 512 such entries,
512 # after which new entries will not be made.
514 # If you use the + operator in the trust file, it may grow
515 # considerably over time.
517 # It is recommended that Privoxy be compiled with the
518 # --disable-force, --disable-toggle and --disable-editor options,
519 # if this feature is to be used.
521 # Possible applications include limiting Internet access for
530 # These options are mainly useful when tracing a problem. Note that
531 # you might also want to invoke Privoxy with the --no-daemon command
532 # line option when debugging.
541 # Key values that determine what information gets logged.
549 # 0 (i.e.: only fatal errors (that cause Privoxy to exit) are logged)
553 # Default value is used (see above).
557 # The available debug levels are:
559 # debug 1 # Log the destination for each request Privoxy let through. See also debug 1024.
560 # debug 2 # show each connection status
561 # debug 4 # show I/O status
562 # debug 8 # show header parsing
563 # debug 16 # log all data written to the network into the logfile
564 # debug 32 # debug force feature
565 # debug 64 # debug regular expression filters
566 # debug 128 # debug redirects
567 # debug 256 # debug GIF de-animation
568 # debug 512 # Common Log Format
569 # debug 1024 # Log the destination for requests Privoxy didn't let through, and the reason why.
570 # debug 2048 # CGI user interface
571 # debug 4096 # Startup banner and warnings.
572 # debug 8192 # Non-fatal errors
575 # To select multiple debug levels, you can either add them or
576 # use multiple debug lines.
578 # A debug level of 1 is informative because it will show you each
579 # request as it happens. 1, 1024, 4096 and 8192 are recommended
580 # so that you will notice when things go wrong. The other levels
581 # are probably only of interest if you are hunting down a specific
582 # problem. They can produce a hell of an output (especially 16).
584 # Privoxy used to ship with the debug levels recommended above
585 # enabled by default, but due to privacy concerns 3.0.7 and later
586 # are configured to only log fatal errors.
588 # If you are used to the more verbose settings, simply enable
589 # the debug lines below again.
591 # If you want to use pure CLF (Common Log Format), you should set
592 # "debug 512" ONLY and not enable anything else.
594 # Privoxy has a hard-coded limit for the length of log messages. If
595 # it's reached, messages are logged truncated and marked with
596 # "... [too long, truncated]".
598 # Please don't file any support requests without trying to
599 # reproduce the problem with increased debug level first. Once
600 # you read the log messages, you may even be able to solve the
601 # problem on your own.
603 #debug 1 # Log the destination for each request Privoxy let through.
604 #debug 1024 # Log the destination for requests Privoxy didn't let through, and the reason why.
605 #debug 4096 # Startup banner and warnings
606 #debug 8192 # Non-fatal errors
609 # 3.2. single-threaded
610 # =====================
614 # Whether to run only one server thread.
626 # Multi-threaded (or, where unavailable: forked) operation,
627 # i.e. the ability to serve multiple requests simultaneously.
631 # This option is only there for debugging purposes. It will
632 # drastically reduce performance.
642 # The hostname shown on the CGI pages.
654 # The hostname provided by the operating system is used.
658 # On some misconfigured systems resolving the hostname fails or
659 # takes too much time and slows Privoxy down. Setting a fixed
660 # hostname works around the problem.
662 # In other circumstances it might be desirable to show a hostname
663 # other than the one returned by the operating system. For example
664 # if the system has several different hostnames and you don't
665 # want to use the first one.
667 # Note that Privoxy does not validate the specified hostname value.
669 #hostname hostname.example.org
672 # 4. ACCESS CONTROL AND SECURITY
673 # ===============================
675 # This section of the config file controls the security-relevant
676 # aspects of Privoxy's configuration.
680 # 4.1. listen-address
681 # ====================
685 # The IP address and TCP port on which Privoxy will listen for
698 # Bind to 127.0.0.1 (IPv4 localhost), port 8118. This is suitable
699 # and recommended for home users who run Privoxy on the same
700 # machine as their browser.
704 # You will need to configure your browser(s) to this proxy address
707 # If you already have another service running on port 8118, or
708 # if you want to serve requests from other machines (e.g. on your
709 # local network) as well, you will need to override the default.
711 # IPv6 addresses containing colons have to be quoted by brackets.
713 # If you leave out the IP address, Privoxy will bind to all IPv4
714 # interfaces (addresses) on your machine and may become reachable
715 # from the Internet. In that case, consider using access control
716 # lists (ACL's, see below), and/or a firewall.
718 # If you open Privoxy to untrusted users, you will also
719 # want to make sure that the following actions are disabled:
720 # enable-edit-actions and enable-remote-toggle
724 # Suppose you are running Privoxy on a machine which has the
725 # address 192.168.0.1 on your local private network (192.168.0.0)
726 # and has another outside connection with a different address. You
727 # want it to serve requests from inside only:
729 # listen-address 192.168.0.1:8118
732 # Suppose you are running Privoxy on an IPv6-capable machine and
733 # you want it to listen on the IPv6 address of the loopback device:
735 # listen-address [::1]:8118
738 listen-address 127.0.0.1:8118
746 # Initial state of "toggle" status
758 # Act as if toggled on
762 # If set to 0, Privoxy will start in "toggled off" mode,
763 # i.e. mostly behave like a normal, content-neutral proxy
764 # with both ad blocking and content filtering disabled. See
765 # enable-remote-toggle below.
767 # The windows version will only display the toggle icon in the
768 # system tray if this option is present.
773 # 4.3. enable-remote-toggle
774 # ==========================
778 # Whether or not the web-based toggle feature may be used
790 # The web-based toggle feature is disabled.
794 # When toggled off, Privoxy mostly acts like a normal,
795 # content-neutral proxy, i.e. doesn't block ads or filter content.
797 # Access to the toggle feature can not be controlled separately by
798 # "ACLs" or HTTP authentication, so that everybody who can access
799 # Privoxy (see "ACLs" and listen-address above) can toggle it
800 # for all users. So this option is not recommended for multi-user
801 # environments with untrusted users.
803 # Note that malicious client side code (e.g Java) is also capable
804 # of using this option.
806 # As a lot of Privoxy users don't read documentation, this feature
807 # is disabled by default.
809 # Note that you must have compiled Privoxy with support for this
810 # feature, otherwise this option has no effect.
812 enable-remote-toggle 0
815 # 4.4. enable-remote-http-toggle
816 # ===============================
820 # Whether or not Privoxy recognizes special HTTP headers to change
833 # Privoxy ignores special HTTP headers.
837 # When toggled on, the client can change Privoxy's behaviour by
838 # setting special HTTP headers. Currently the only supported
839 # special header is "X-Filter: No", to disable filtering for
840 # the ongoing request, even if it is enabled in one of the
843 # This feature is disabled by default. If you are using Privoxy in
844 # a environment with trusted clients, you may enable this feature
845 # at your discretion. Note that malicious client side code (e.g
846 # Java) is also capable of using this feature.
848 # This option will be removed in future releases as it has been
849 # obsoleted by the more general header taggers.
851 enable-remote-http-toggle 0
854 # 4.5. enable-edit-actions
855 # =========================
859 # Whether or not the web-based actions file editor may be used
871 # The web-based actions file editor is disabled.
875 # Access to the editor can not be controlled separately by
876 # "ACLs" or HTTP authentication, so that everybody who can access
877 # Privoxy (see "ACLs" and listen-address above) can modify its
878 # configuration for all users.
880 # This option is not recommended for environments with untrusted
881 # users and as a lot of Privoxy users don't read documentation,
882 # this feature is disabled by default.
884 # Note that malicious client side code (e.g Java) is also capable
885 # of using the actions editor and you shouldn't enable this
886 # options unless you understand the consequences and are sure
887 # your browser is configured correctly.
889 # Note that you must have compiled Privoxy with support for this
890 # feature, otherwise this option has no effect.
892 enable-edit-actions 0
895 # 4.6. enforce-blocks
896 # ====================
900 # Whether the user is allowed to ignore blocks and can "go there
913 # Blocks are not enforced.
917 # Privoxy is mainly used to block and filter requests as a service
918 # to the user, for example to block ads and other junk that clogs
919 # the pipes. Privoxy's configuration isn't perfect and sometimes
920 # innocent pages are blocked. In this situation it makes sense to
921 # allow the user to enforce the request and have Privoxy ignore
924 # In the default configuration Privoxy's "Blocked" page contains
925 # a "go there anyway" link to adds a special string (the force
926 # prefix) to the request URL. If that link is used, Privoxy
927 # will detect the force prefix, remove it again and let the
930 # Of course Privoxy can also be used to enforce a network
931 # policy. In that case the user obviously should not be able to
932 # bypass any blocks, and that's what the "enforce-blocks" option
933 # is for. If it's enabled, Privoxy hides the "go there anyway"
934 # link. If the user adds the force prefix by hand, it will not
935 # be accepted and the circumvention attempt is logged.
944 # 4.7. ACLs: permit-access and deny-access
945 # =========================================
949 # Who can access what.
953 # src_addr[:port][/src_masklen] [dst_addr[:port][/dst_masklen]]
955 # Where src_addr and dst_addr are IPv4 addresses in dotted
956 # decimal notation or valid DNS names, port is a port number, and
957 # src_masklen and dst_masklen are subnet masks in CIDR notation,
958 # i.e. integer values from 2 to 30 representing the length
959 # (in bits) of the network address. The masks and the whole
960 # destination part are optional.
962 # If your system implements RFC 3493, then src_addr and dst_addr
963 # can be IPv6 addresses delimeted by brackets, port can be a
964 # number or a service name, and src_masklen and dst_masklen can
965 # be a number from 0 to 128.
971 # If no port is specified, any port will match. If no src_masklen
972 # or src_masklen is given, the complete IP address has to match
973 # (i.e. 32 bits for IPv4 and 128 bits for IPv6).
977 # Don't restrict access further than implied by listen-address
981 # Access controls are included at the request of ISPs and systems
982 # administrators, and are not usually needed by individual
983 # users. For a typical home user, it will normally suffice to
984 # ensure that Privoxy only listens on the localhost (127.0.0.1)
985 # or internal (home) network address by means of the listen-address
988 # Please see the warnings in the FAQ that Privoxy is not intended
989 # to be a substitute for a firewall or to encourage anyone to
990 # defer addressing basic security weaknesses.
992 # Multiple ACL lines are OK. If any ACLs are specified, Privoxy
993 # only talks to IP addresses that match at least one permit-access
994 # line and don't match any subsequent deny-access line. In other
995 # words, the last match wins, with the default being deny-access.
997 # If Privoxy is using a forwarder (see forward below) for a
998 # particular destination URL, the dst_addr that is examined is
999 # the address of the forwarder and NOT the address of the ultimate
1000 # target. This is necessary because it may be impossible for the
1001 # local Privoxy to determine the IP address of the ultimate target
1002 # (that's often what gateways are used for).
1004 # You should prefer using IP addresses over DNS names, because
1005 # the address lookups take time. All DNS names must resolve! You
1006 # can not use domain patterns like "*.org" or partial domain
1007 # names. If a DNS name resolves to multiple IP addresses, only
1008 # the first one is used.
1010 # Some systems allows IPv4 client to connect to IPv6 server
1011 # socket. Then the client's IPv4 address will be translated by
1012 # system into IPv6 address space with special prefix ::ffff:0:0/96
1013 # (so called IPv4 mapped IPv6 address). Privoxy can handle it
1014 # and maps such ACL addresses automatically.
1016 # Denying access to particular sites by ACL may have undesired
1017 # side effects if the site in question is hosted on a machine
1018 # which also hosts other sites (most sites are).
1022 # Explicitly define the default behavior if no ACL and
1023 # listen-address are set: "localhost" is OK. The absence of a
1024 # dst_addr implies that all destination addresses are OK:
1026 # permit-access localhost
1029 # Allow any host on the same class C subnet as www.privoxy.org
1030 # access to nothing but www.example.com (or other domains hosted
1031 # on the same system):
1033 # permit-access www.privoxy.org/24 www.example.com/32
1036 # Allow access from any host on the 26-bit subnet 192.168.45.64 to
1037 # anywhere, with the exception that 192.168.45.73 may not access
1038 # the IP address behind www.dirty-stuff.example.com:
1040 # permit-access 192.168.45.64/26
1041 # deny-access 192.168.45.73 www.dirty-stuff.example.com
1043 # Allow access from the IPv4 network 192.0.2.0/24 even if listening
1044 # on an IPv6 wild card address (not supported on all platforms):
1046 # permit-access 192.0.2.0/24
1049 # This is equivalent to the following line even if listening on
1050 # an IPv4 address (not supported on all platforms):
1052 # permit-access [::ffff:192.0.2.0]/120
1056 # ==================
1060 # Maximum size of the buffer for content filtering.
1072 # Use a 4MB (4096 KB) limit.
1076 # For content filtering, i.e. the +filter and +deanimate-gif
1077 # actions, it is necessary that Privoxy buffers the entire document
1078 # body. This can be potentially dangerous, since a server could
1079 # just keep sending data indefinitely and wait for your RAM to
1080 # exhaust -- with nasty consequences. Hence this option.
1082 # When a document buffer size reaches the buffer-limit, it is
1083 # flushed to the client unfiltered and no further attempt to filter
1084 # the rest of the document is made. Remember that there may be
1085 # multiple threads running, which might require up to buffer-limit
1086 # Kbytes each, unless you have enabled "single-threaded" above.
1094 # This feature allows routing of HTTP requests through a chain of
1097 # Forwarding can be used to chain Privoxy with a caching proxy to
1098 # speed up browsing. Using a parent proxy may also be necessary if
1099 # the machine that Privoxy runs on has no direct Internet access.
1101 # Note that parent proxies can severely decrease your privacy
1102 # level. For example a parent proxy could add your IP address to the
1103 # request headers and if it's a caching proxy it may add the "Etag"
1104 # header to revalidation requests again, even though you configured
1105 # Privoxy to remove it. It may also ignore Privoxy's header time
1106 # randomization and use the original values which could be used by
1107 # the server as cookie replacement to track your steps between visits.
1109 # Also specified here are SOCKS proxies. Privoxy supports the SOCKS
1110 # 4 and SOCKS 4A protocols.
1119 # To which parent HTTP proxy specific requests should be routed.
1123 # target_pattern http_parent[:port]
1125 # where target_pattern is a URL pattern that specifies to which
1126 # requests (i.e. URLs) this forward rule shall apply. Use /
1127 # to denote "all URLs". http_parent[:port] is the DNS name or
1128 # IP address of the parent HTTP proxy through which the requests
1129 # should be forwarded, optionally followed by its listening port
1130 # (default: 8000). Use a single dot (.) to denote "no forwarding".
1138 # Don't use parent HTTP proxies.
1142 # If http_parent is ".", then requests are not forwarded to
1143 # another HTTP proxy but are made directly to the web servers.
1145 # http_parent can be a numerical IPv6 address (if RFC 3493 is
1146 # implemented). To prevent clashes with the port delimiter,
1147 # the whole IP address has to be put into brackets. On the other
1148 # hand a target_pattern containing an IPv6 address has to be put
1149 # into angle brackets (normal brackets are reserved for regular
1150 # expressions already).
1152 # Multiple lines are OK, they are checked in sequence, and the
1157 # Everything goes to an example parent proxy, except SSL on port
1158 # 443 (which it doesn't handle):
1160 # forward / parent-proxy.example.org:8080
1164 # Everything goes to our example ISP's caching proxy, except for
1165 # requests to that ISP's sites:
1167 # forward / caching-proxy.isp.example.net:8000
1168 # forward .isp.example.net .
1171 # Parent proxy specified by an IPv6 address:
1173 # foward / [2001:DB8::1]:8000
1176 # Suppose your parent proxy doesn't support IPv6:
1178 # forward / parent-proxy.example.org:8000
1179 # forward ipv6-server.example.org .
1180 # forward <[2-3][0-9a-f][0-9a-f][0-9a-f]:*> .
1183 # 5.2. forward-socks4, forward-socks4a and forward-socks5
1184 # ========================================================
1188 # Through which SOCKS proxy (and optionally to which parent HTTP
1189 # proxy) specific requests should be routed.
1193 # target_pattern socks_proxy[:port] http_parent[:port]
1195 # where target_pattern is a URL pattern that specifies to which
1196 # requests (i.e. URLs) this forward rule shall apply. Use / to
1197 # denote "all URLs". http_parent and socks_proxy are IP addresses
1198 # in dotted decimal notation or valid DNS names (http_parent may
1199 # be "." to denote "no HTTP forwarding"), and the optional port
1200 # parameters are TCP ports, i.e. integer values from 1 to 65535
1208 # Don't use SOCKS proxies.
1212 # Multiple lines are OK, they are checked in sequence, and the
1215 # The difference between forward-socks4 and forward-socks4a
1216 # is that in the SOCKS 4A protocol, the DNS resolution of the
1217 # target hostname happens on the SOCKS server, while in SOCKS 4
1218 # it happens locally.
1220 # With forward-socks5 the DNS resolution will happen on the remote
1223 # socks_proxy and http_parent can be a numerical IPv6 address
1224 # (if RFC 3493 is implemented). To prevent clashes with the port
1225 # delimiter, the whole IP address has to be put into brackets. On
1226 # the other hand a target_pattern containing an IPv6 address has
1227 # to be put into angle brackets (normal brackets are reserved
1228 # for regular expressions already).
1230 # If http_parent is ".", then requests are not forwarded to another
1231 # HTTP proxy but are made (HTTP-wise) directly to the web servers,
1232 # albeit through a SOCKS proxy.
1236 # From the company example.com, direct connections are made to all
1237 # "internal" domains, but everything outbound goes through their
1238 # ISP's proxy by way of example.com's corporate SOCKS 4A gateway
1241 # forward-socks4a / socks-gw.example.com:1080 www-cache.isp.example.net:8080
1242 # forward .example.com .
1245 # A rule that uses a SOCKS 4 gateway for all destinations but no
1246 # HTTP parent looks like this:
1248 # forward-socks4 / socks-gw.example.com:1080 .
1251 # To chain Privoxy and Tor, both running on the same system,
1252 # you would use something like:
1254 # forward-socks5 / 127.0.0.1:9050 .
1257 # The public Tor network can't be used to reach your local network,
1258 # if you need to access local servers you therefore might want
1259 # to make some exceptions:
1261 # forward 192.168.*.*/ .
1262 # forward 10.*.*.*/ .
1263 # forward 127.*.*.*/ .
1266 # Unencrypted connections to systems in these address ranges will
1267 # be as (un) secure as the local network is, but the alternative
1268 # is that you can't reach the local network through Privoxy at
1269 # all. Of course this may actually be desired and there is no
1270 # reason to make these exceptions if you aren't sure you need them.
1272 # If you also want to be able to reach servers in your local
1273 # network by using their names, you will need additional exceptions
1274 # that look like this:
1276 # forward localhost/ .
1281 # 5.3. forwarded-connect-retries
1282 # ===============================
1286 # How often Privoxy retries if a forwarded connection request
1291 # Number of retries.
1299 # Connections forwarded through other proxies are treated like
1300 # direct connections and no retry attempts are made.
1304 # forwarded-connect-retries is mainly interesting for socks4a
1305 # connections, where Privoxy can't detect why the connections
1306 # failed. The connection might have failed because of a DNS timeout
1307 # in which case a retry makes sense, but it might also have failed
1308 # because the server doesn't exist or isn't reachable. In this
1309 # case the retry will just delay the appearance of Privoxy's
1312 # Note that in the context of this option, "forwarded connections"
1313 # includes all connections that Privoxy forwards through other
1314 # proxies. This option is not limited to the HTTP CONNECT method.
1316 # Only use this option, if you are getting lots of
1317 # forwarding-related error messages that go away when you try again
1318 # manually. Start with a small value and check Privoxy's logfile
1319 # from time to time, to see how many retries are usually needed.
1323 # forwarded-connect-retries 1
1325 forwarded-connect-retries 0
1331 # 6.1. accept-intercepted-requests
1332 # =================================
1336 # Whether intercepted requests should be treated as valid.
1348 # Only proxy requests are accepted, intercepted requests are
1349 # treated as invalid.
1353 # If you don't trust your clients and want to force them to use
1354 # Privoxy, enable this option and configure your packet filter
1355 # to redirect outgoing HTTP connections into Privoxy.
1357 # Make sure that Privoxy's own requests aren't redirected as well.
1358 # Additionally take care that Privoxy can't intentionally connect
1359 # to itself, otherwise you could run into redirection loops if
1360 # Privoxy's listening port is reachable by the outside or an
1361 # attacker has access to the pages you visit.
1365 # accept-intercepted-requests 1
1367 accept-intercepted-requests 0
1370 # 6.2. allow-cgi-request-crunching
1371 # =================================
1375 # Whether requests to Privoxy's CGI pages can be blocked or
1388 # Privoxy ignores block and redirect actions for its CGI pages.
1392 # By default Privoxy ignores block or redirect actions for
1393 # its CGI pages. Intercepting these requests can be useful in
1394 # multi-user setups to implement fine-grained access control,
1395 # but it can also render the complete web interface useless and
1396 # make debugging problems painful if done without care.
1398 # Don't enable this option unless you're sure that you really
1403 # allow-cgi-request-crunching 1
1405 allow-cgi-request-crunching 0
1408 # 6.3. split-large-forms
1409 # =======================
1413 # Whether the CGI interface should stay compatible with broken
1426 # The CGI form generate long GET URLs.
1430 # Privoxy's CGI forms can lead to rather long URLs. This isn't
1431 # a problem as far as the HTTP standard is concerned, but it can
1432 # confuse clients with arbitrary URL length limitations.
1434 # Enabling split-large-forms causes Privoxy to divide big forms
1435 # into smaller ones to keep the URL length down. It makes editing
1436 # a lot less convenient and you can no longer submit all changes
1437 # at once, but at least it works around this browser bug.
1439 # If you don't notice any editing problems, there is no reason
1440 # to enable this option, but if one of the submit buttons appears
1441 # to be broken, you should give it a try.
1445 # split-large-forms 1
1450 # 6.4. keep-alive-timeout
1451 # ========================
1455 # Number of seconds after which an open connection will no longer
1468 # Connections are not kept alive.
1472 # This option allows clients to keep the connection to Privoxy
1473 # alive. If the server supports it, Privoxy will keep the
1474 # connection to the server alive as well. Under certain
1475 # circumstances this may result in speed-ups.
1477 # By default, Privoxy will close the connection to the server if
1478 # the client connection gets closed, or if the specified timeout
1479 # has been reached without a new request coming in. This behaviour
1480 # can be changed with the connection-sharing option.
1482 # This option has no effect if Privoxy has been compiled without
1483 # keep-alive support.
1487 # keep-alive-timeout 300
1489 keep-alive-timeout 300
1492 # 6.5. default-server-timeout
1493 # ============================
1497 # Assumed server-side keep-alive timeout if not specified by
1510 # Connections for which the server didn't specify the keep-alive
1511 # timeout are not reused.
1515 # Enabling this option significantly increases the number of
1516 # connections that are reused, provided the keep-alive-timeout
1517 # option is also enabled.
1519 # While it also increases the number of connections problems when
1520 # Privoxy tries to reuse a connection that already has been closed
1521 # on the server side, or is closed while Privoxy is trying to
1522 # reuse it, this should only be a problem if it happens for the
1523 # first request sent by the client. If it happens for requests
1524 # on reused client connections, Privoxy will simply close the
1525 # connection and the client is supposed to retry the request
1526 # without bothering the user.
1528 # Enabling this option is therefore only recommended if the
1529 # connection-sharing option is disabled.
1531 # It is an error to specify a value larger than the
1532 # keep-alive-timeout value.
1534 # This option has no effect if Privoxy has been compiled without
1535 # keep-alive support.
1539 # default-server-timeout 60
1541 #default-server-timeout 60
1543 # 6.6. connection-sharing
1544 # ========================
1548 # Whether or not outgoing connections that have been kept alive
1549 # should be shared between different incoming connections.
1561 # Connections are not shared.
1565 # This option has no effect if Privoxy has been compiled without
1566 # keep-alive support, or if it's disabled.
1570 # Note that reusing connections doesn't necessary cause
1571 # speedups. There are also a few privacy implications you should
1574 # If this option is effective, outgoing connections are shared
1575 # between clients (if there are more than one) and closing the
1576 # browser that initiated the outgoing connection does no longer
1577 # affect the connection between Privoxy and the server unless
1578 # the client's request hasn't been completed yet.
1580 # If the outgoing connection is idle, it will not be closed until
1581 # either Privoxy's or the server's timeout is reached. While
1582 # it's open, the server knows that the system running Privoxy is
1585 # If there are more than one client (maybe even belonging to
1586 # multiple users), they will be able to reuse each others
1587 # connections. This is potentially dangerous in case of
1588 # authentication schemes like NTLM where only the connection
1589 # is authenticated, instead of requiring authentication for
1592 # If there is only a single client, and if said client can keep
1593 # connections alive on its own, enabling this option has next to
1594 # no effect. If the client doesn't support connection keep-alive,
1595 # enabling this option may make sense as it allows Privoxy to keep
1596 # outgoing connections alive even if the client itself doesn't
1599 # You should also be aware that enabling this option increases
1600 # the likelihood of getting the "No server or forwarder data"
1601 # error message, especially if you are using a slow connection
1604 # This option should only be used by experienced users who
1605 # understand the risks and can weight them against the benefits.
1609 # connection-sharing 1
1611 #connection-sharing 1
1614 # 6.7. socket-timeout
1615 # ====================
1619 # Number of seconds after which a socket times out if no data
1632 # A default value of 300 seconds is used.
1636 # For SOCKS requests the timeout currently doesn't start until
1637 # the SOCKS server accepted the request. This will be fixed in
1642 # socket-timeout 300
1647 # 6.8. max-client-connections
1648 # ============================
1652 # Maximum number of client connections that will be served.
1664 # Connections are served until a resource limit is reached.
1668 # Privoxy creates one thread (or process) for every incoming
1669 # client connection that isn't rejected based on the access
1672 # If the system is powerful enough, Privoxy can theoretically deal
1673 # with several hundred (or thousand) connections at the same time,
1674 # but some operating systems enforce resource limits by shutting
1675 # down offending processes and their default limits may be below
1676 # the ones Privoxy would require under heavy load.
1678 # Configuring Privoxy to enforce a connection limit below the
1679 # thread or process limit used by the operating system makes
1680 # sure this doesn't happen. Simply increasing the operating
1681 # system's limit would work too, but if Privoxy isn't the only
1682 # application running on the system, you may actually want to
1683 # limit the resources used by Privoxy.
1685 # If Privoxy is only used by a single trusted user, limiting the
1686 # number of client connections is probably unnecessary. If there
1687 # are multiple possibly untrusted users you probably still want
1688 # to additionally use a packet filter to limit the maximal number
1689 # of incoming connections per client. Otherwise a malicious user
1690 # could intentionally create a high number of connections to
1691 # prevent other users from using Privoxy.
1693 # Obviously using this option only makes sense if you choose a
1694 # limit below the one enforced by the operating system.
1698 # max-client-connections 256
1700 #max-client-connections 256
1703 # 6.9. handle-as-empty-doc-returns-ok
1704 # ====================================
1708 # This is a work-around for Firefox bug 492459: " Websites are no
1709 # longer rendered if SSL requests for JavaScripts are blocked by
1710 # a proxy. " (https:/ /bugzilla.mozilla.org/show_bug.cgi?id=492459)
1714 # The status code Privoxy returns for pages blocked with
1715 # +handle-as-empty-document.
1727 # Privoxy returns a status 403(forbidden) for all blocked pages.
1731 # Privoxy returns a status 200(OK) for pages blocked with
1732 # +handle-as-empty-document and a status 403(Forbidden) for all
1733 # other blocked pages.
1735 handle-as-empty-doc-returns-ok 1
1738 # 7. WINDOWS GUI OPTIONS
1739 # =======================
1741 # Privoxy has a number of options specific to the Windows GUI
1745 # If "activity-animation" is set to 1, the Privoxy icon will animate
1746 # when "Privoxy" is active. To turn off, set to 0.
1748 #activity-animation 1
1750 # If "log-messages" is set to 1, Privoxy will log messages to the
1755 # If "log-buffer-size" is set to 1, the size of the log buffer,
1756 # i.e. the amount of memory used for the log messages displayed in
1757 # the console window, will be limited to "log-max-lines" (see below).
1759 # Warning: Setting this to 0 will result in the buffer to grow
1760 # infinitely and eat up all your memory!
1764 # log-max-lines is the maximum number of lines held in the log
1765 # buffer. See above.
1769 # If "log-highlight-messages" is set to 1, Privoxy will highlight
1770 # portions of the log messages with a bold-faced font:
1772 #log-highlight-messages 1
1774 # The font used in the console window:
1776 #log-font-name Comic Sans MS
1778 # Font size used in the console window:
1782 # "show-on-task-bar" controls whether or not Privoxy will appear as
1783 # a button on the Task bar when minimized:
1787 # If "close-button-minimizes" is set to 1, the Windows close button
1788 # will minimize Privoxy instead of closing the program (close with
1789 # the exit option on the File menu).
1791 #close-button-minimizes 1
1793 # The "hide-console" option is specific to the MS-Win console version
1794 # of Privoxy. If this option is used, Privoxy will disconnect from
1795 # and hide the command console.