1 # Sample Configuration File for Privoxy v3.0.5
3 # $Id: config,v 1.54 2006/09/10 14:57:25 hal9 Exp $
5 # Copyright (C) 2001-2006 Privoxy Developers http://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 the Privoxy configuration. If you modify this file,
28 # you will need to send a couple of requests (of any kind) to the
29 # proxy before any changes take effect.
31 # When starting Privoxy on Unix systems, give the name of this file as
32 # an argument. On Windows systems, Privoxy will look for this file
33 # with the name 'config.txt' in the same directory where Privoxy
37 # II. FORMAT OF THE CONFIGURATION FILE
38 # ====================================
40 # Configuration lines consist of an initial keyword followed by a
41 # list of values, all separated by whitespace (any number of spaces
42 # or tabs). For example,
44 # actionsfile default.action
46 # Indicates that the actionsfile is named 'default.action'.
48 # The '#' indicates a comment. Any part of a line following a '#'
49 # is ignored, except if the '#' is preceded by a '\'.
51 # Thus, by placing a # at the start of an existing configuration line,
52 # you can make it a comment and it will be treated as if it weren't
53 # there. This is called "commenting out" an option and can be useful.
55 # Note that commenting out and option and leaving it at its default
56 # are two completely different things! Most options behave very
57 # differently when unset. See the the "Effect if unset" explanation
58 # in each option's description for details.
60 # Long lines can be continued on the next line by using a `\' as the
65 # 1. LOCAL SET-UP DOCUMENTATION
66 # =============================
68 # If you intend to operate Privoxy for more users than just yourself,
69 # it might be a good idea to let them know how to reach you, what
70 # you block and why you do that, your policies, etc.
79 # Location of the Privoxy User Manual.
83 # A fully qualified URI
91 # http://www.privoxy.org/version/user-manual/ will be used,
92 # where version is the Privoxy version.
96 # The User Manual URI is the single best source of information on
97 # Privoxy, and is used for help links from some of the internal
98 # CGI pages. The manual itself is normally packaged with the
99 # binary distributions, so you probably want to set this to
100 # a locally installed copy. For multi-user setups, you could
101 # provide a copy on a local webserver for all your users and use
102 # the corresponding URL here.
106 # The best all purpose solution is simply to put the full local
107 # PATH to where the User Manual is located:
109 # user-manual /usr/share/doc/privoxy/user-manual
111 # The User Manual is then available to anyone with
112 # access to the proxy, by following the built-in URL:
113 # http://config.privoxy.org/user-manual/ (or the shortcut:
114 # http://p.p/user-manual/).
116 # If the documentation is not on the local system, it can be
117 # accessed from a remote server, as:
119 # user-manual http://example.com/privoxy/user-manual/
123 # If set, this option should be the first option in the config
124 # file, because it is used while the config file is being read.
126 #user-manual http://www.privoxy.org/user-manual/
129 # 1.2. trust-info-url
130 # ===================
134 # A URL to be displayed in the error page that users will see if
135 # access to an untrusted page is denied.
143 # Two example URL are provided
147 # No links are displayed on the "untrusted" error page.
151 # The value of this option only matters if the experimental trust
152 # mechanism has been activated. (See trustfile above.)
154 # If you use the trust mechanism, it is a good idea to write
155 # up some on-line documentation about your trust policy and to
156 # specify the URL(s) here. Use multiple times for multiple URLs.
158 # The URL(s) should be added to the trustfile as well, so users
159 # don't end up locked out from the information on why they were
160 # locked out in the first place!
162 trust-info-url http://www.example.com/why_we_block.html
163 trust-info-url http://www.example.com/what_we_allow.html
171 # An email address to reach the proxy administrator.
183 # No email address is displayed on error pages and the CGI user
188 # If both admin-address and proxy-info-url are unset, the whole
189 # "Local Privoxy Support" box on all generated pages will not
192 #admin-address privoxy-admin@example.com
195 # 1.4. proxy-info-url
196 # ===================
200 # A URL to documentation about the local Privoxy setup,
201 # configuration or policies.
213 # No link to local documentation is displayed on error pages and
214 # the CGI user interface.
218 # If both admin-address and proxy-info-url are unset, the whole
219 # "Local Privoxy Support" box on all generated pages will not
222 # This URL shouldn't be blocked ;-)
224 #proxy-info-url http://www.example.com/proxy-service.html
227 # 2. CONFIGURATION AND LOG FILE LOCATIONS
228 # =======================================
230 # Privoxy can (and normally does) use a number of other files for
231 # additional configuration, help and logging. This section of the
232 # configuration file tells Privoxy where to find those other files.
234 # The user running Privoxy, must have read permission for all
235 # configuration files, and write permission to any files that would
236 # 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
263 # When development goes modular and multi-user, the blocker,
264 # filter, and per-user config will be stored in subdirectories of
265 # "confdir". For now, the configuration directory structure is
266 # flat, except for confdir/templates, where the HTML templates
267 # for CGI output reside (e.g. Privoxy's 404 error page).
277 # The directory where all logging takes place (i.e. where logfile
278 # and jarfile are located)
286 # /var/log/privoxy (Unix) or Privoxy installation dir (Windows)
294 # No trailing "/", please
304 # The actions file(s) to use
308 # File name, relative to confdir, without the .action suffix
312 # standard # Internal purposes, no editing recommended
314 # default # Main actions file
316 # user # User customizations
320 # No actions are taken at all. Simple neutral proxying.
324 # Multiple actionsfile lines are permitted, and are in fact
327 # The default values include standard.action, which is used
328 # for internal purposes and should be loaded, default.action,
329 # which is the "main" actions file maintained by the developers,
330 # and user.action, where you can make your personal additions.
332 # Actions files are where all the per site and per URL
333 # configuration is done for ad blocking, cookie management,
334 # privacy considerations, etc. There is no point in using Privoxy
335 # without at least one actions file.
337 actionsfile standard # Internal purpose, recommended
338 actionsfile default # Main actions file
339 actionsfile user # User customizations
347 # The filter file(s) to use
351 # File name, relative to confdir
355 # default.filter (Unix) or default.filter.txt (Windows)
359 # No textual content filtering takes place, i.e. all +filter{name}
360 # actions in the actions files are turned neutral.
364 # Multiple filterfile lines are permitted.
366 # The filter files contain content modification rules that use
367 # regular expressions. These rules permit powerful changes on
368 # the content of Web pages, and optionally the headers as well,
369 # e.g., you could disable your favorite JavaScript annoyances,
370 # re-write the actual displayed text, or just have some fun
371 # playing buzzword bingo with web pages.
373 # The +filter{name} actions rely on the relevant filter (name)
374 # to be defined in a filter file!
376 # A pre-defined filter file called default.filter that contains a
377 # number of useful filters for common problems is included in the
378 # distribution. See the section on the filter action for a list.
380 # It is recommended to place any locally adapted filters into a
381 # separate file, such as user.filter.
383 filterfile default.filter
384 #filterfile user.filter # User customizations
392 # The log file to use
396 # File name, relative to logdir
400 # logfile (Unix) or privoxy.log (Windows)
404 # No log file is used, all log messages go to the console (STDERR).
408 # The logfile is where all logging and error messages are
409 # written. The level of detail and number of messages are set with
410 # the debug option (see below). The logfile can be useful for
411 # tracking down a problem with Privoxy (e.g., it's not blocking
412 # an ad you think it should block) but in most cases you probably
413 # will never look at it.
415 # Your logfile will grow indefinitely, and you will probably
416 # want to periodically remove it. On Unix systems, you can do
417 # this with a cron job (see "man cron"). For Red Hat, a logrotate
418 # script has been included.
420 # On SuSE Linux systems, you can place a line like
421 # "/var/log/privoxy.* +1024k 644 nobody.nogroup" in /etc/logfiles,
422 # with the effect that cron.daily will automatically archive,
423 # gzip, and empty the log, when it exceeds 1M size.
425 # Any log files must be writable by whatever user Privoxy is
426 # being run as (default on UNIX, user id is "privoxy").
436 # The file to store intercepted cookies in
440 # File name, relative to logdir
444 # Unset (commented out). When activated: jarfile (Unix) or
445 # privoxy.jar (Windows)
449 # Intercepted cookies are not stored in a dedicated log file.
453 # The jarfile may grow to ridiculous sizes over time.
455 # If debug 8 (show header parsing) is enabled, cookies are written
456 # to the logfile with the rest of the headers.
466 # The trust file to use
470 # File name, relative to confdir
474 # Unset (commented out). When activated: trust (Unix) or trust.txt
479 # The entire trust mechanism is turned off.
483 # The trust mechanism is an experimental feature for building
484 # white-lists and should be used with care. It is NOT recommended
485 # for the casual user.
487 # If you specify a trust file, Privoxy will only allow access to
488 # sites that are specified in the trustfile. Sites can be listed
489 # in one of two ways:
491 # Prepending a ~ character limits access to this site only (and
492 # any sub-paths within this site), e.g. ~www.example.com.
494 # Or, you can designate sites as trusted referrers, by prepending
495 # the name with a + character. The effect is that access to
496 # untrusted sites will be granted -- but only if a link from this
497 # trusted referrer was used. The link target will then be added
498 # to the "trustfile" so that future, direct accesses will be
499 # granted. Sites added via this mechanism do not become trusted
500 # referrers themselves (i.e. they are added with a ~ designation).
502 # If you use the + operator in the trust file, it may grow
503 # considerably over time.
505 # It is recommended that Privoxy be compiled with the
506 # --disable-force, --disable-toggle and --disable-editor options,
507 # if this feature is to be used.
509 # Possible applications include limiting Internet access for
518 # These options are mainly useful when tracing a problem. Note that
519 # you might also want to invoke Privoxy with the --no-daemon command
520 # line option when debugging.
529 # Key values that determine what information gets logged to
538 # 12289 (i.e.: URLs plus informational and warning messages)
542 # Nothing gets logged.
546 # The available debug levels are:
548 # debug 1 # show each GET/POST/CONNECT request
549 # debug 2 # show each connection status
550 # debug 4 # show I/O status
551 # debug 8 # show header parsing
552 # debug 16 # log all data into the logfile
553 # debug 32 # debug force feature
554 # debug 64 # debug regular expression filter
555 # debug 128 # debug fast redirects
556 # debug 256 # debug GIF de-animation
557 # debug 512 # Common Log Format
558 # debug 1024 # debug kill pop-ups
559 # debug 2048 # CGI user interface
560 # debug 4096 # Startup banner and warnings.
561 # debug 8192 # Non-fatal errors
563 # To select multiple debug levels, you can either add them or
564 # use multiple debug lines.
566 # A debug level of 1 is informative because it will show you each
567 # request as it happens. 1, 4096 and 8192 are highly recommended
568 # so that you will notice when things go wrong. The other levels
569 # are probably only of interest if you are hunting down a specific
570 # problem. They can produce a hell of an output (especially 16).
572 # The reporting of fatal errors (i.e. ones which crash Privoxy)
573 # is always on and cannot be disabled.
575 # If you want to use CLF (Common Log Format), you should set
576 # "debug 512" ONLY and not enable anything else.
578 debug 1 # show each GET/POST/CONNECT request
579 debug 4096 # Startup banner and warnings
580 debug 8192 # Errors - *we highly recommended enabling this*
583 # 3.2. single-threaded
584 # ====================
588 # Whether to run only one server thread
600 # Multi-threaded (or, where unavailable: forked) operation,
601 # i.e. the ability to serve multiple requests simultaneously.
605 # This option is only there for debug purposes and you should
606 # never need to use it. It will drastically reduce performance.
611 # 4. ACCESS CONTROL AND SECURITY
612 # ==============================
614 # This section of the config file controls the security-relevant
615 # aspects of Privoxy's configuration.
619 # 4.1. listen-address
620 # ===================
624 # The IP address and TCP port on which Privoxy will listen for
637 # Bind to 127.0.0.1 (localhost), port 8118. This is suitable and
638 # recommended for home users who run Privoxy on the same machine
643 # You will need to configure your browser(s) to this proxy address
646 # If you already have another service running on port 8118, or
647 # if you want to serve requests from other machines (e.g. on your
648 # local network) as well, you will need to override the default.
650 # If you leave out the IP address, Privoxy will bind to all
651 # interfaces (addresses) on your machine and may become reachable
652 # from the Internet. In that case, consider using access control
653 # lists (ACL's, see below), and/or a firewall.
655 # If you open Privoxy to untrusted users, you will also want
656 # to turn off the enable-edit-actions and enable-remote-toggle
661 # Suppose you are running Privoxy on a machine which has the
662 # address 192.168.0.1 on your local private network (192.168.0.0)
663 # and has another outside connection with a different address. You
664 # want it to serve requests from inside only:
666 # listen-address 192.168.0.1:8118
668 listen-address 127.0.0.1:8118
676 # Initial state of "toggle" status
688 # Act as if toggled on
692 # If set to 0, Privoxy will start in "toggled off" mode,
693 # i.e. behave like a normal, content-neutral proxy where all ad
694 # blocking, filtering, etc are disabled. See enable-remote-toggle
695 # below. This is not really useful anymore, since toggling is
696 # much easier via the web interface than via editing the conf file.
698 # The windows version will only display the toggle icon in the
699 # system tray if this option is present.
704 # 4.3. enable-remote-toggle
705 # =========================
709 # Whether or not the web-based toggle feature may be used
721 # The web-based toggle feature is disabled.
725 # When toggled off, Privoxy acts like a normal, content-neutral
726 # proxy, i.e. it acts as if none of the actions applied to
729 # For the time being, access to the toggle feature can not be
730 # controlled separately by "ACLs" or HTTP authentication, so that
731 # everybody who can access Privoxy (see "ACLs" and listen-address
732 # above) can toggle it for all users. So this option is not
733 # recommended for multi-user environments with untrusted users.
735 # Note that you must have compiled Privoxy with support for this
736 # feature, otherwise this option has no effect.
738 enable-remote-toggle 1
741 # 4.4. enable-remote-http-toggle
742 # ==============================
746 # Whether or not Privoxy recognizes special HTTP headers to change
759 # Privoxy ignores special HTTP headers.
763 # When toggled on, the client can change Privoxy's behaviour by
764 # setting special HTTP headers. Currently the only supported
765 # special header is "X-Filter: No", to disable filtering for
766 # the ongoing request, even if it is enabled in one of the
769 # If you are using Privoxy in a multi-user environment or with
770 # untrustworthy clients and want to enforce filtering, you will
771 # have to disable this option, otherwise you can ignore it.
773 enable-remote-http-toggle 1
776 # 4.5. enable-edit-actions
777 # ========================
781 # Whether or not the web-based actions file editor may be used
793 # The web-based actions file editor is disabled.
797 # For the time being, access to the editor can not be controlled
798 # separately by "ACLs" or HTTP authentication, so that everybody
799 # who can access Privoxy (see "ACLs" and listen-address above)
800 # can modify its configuration for all users. So this option is
801 # not recommended for multi-user environments with untrusted users.
803 # Note that you must have compiled Privoxy with support for this
804 # feature, otherwise this option has no effect.
806 enable-edit-actions 1
809 # 4.6. ACLs: permit-access and deny-access
810 # ========================================
814 # Who can access what.
818 # src_addr[/src_masklen] [dst_addr[/dst_masklen]]
820 # Where src_addr and dst_addr are IP addresses in dotted decimal
821 # notation or valid DNS names, and src_masklen and dst_masklen are
822 # subnet masks in CIDR notation, i.e. integer values from 2 to 30
823 # representing the length (in bits) of the network address. The
824 # masks and the whole destination part are optional.
832 # Don't restrict access further than implied by listen-address
836 # Access controls are included at the request of ISPs and systems
837 # administrators, and are not usually needed by individual
838 # users. For a typical home user, it will normally suffice to
839 # ensure that Privoxy only listens on the localhost (127.0.0.1)
840 # or internal (home) network address by means of the listen-address
843 # Please see the warnings in the FAQ that this proxy is not
844 # intended to be a substitute for a firewall or to encourage
845 # anyone to defer addressing basic security weaknesses.
847 # Multiple ACL lines are OK. If any ACLs are specified, then
848 # the Privoxy talks only to IP addresses that match at least one
849 # permit-access line and don't match any subsequent deny-access
850 # line. In other words, the last match wins, with the default
853 # If Privoxy is using a forwarder (see forward below) for a
854 # particular destination URL, the dst_addr that is examined is
855 # the address of the forwarder and NOT the address of the ultimate
856 # target. This is necessary because it may be impossible for the
857 # local Privoxy to determine the IP address of the ultimate target
858 # (that's often what gateways are used for).
860 # You should prefer using IP addresses over DNS names, because
861 # the address lookups take time. All DNS names must resolve! You
862 # can not use domain patterns like "*.org" or partial domain
863 # names. If a DNS name resolves to multiple IP addresses, only
864 # the first one is used.
866 # Denying access to particular sites by ACL may have undesired
867 # side effects if the site in question is hosted on a machine
868 # which also hosts other sites.
872 # Explicitly define the default behavior if no ACL and
873 # listen-address are set: "localhost" is OK. The absence of a
874 # dst_addr implies that all destination addresses are OK:
876 # permit-access localhost
878 # Allow any host on the same class C subnet as www.privoxy.org
879 # access to nothing but www.example.com:
881 # permit-access www.privoxy.org/24 www.example.com/32
883 # Allow access from any host on the 26-bit subnet 192.168.45.64
884 # to anywhere, with the exception that 192.168.45.73 may not
885 # access www.dirty-stuff.example.com:
887 # permit-access 192.168.45.64/26
888 # deny-access 192.168.45.73 www.dirty-stuff.example.com
897 # Maximum size of the buffer for content filtering.
909 # Use a 4MB (4096 KB) limit.
913 # For content filtering, i.e. the +filter and +deanimate-gif
914 # actions, it is necessary that Privoxy buffers the entire document
915 # body. This can be potentially dangerous, since a server could
916 # just keep sending data indefinitely and wait for your RAM to
917 # exhaust -- with nasty consequences. Hence this option.
919 # When a document buffer size reaches the buffer-limit, it is
920 # flushed to the client unfiltered and no further attempt to filter
921 # the rest of the document is made. Remember that there may be
922 # multiple threads running, which might require up to buffer-limit
923 # Kbytes each, unless you have enabled "single-threaded" above.
931 # This feature allows routing of HTTP requests through a chain
932 # of multiple proxies. It can be used to better protect privacy
933 # and confidentiality when accessing specific domains by routing
934 # requests to those domains through an anonymous public proxy.
935 # Or to use a caching proxy to speed up browsing. Or chaining to
936 # a parent proxy may be necessary because the machine that Privoxy
937 # runs on has no direct Internet access.
939 # Also specified here are SOCKS proxies. Privoxy supports the SOCKS
940 # 4 and SOCKS 4A protocols.
949 # To which parent HTTP proxy specific requests should be routed.
953 # target_pattern http_parent[:port]
955 # where target_pattern is a URL pattern that specifies to which
956 # requests (i.e. URLs) this forward rule shall apply. Use /
957 # to denote "all URLs". http_parent[:port] is the DNS name or
958 # IP address of the parent HTTP proxy through which the requests
959 # should be forwarded, optionally followed by its listening port
960 # (default: 8080). Use a single dot (.) to denote "no forwarding".
968 # Don't use parent HTTP proxies.
972 # If http_parent is ".", then requests are not forwarded to
973 # another HTTP proxy but are made directly to the web servers.
975 # Multiple lines are OK, they are checked in sequence, and the
980 # Everything goes to an example anonymizing proxy, except SSL on
981 # port 443 (which it doesn't handle):
983 # forward / anon-proxy.example.org:8080
986 # Everything goes to our example ISP's caching proxy, except for
987 # requests to that ISP's sites:
989 # forward / caching-proxy.example-isp.net:8000
990 # forward .example-isp.net .
994 # 5.2. forward-socks4 and forward-socks4a
995 # =======================================
999 # Through which SOCKS proxy (and to which parent HTTP proxy)
1000 # specific requests should be routed.
1004 # target_pattern socks_proxy[:port] http_parent[:port]
1006 # where target_pattern is a URL pattern that specifies to which
1007 # requests (i.e. URLs) this forward rule shall apply. Use / to
1008 # denote "all URLs". http_parent and socks_proxy are IP addresses
1009 # in dotted decimal notation or valid DNS names (http_parent may
1010 # be "." to denote "no HTTP forwarding"), and the optional port
1011 # parameters are TCP ports, i.e. integer values from 1 to 64535
1019 # Don't use SOCKS proxies.
1023 # Multiple lines are OK, they are checked in sequence, and the
1026 # The difference between forward-socks4 and forward-socks4a
1027 # is that in the SOCKS 4A protocol, the DNS resolution of the
1028 # target hostname happens on the SOCKS server, while in SOCKS 4
1029 # it happens locally.
1031 # If http_parent is ".", then requests are not forwarded to another
1032 # HTTP proxy but are made (HTTP-wise) directly to the web servers,
1033 # albeit through a SOCKS proxy.
1037 # From the company example.com, direct connections are made to all
1038 # "internal" domains, but everything outbound goes through their
1039 # ISP's proxy by way of example.com's corporate SOCKS 4A gateway
1042 # forward-socks4a / socks-gw.example.com:1080 www-cache.example-isp.net:8080
1043 # forward .example.com .
1045 # A rule that uses a SOCKS 4 gateway for all destinations but no
1046 # HTTP parent looks like this:
1048 # forward-socks4 / socks-gw.example.com:1080 .
1050 # To chain Privoxy and Tor, both running on the same system,
1051 # you should use the rule:
1053 # forward-socks4a / 127.0.0.1:9050 .
1055 # The public Tor network can't be used to reach your local network,
1056 # therefore it's a good idea to make some exceptions:
1058 # forward 192.168.*.*/ .
1059 # forward 10.*.*.*/ .
1060 # forward 127.*.*.*/ .
1062 # Unencrypted connections to systems in these address ranges will
1063 # be as (un)secure as the local network is, but the alternative is
1064 # that you can't reach the network at all.
1066 # If you also want to be able to reach servers in your local
1067 # network by using their names, you will need additional
1068 # exceptions that look like this:
1070 # forward localhost/ .
1074 # 5.3. forwarded-connect-retries
1075 # ==============================
1079 # How often Privoxy retries if a forwarded connection request
1084 # Number of retries.
1092 # Forwarded connections are treated like direct connections and
1093 # no retry attempts are made.
1097 # forwarded-connect-retries is mainly interesting for socks4a
1098 # connections, where Privoxy can't detect why the connections
1099 # failed. The connection might have failed because of a DNS timeout
1100 # in which case a retry makes sense, but it might also have failed
1101 # because the server doesn't exist or isn't reachable. In this
1102 # case the retry will just delay the appearance of Privoxy's
1105 # Only use this option, if you are getting many forwarding related
1106 # error messages, that go away when you try again manually. Start
1107 # with a small value and check Privoxy's logfile from time to time,
1108 # to see how many retries are usually needed.
1112 # forwarded-connect-retries 1
1114 forwarded-connect-retries 0
1117 # 6. WINDOWS GUI OPTIONS
1118 # ======================
1120 # Privoxy has a number of options specific to the Windows GUI
1124 # If "activity-animation" is set to 1, the Privoxy icon will animate
1125 # when "Privoxy" is active. To turn off, set to 0.
1127 #activity-animation 1
1129 # If "log-messages" is set to 1, Privoxy will log messages to the
1134 # If "log-buffer-size" is set to 1, the size of the log buffer,
1135 # i.e. the amount of memory used for the log messages displayed in
1136 # the console window, will be limited to "log-max-lines" (see below).
1138 # Warning: Setting this to 0 will result in the buffer to grow
1139 # infinitely and eat up all your memory!
1143 # log-max-lines is the maximum number of lines held in the log
1144 # buffer. See above.
1148 # If "log-highlight-messages" is set to 1, Privoxy will highlight
1149 # portions of the log messages with a bold-faced font:
1151 #log-highlight-messages 1
1153 # The font used in the console window:
1155 #log-font-name Comic Sans MS
1157 # Font size used in the console window:
1161 # "show-on-task-bar" controls whether or not Privoxy will appear as
1162 # a button on the Task bar when minimized:
1166 # If "close-button-minimizes" is set to 1, the Windows close button
1167 # will minimize Privoxy instead of closing the program (close with
1168 # the exit option on the File menu).
1170 #close-button-minimizes 1
1172 # The "hide-console" option is specific to the MS-Win console version
1173 # of Privoxy. If this option is used, Privoxy will disconnect from
1174 # and hide the command console.