1 # Sample Configuration File for Privoxy v3.0.11
3 # $Id: config,v 1.68 2008/12/13 18:19:44 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
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.
150 # Two example URLs are provided
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 # standard.action # Internal purposes, no editing recommended
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 include standard.action, which is used
359 # for internal purposes and should be loaded, default.action,
360 # which is the "main" actions file maintained by the developers,
361 # and user.action, where you can make your personal additions.
363 # Actions files contain all the per site and per URL configuration
364 # for ad blocking, cookie management, privacy considerations,
365 # etc. There is no point in using Privoxy without at least one
368 # Note that since Privoxy 3.0.7, the complete filename, including
369 # the ".action" extension has to be specified. The syntax change
370 # was necessary to be consistent with the other file options and
371 # to allow previously forbidden characters.
373 actionsfile standard.action # Internal purpose, recommended
374 actionsfile default.action # Main actions file
375 actionsfile user.action # User customizations
383 # The filter file(s) to use
387 # File name, relative to confdir
391 # default.filter (Unix) or default.filter.txt (Windows)
395 # No textual content filtering takes place, i.e. all +filter{name}
396 # actions in the actions files are turned neutral.
400 # Multiple filterfile lines are permitted.
402 # The filter files contain content modification rules that use
403 # regular expressions. These rules permit powerful changes on the
404 # content of Web pages, and optionally the headers as well, e.g.,
405 # you could try to disable your favorite JavaScript annoyances,
406 # re-write the actual displayed text, or just have some fun
407 # playing buzzword bingo with web pages.
409 # The +filter{name} actions rely on the relevant filter (name)
410 # to be defined in a filter file!
412 # A pre-defined filter file called default.filter that contains a
413 # number of useful filters for common problems is included in the
414 # distribution. See the section on the filter action for a list.
416 # It is recommended to place any locally adapted filters into a
417 # separate file, such as user.filter.
419 filterfile default.filter
420 #filterfile user.filter # User customizations
428 # The log file to use
432 # File name, relative to logdir
436 # Unset (commented out). When activated: logfile (Unix) or
437 # privoxy.log (Windows).
441 # No logfile is written.
445 # The logfile is where all logging and error messages are
446 # written. The level of detail and number of messages are set with
447 # the debug option (see below). The logfile can be useful for
448 # tracking down a problem with Privoxy (e.g., it's not blocking
449 # an ad you think it should block) and it can help you to monitor
450 # what your browser is doing.
452 # Depending on the debug options below, the logfile may be a
453 # privacy risk if third parties can get access to it. As most
454 # users will never look at it, Privoxy 3.0.7 and later only log
455 # fatal errors by default.
457 # For most troubleshooting purposes, you will have to change that,
458 # please refer to the debugging section for details.
460 # Your logfile will grow indefinitely, and you will probably
461 # want to periodically remove it. On Unix systems, you can do
462 # this with a cron job (see "man cron"). For Red Hat based Linux
463 # distributions, a logrotate script has been included.
465 # Any log files must be writable by whatever user Privoxy is
466 # being run as (on Unix, default user id is "privoxy").
476 # The name of the trust file to use
480 # File name, relative to confdir
484 # Unset (commented out). When activated: trust (Unix) or trust.txt
489 # The entire trust mechanism is disabled.
493 # The trust mechanism is an experimental feature for building
494 # white-lists and should be used with care. It is NOT recommended
495 # for the casual user.
497 # If you specify a trust file, Privoxy will only allow access to
498 # sites that are specified in the trustfile. Sites can be listed
499 # in one of two ways:
501 # Prepending a ~ character limits access to this site only (and
502 # any sub-paths within this site), e.g. ~www.example.com allows
503 # access to ~www.example.com/ features/news.html, etc.
505 # Or, you can designate sites as trusted referrers, by prepending
506 # the name with a + character. The effect is that access to
507 # untrusted sites will be granted -- but only if a link from
508 # this trusted referrer was used to get there. The link target
509 # will then be added to the "trustfile" so that future, direct
510 # accesses will be granted. Sites added via this mechanism do
511 # not become trusted referrers themselves (i.e. they are added
512 # with a ~ designation). There is a limit of 512 such entries,
513 # after which new entries will not be made.
515 # If you use the + operator in the trust file, it may grow
516 # considerably over time.
518 # It is recommended that Privoxy be compiled with the
519 # --disable-force, --disable-toggle and --disable-editor options,
520 # if this feature is to be used.
522 # Possible applications include limiting Internet access for
531 # These options are mainly useful when tracing a problem. Note that
532 # you might also want to invoke Privoxy with the --no-daemon command
533 # line option when debugging.
542 # Key values that determine what information gets logged.
550 # 0 (i.e.: only fatal errors (that cause Privoxy to exit) are logged)
554 # Default value is used (see above).
558 # The available debug levels are:
560 # debug 1 # Log the destination for each request Privoxy let through. See also debug 1024.
561 # debug 2 # show each connection status
562 # debug 4 # show I/O status
563 # debug 8 # show header parsing
564 # debug 16 # log all data written to the network into the logfile
565 # debug 32 # debug force feature
566 # debug 64 # debug regular expression filters
567 # debug 128 # debug redirects
568 # debug 256 # debug GIF de-animation
569 # debug 512 # Common Log Format
570 # debug 1024 # Log the destination for requests Privoxy didn't let through, and the reason why.
571 # debug 2048 # CGI user interface
572 # debug 4096 # Startup banner and warnings.
573 # debug 8192 # Non-fatal errors
576 # To select multiple debug levels, you can either add them or
577 # use multiple debug lines.
579 # A debug level of 1 is informative because it will show you each
580 # request as it happens. 1, 4096 and 8192 are recommended so that
581 # you will notice when things go wrong. The other levels are
582 # probably only of interest if you are hunting down a specific
583 # problem. They can produce a hell of an output (especially 16).
585 # Privoxy used to ship with the debug levels recommended above
586 # enabled by default, but due to privacy concerns 3.0.7 and later
587 # are configured to only log fatal errors.
589 # If you are used to the more verbose settings, simply enable
590 # the debug lines below again.
592 # If you want to use pure CLF (Common Log Format), you should set
593 # "debug 512" ONLY and not enable anything else.
595 # Privoxy has a hard-coded limit for the length of log messages. If
596 # it's reached, messages are logged truncated and marked with
597 # "... [too long, truncated]".
599 # Please don't file any support requests without trying to
600 # reproduce the problem with increased debug level first. Once
601 # you read the log messages, you may even be able to solve the
602 # problem on your own.
604 #debug 1 # Log the destination for each request Privoxy let through.
605 #debug 1024 # Log the destination for requests Privoxy didn't let through, and the reason why.
606 #debug 4096 # Startup banner and warnings
607 #debug 8192 # Non-fatal errors
610 # 3.2. single-threaded
611 # =====================
615 # Whether to run only one server thread.
627 # Multi-threaded (or, where unavailable: forked) operation,
628 # i.e. the ability to serve multiple requests simultaneously.
632 # This option is only there for debugging purposes. It will
633 # drastically reduce performance.
643 # The hostname shown on the CGI pages.
655 # The hostname provided by the operating system is used.
659 # On some misconfigured systems resolving the hostname fails or
660 # takes too much time and slows Privoxy down. Setting a fixed
661 # hostname works around the problem.
663 # In other circumstances it might be desirable to show a hostname
664 # other than the one returned by the operating system. For example
665 # if the system has several different hostnames and you don't
666 # want to use the first one.
668 # Note that Privoxy does not validate the specified hostname value.
670 #hostname hostname.example.org
673 # 4. ACCESS CONTROL AND SECURITY
674 # ===============================
676 # This section of the config file controls the security-relevant
677 # aspects of Privoxy's configuration.
681 # 4.1. listen-address
682 # ====================
686 # The IP address and TCP port on which Privoxy will listen for
699 # Bind to 127.0.0.1 (localhost), port 8118. This is suitable and
700 # recommended for home users who run Privoxy on the same machine
705 # You will need to configure your browser(s) to this proxy address
708 # If you already have another service running on port 8118, or
709 # if you want to serve requests from other machines (e.g. on your
710 # local network) as well, you will need to override the default.
712 # If you leave out the IP address, Privoxy will bind to all
713 # interfaces (addresses) on your machine and may become reachable
714 # from the Internet. In that case, consider using access control
715 # lists (ACL's, see below), and/or a firewall.
717 # If you open Privoxy to untrusted users, you will also
718 # want to make sure that the following actions are disabled:
719 # enable-edit-actions and enable-remote-toggle
723 # Suppose you are running Privoxy on a machine which has the
724 # address 192.168.0.1 on your local private network (192.168.0.0)
725 # and has another outside connection with a different address. You
726 # want it to serve requests from inside only:
728 # listen-address 192.168.0.1:8118
731 listen-address 127.0.0.1:8118
739 # Initial state of "toggle" status
751 # Act as if toggled on
755 # If set to 0, Privoxy will start in "toggled off" mode,
756 # i.e. mostly behave like a normal, content-neutral proxy
757 # with both ad blocking and content filtering disabled. See
758 # enable-remote-toggle below.
760 # The windows version will only display the toggle icon in the
761 # system tray if this option is present.
766 # 4.3. enable-remote-toggle
767 # ==========================
771 # Whether or not the web-based toggle feature may be used
783 # The web-based toggle feature is disabled.
787 # When toggled off, Privoxy mostly acts like a normal,
788 # content-neutral proxy, i.e. doesn't block ads or filter content.
790 # Access to the toggle feature can not be controlled separately by
791 # "ACLs" or HTTP authentication, so that everybody who can access
792 # Privoxy (see "ACLs" and listen-address above) can toggle it
793 # for all users. So this option is not recommended for multi-user
794 # environments with untrusted users.
796 # Note that malicious client side code (e.g Java) is also capable
797 # of using this option.
799 # As a lot of Privoxy users don't read documentation, this feature
800 # is disabled by default.
802 # Note that you must have compiled Privoxy with support for this
803 # feature, otherwise this option has no effect.
805 enable-remote-toggle 0
808 # 4.4. enable-remote-http-toggle
809 # ===============================
813 # Whether or not Privoxy recognizes special HTTP headers to change
826 # Privoxy ignores special HTTP headers.
830 # When toggled on, the client can change Privoxy's behaviour by
831 # setting special HTTP headers. Currently the only supported
832 # special header is "X-Filter: No", to disable filtering for
833 # the ongoing request, even if it is enabled in one of the
836 # This feature is disabled by default. If you are using Privoxy in
837 # a environment with trusted clients, you may enable this feature
838 # at your discretion. Note that malicious client side code (e.g
839 # Java) is also capable of using this feature.
841 # This option will be removed in future releases as it has been
842 # obsoleted by the more general header taggers.
844 enable-remote-http-toggle 0
847 # 4.5. enable-edit-actions
848 # =========================
852 # Whether or not the web-based actions file editor may be used
864 # The web-based actions file editor is disabled.
868 # Access to the editor can not be controlled separately by
869 # "ACLs" or HTTP authentication, so that everybody who can access
870 # Privoxy (see "ACLs" and listen-address above) can modify its
871 # configuration for all users.
873 # This option is not recommended for environments with untrusted
874 # users and as a lot of Privoxy users don't read documentation,
875 # this feature is disabled by default.
877 # Note that malicious client side code (e.g Java) is also capable
878 # of using the actions editor and you shouldn't enable this
879 # options unless you understand the consequences and are sure
880 # your browser is configured correctly.
882 # Note that you must have compiled Privoxy with support for this
883 # feature, otherwise this option has no effect.
885 enable-edit-actions 0
888 # 4.6. enforce-blocks
889 # ====================
893 # Whether the user is allowed to ignore blocks and can "go there
906 # Blocks are not enforced.
910 # Privoxy is mainly used to block and filter requests as a service
911 # to the user, for example to block ads and other junk that clogs
912 # the pipes. Privoxy's configuration isn't perfect and sometimes
913 # innocent pages are blocked. In this situation it makes sense to
914 # allow the user to enforce the request and have Privoxy ignore
917 # In the default configuration Privoxy's "Blocked" page contains
918 # a "go there anyway" link to adds a special string (the force
919 # prefix) to the request URL. If that link is used, Privoxy
920 # will detect the force prefix, remove it again and let the
923 # Of course Privoxy can also be used to enforce a network
924 # policy. In that case the user obviously should not be able to
925 # bypass any blocks, and that's what the "enforce-blocks" option
926 # is for. If it's enabled, Privoxy hides the "go there anyway"
927 # link. If the user adds the force prefix by hand, it will not
928 # be accepted and the circumvention attempt is logged.
937 # 4.7. ACLs: permit-access and deny-access
938 # =========================================
942 # Who can access what.
946 # src_addr[/src_masklen] [dst_addr[/dst_masklen]]
948 # Where src_addr and dst_addr are IP addresses in dotted decimal
949 # notation or valid DNS names, and src_masklen and dst_masklen are
950 # subnet masks in CIDR notation, i.e. integer values from 2 to 30
951 # representing the length (in bits) of the network address. The
952 # masks and the whole destination part are optional.
960 # Don't restrict access further than implied by listen-address
964 # Access controls are included at the request of ISPs and systems
965 # administrators, and are not usually needed by individual
966 # users. For a typical home user, it will normally suffice to
967 # ensure that Privoxy only listens on the localhost (127.0.0.1)
968 # or internal (home) network address by means of the listen-address
971 # Please see the warnings in the FAQ that Privoxy is not intended
972 # to be a substitute for a firewall or to encourage anyone to
973 # defer addressing basic security weaknesses.
975 # Multiple ACL lines are OK. If any ACLs are specified, Privoxy
976 # only talks to IP addresses that match at least one permit-access
977 # line and don't match any subsequent deny-access line. In other
978 # words, the last match wins, with the default being deny-access.
980 # If Privoxy is using a forwarder (see forward below) for a
981 # particular destination URL, the dst_addr that is examined is
982 # the address of the forwarder and NOT the address of the ultimate
983 # target. This is necessary because it may be impossible for the
984 # local Privoxy to determine the IP address of the ultimate target
985 # (that's often what gateways are used for).
987 # You should prefer using IP addresses over DNS names, because
988 # the address lookups take time. All DNS names must resolve! You
989 # can not use domain patterns like "*.org" or partial domain
990 # names. If a DNS name resolves to multiple IP addresses, only
991 # the first one is used.
993 # Denying access to particular sites by ACL may have undesired
994 # side effects if the site in question is hosted on a machine
995 # which also hosts other sites (most sites are).
999 # Explicitly define the default behavior if no ACL and
1000 # listen-address are set: "localhost" is OK. The absence of a
1001 # dst_addr implies that all destination addresses are OK:
1003 # permit-access localhost
1006 # Allow any host on the same class C subnet as www.privoxy.org
1007 # access to nothing but www.example.com (or other domains hosted
1008 # on the same system):
1010 # permit-access www.privoxy.org/24 www.example.com/32
1013 # Allow access from any host on the 26-bit subnet 192.168.45.64 to
1014 # anywhere, with the exception that 192.168.45.73 may not access
1015 # the IP address behind www.dirty-stuff.example.com:
1017 # permit-access 192.168.45.64/26
1018 # deny-access 192.168.45.73 www.dirty-stuff.example.com
1023 # ==================
1027 # Maximum size of the buffer for content filtering.
1039 # Use a 4MB (4096 KB) limit.
1043 # For content filtering, i.e. the +filter and +deanimate-gif
1044 # actions, it is necessary that Privoxy buffers the entire document
1045 # body. This can be potentially dangerous, since a server could
1046 # just keep sending data indefinitely and wait for your RAM to
1047 # exhaust -- with nasty consequences. Hence this option.
1049 # When a document buffer size reaches the buffer-limit, it is
1050 # flushed to the client unfiltered and no further attempt to filter
1051 # the rest of the document is made. Remember that there may be
1052 # multiple threads running, which might require up to buffer-limit
1053 # Kbytes each, unless you have enabled "single-threaded" above.
1061 # This feature allows routing of HTTP requests through a chain of
1064 # Forwarding can be used to chain Privoxy with a caching proxy to
1065 # speed up browsing. Using a parent proxy may also be necessary if
1066 # the machine that Privoxy runs on has no direct Internet access.
1068 # Note that parent proxies can severely decrease your privacy
1069 # level. For example a parent proxy could add your IP address to the
1070 # request headers and if it's a caching proxy it may add the "Etag"
1071 # header to revalidation requests again, even though you configured
1072 # Privoxy to remove it. It may also ignore Privoxy's header time
1073 # randomization and use the original values which could be used by
1074 # the server as cookie replacement to track your steps between visits.
1076 # Also specified here are SOCKS proxies. Privoxy supports the SOCKS
1077 # 4 and SOCKS 4A protocols.
1086 # To which parent HTTP proxy specific requests should be routed.
1090 # target_pattern http_parent[:port]
1092 # where target_pattern is a URL pattern that specifies to which
1093 # requests (i.e. URLs) this forward rule shall apply. Use /
1094 # to denote "all URLs". http_parent[:port] is the DNS name or
1095 # IP address of the parent HTTP proxy through which the requests
1096 # should be forwarded, optionally followed by its listening port
1097 # (default: 8080). Use a single dot (.) to denote "no forwarding".
1105 # Don't use parent HTTP proxies.
1109 # If http_parent is ".", then requests are not forwarded to
1110 # another HTTP proxy but are made directly to the web servers.
1112 # Multiple lines are OK, they are checked in sequence, and the
1117 # Everything goes to an example parent proxy, except SSL on port
1118 # 443 (which it doesn't handle):
1120 # forward / parent-proxy.example.org:8080
1124 # Everything goes to our example ISP's caching proxy, except for
1125 # requests to that ISP's sites:
1127 # forward / caching-proxy.isp.example.net:8000
1128 # forward .isp.example.net .
1133 # 5.2. forward-socks4, forward-socks4a and forward-socks5
1134 # ========================================================
1138 # Through which SOCKS proxy (and optionally to which parent HTTP
1139 # proxy) specific requests should be routed.
1143 # target_pattern socks_proxy[:port] http_parent[:port]
1145 # where target_pattern is a URL pattern that specifies to which
1146 # requests (i.e. URLs) this forward rule shall apply. Use / to
1147 # denote "all URLs". http_parent and socks_proxy are IP addresses
1148 # in dotted decimal notation or valid DNS names (http_parent may
1149 # be "." to denote "no HTTP forwarding"), and the optional port
1150 # parameters are TCP ports, i.e. integer values from 1 to 65535
1158 # Don't use SOCKS proxies.
1162 # Multiple lines are OK, they are checked in sequence, and the
1165 # The difference between forward-socks4 and forward-socks4a
1166 # is that in the SOCKS 4A protocol, the DNS resolution of the
1167 # target hostname happens on the SOCKS server, while in SOCKS 4
1168 # it happens locally.
1170 # With forward-socks5 the DNS resolution will happen on the remote
1173 # If http_parent is ".", then requests are not forwarded to another
1174 # HTTP proxy but are made (HTTP-wise) directly to the web servers,
1175 # albeit through a SOCKS proxy.
1179 # From the company example.com, direct connections are made to all
1180 # "internal" domains, but everything outbound goes through their
1181 # ISP's proxy by way of example.com's corporate SOCKS 4A gateway
1184 # forward-socks4a / socks-gw.example.com:1080 www-cache.isp.example.net:8080
1185 # forward .example.com .
1188 # A rule that uses a SOCKS 4 gateway for all destinations but no
1189 # HTTP parent looks like this:
1191 # forward-socks4 / socks-gw.example.com:1080 .
1194 # To chain Privoxy and Tor, both running on the same system,
1195 # you would use something like:
1197 # forward-socks4a / 127.0.0.1:9050 .
1200 # The public Tor network can't be used to reach your local network,
1201 # if you need to access local servers you therefore might want
1202 # to make some exceptions:
1204 # forward 192.168.*.*/ .
1205 # forward 10.*.*.*/ .
1206 # forward 127.*.*.*/ .
1209 # Unencrypted connections to systems in these address ranges will
1210 # be as (un) secure as the local network is, but the alternative
1211 # is that you can't reach the local network through Privoxy at
1212 # all. Of course this may actually be desired and there is no
1213 # reason to make these exceptions if you aren't sure you need them.
1215 # If you also want to be able to reach servers in your local
1216 # network by using their names, you will need additional exceptions
1217 # that look like this:
1219 # forward localhost/ .
1224 # 5.3. forwarded-connect-retries
1225 # ===============================
1229 # How often Privoxy retries if a forwarded connection request
1234 # Number of retries.
1242 # Connections forwarded through other proxies are treated like
1243 # direct connections and no retry attempts are made.
1247 # forwarded-connect-retries is mainly interesting for socks4a
1248 # connections, where Privoxy can't detect why the connections
1249 # failed. The connection might have failed because of a DNS timeout
1250 # in which case a retry makes sense, but it might also have failed
1251 # because the server doesn't exist or isn't reachable. In this
1252 # case the retry will just delay the appearance of Privoxy's
1255 # Note that in the context of this option, "forwarded connections"
1256 # includes all connections that Privoxy forwards through other
1257 # proxies. This option is not limited to the HTTP CONNECT method.
1259 # Only use this option, if you are getting lots of
1260 # forwarding-related error messages that go away when you try again
1261 # manually. Start with a small value and check Privoxy's logfile
1262 # from time to time, to see how many retries are usually needed.
1266 # forwarded-connect-retries 1
1268 forwarded-connect-retries 0
1271 # 5.4. accept-intercepted-requests
1272 # =================================
1276 # Whether intercepted requests should be treated as valid.
1288 # Only proxy requests are accepted, intercepted requests are
1289 # treated as invalid.
1293 # If you don't trust your clients and want to force them to use
1294 # Privoxy, enable this option and configure your packet filter
1295 # to redirect outgoing HTTP connections into Privoxy.
1297 # Make sure that Privoxy's own requests aren't redirected as well.
1298 # Additionally take care that Privoxy can't intentionally connect
1299 # to itself, otherwise you could run into redirection loops if
1300 # Privoxy's listening port is reachable by the outside or an
1301 # attacker has access to the pages you visit.
1305 # accept-intercepted-requests 1
1307 accept-intercepted-requests 0
1310 # 5.5. allow-cgi-request-crunching
1311 # =================================
1315 # Whether requests to Privoxy's CGI pages can be blocked or
1328 # Privoxy ignores block and redirect actions for its CGI pages.
1332 # By default Privoxy ignores block or redirect actions for
1333 # its CGI pages. Intercepting these requests can be useful in
1334 # multi-user setups to implement fine-grained access control,
1335 # but it can also render the complete web interface useless and
1336 # make debugging problems painful if done without care.
1338 # Don't enable this option unless you're sure that you really
1343 # allow-cgi-request-crunching 1
1345 allow-cgi-request-crunching 0
1348 # 5.6. split-large-forms
1349 # =======================
1353 # Whether the CGI interface should stay compatible with broken
1366 # The CGI form generate long GET URLs.
1370 # Privoxy's CGI forms can lead to rather long URLs. This isn't
1371 # a problem as far as the HTTP standard is concerned, but it can
1372 # confuse clients with arbitrary URL length limitations.
1374 # Enabling split-large-forms causes Privoxy to divide big forms
1375 # into smaller ones to keep the URL length down. It makes editing
1376 # a lot less convenient and you can no longer submit all changes
1377 # at once, but at least it works around this browser bug.
1379 # If you don't notice any editing problems, there is no reason
1380 # to enable this option, but if one of the submit buttons appears
1381 # to be broken, you should give it a try.
1385 # split-large-forms 1
1390 # 5.7. keep-alive-timeout
1391 # ========================
1395 # Number of seconds after which an open connection will no longer
1408 # Connections are not reused.
1412 # This option has no effect if Privoxy has been compiled without
1413 # keep-alive support.
1417 # keep-alive-timeout 300
1419 keep-alive-timeout 300
1422 # 6. WINDOWS GUI OPTIONS
1423 # =======================
1425 # Privoxy has a number of options specific to the Windows GUI
1429 # If "activity-animation" is set to 1, the Privoxy icon will animate
1430 # when "Privoxy" is active. To turn off, set to 0.
1432 #activity-animation 1
1434 # If "log-messages" is set to 1, Privoxy will log messages to the
1439 # If "log-buffer-size" is set to 1, the size of the log buffer,
1440 # i.e. the amount of memory used for the log messages displayed in
1441 # the console window, will be limited to "log-max-lines" (see below).
1443 # Warning: Setting this to 0 will result in the buffer to grow
1444 # infinitely and eat up all your memory!
1448 # log-max-lines is the maximum number of lines held in the log
1449 # buffer. See above.
1453 # If "log-highlight-messages" is set to 1, Privoxy will highlight
1454 # portions of the log messages with a bold-faced font:
1456 #log-highlight-messages 1
1458 # The font used in the console window:
1460 #log-font-name Comic Sans MS
1462 # Font size used in the console window:
1466 # "show-on-task-bar" controls whether or not Privoxy will appear as
1467 # a button on the Task bar when minimized:
1471 # If "close-button-minimizes" is set to 1, the Windows close button
1472 # will minimize Privoxy instead of closing the program (close with
1473 # the exit option on the File menu).
1475 #close-button-minimizes 1
1477 # The "hide-console" option is specific to the MS-Win console version
1478 # of Privoxy. If this option is used, Privoxy will disconnect from
1479 # and hide the command console.