4 >The Main Configuration File</TITLE
7 CONTENT="Modular DocBook HTML Stylesheet Version 1.64
10 TITLE="Privoxy User Manual"
11 HREF="index.html"><LINK
13 TITLE="Privoxy Configuration"
14 HREF="configuration.html"><LINK
17 HREF="actions-file.html"><LINK
20 HREF="../p_doc.css"></HEAD
39 >Privoxy User Manual</TH
47 HREF="configuration.html"
60 HREF="actions-file.html"
74 >7. The Main Configuration File</A
77 > Again, the main configuration file is named <TT
81 Linux/Unix/BSD and OS/2, and <TT
85 Configuration lines consist of an initial keyword followed by a list of
86 values, all separated by whitespace (any number of spaces or tabs). For
95 >confdir /etc/privoxy</I
101 > Assigns the value <TT
108 > and thus indicates that the configuration
109 directory is named <SPAN
111 >"/etc/privoxy/"</SPAN
114 > All options in the config file except for <TT
121 > are optional. Watch out in the below description
122 for what happens if you leave them unset.</P
124 > The main config file controls all aspects of <SPAN
128 operation that are not location dependent (i.e. they apply universally, no matter
129 where you may be surfing).</P
136 >7.1. Configuration and Log File Locations</A
142 > can (and normally does) use a number of
143 other files for additional configuration, help and logging.
144 This section of the configuration file tells <SPAN
148 where to find those other files. </P
150 > The user running Privoxy, must have read permission for all
151 configuration files, and write permission to any files that would
152 be modified, such as log files.</P
170 >The directory where the other configuration files are located</P
182 >/etc/privoxy (Unix) <I
188 > installation dir (Windows) </P
191 >Effect if unset:</DT
212 > When development goes modular and multi-user, the blocker, filter, and
213 per-user config will be stored in subdirectories of <SPAN
217 For now, the configuration directory structure is flat, except for
220 >confdir/templates</TT
221 >, where the HTML templates for CGI
222 output reside (e.g. <SPAN
248 > The directory where all logging takes place (i.e. where <TT
268 >/var/log/privoxy (Unix) <I
274 > installation dir (Windows) </P
277 >Effect if unset:</DT
307 >7.1.3. actionsfile</A
310 NAME="DEFAULT.ACTION"
313 NAME="STANDARD.ACTION"
328 HREF="actions-file.html"
337 >File name, relative to <TT
356 CLASS="LITERALLAYOUT"
357 > standard # Internal purposes, no editing recommended</P
364 CLASS="LITERALLAYOUT"
365 > default # Main actions file</P
372 CLASS="LITERALLAYOUT"
373 > user # User customizations</P
383 >Effect if unset:</DT
386 > No actions are taken at all. Simple neutral proxying.
396 > lines are permitted, and are in fact recommended!
400 The default values include standard.action, which is used for internal
401 purposes and should be loaded, default.action, which is the
405 > actions file maintained by the developers, and
409 >, where you can make your personal additions.
413 Actions files are where all the per site and per URL configuration is done for
414 ad blocking, cookie management, privacy considerations, etc.
415 There is no point in using <SPAN
419 least one actions file.
431 >7.1.4. filterfile</A
434 NAME="DEFAULT.FILTER"
446 HREF="filter-file.html"
455 >File name, relative to <TT
464 >default.filter (Unix) <I
467 > default.filter.txt (Windows)</P
470 >Effect if unset:</DT
473 > No textual content filtering takes place, i.e. all
477 HREF="actions-file.html#FILTER"
486 actions in the actions files are turned neutral.
494 HREF="filter-file.html"
496 > contains content modification
498 HREF="appendix.html#REGEX"
499 >regular expressions</A
500 >. These rules permit
501 powerful changes on the content of Web pages, e.g., you could disable your favorite
502 JavaScript annoyances, re-write the actual displayed text, or just have some
510 it appears on a Web page.
517 HREF="actions-file.html#FILTER"
526 actions rely on the relevant filter (<TT
532 to be defined in the filter file!
535 > A pre-defined filter file called <TT
539 a bunch of handy filters for common problems is included in the distribution.
540 See the section on the <TT
543 HREF="actions-file.html#FILTER"
570 > The log file to use
577 >File name, relative to <TT
589 > privoxy.log (Windows)</P
592 >Effect if unset:</DT
595 > No log file is used, all log messages go to the console (<TT
605 > The windows version will additionally log to the console.
608 > The logfile is where all logging and error messages are written. The level
609 of detail and number of messages are set with the <TT
613 option (see below). The logfile can be useful for tracking down a problem with
617 > (e.g., it's not blocking an ad you
618 think it should block) but in most cases you probably will never look at it.
621 > Your logfile will grow indefinitely, and you will probably want to
622 periodically remove it. On Unix systems, you can do this with a cron job
626 >). For Red Hat, a <B
630 script has been included.
633 > On SuSE Linux systems, you can place a line like <SPAN
636 +1024k 644 nobody.nogroup"</SPAN
641 the effect that cron.daily will automatically archive, gzip, and empty the
642 log, when it exceeds 1M size.
645 > Any log files must be writable by whatever user <SPAN
649 is being run as (default on UNIX, user id is <SPAN
675 > The file to store intercepted cookies in
682 >File name, relative to <TT
694 > privoxy.jar (Windows)</P
697 >Effect if unset:</DT
700 > Intercepted cookies are not stored at all.
707 > The jarfile may grow to ridiculous sizes over time.
730 > The trust file to use
737 >File name, relative to <TT
748 >Unset (commented out)</I
749 >. When activated: trust (Unix) <I
752 > trust.txt (Windows)</P
755 >Effect if unset:</DT
758 > The whole trust mechanism is turned off.
765 > The trust mechanism is an experimental feature for building white-lists and should
766 be used with care. It is <I
769 > recommended for the casual user.
772 > If you specify a trust file, <SPAN
776 access to sites that are named in the trustfile.
777 You can also mark sites as trusted referrers (with <TT
781 the effect that access to untrusted sites will be granted, if a link from a
782 trusted referrer was used.
783 The link target will then be added to the <SPAN
787 Possible applications include limiting Internet access for children.
793 > operator in the trust file, it may grow considerably over time.
806 >7.2. Local Set-up Documentation</A
809 > If you intend to operate <SPAN
813 than just yourself, it might be a good idea to let them know how to reach
814 you, what you block and why you do that, your policies, etc.
822 >7.2.1. user-manual</A
833 > Location of the <SPAN
843 >A fully qualified URI</P
855 >Effect if unset:</DT
859 HREF="http://www.privoxy.org/user-manual/"
861 >http://www.privoxy.org/<TT
868 will be used, where <TT
883 > The User Manual URI is used for help links from some of the internal CGI pages.
884 The manual itself is normally packaged with the binary distributions, so you probably want
885 to set this to a locally installed copy. For multi-user setups, you could provide a copy on
886 a local webserver for all your users and use the corresponding URL here.
892 > Unix, in local filesystem:
903 >user-manual  file:///usr/share/doc/privoxy-2.9.15/user-manual/</PRE
910 > Any platform, on local webserver (called <SPAN
912 >"local-webserver"</SPAN
924 >user-manual  http://local-webserver/privoxy-user-manual/</PRE
949 > If set, this option should be <I
951 >the first option in the config file</I
953 it is used while the config file is being read.
968 NAME="TRUST-INFO-URL"
969 >7.2.2. trust-info-url</A
980 > A URL to be displayed in the error page that users will see if access to an untrusted page is denied.
993 >Two example URL are provided</P
996 >Effect if unset:</DT
999 > No links are displayed on the "untrusted" error page.
1006 > The value of this option only matters if the experimental trust mechanism has been
1008 HREF="config.html#TRUSTFILE"
1016 > If you use the trust mechanism, it is a good idea to write up some on-line
1017 documentation about your trust policy and to specify the URL(s) here.
1018 Use multiple times for multiple URLs.
1021 > The URL(s) should be added to the trustfile as well, so users don't end up
1022 locked out from the information on why they were locked out in the first place!
1033 NAME="ADMIN-ADDRESS"
1034 >7.2.3. admin-address</A
1039 CLASS="VARIABLELIST"
1045 > An email address to reach the proxy administrator.
1064 >Effect if unset:</DT
1067 > No email address is displayed on error pages and the CGI user interface.
1081 are unset, the whole "Local Privoxy Support" box on all generated pages will
1093 NAME="PROXY-INFO-URL"
1094 >7.2.4. proxy-info-url</A
1099 CLASS="VARIABLELIST"
1105 > A URL to documentation about the local <SPAN
1109 configuration or policies.
1128 >Effect if unset:</DT
1131 > No link to local documentation is displayed on error pages and the CGI user interface.
1145 are unset, the whole "Local Privoxy Support" box on all generated pages will
1149 > This URL shouldn't be blocked ;-)
1165 > These options are mainly useful when tracing a problem.
1166 Note that you might also want to invoke
1174 command line option when debugging.
1187 CLASS="VARIABLELIST"
1193 > Key values that determine what information gets logged to the
1195 HREF="config.html#LOGFILE"
1213 >12289 (i.e.: URLs plus informational and warning messages)</P
1216 >Effect if unset:</DT
1219 > Nothing gets logged.
1226 > The available debug levels are:
1236 CLASS="PROGRAMLISTING"
1237 > debug 1 # show each GET/POST/CONNECT request
1238 debug 2 # show each connection status
1239 debug 4 # show I/O status
1240 debug 8 # show header parsing
1241 debug 16 # log all data into the logfile
1242 debug 32 # debug force feature
1243 debug 64 # debug regular expression filter
1244 debug 128 # debug fast redirects
1245 debug 256 # debug GIF de-animation
1246 debug 512 # Common Log Format
1247 debug 1024 # debug kill pop-ups
1248 debug 4096 # Startup banner and warnings.
1249 debug 8192 # Non-fatal errors</PRE
1256 > To select multiple debug levels, you can either add them or use
1263 > A debug level of 1 is informative because it will show you each request
1266 >1, 4096 and 8192 are highly recommended</I
1268 so that you will notice when things go wrong. The other levels are probably
1269 only of interest if you are hunting down a specific problem. They can produce
1270 a hell of an output (especially 16).
1274 > The reporting of <I
1277 > errors (i.e. ones which crash
1281 >) is always on and cannot be disabled.
1284 > If you want to use CLF (Common Log Format), you should set <SPAN
1291 > and not enable anything else.
1302 NAME="SINGLE-THREADED"
1303 >7.3.2. single-threaded</A
1308 CLASS="VARIABLELIST"
1314 > Whether to run only one server thread
1336 >Effect if unset:</DT
1339 > Multi-threaded (or, where unavailable: forked) operation, i.e. the ability to
1340 serve multiple requests simultaneously.
1347 > This option is only there for debug purposes and you should never
1350 >It will drastically reduce performance.</I
1363 NAME="ACCESS-CONTROL"
1364 >7.4. Access Control and Security</A
1367 > This section of the config file controls the security-relevant aspects
1378 NAME="LISTEN-ADDRESS"
1379 >7.4.1. listen-address</A
1384 CLASS="VARIABLELIST"
1390 > The IP address and TCP port on which <SPAN
1394 listen for client requests.
1420 >Effect if unset:</DT
1423 > Bind to 127.0.0.1 (localhost), port 8118. This is suitable and recommended for
1424 home users who run <SPAN
1427 > on the same machine as
1435 > You will need to configure your browser(s) to this proxy address and port.
1438 > If you already have another service running on port 8118, or if you want to
1439 serve requests from other machines (e.g. on your local network) as well, you
1440 will need to override the default.
1443 > If you leave out the IP address, <SPAN
1447 bind to all interfaces (addresses) on your machine and may become reachable
1448 from the Internet. In that case, consider using access control lists (ACL's)
1452 > below), or a firewall.
1459 > Suppose you are running <SPAN
1463 a machine which has the address 192.168.0.1 on your local private network
1464 (192.168.0.0) and has another outside connection with a different address.
1465 You want it to serve requests from inside only:
1475 CLASS="PROGRAMLISTING"
1476 > listen-address 192.168.0.1:8118</PRE
1497 CLASS="VARIABLELIST"
1503 > Initial state of "toggle" status
1519 >Effect if unset:</DT
1522 > Act as if toggled on
1529 > If set to 0, <SPAN
1535 >"toggled off"</SPAN
1536 > mode, i.e. behave like a normal, content-neutral
1537 proxy where all ad blocking, filtering, etc are disabled. See
1540 >enable-remote-toggle</TT
1541 > below. This is not really useful
1542 anymore, since toggling is much easier via <A
1543 HREF="http://config.privoxy.org/toggle"
1545 >the web interface</A
1553 > The windows version will only display the toggle icon in the system tray
1554 if this option is present.
1565 NAME="ENABLE-REMOTE-TOGGLE"
1566 >7.4.3. enable-remote-toggle</A
1571 CLASS="VARIABLELIST"
1577 > Whether or not the <A
1578 HREF="http://config.privoxy.org/toggle"
1598 >Effect if unset:</DT
1601 > The web-based toggle feature is disabled.
1608 > When toggled off, <SPAN
1611 > acts like a normal,
1612 content-neutral proxy, i.e. it acts as if none of the actions applied to
1616 > For the time being, access to the toggle feature can <I
1620 controlled separately by <SPAN
1623 > or HTTP authentication,
1624 so that everybody who can access <SPAN
1635 toggle it for all users. So this option is <I
1639 for multi-user environments with untrusted users.
1642 > Note that you must have compiled <SPAN
1646 support for this feature, otherwise this option has no effect.
1657 NAME="ENABLE-EDIT-ACTIONS"
1658 >7.4.4. enable-edit-actions</A
1663 CLASS="VARIABLELIST"
1669 > Whether or not the <A
1670 HREF="http://config.privoxy.org/show-status"
1690 >Effect if unset:</DT
1693 > The web-based actions file editor is disabled.
1700 > For the time being, access to the editor can <I
1704 controlled separately by <SPAN
1707 > or HTTP authentication,
1708 so that everybody who can access <SPAN
1719 modify its configuration for all users. So this option is <I
1723 > for multi-user environments with untrusted users.
1726 > Note that you must have compiled <SPAN
1730 support for this feature, otherwise this option has no effect.
1742 >7.4.5. ACLs: permit-access and deny-access</A
1753 CLASS="VARIABLELIST"
1759 > Who can access what.
1801 > are IP addresses in dotted decimal notation or valid
1813 > are subnet masks in CIDR notation, i.e. integer
1814 values from 2 to 30 representing the length (in bits) of the network address. The masks and the whole
1815 destination part are optional.
1828 >Effect if unset:</DT
1831 > Don't restrict access further than implied by <TT
1841 > Access controls are included at the request of ISPs and systems
1842 administrators, and <I
1844 >are not usually needed by individual users</I
1846 For a typical home user, it will normally suffice to ensure that
1850 > only listens on the localhost
1851 (127.0.0.1) or internal (home) network address by means of the
1853 HREF="config.html#LISTEN-ADDRESS"
1862 > Please see the warnings in the FAQ that this proxy is not intended to be a substitute
1863 for a firewall or to encourage anyone to defer addressing basic security
1867 > Multiple ACL lines are OK.
1868 If any ACLs are specified, then the <SPAN
1872 talks only to IP addresses that match at least one <TT
1876 and don't match any subsequent <TT
1879 > line. In other words, the
1880 last match wins, with the default being <TT
1889 > is using a forwarder (see <TT
1893 for a particular destination URL, the <TT
1899 that is examined is the address of the forwarder and <I
1903 of the ultimate target. This is necessary because it may be impossible for the local
1907 > to determine the IP address of the
1908 ultimate target (that's often what gateways are used for).
1911 > You should prefer using IP addresses over DNS names, because the address lookups take
1912 time. All DNS names must resolve! You can <I
1915 > use domain patterns
1919 > or partial domain names. If a DNS name resolves to multiple
1920 IP addresses, only the first one is used.
1923 > Denying access to particular sites by ACL may have undesired side effects
1924 if the site in question is hosted on a machine which also hosts other sites.
1931 > Explicitly define the default behavior if no ACL and
1939 is OK. The absence of a <TT
1948 > destination addresses are OK:
1959 > permit-access localhost</PRE
1966 > Allow any host on the same class C subnet as www.privoxy.org access to
1967 nothing but www.example.com:
1978 > permit-access www.privoxy.org/24 www.example.com/32</PRE
1985 > Allow access from any host on the 26-bit subnet 192.168.45.64 to anywhere,
1986 with the exception that 192.168.45.73 may not access www.dirty-stuff.example.com:
1997 > permit-access 192.168.45.64/26
1998 deny-access 192.168.45.73 www.dirty-stuff.example.com</PRE
2014 >7.4.6. buffer-limit</A
2019 CLASS="VARIABLELIST"
2025 > Maximum size of the buffer for content filtering.
2041 >Effect if unset:</DT
2044 > Use a 4MB (4096 KB) limit.
2051 > For content filtering, i.e. the <TT
2058 > actions, it is necessary that
2062 > buffers the entire document body.
2063 This can be potentially dangerous, since a server could just keep sending
2064 data indefinitely and wait for your RAM to exhaust -- with nasty consequences.
2068 > When a document buffer size reaches the <TT
2072 flushed to the client unfiltered and no further attempt to
2073 filter the rest of the document is made. Remember that there may be multiple threads
2074 running, which might require up to <TT
2081 >, unless you have enabled <SPAN
2083 >"single-threaded"</SPAN
2101 > This feature allows routing of HTTP requests through a chain of
2103 It can be used to better protect privacy and confidentiality when
2104 accessing specific domains by routing requests to those domains
2105 through an anonymous public proxy (see e.g. <A
2106 HREF="http://www.multiproxy.org/anon_list.htm"
2108 >http://www.multiproxy.org/anon_list.htm</A
2110 Or to use a caching proxy to speed up browsing. Or chaining to a parent
2111 proxy may be necessary because the machine that <SPAN
2115 runs on has no direct Internet access.</P
2117 > Also specified here are SOCKS proxies. <SPAN
2121 supports the SOCKS 4 and SOCKS 4A protocols.</P
2133 CLASS="VARIABLELIST"
2139 > To which parent HTTP proxy specific requests should be routed.
2175 > is a domain name pattern (see the
2176 chapter on domain matching in the <TT
2185 > is the address of the parent HTTP proxy
2186 as an IP addresses in dotted decimal notation or as a valid DNS name (or <SPAN
2192 >"no forwarding"</SPAN
2199 > parameters are TCP ports, i.e. integer
2200 values from 1 to 64535
2213 >Effect if unset:</DT
2216 > Don't use parent HTTP proxies.
2231 >, then requests are not
2232 forwarded to another HTTP proxy but are made directly to the web servers.
2235 > Multiple lines are OK, they are checked in sequence, and the last match wins.
2242 > Everything goes to an example anonymizing proxy, except SSL on port 443 (which it doesn't handle):
2253 > forward .* anon-proxy.example.org:8080
2261 > Everything goes to our example ISP's caching proxy, except for requests
2262 to that ISP's sites:
2273 > forward .*. caching-proxy.example-isp.net:8000
2274 forward .example-isp.net .</PRE
2290 >7.5.2. forward-socks4 and forward-socks4a</A
2293 NAME="FORWARD-SOCKS4"
2296 NAME="FORWARD-SOCKS4A"
2301 CLASS="VARIABLELIST"
2307 > Through which SOCKS proxy (and to which parent HTTP proxy) specific requests should be routed.
2354 > is a domain name pattern (see the
2355 chapter on domain matching in the <TT
2370 are IP addresses in dotted decimal notation or valid DNS names (<TT
2381 >"no HTTP forwarding"</SPAN
2382 >), and the optional
2388 > parameters are TCP ports, i.e. integer values from 1 to 64535
2401 >Effect if unset:</DT
2404 > Don't use SOCKS proxies.
2411 > Multiple lines are OK, they are checked in sequence, and the last match wins.
2414 > The difference between <TT
2419 >forward-socks4a</TT
2421 is that in the SOCKS 4A protocol, the DNS resolution of the target hostname happens on the SOCKS
2422 server, while in SOCKS 4 it happens locally.
2433 >, then requests are not
2434 forwarded to another HTTP proxy but are made (HTTP-wise) directly to the web servers, albeit through
2442 > From the company example.com, direct connections are made to all
2446 > domains, but everything outbound goes through
2447 their ISP's proxy by way of example.com's corporate SOCKS 4A gateway to
2459 > forward-socks4a .*. socks-gw.example.com:1080 www-cache.example-isp.net:8080
2460 forward .example.com .</PRE
2467 > A rule that uses a SOCKS 4 gateway for all destinations but no HTTP parent looks like this:
2478 > forward-socks4 .*. socks-gw.example.com:1080 .</PRE
2493 NAME="ADVANCED-FORWARDING-EXAMPLES"
2494 >7.5.3. Advanced Forwarding Examples</A
2497 > If you have links to multiple ISPs that provide various special content
2498 only to their subscribers, you can configure multiple <SPAN
2502 which have connections to the respective ISPs to act as forwarders to each other, so that
2506 > users can see the internal content of all ISPs.</P
2508 > Assume that host-a has a PPP connection to isp-a.net. And host-b has a PPP connection to
2509 isp-b.net. Both run <SPAN
2513 configuration can look like this:</P
2526 forward .isp-b.net host-b:8118</PRE
2543 forward .isp-a.net host-a:8118</PRE
2549 > Now, your users can set their browser's proxy to use either
2550 host-a or host-b and be able to browse the internal content
2551 of both isp-a and isp-b.</P
2553 > If you intend to chain <SPAN
2560 > locally, then chain as
2563 >browser -> squid -> privoxy</TT
2564 > is the recommended way. </P
2566 > Assuming that <SPAN
2573 run on the same box, your squid configuration could then look like this:</P
2583 > # Define Privoxy as parent proxy (without ICP)
2584 cache_peer 127.0.0.1 parent 8118 7 no-query
2586 # Define ACL for protocol FTP
2589 # Do not forward FTP requests to Privoxy
2590 always_direct allow ftp
2592 # Forward all the rest to Privoxy
2593 never_direct allow all</PRE
2599 > You would then need to change your browser's proxy settings to <SPAN
2602 >'s address and port.
2603 Squid normally uses port 3128. If unsure consult <TT
2618 >7.6. Windows GUI Options</A
2624 > has a number of options specific to the
2625 Windows GUI interface:</P
2627 NAME="ACTIVITY-ANIMATION"
2632 >"activity-animation"</SPAN
2637 > icon will animate when
2641 > is active. To turn off, set to 0.</P
2646 CLASS="LITERALLAYOUT"
2649 >activity-animation 1</I
2651 </P
2661 >"log-messages"</SPAN
2666 > will log messages to the console
2672 CLASS="LITERALLAYOUT"
2677 </P
2682 NAME="LOG-BUFFER-SIZE"
2688 >"log-buffer-size"</SPAN
2689 > is set to 1, the size of the log buffer,
2690 i.e. the amount of memory used for the log messages displayed in the
2691 console window, will be limited to <SPAN
2693 >"log-max-lines"</SPAN
2696 > Warning: Setting this to 0 will result in the buffer to grow infinitely and
2697 eat up all your memory!</P
2702 CLASS="LITERALLAYOUT"
2705 >log-buffer-size 1</I
2707 </P
2712 NAME="LOG-MAX-LINES"
2717 >log-max-lines</SPAN
2718 > is the maximum number of lines held
2719 in the log buffer. See above.</P
2724 CLASS="LITERALLAYOUT"
2727 >log-max-lines 200</I
2729 </P
2734 NAME="LOG-HIGHLIGHT-MESSAGES"
2739 >"log-highlight-messages"</SPAN
2744 > will highlight portions of the log
2745 messages with a bold-faced font:</P
2750 CLASS="LITERALLAYOUT"
2753 >log-highlight-messages 1</I
2755 </P
2760 NAME="LOG-FONT-NAME"
2763 > The font used in the console window:</P
2768 CLASS="LITERALLAYOUT"
2771 >log-font-name Comic Sans MS</I
2773 </P
2778 NAME="LOG-FONT-SIZE"
2781 > Font size used in the console window:</P
2786 CLASS="LITERALLAYOUT"
2791 </P
2796 NAME="SHOW-ON-TASK-BAR"
2802 >"show-on-task-bar"</SPAN
2803 > controls whether or not
2807 > will appear as a button on the Task bar
2813 CLASS="LITERALLAYOUT"
2816 >show-on-task-bar 0</I
2818 </P
2823 NAME="CLOSE-BUTTON-MINIMIZES"
2828 >"close-button-minimizes"</SPAN
2829 > is set to 1, the Windows close
2830 button will minimize <SPAN
2833 > instead of closing
2834 the program (close with the exit option on the File menu).</P
2839 CLASS="LITERALLAYOUT"
2842 >close-button-minimizes 1</I
2844 </P
2854 >"hide-console"</SPAN
2855 > option is specific to the MS-Win console
2859 >. If this option is used,
2863 > will disconnect from and hide the
2869 CLASS="LITERALLAYOUT"
2874 </P
2895 HREF="configuration.html"
2911 HREF="actions-file.html"