1 # Sample Configuration File for Privoxy v3.0.8
3 # $Id: config,v 1.62 2007/12/09 07:51:46 fabiankeil Exp $
5 # Copyright (C) 2001-2008 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
74 # If you intend to operate Privoxy for more users than just yourself,
75 # it might be a good idea to let them know how to reach you, what
76 # you block and why you do that, your policies, etc.
84 # Location of the Privoxy User Manual.
88 # A fully qualified URI
96 # http://www.privoxy.org/version/user-manual/ will be used,
97 # where version is the Privoxy version.
101 # The User Manual URI is the single best source of information on
102 # Privoxy, and is used for help links from some of the internal
103 # CGI pages. The manual itself is normally packaged with the
104 # binary distributions, so you probably want to set this to a
105 # locally installed copy.
109 # The best all purpose solution is simply to put the full local
110 # PATH to where the User Manual is located:
112 # user-manual /usr/share/doc/privoxy/user-manual
115 # The User Manual is then available to anyone with
116 # access to Privoxy, by following the built-in URL:
117 # http://config.privoxy.org/user-manual/ (or the shortcut:
118 # http://p.p/user-manual/).
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/
128 # If set, this option should be the first option in the config
129 # file, because it is used while the config file is being read.
131 #user-manual http://www.privoxy.org/user-manual/
134 # 1.2. trust-info-url
138 # A URL to be displayed in the error page that users will see if
139 # access to an untrusted page is denied.
147 # Two example URLs are provided
151 # No links are displayed on the "untrusted" error page.
155 # The value of this option only matters if the experimental trust
156 # mechanism has been activated. (See trustfile below.)
158 # If you use the trust mechanism, it is a good idea to write
159 # up 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
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
195 #admin-address privoxy-admin@example.com
198 # 1.4. proxy-info-url
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
224 # This URL shouldn't be blocked ;-)
226 #proxy-info-url http://www.example.com/proxy-service.html
229 # 2. CONFIGURATION AND LOG FILE LOCATIONS
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 logfile
300 # and jarfile are 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 # standard.action # Internal purposes, no editing recommended
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 include standard.action, which is used
349 # for internal purposes and should be loaded, default.action,
350 # which is the "main" actions file maintained by the developers,
351 # and user.action, where you can make your personal additions.
353 # Actions files contain all the per site and per URL configuration
354 # for ad blocking, cookie management, privacy considerations,
355 # etc. There is no point in using Privoxy without at least one
358 # Note that since Privoxy 3.0.7, the complete filename, including
359 # the ".action" extension has to be specified. The syntax change
360 # was necessary to be consistent with the other file options and
361 # to allow previously forbidden characters.
363 actionsfile standard.action # Internal purpose, recommended
364 actionsfile default.action # Main actions file
365 actionsfile user.action # User customizations
372 # The filter file(s) to use
376 # File name, relative to confdir
380 # default.filter (Unix) or default.filter.txt (Windows)
384 # No textual content filtering takes place, i.e. all +filter{name}
385 # actions in the actions files are turned neutral.
389 # Multiple filterfile lines are permitted.
391 # The filter files contain content modification rules that use
392 # regular expressions. These rules permit powerful changes on the
393 # content of Web pages, and optionally the headers as well, e.g.,
394 # you could try to disable your favorite JavaScript annoyances,
395 # re-write the actual displayed text, or just have some fun
396 # playing buzzword bingo with web pages.
398 # The +filter{name} actions rely on the relevant filter (name)
399 # to be defined in a filter file!
401 # A pre-defined filter file called default.filter that contains a
402 # number of useful filters for common problems is included in the
403 # distribution. See the section on the filter action for a list.
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 with
435 # the debug option (see below). The logfile can be useful for
436 # tracking down a problem with Privoxy (e.g., it's not blocking
437 # an ad you think it should block) and it can help you to monitor
438 # what your browser is doing.
440 # Depending on the debug options below, the logfile may be a privacy
441 # risk if third parties can get access to it. As most users will never
442 # look at it, Privoxy 3.0.7 and later only log fatal errors by default.
444 # For most troubleshooting purposes, you will have to change that, please
445 # refer to the debugging section for details.
447 # Your logfile will grow indefinitely, and you will probably
448 # want to periodically remove it. On Unix systems, you can do
449 # this with a cron job (see "man cron"). For Red Hat based Linux
450 # distributions, a logrotate script has been included.
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 file to store intercepted cookies in
466 # File name, relative to logdir
470 # Unset (commented out). When activated: jarfile (Unix) or
471 # privoxy.jar (Windows).
475 # Intercepted cookies are not stored in a dedicated log file.
479 # The jarfile may grow to ridiculous sizes over time.
481 # If debug 8 (show header parsing) is enabled, cookies are also
482 # written to the logfile with the rest of the headers. Therefore
483 # this option isn't very useful and may be removed in future
484 # releases. Please report to the developers if you are still
494 # The name of the trust file to use
498 # File name, relative to confdir
502 # Unset (commented out). When activated: trust (Unix) or trust.txt
507 # The entire trust mechanism is disabled.
511 # The trust mechanism is an experimental feature for building
512 # white-lists and should be used with care. It is NOT recommended
513 # for the casual user.
515 # If you specify a trust file, Privoxy will only allow access to
516 # sites that are specified in the trustfile. Sites can be listed
517 # in one of two ways:
519 # Prepending a ~ character limits access to this site only (and
520 # any sub-paths within this site), e.g. ~www.example.com allows
521 # access to ~www.example.com/ features/news.html, etc.
523 # Or, you can designate sites as trusted referrers, by prepending
524 # the name with a + character. The effect is that access to
525 # untrusted sites will be granted -- but only if a link from
526 # this trusted referrer was used to get there. The link target
527 # will then be added to the "trustfile" so that future, direct
528 # accesses will be granted. Sites added via this mechanism do
529 # not become trusted referrers themselves (i.e. they are added
530 # with a ~ designation). There is a limit of 512 such entries,
531 # after which new entries will not be made.
533 # If you use the + operator in the trust file, it may grow
534 # considerably over time.
536 # It is recommended that Privoxy be compiled with the
537 # --disable-force, --disable-toggle and --disable-editor options,
538 # if this feature is to be used.
540 # Possible applications include limiting Internet access for
548 # These options are mainly useful when tracing a problem. Note that
549 # you might also want to invoke Privoxy with the --no-daemon command
550 # line option when debugging.
558 # Key values that determine what information gets logged.
566 # 0 (i.e.: only fatal errors (that cause Privoxy to exit) are logged)
570 # Default value is used (see above).
574 # The available debug levels are:
576 # debug 1 # log each request destination (and the crunch reason if Privoxy intercepted the request)
577 # debug 2 # show each connection status
578 # debug 4 # show I/O status
579 # debug 8 # show header parsing
580 # debug 16 # log all data written to the network into the logfile
581 # debug 32 # debug force feature
582 # debug 64 # debug regular expression filters
583 # debug 128 # debug redirects
584 # debug 256 # debug GIF de-animation
585 # debug 512 # Common Log Format
586 # debug 1024 # debug kill pop-ups
587 # debug 2048 # CGI user interface
588 # debug 4096 # Startup banner and warnings.
589 # debug 8192 # Non-fatal errors
592 # To select multiple debug levels, you can either add them or
593 # use multiple debug lines.
595 # A debug level of 1 is informative because it will show you each
596 # request as it happens. 1, 4096 and 8192 are recommended so that you
597 # will notice when things go wrong. The other levels are probably only
598 # of interest if you are hunting down a specific problem. They can
599 # produce a hell of an output (especially 16).
601 # Privoxy used to ship with the debug levels recommended above enabled
602 # by default, but due to privacy concerns 3.0.7 and later are
603 # configured to only log fatal errors.
605 # If you are used to the more verbose settings, simply enable the debug
608 # If you want to use pure CLF (Common Log Format), you should set
609 # debug 512 ONLY and not enable anything else.
611 # Privoxy has a hard-coded limit for the length of log messages. If
612 # it's reached, messages are logged truncated and marked with
613 # "... [too long, truncated]".
615 # Please don't file any support requests without trying to reproduce
616 # the problem with increased debug level first. Once you read the log
617 # messages, you may even be able to solve the problem on your own.
619 #debug 1 # log each request destination (and the crunch reason if Privoxy intercepted the request)
620 #debug 4096 # Startup banner and warnings
621 #debug 8192 # Non-fatal errors
624 # 3.2. single-threaded
628 # Whether to run only one server thread.
640 # Multi-threaded (or, where unavailable: forked) operation,
641 # i.e. the ability to serve multiple requests simultaneously.
645 # This option is only there for debugging purposes. It will
646 # drastically reduce performance.
651 # 4. ACCESS CONTROL AND SECURITY
653 # This section of the config file controls the security-relevant
654 # aspects of Privoxy's configuration.
658 # 4.1. listen-address
662 # The IP address and TCP port on which Privoxy will listen for
675 # Bind to 127.0.0.1 (localhost), port 8118. This is suitable and
676 # recommended for home users who run Privoxy on the same machine
681 # You will need to configure your browser(s) to this proxy address
684 # If you already have another service running on port 8118, or
685 # if you want to serve requests from other machines (e.g. on your
686 # local network) as well, you will need to override the default.
688 # If you leave out the IP address, Privoxy will bind to all
689 # interfaces (addresses) on your machine and may become reachable
690 # from the Internet. In that case, consider using access control
691 # lists (ACL's, see below), and/or a firewall.
693 # If you open Privoxy to untrusted users, you will also
694 # want to make sure that the following actions are disabled:
695 # enable-edit-actions and enable-remote-toggle
699 # Suppose you are running Privoxy on a machine which has the
700 # address 192.168.0.1 on your local private network (192.168.0.0)
701 # and has another outside connection with a different address. You
702 # want it to serve requests from inside only:
704 # listen-address 192.168.0.1:8118
707 listen-address 127.0.0.1:8118
714 # Initial state of "toggle" status
726 # Act as if toggled on
730 # If set to 0, Privoxy will start in "toggled off" mode,
731 # i.e. mostly behave like a normal, content-neutral proxy
732 # with both ad blocking and content filtering disabled. See
733 # enable-remote-toggle below.
735 # The windows version will only display the toggle icon in the
736 # system tray if this option is present.
741 # 4.3. enable-remote-toggle
745 # Whether or not the web-based toggle feature may be used
757 # The web-based toggle feature is disabled.
761 # When toggled off, Privoxy mostly acts like a normal,
762 # content-neutral proxy, i.e. doesn't block ads or filter content.
764 # Access to the toggle feature can not be controlled separately by
765 # "ACLs" or HTTP authentication, so that everybody who can access
766 # Privoxy (see "ACLs" and listen-address above) can toggle it
767 # for all users. So this option is not recommended for multi-user
768 # environments with untrusted users.
770 # Note that malicious client side code (e.g Java) is also capable
771 # of using this option.
773 # As a lot of Privoxy users don't read documentation, this feature
774 # is disabled by default.
776 # Note that you must have compiled Privoxy with support for this
777 # feature, otherwise this option has no effect.
779 enable-remote-toggle 0
782 # 4.4. enable-remote-http-toggle
786 # Whether or not Privoxy recognizes special HTTP headers to change
799 # Privoxy ignores special HTTP headers.
803 # When toggled on, the client can change Privoxy's behaviour by
804 # setting special HTTP headers. Currently the only supported
805 # special header is "X-Filter: No", to disable filtering for
806 # the ongoing request, even if it is enabled in one of the
809 # This feature is disabled by default. If you are using Privoxy in
810 # a environment with trusted clients, you may enable this feature
811 # at your discretion. Note that malicious client side code (e.g
812 # Java) is also capable of using this feature.
814 # This option will be removed in future releases as it has been
815 # obsoleted by the more general header taggers.
817 enable-remote-http-toggle 0
820 # 4.5. enable-edit-actions
824 # Whether or not the web-based actions file editor may be used
836 # The web-based actions file editor is disabled.
840 # Access to the editor can not be controlled separately by
841 # "ACLs" or HTTP authentication, so that everybody who can access
842 # Privoxy (see "ACLs" and listen-address above) can modify its
843 # configuration for all users.
845 # This option is not recommended for environments with untrusted
846 # users and as a lot of Privoxy users don't read documentation,
847 # this feature is disabled by default.
849 # Note that malicious client side code (e.g Java) is also capable
850 # of using the actions editor and you shouldn't enable this
851 # options unless you understand the consequences and are sure
852 # your browser is configured correctly.
854 # Note that you must have compiled Privoxy with support for this
855 # feature, otherwise this option has no effect.
857 enable-edit-actions 0
860 # 4.6. enforce-blocks
864 # Whether the user is allowed to ignore blocks and can "go there
877 # Blocks are not enforced.
881 # Privoxy is mainly used to block and filter requests as a service
882 # to the user, for example to block ads and other junk that clogs
883 # the pipes. Privoxy's configuration isn't perfect and sometimes
884 # innocent pages are blocked. In this situation it makes sense to
885 # allow the user to enforce the request and have Privoxy ignore
888 # In the default configuration Privoxy's "Blocked" page contains
889 # a "go there anyway" link to adds a special string (the force
890 # prefix) to the request URL. If that link is used, Privoxy
891 # will detect the force prefix, remove it again and let the
894 # Of course Privoxy can also be used to enforce a network
895 # policy. In that case the user obviously should not be able to
896 # bypass any blocks, and that's what the "enforce-blocks" option
897 # is for. If it's enabled, Privoxy hides the "go there anyway"
898 # link. If the user adds the force prefix by hand, it will not
899 # be accepted and the circumvention attempt is logged.
908 # 4.7. ACLs: permit-access and deny-access
912 # Who can access what.
916 # src_addr[/src_masklen] [dst_addr[/dst_masklen]]
918 # Where src_addr and dst_addr are IP addresses in dotted decimal
919 # notation or valid DNS names, and src_masklen and dst_masklen are
920 # subnet masks in CIDR notation, i.e. integer values from 2 to 30
921 # representing the length (in bits) of the network address. The
922 # masks and the whole destination part are optional.
930 # Don't restrict access further than implied by listen-address
934 # Access controls are included at the request of ISPs and systems
935 # administrators, and are not usually needed by individual
936 # users. For a typical home user, it will normally suffice to
937 # ensure that Privoxy only listens on the localhost (127.0.0.1)
938 # or internal (home) network address by means of the listen-address
941 # Please see the warnings in the FAQ that Privoxy is not intended
942 # to be a substitute for a firewall or to encourage anyone to
943 # defer addressing basic security weaknesses.
945 # Multiple ACL lines are OK. If any ACLs are specified, Privoxy
946 # only talks to IP addresses that match at least one permit-access
947 # line and don't match any subsequent deny-access line. In other
948 # words, the last match wins, with the default being deny-access.
950 # If Privoxy is using a forwarder (see forward below) for a
951 # particular destination URL, the dst_addr that is examined is
952 # the address of the forwarder and NOT the address of the ultimate
953 # target. This is necessary because it may be impossible for the
954 # local Privoxy to determine the IP address of the ultimate target
955 # (that's often what gateways are used for).
957 # You should prefer using IP addresses over DNS names, because
958 # the address lookups take time. All DNS names must resolve! You
959 # can not use domain patterns like "*.org" or partial domain
960 # names. If a DNS name resolves to multiple IP addresses, only
961 # the first one is used.
963 # Denying access to particular sites by ACL may have undesired
964 # side effects if the site in question is hosted on a machine
965 # which also hosts other sites (most sites are).
969 # Explicitly define the default behavior if no ACL and
970 # listen-address are set: "localhost" is OK. The absence of a
971 # dst_addr implies that all destination addresses are OK:
973 # permit-access localhost
976 # Allow any host on the same class C subnet as www.privoxy.org
977 # access to nothing but www.example.com (or other domains hosted
978 # on the same system):
980 # permit-access www.privoxy.org/24 www.example.com/32
983 # Allow access from any host on the 26-bit subnet 192.168.45.64 to
984 # anywhere, with the exception that 192.168.45.73 may not access
985 # the IP address behind www.dirty-stuff.example.com:
987 # permit-access 192.168.45.64/26
988 # deny-access 192.168.45.73 www.dirty-stuff.example.com
996 # Maximum size of the buffer for content filtering.
1008 # Use a 4MB (4096 KB) limit.
1012 # For content filtering, i.e. the +filter and +deanimate-gif
1013 # actions, it is necessary that Privoxy buffers the entire document
1014 # body. This can be potentially dangerous, since a server could
1015 # just keep sending data indefinitely and wait for your RAM to
1016 # exhaust -- with nasty consequences. Hence this option.
1018 # When a document buffer size reaches the buffer-limit, it is
1019 # flushed to the client unfiltered and no further attempt to filter
1020 # the rest of the document is made. Remember that there may be
1021 # multiple threads running, which might require up to buffer-limit
1022 # Kbytes each, unless you have enabled "single-threaded" above.
1029 # This feature allows routing of HTTP requests through a chain of
1032 # Forwarding can be used to chain Privoxy with a caching proxy to
1033 # speed up browsing. Using a parent proxy may also be necessary if
1034 # the machine that Privoxy runs on has no direct Internet access.
1036 # Note that parent proxies can severely decrease your privacy
1037 # level. For example a parent proxy could add your IP address to the
1038 # request headers and if it's a caching proxy it may add the "Etag"
1039 # header to revalidation requests again, even though you configured
1040 # Privoxy to remove it. It may also ignore Privoxy's header time
1041 # randomization and use the original values which could be used by
1042 # the server as cookie replacement to track your steps between visits.
1044 # Also specified here are SOCKS proxies. Privoxy supports the SOCKS
1045 # 4 and SOCKS 4A protocols.
1053 # To which parent HTTP proxy specific requests should be routed.
1057 # target_pattern http_parent[:port]
1059 # where target_pattern is a URL pattern that specifies to which
1060 # requests (i.e. URLs) this forward rule shall apply. Use /
1061 # to denote "all URLs". http_parent[:port] is the DNS name or
1062 # IP address of the parent HTTP proxy through which the requests
1063 # should be forwarded, optionally followed by its listening port
1064 # (default: 8080). Use a single dot (.) to denote "no forwarding".
1072 # Don't use parent HTTP proxies.
1076 # If http_parent is ".", then requests are not forwarded to
1077 # another HTTP proxy but are made directly to the web servers.
1079 # Multiple lines are OK, they are checked in sequence, and the
1084 # Everything goes to an example parent proxy, except SSL on port
1085 # 443 (which it doesn't handle):
1087 # forward / parent-proxy.example.org:8080
1091 # Everything goes to our example ISP's caching proxy, except for
1092 # requests to that ISP's sites:
1094 # forward / caching-proxy.isp.example.net:8000
1095 # forward .isp.example.net .
1100 # 5.2. forward-socks4 and forward-socks4a
1104 # Through which SOCKS proxy (and optionally to which parent HTTP
1105 # proxy) specific requests should be routed.
1109 # target_pattern socks_proxy[:port] http_parent[:port]
1111 # where target_pattern is a URL pattern that specifies to which
1112 # requests (i.e. URLs) this forward rule shall apply. Use / to
1113 # denote "all URLs". http_parent and socks_proxy are IP addresses
1114 # in dotted decimal notation or valid DNS names (http_parent may
1115 # be "." to denote "no HTTP forwarding"), and the optional port
1116 # parameters are TCP ports, i.e. integer values from 1 to 64535
1124 # Don't use SOCKS proxies.
1128 # Multiple lines are OK, they are checked in sequence, and the
1131 # The difference between forward-socks4 and forward-socks4a
1132 # is that in the SOCKS 4A protocol, the DNS resolution of the
1133 # target hostname happens on the SOCKS server, while in SOCKS 4
1134 # it happens locally.
1136 # If http_parent is ".", then requests are not forwarded to another
1137 # HTTP proxy but are made (HTTP-wise) directly to the web servers,
1138 # albeit through a SOCKS proxy.
1142 # From the company example.com, direct connections are made to all
1143 # "internal" domains, but everything outbound goes through their
1144 # ISP's proxy by way of example.com's corporate SOCKS 4A gateway
1147 # forward-socks4a / socks-gw.example.com:1080 www-cache.isp.example.net:8080
1148 # forward .example.com .
1151 # A rule that uses a SOCKS 4 gateway for all destinations but no
1152 # HTTP parent looks like this:
1154 # forward-socks4 / socks-gw.example.com:1080 .
1157 # To chain Privoxy and Tor, both running on the same system,
1158 # you would use something like:
1160 # forward-socks4a / 127.0.0.1:9050 .
1163 # The public Tor network can't be used to reach your local network,
1164 # if you need to access local servers you therefore might want
1165 # to make some exceptions:
1167 # forward 192.168.*.*/ .
1168 # forward 10.*.*.*/ .
1169 # forward 127.*.*.*/ .
1172 # Unencrypted connections to systems in these address ranges will
1173 # be as (un) secure as the local network is, but the alternative
1174 # is that you can't reach the local network through Privoxy at
1175 # all. Of course this may actually be desired and there is no
1176 # reason to make these exceptions if you aren't sure you need them.
1178 # If you also want to be able to reach servers in your local
1179 # network by using their names, you will need additional exceptions
1180 # that look like this:
1182 # forward localhost/ .
1187 # 5.3. forwarded-connect-retries
1191 # How often Privoxy retries if a forwarded connection request
1196 # Number of retries.
1204 # Connections forwarded through other proxies are treated like
1205 # direct connections and no retry attempts are made.
1209 # forwarded-connect-retries is mainly interesting for socks4a
1210 # connections, where Privoxy can't detect why the connections
1211 # failed. The connection might have failed because of a DNS timeout
1212 # in which case a retry makes sense, but it might also have failed
1213 # because the server doesn't exist or isn't reachable. In this
1214 # case the retry will just delay the appearance of Privoxy's
1217 # Note that in the context of this option, "forwarded connections"
1218 # includes all connections that Privoxy forwards through other
1219 # proxies. This option is not limited to the HTTP CONNECT method.
1221 # Only use this option, if you are getting lots of
1222 # forwarding-related error messages that go away when you try again
1223 # manually. Start with a small value and check Privoxy's logfile
1224 # from time to time, to see how many retries are usually needed.
1228 # forwarded-connect-retries 1
1230 forwarded-connect-retries 0
1233 # 5.4. accept-intercepted-requests
1237 # Whether intercepted requests should be treated as valid.
1249 # Only proxy requests are accepted, intercepted requests are
1250 # treated as invalid.
1254 # If you don't trust your clients and want to force them to use
1255 # Privoxy, enable this option and configure your packet filter
1256 # to redirect outgoing HTTP connections into Privoxy.
1258 # Make sure that Privoxy's own requests aren't redirected as well.
1259 # Additionally take care that Privoxy can't intentionally connect
1260 # to itself, otherwise you could run into redirection loops if
1261 # Privoxy's listening port is reachable by the outside or an
1262 # attacker has access to the pages you visit.
1266 # accept-intercepted-requests 1
1268 accept-intercepted-requests 0
1271 # 5.5. allow-cgi-request-crunching
1275 # Whether requests to Privoxy's CGI pages can be blocked or
1288 # Privoxy ignores block and redirect actions for its CGI pages.
1292 # By default Privoxy ignores block or redirect actions for
1293 # its CGI pages. Intercepting these requests can be useful in
1294 # multi-user setups to implement fine-grained access control,
1295 # but it can also render the complete web interface useless and
1296 # make debugging problems painful if done without care.
1298 # Don't enable this option unless you're sure that you really
1303 # allow-cgi-request-crunching 1
1305 allow-cgi-request-crunching 0
1308 # 5.6. split-large-forms
1312 # Whether the CGI interface should stay compatible with broken
1325 # The CGI form generate long GET URLs.
1329 # Privoxy's CGI forms can lead to rather long URLs. This isn't
1330 # a problem as far as the HTTP standard is concerned, but it can
1331 # confuse clients with arbitrary URL length limitations.
1333 # Enabling split-large-forms causes Privoxy to divide big forms
1334 # into smaller ones to keep the URL length down. It makes editing
1335 # a lot less convenient and you can no longer submit all changes
1336 # at once, but at least it works around this browser bug.
1338 # If you don't notice any editing problems, there is no reason
1339 # to enable this option, but if one of the submit buttons appears
1340 # to be broken, you should give it a try.
1344 # split-large-forms 1
1349 # 6. WINDOWS GUI OPTIONS
1351 # Privoxy has a number of options specific to the Windows GUI
1355 # If "activity-animation" is set to 1, the Privoxy icon will animate
1356 # when "Privoxy" is active. To turn off, set to 0.
1358 #activity-animation 1
1360 # If "log-messages" is set to 1, Privoxy will log messages to the
1365 # If "log-buffer-size" is set to 1, the size of the log buffer,
1366 # i.e. the amount of memory used for the log messages displayed in
1367 # the console window, will be limited to "log-max-lines" (see below).
1369 # Warning: Setting this to 0 will result in the buffer to grow
1370 # infinitely and eat up all your memory!
1374 # log-max-lines is the maximum number of lines held in the log
1375 # buffer. See above.
1379 # If "log-highlight-messages" is set to 1, Privoxy will highlight
1380 # portions of the log messages with a bold-faced font:
1382 #log-highlight-messages 1
1384 # The font used in the console window:
1386 #log-font-name Comic Sans MS
1388 # Font size used in the console window:
1392 # "show-on-task-bar" controls whether or not Privoxy will appear as
1393 # a button on the Task bar when minimized:
1397 # If "close-button-minimizes" is set to 1, the Windows close button
1398 # will minimize Privoxy instead of closing the program (close with
1399 # the exit option on the File menu).
1401 #close-button-minimizes 1
1403 # The "hide-console" option is specific to the MS-Win console version
1404 # of Privoxy. If this option is used, Privoxy will disconnect from
1405 # and hide the command console.