4 >The Main Configuration File</TITLE
7 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
10 TITLE="Privoxy 3.0.5 User Manual"
11 HREF="index.html"><LINK
13 TITLE="Privoxy Configuration"
14 HREF="configuration.html"><LINK
17 HREF="actions-file.html"><LINK
21 <LINK REL="STYLESHEET" TYPE="text/css" HREF="p_doc.css">
33 SUMMARY="Header navigation table"
42 >Privoxy 3.0.5 User Manual</TH
50 HREF="configuration.html"
64 HREF="actions-file.html"
80 >7. The Main Configuration File</H1
82 > Again, the main configuration file is named <TT
86 Linux/Unix/BSD and OS/2, and <TT
90 Configuration lines consist of an initial keyword followed by a list of
91 values, all separated by whitespace (any number of spaces or tabs). For
102 >confdir /etc/privoxy</I
109 > Assigns the value <TT
116 > and thus indicates that the configuration
117 directory is named <SPAN
119 >"/etc/privoxy/"</SPAN
122 > All options in the config file except for <TT
129 > are optional. Watch out in the below description
130 for what happens if you leave them unset.</P
132 > The main config file controls all aspects of <SPAN
136 operation that are not location dependent (i.e. they apply universally, no matter
137 where you may be surfing).</P
145 >7.1. Local Set-up Documentation</H2
147 > If you intend to operate <SPAN
151 than just yourself, it might be a good idea to let them know how to reach
152 you, what you block and why you do that, your policies, etc.
161 >7.1.1. user-manual</H4
171 > Location of the <SPAN
181 >A fully qualified URI</P
196 >Effect if unset:</DT
200 HREF="http://www.privoxy.org/user-manual/"
202 >http://www.privoxy.org/<TT
209 will be used, where <TT
224 > The User Manual URI is the single best source of information on
228 >, and is used for help links from some
229 of the internal CGI pages. The manual itself is normally packaged with the
230 binary distributions, so you probably want to set this to a locally
237 > The best all purpose solution is simply to put the full local
256 >  user-manual  /usr/share/doc/privoxy/user-manual</PRE
263 > The User Manual is then available to anyone with access to the proxy, by
264 following the built-in URL: <TT
266 >http://config.privoxy.org/user-manual/</TT
268 (or the shortcut: <TT
270 >http://p.p/user-manual/</TT
274 > If the documentation is not on the local system, it can be accessed
275 from a remote server, as:
286 >  user-manual  http://example.com/privoxy/user-manual/</PRE
311 > If set, this option should be <SPAN
315 >the first option in the config
318 >, because it is used while the config file is being read
334 NAME="TRUST-INFO-URL"
336 >7.1.2. trust-info-url</H4
346 > A URL to be displayed in the error page that users will see if access to an untrusted page is denied.
359 >Two example URL are provided</P
362 >Effect if unset:</DT
365 > No links are displayed on the "untrusted" error page.
372 > The value of this option only matters if the experimental trust mechanism has been
374 HREF="config.html#TRUSTFILE"
385 > If you use the trust mechanism, it is a good idea to write up some on-line
386 documentation about your trust policy and to specify the URL(s) here.
387 Use multiple times for multiple URLs.
390 > The URL(s) should be added to the trustfile as well, so users don't end up
391 locked out from the information on why they were locked out in the first place!
404 >7.1.3. admin-address</H4
414 > An email address to reach the proxy administrator.
436 >Effect if unset:</DT
439 > No email address is displayed on error pages and the CGI user interface.
453 are unset, the whole "Local Privoxy Support" box on all generated pages will
465 NAME="PROXY-INFO-URL"
467 >7.1.4. proxy-info-url</H4
477 > A URL to documentation about the local <SPAN
481 configuration or policies.
503 >Effect if unset:</DT
506 > No link to local documentation is displayed on error pages and the CGI user interface.
520 are unset, the whole "Local Privoxy Support" box on all generated pages will
524 > This URL shouldn't be blocked ;-)
538 >7.2. Configuration and Log File Locations</H2
543 > can (and normally does) use a number of
544 other files for additional configuration, help and logging.
545 This section of the configuration file tells <SPAN
549 where to find those other files. </P
551 > The user running <SPAN
555 permission for all configuration files, and write permission to any files
556 that would be modified, such as log files and actions files.</P
574 >The directory where the other configuration files are located</P
586 >/etc/privoxy (Unix) <SPAN
595 > installation dir (Windows) </P
598 >Effect if unset:</DT
642 > The directory where all logging takes place (i.e. where <TT
662 >/var/log/privoxy (Unix) <SPAN
671 > installation dir (Windows) </P
674 >Effect if unset:</DT
708 >7.2.3. actionsfile</H4
710 NAME="DEFAULT.ACTION"
713 NAME="STANDARD.ACTION"
728 HREF="actions-file.html"
737 >File name, relative to <TT
756 CLASS="LITERALLAYOUT"
757 > standard # Internal purposes, no editing recommended</P
764 CLASS="LITERALLAYOUT"
765 > default # Main actions file</P
772 CLASS="LITERALLAYOUT"
773 > user # User customizations</P
783 >Effect if unset:</DT
786 > No actions are taken at all. Simple neutral proxying.
796 > lines are permitted, and are in fact recommended!
800 The default values include standard.action, which is used for internal
801 purposes and should be loaded, default.action, which is the
805 > actions file maintained by the developers, and
809 >, where you can make your personal additions.
813 Actions files are where all the per site and per URL configuration is done for
814 ad blocking, cookie management, privacy considerations, etc.
815 There is no point in using <SPAN
819 least one actions file.
832 >7.2.4. filterfile</H4
834 NAME="DEFAULT.FILTER"
846 HREF="filter-file.html"
855 >File name, relative to <TT
864 >default.filter (Unix) <SPAN
870 > default.filter.txt (Windows)</P
873 >Effect if unset:</DT
876 > No textual content filtering takes place, i.e. all
880 HREF="actions-file.html#FILTER"
889 actions in the actions files are turned neutral.
899 > lines are permitted.
903 HREF="filter-file.html"
905 > contain content modification
907 HREF="appendix.html#REGEX"
908 >regular expressions</A
909 >. These rules permit
910 powerful changes on the content of Web pages, and optionally the headers
911 as well, e.g., you could disable your favorite JavaScript annoyances,
912 re-write the actual displayed text, or just have some fun
913 playing buzzword bingo with web pages.
920 HREF="actions-file.html#FILTER"
929 actions rely on the relevant filter (<TT
935 to be defined in a filter file!
938 > A pre-defined filter file called <TT
942 a number of useful filters for common problems is included in the distribution.
943 See the section on the <TT
946 HREF="actions-file.html#FILTER"
953 > It is recommended to place any locally adapted filters into a separate
980 > The log file to use
987 >File name, relative to <TT
996 >logfile (Unix) <SPAN
1002 > privoxy.log (Windows)</P
1005 >Effect if unset:</DT
1008 > No log file is used, all log messages go to the console (<TT
1018 > The logfile is where all logging and error messages are written. The level
1019 of detail and number of messages are set with the <TT
1023 option (see below). The logfile can be useful for tracking down a problem with
1027 > (e.g., it's not blocking an ad you
1028 think it should block) but in most cases you probably will never look at it.
1031 > Your logfile will grow indefinitely, and you will probably want to
1032 periodically remove it. On Unix systems, you can do this with a cron job
1036 >). For Red Hat, a <B
1040 script has been included.
1043 > On SuSE Linux systems, you can place a line like <SPAN
1045 >"/var/log/privoxy.*
1046 +1024k 644 nobody.nogroup"</SPAN
1051 the effect that cron.daily will automatically archive, gzip, and empty the
1052 log, when it exceeds 1M size.
1055 > Any log files must be writable by whatever user <SPAN
1059 is being run as (default on UNIX, user id is <SPAN
1079 CLASS="VARIABLELIST"
1085 > The file to store intercepted cookies in
1092 >File name, relative to <TT
1101 >Unset (commented out). When activated: jarfile (Unix) <SPAN
1107 > privoxy.jar (Windows)</P
1110 >Effect if unset:</DT
1113 > Intercepted cookies are not stored in a dedicated log file.
1120 > The jarfile may grow to ridiculous sizes over time.
1123 > If debug 8 (show header parsing) is enabled, cookies are
1124 written to the logfile with the rest of the headers.
1137 >7.2.7. trustfile</H4
1141 CLASS="VARIABLELIST"
1147 > The name of the trust file to use
1154 >File name, relative to <TT
1167 >Unset (commented out)</I
1169 >. When activated: trust (Unix) <SPAN
1175 > trust.txt (Windows)</P
1178 >Effect if unset:</DT
1181 > The entire trust mechanism is disabled.
1188 > The trust mechanism is an experimental feature for building white-lists and should
1189 be used with care. It is <SPAN
1195 > recommended for the casual user.
1198 > If you specify a trust file, <SPAN
1202 access to sites that are specified in the trustfile. Sites can be listed
1209 > character limits access to this site
1210 only (and any sub-paths within this site), e.g.
1213 >~www.example.com</TT
1217 >~www.example.com/features/news.html</TT
1221 > Or, you can designate sites as <SPAN
1225 >trusted referrers</I
1228 prepending the name with a <TT
1231 > character. The effect is that
1232 access to untrusted sites will be granted -- but only if a link from this
1233 trusted referrer was used to get there. The link target will then be added
1237 > so that future, direct accesses will be
1238 granted. Sites added via this mechanism do not become trusted referrers
1239 themselves (i.e. they are added with a <TT
1243 There is a limit of 512 such entries, after which new entries will not be
1247 > If you use the <TT
1250 > operator in the trust file, it may grow
1251 considerably over time.
1254 > It is recommended that <SPAN
1260 >--disable-force</TT
1263 >--disable-toggle</TT
1267 > --disable-editor</TT
1268 > options, if this feature is to be
1272 > Possible applications include limiting Internet access for children.
1288 > These options are mainly useful when tracing a problem.
1289 Note that you might also want to invoke
1297 command line option when debugging.
1310 CLASS="VARIABLELIST"
1316 > Key values that determine what information gets logged to the
1318 HREF="config.html#LOGFILE"
1339 >12289 (i.e.: URLs plus informational and warning messages)</P
1342 >Effect if unset:</DT
1345 > Nothing gets logged.
1352 > The available debug levels are:
1362 CLASS="PROGRAMLISTING"
1363 > debug 1 # show each GET/POST/CONNECT request
1364 debug 2 # show each connection status
1365 debug 4 # show I/O status
1366 debug 8 # show header parsing
1367 debug 16 # log all data into the logfile
1368 debug 32 # debug force feature
1369 debug 64 # debug regular expression filter
1370 debug 128 # debug fast redirects
1371 debug 256 # debug GIF de-animation
1372 debug 512 # Common Log Format
1373 debug 1024 # debug kill pop-ups
1374 debug 2048 # CGI user interface
1375 debug 4096 # Startup banner and warnings.
1376 debug 8192 # Non-fatal errors</PRE
1383 > To select multiple debug levels, you can either add them or use
1390 > A debug level of 1 is informative because it will show you each request
1391 as it happens. <SPAN
1395 >1, 4096 and 8192 are highly recommended</I
1398 so that you will notice when things go wrong. The other levels are probably
1399 only of interest if you are hunting down a specific problem. They can produce
1400 a hell of an output (especially 16).
1404 > The reporting of <SPAN
1410 > errors (i.e. ones which crash
1414 >) is always on and cannot be disabled.
1417 > If you want to use CLF (Common Log Format), you should set <SPAN
1427 > and not enable anything else.
1438 NAME="SINGLE-THREADED"
1440 >7.3.2. single-threaded</H4
1444 CLASS="VARIABLELIST"
1450 > Whether to run only one server thread
1478 >Effect if unset:</DT
1481 > Multi-threaded (or, where unavailable: forked) operation, i.e. the ability to
1482 serve multiple requests simultaneously.
1489 > This option is only there for debug purposes and you should never
1490 need to use it. <SPAN
1494 >It will drastically reduce performance.</I
1508 NAME="ACCESS-CONTROL"
1510 >7.4. Access Control and Security</H2
1512 > This section of the config file controls the security-relevant aspects
1523 NAME="LISTEN-ADDRESS"
1525 >7.4.1. listen-address</H4
1529 CLASS="VARIABLELIST"
1535 > The IP address and TCP port on which <SPAN
1539 listen for client requests.
1565 >Effect if unset:</DT
1568 > Bind to 127.0.0.1 (localhost), port 8118. This is suitable and recommended for
1569 home users who run <SPAN
1572 > on the same machine as
1580 > You will need to configure your browser(s) to this proxy address and port.
1583 > If you already have another service running on port 8118, or if you want to
1584 serve requests from other machines (e.g. on your local network) as well, you
1585 will need to override the default.
1588 > If you leave out the IP address, <SPAN
1592 bind to all interfaces (addresses) on your machine and may become reachable
1593 from the Internet. In that case, consider using <A
1594 HREF="config.html#ACLS"
1595 >access control lists</A
1596 > (ACL's, see below), and/or
1603 > to untrusted users, you will
1604 also want to turn off the <TT
1607 HREF="config.html#ENABLE-EDIT-ACTIONS"
1608 >enable-edit-actions</A
1614 HREF="config.html#ENABLE-REMOTE-TOGGLE"
1615 >enable-remote-toggle</A
1625 > Suppose you are running <SPAN
1629 a machine which has the address 192.168.0.1 on your local private network
1630 (192.168.0.0) and has another outside connection with a different address.
1631 You want it to serve requests from inside only:
1641 CLASS="PROGRAMLISTING"
1642 > listen-address 192.168.0.1:8118</PRE
1663 CLASS="VARIABLELIST"
1669 > Initial state of "toggle" status
1685 >Effect if unset:</DT
1688 > Act as if toggled on
1695 > If set to 0, <SPAN
1701 >"toggled off"</SPAN
1702 > mode, i.e. behave like a normal, content-neutral
1703 proxy where all ad blocking, filtering, etc are disabled. See
1706 >enable-remote-toggle</TT
1707 > below. This is not really useful
1708 anymore, since toggling is much easier via <A
1709 HREF="http://config.privoxy.org/toggle"
1711 >the web interface</A
1719 > The windows version will only display the toggle icon in the system tray
1720 if this option is present.
1731 NAME="ENABLE-REMOTE-TOGGLE"
1733 >7.4.3. enable-remote-toggle</H4
1737 CLASS="VARIABLELIST"
1743 > Whether or not the <A
1744 HREF="http://config.privoxy.org/toggle"
1764 >Effect if unset:</DT
1767 > The web-based toggle feature is disabled.
1774 > When toggled off, <SPAN
1777 > acts like a normal,
1778 content-neutral proxy, i.e. it acts as if none of the actions applied to
1782 > For the time being, access to the toggle feature can <SPAN
1789 controlled separately by <SPAN
1792 > or HTTP authentication,
1793 so that everybody who can access <SPAN
1804 toggle it for all users. So this option is <SPAN
1811 for multi-user environments with untrusted users.
1814 > Note that you must have compiled <SPAN
1818 support for this feature, otherwise this option has no effect.
1829 NAME="ENABLE-REMOTE-HTTP-TOGGLE"
1831 >7.4.4. enable-remote-http-toggle</H4
1835 CLASS="VARIABLELIST"
1841 > Whether or not Privoxy recognizes special HTTP headers to change its behaviour.
1857 >Effect if unset:</DT
1860 > Privoxy ignores special HTTP headers.
1867 > When toggled on, the client can change <SPAN
1871 behaviour by setting special HTTP headers. Currently the only supported
1872 special header is <SPAN
1874 >"X-Filter: No"</SPAN
1875 >, to disable filtering for
1876 the ongoing request, even if it is enabled in one of the action files.
1879 > If you are using <SPAN
1883 multi-user environment or with untrustworthy clients and want to
1884 enforce filtering, you will have to disable this option,
1885 otherwise you can ignore it.
1896 NAME="ENABLE-EDIT-ACTIONS"
1898 >7.4.5. enable-edit-actions</H4
1902 CLASS="VARIABLELIST"
1908 > Whether or not the <A
1909 HREF="http://config.privoxy.org/show-status"
1929 >Effect if unset:</DT
1932 > The web-based actions file editor is disabled.
1939 > For the time being, access to the editor can <SPAN
1946 controlled separately by <SPAN
1949 > or HTTP authentication,
1950 so that everybody who can access <SPAN
1961 modify its configuration for all users. So this option is <SPAN
1968 > for multi-user environments with untrusted users.
1971 > Note that you must have compiled <SPAN
1975 support for this feature, otherwise this option has no effect.
1988 >7.4.6. ACLs: permit-access and deny-access</H4
1990 NAME="PERMIT-ACCESS"
1998 CLASS="VARIABLELIST"
2004 > Who can access what.
2046 > are IP addresses in dotted decimal notation or valid
2058 > are subnet masks in CIDR notation, i.e. integer
2059 values from 2 to 30 representing the length (in bits) of the network address. The masks and the whole
2060 destination part are optional.
2076 >Effect if unset:</DT
2079 > Don't restrict access further than implied by <TT
2089 > Access controls are included at the request of ISPs and systems
2090 administrators, and <SPAN
2094 >are not usually needed by individual users</I
2097 For a typical home user, it will normally suffice to ensure that
2101 > only listens on the localhost
2102 (127.0.0.1) or internal (home) network address by means of the
2104 HREF="config.html#LISTEN-ADDRESS"
2116 > Please see the warnings in the FAQ that this proxy is not intended to be a substitute
2117 for a firewall or to encourage anyone to defer addressing basic security
2121 > Multiple ACL lines are OK.
2122 If any ACLs are specified, then the <SPAN
2126 talks only to IP addresses that match at least one <TT
2130 and don't match any subsequent <TT
2133 > line. In other words, the
2134 last match wins, with the default being <TT
2143 > is using a forwarder (see <TT
2147 for a particular destination URL, the <TT
2153 that is examined is the address of the forwarder and <SPAN
2160 of the ultimate target. This is necessary because it may be impossible for the local
2164 > to determine the IP address of the
2165 ultimate target (that's often what gateways are used for).
2168 > You should prefer using IP addresses over DNS names, because the address lookups take
2169 time. All DNS names must resolve! You can <SPAN
2175 > use domain patterns
2179 > or partial domain names. If a DNS name resolves to multiple
2180 IP addresses, only the first one is used.
2183 > Denying access to particular sites by ACL may have undesired side effects
2184 if the site in question is hosted on a machine which also hosts other sites.
2191 > Explicitly define the default behavior if no ACL and
2199 is OK. The absence of a <TT
2211 > destination addresses are OK:
2222 > permit-access localhost</PRE
2229 > Allow any host on the same class C subnet as www.privoxy.org access to
2230 nothing but www.example.com:
2241 > permit-access www.privoxy.org/24 www.example.com/32</PRE
2248 > Allow access from any host on the 26-bit subnet 192.168.45.64 to anywhere,
2249 with the exception that 192.168.45.73 may not access www.dirty-stuff.example.com:
2260 > permit-access 192.168.45.64/26
2261 deny-access 192.168.45.73 www.dirty-stuff.example.com</PRE
2278 >7.4.7. buffer-limit</H4
2282 CLASS="VARIABLELIST"
2288 > Maximum size of the buffer for content filtering.
2304 >Effect if unset:</DT
2307 > Use a 4MB (4096 KB) limit.
2314 > For content filtering, i.e. the <TT
2321 > actions, it is necessary that
2325 > buffers the entire document body.
2326 This can be potentially dangerous, since a server could just keep sending
2327 data indefinitely and wait for your RAM to exhaust -- with nasty consequences.
2331 > When a document buffer size reaches the <TT
2335 flushed to the client unfiltered and no further attempt to
2336 filter the rest of the document is made. Remember that there may be multiple threads
2337 running, which might require up to <TT
2347 >, unless you have enabled <SPAN
2349 >"single-threaded"</SPAN
2365 >7.5. Forwarding</H2
2367 > This feature allows routing of HTTP requests through a chain of
2369 It can be used to better protect privacy and confidentiality when
2370 accessing specific domains by routing requests to those domains
2371 through an anonymous public proxy. Or to use a caching proxy to speed up browsing. Or chaining to a parent
2372 proxy may be necessary because the machine that <SPAN
2376 runs on has no direct Internet access.</P
2378 > Also specified here are SOCKS proxies. <SPAN
2382 supports the SOCKS 4 and SOCKS 4A protocols.</P
2394 CLASS="VARIABLELIST"
2400 > To which parent HTTP proxy specific requests should be routed.
2432 HREF="actions-file.html#AF-PATTERNS"
2435 that specifies to which requests (i.e. URLs) this forward rule shall apply. Use <TT
2454 is the DNS name or IP address of the parent HTTP proxy through which the requests should be forwarded,
2455 optionally followed by its listening port (default: 8080).
2456 Use a single dot (<TT
2461 >"no forwarding"</SPAN
2478 >Effect if unset:</DT
2481 > Don't use parent HTTP proxies.
2496 >, then requests are not
2497 forwarded to another HTTP proxy but are made directly to the web servers.
2500 > Multiple lines are OK, they are checked in sequence, and the last match wins.
2507 > Everything goes to an example anonymizing proxy, except SSL on port 443 (which it doesn't handle):
2518 > forward / anon-proxy.example.org:8080
2526 > Everything goes to our example ISP's caching proxy, except for requests
2527 to that ISP's sites:
2538 > forward / caching-proxy.example-isp.net:8000
2539 forward .example-isp.net .</PRE
2556 >7.5.2. forward-socks4 and forward-socks4a</H4
2558 NAME="FORWARD-SOCKS4"
2561 NAME="FORWARD-SOCKS4A"
2566 CLASS="VARIABLELIST"
2572 > Through which SOCKS proxy (and to which parent HTTP proxy) specific requests should be routed.
2615 HREF="actions-file.html#AF-PATTERNS"
2618 that specifies to which requests (i.e. URLs) this forward rule shall apply. Use <TT
2637 are IP addresses in dotted decimal notation or valid DNS names (<TT
2648 >"no HTTP forwarding"</SPAN
2649 >), and the optional
2655 > parameters are TCP ports, i.e. integer values from 1 to 64535
2671 >Effect if unset:</DT
2674 > Don't use SOCKS proxies.
2681 > Multiple lines are OK, they are checked in sequence, and the last match wins.
2684 > The difference between <TT
2689 >forward-socks4a</TT
2691 is that in the SOCKS 4A protocol, the DNS resolution of the target hostname happens on the SOCKS
2692 server, while in SOCKS 4 it happens locally.
2703 >, then requests are not
2704 forwarded to another HTTP proxy but are made (HTTP-wise) directly to the web servers, albeit through
2712 > From the company example.com, direct connections are made to all
2716 > domains, but everything outbound goes through
2717 their ISP's proxy by way of example.com's corporate SOCKS 4A gateway to
2729 > forward-socks4a / socks-gw.example.com:1080 www-cache.example-isp.net:8080
2730 forward .example.com .</PRE
2737 > A rule that uses a SOCKS 4 gateway for all destinations but no HTTP parent looks like this:
2748 > forward-socks4 / socks-gw.example.com:1080 .</PRE
2755 > To chain Privoxy and Tor, both running on the same system, you should use
2767 > forward-socks4 / 127.0.0.1:9050 .</PRE
2777 > network can't be used to reach your local network,
2778 therefore it's a good idea to make some exceptions:
2789 > forward 192.168.*.*/ .
2791 forward 127.*.*.*/ .</PRE
2798 > Unencrypted connections to systems in these address ranges will
2799 be as (un)secure as the local network is, but the alternative is that you
2800 can't reach the network at all.
2803 > If you also want to be able to reach servers in your local network by
2804 using their names, you will need additional exceptions that look like
2816 > forward localhost/ .</PRE
2831 NAME="ADVANCED-FORWARDING-EXAMPLES"
2833 >7.5.3. Advanced Forwarding Examples</H4
2835 > If you have links to multiple ISPs that provide various special content
2836 only to their subscribers, you can configure multiple <SPAN
2840 which have connections to the respective ISPs to act as forwarders to each other, so that
2847 > users can see the internal content of all ISPs.</P
2849 > Assume that host-a has a PPP connection to isp-a.net. And host-b has a PPP connection to
2850 isp-b.net. Both run <SPAN
2854 configuration can look like this:</P
2867 forward .isp-b.net host-b:8118</PRE
2884 forward .isp-a.net host-a:8118</PRE
2890 > Now, your users can set their browser's proxy to use either
2891 host-a or host-b and be able to browse the internal content
2892 of both isp-a and isp-b.</P
2894 > If you intend to chain <SPAN
2901 > locally, then chain as
2904 >browser -> squid -> privoxy</TT
2905 > is the recommended way. </P
2907 > Assuming that <SPAN
2914 run on the same box, your <SPAN
2917 > configuration could then look like this:</P
2927 > # Define Privoxy as parent proxy (without ICP)
2928 cache_peer 127.0.0.1 parent 8118 7 no-query
2930 # Define ACL for protocol FTP
2933 # Do not forward FTP requests to Privoxy
2934 always_direct allow ftp
2936 # Forward all the rest to Privoxy
2937 never_direct allow all</PRE
2943 > You would then need to change your browser's proxy settings to <SPAN
2946 >'s address and port.
2947 Squid normally uses port 3128. If unsure consult <TT
2955 > You could just as well decide to only forward requests for Windows executables through
2956 a virus-scanning parent proxy, say, on <TT
2958 >antivir.example.com</TT
2970 forward /.*\.(exe|com|dll|zip)$ antivir.example.com:8010</PRE
2981 NAME="FORWARDED-CONNECT-RETRIES"
2983 >7.5.4. forwarded-connect-retries</H4
2987 CLASS="VARIABLELIST"
2993 > How often Privoxy retries if a forwarded connection request fails.
3003 >Number of retries.</I
3021 >Effect if unset:</DT
3024 > Forwarded connections are treated like direct connections and no retry attempts are made.
3034 >forwarded-connect-retries</I
3036 > is mainly interesting
3037 for socks4a connections, where Privoxy can't detect why the connections failed.
3038 The connection might have failed because of a DNS timeout in which case a retry makes sense,
3039 but it might also have failed because the server doesn't exist or isn't reachable. In this
3040 case the retry will just delay the appearance of Privoxy's error message.
3043 > Only use this option, if you are getting many forwarding related error messages,
3044 that go away when you try again manually. Start with a small value and check Privoxy's
3045 logfile from time to time, to see how many retries are usually needed.
3052 > forwarded-connect-retries 1
3066 >7.6. Windows GUI Options</H2
3071 > has a number of options specific to the
3072 Windows GUI interface:</P
3074 NAME="ACTIVITY-ANIMATION"
3079 >"activity-animation"</SPAN
3084 > icon will animate when
3088 > is active. To turn off, set to 0.</P
3093 CLASS="LITERALLAYOUT"
3098 >activity-animation 1</I
3101 </P
3111 >"log-messages"</SPAN
3116 > will log messages to the console
3122 CLASS="LITERALLAYOUT"
3130 </P
3135 NAME="LOG-BUFFER-SIZE"
3141 >"log-buffer-size"</SPAN
3142 > is set to 1, the size of the log buffer,
3143 i.e. the amount of memory used for the log messages displayed in the
3144 console window, will be limited to <SPAN
3146 >"log-max-lines"</SPAN
3149 > Warning: Setting this to 0 will result in the buffer to grow infinitely and
3150 eat up all your memory!</P
3155 CLASS="LITERALLAYOUT"
3160 >log-buffer-size 1</I
3163 </P
3168 NAME="LOG-MAX-LINES"
3173 >log-max-lines</SPAN
3174 > is the maximum number of lines held
3175 in the log buffer. See above.</P
3180 CLASS="LITERALLAYOUT"
3185 >log-max-lines 200</I
3188 </P
3193 NAME="LOG-HIGHLIGHT-MESSAGES"
3198 >"log-highlight-messages"</SPAN
3203 > will highlight portions of the log
3204 messages with a bold-faced font:</P
3209 CLASS="LITERALLAYOUT"
3214 >log-highlight-messages 1</I
3217 </P
3222 NAME="LOG-FONT-NAME"
3225 > The font used in the console window:</P
3230 CLASS="LITERALLAYOUT"
3235 >log-font-name Comic Sans MS</I
3238 </P
3243 NAME="LOG-FONT-SIZE"
3246 > Font size used in the console window:</P
3251 CLASS="LITERALLAYOUT"
3259 </P
3264 NAME="SHOW-ON-TASK-BAR"
3270 >"show-on-task-bar"</SPAN
3271 > controls whether or not
3275 > will appear as a button on the Task bar
3281 CLASS="LITERALLAYOUT"
3286 >show-on-task-bar 0</I
3289 </P
3294 NAME="CLOSE-BUTTON-MINIMIZES"
3299 >"close-button-minimizes"</SPAN
3300 > is set to 1, the Windows close
3301 button will minimize <SPAN
3304 > instead of closing
3305 the program (close with the exit option on the File menu).</P
3310 CLASS="LITERALLAYOUT"
3315 >close-button-minimizes 1</I
3318 </P
3328 >"hide-console"</SPAN
3329 > option is specific to the MS-Win console
3333 >. If this option is used,
3337 > will disconnect from and hide the
3343 CLASS="LITERALLAYOUT"
3351 </P
3362 SUMMARY="Footer navigation table"
3373 HREF="configuration.html"
3391 HREF="actions-file.html"
3401 >Privoxy Configuration</TD