4 >The Main Configuration File</TITLE
7 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
10 TITLE="Privoxy 3.0.7 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.7 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 >An alternative directory where the templates are loaded from</P
657 >Effect if unset:</DT
660 >The templates are assumed to be located in confdir/template.</P
666 > Privoxy's original templates are usually overwritten
667 with each update. Use this option to relocate customized templates
668 that should be kept. Note that you might be missing new features
669 if you use outdated templates.
692 > The directory where all logging takes place (i.e. where <TT
712 >/var/log/privoxy (Unix) <SPAN
721 > installation dir (Windows) </P
724 >Effect if unset:</DT
758 >7.2.4. actionsfile</H4
760 NAME="DEFAULT.ACTION"
763 NAME="STANDARD.ACTION"
778 HREF="actions-file.html"
787 >Complete file name, relative to <TT
803 CLASS="LITERALLAYOUT"
804 > standard.action # Internal purposes, no editing recommended</P
811 CLASS="LITERALLAYOUT"
812 > default.action # Main actions file</P
819 CLASS="LITERALLAYOUT"
820 > user.action # User customizations</P
830 >Effect if unset:</DT
833 > No actions are taken at all. More or less neutral proxying.
843 > lines are permitted, and are in fact recommended!
847 The default values include standard.action, which is used for internal
848 purposes and should be loaded, default.action, which is the
852 > actions file maintained by the developers, and
856 >, where you can make your personal additions.
860 Actions files are where all the per site and per URL configuration is done for
861 ad blocking, cookie management, privacy considerations, etc.
862 There is no point in using <SPAN
866 least one actions file.
869 > Note that since Privoxy 3.0.7, the complete filename, including the <SPAN
873 extension has to be specified. The syntax change was necessary to be consistent
874 with the other file options and to allow previously forbidden characters.
887 >7.2.5. filterfile</H4
889 NAME="DEFAULT.FILTER"
901 HREF="filter-file.html"
910 >File name, relative to <TT
919 >default.filter (Unix) <SPAN
925 > default.filter.txt (Windows)</P
928 >Effect if unset:</DT
931 > No textual content filtering takes place, i.e. all
935 HREF="actions-file.html#FILTER"
944 actions in the actions files are turned neutral.
954 > lines are permitted.
958 HREF="filter-file.html"
960 > contain content modification
962 HREF="appendix.html#REGEX"
963 >regular expressions</A
964 >. These rules permit
965 powerful changes on the content of Web pages, and optionally the headers
966 as well, e.g., you could disable your favorite JavaScript annoyances,
967 re-write the actual displayed text, or just have some fun
968 playing buzzword bingo with web pages.
975 HREF="actions-file.html#FILTER"
984 actions rely on the relevant filter (<TT
990 to be defined in a filter file!
993 > A pre-defined filter file called <TT
997 a number of useful filters for common problems is included in the distribution.
998 See the section on the <TT
1001 HREF="actions-file.html#FILTER"
1008 > It is recommended to place any locally adapted filters into a separate
1029 CLASS="VARIABLELIST"
1035 > The log file to use
1042 >File name, relative to <TT
1051 >logfile (Unix) <SPAN
1057 > privoxy.log (Windows)</P
1060 >Effect if unset:</DT
1063 > No log file is used, all log messages go to the console (<TT
1073 > The logfile is where all logging and error messages are written. The level
1074 of detail and number of messages are set with the <TT
1078 option (see below). The logfile can be useful for tracking down a problem with
1082 > (e.g., it's not blocking an ad you
1083 think it should block) but in most cases you probably will never look at it.
1086 > Your logfile will grow indefinitely, and you will probably want to
1087 periodically remove it. On Unix systems, you can do this with a cron job
1091 >). For Red Hat, a <B
1095 script has been included.
1098 > On SuSE Linux systems, you can place a line like <SPAN
1100 >"/var/log/privoxy.*
1101 +1024k 644 nobody.nogroup"</SPAN
1106 the effect that cron.daily will automatically archive, gzip, and empty the
1107 log, when it exceeds 1M size.
1110 > Any log files must be writable by whatever user <SPAN
1114 is being run as (default on UNIX, user id is <SPAN
1134 CLASS="VARIABLELIST"
1140 > The file to store intercepted cookies in
1147 >File name, relative to <TT
1156 >Unset (commented out). When activated: jarfile (Unix) <SPAN
1162 > privoxy.jar (Windows)</P
1165 >Effect if unset:</DT
1168 > Intercepted cookies are not stored in a dedicated log file.
1175 > The jarfile may grow to ridiculous sizes over time.
1178 > If debug 8 (show header parsing) is enabled, cookies are
1179 written to the logfile with the rest of the headers.
1192 >7.2.8. trustfile</H4
1196 CLASS="VARIABLELIST"
1202 > The name of the trust file to use
1209 >File name, relative to <TT
1222 >Unset (commented out)</I
1224 >. When activated: trust (Unix) <SPAN
1230 > trust.txt (Windows)</P
1233 >Effect if unset:</DT
1236 > The entire trust mechanism is disabled.
1243 > The trust mechanism is an experimental feature for building white-lists and should
1244 be used with care. It is <SPAN
1250 > recommended for the casual user.
1253 > If you specify a trust file, <SPAN
1257 access to sites that are specified in the trustfile. Sites can be listed
1264 > character limits access to this site
1265 only (and any sub-paths within this site), e.g.
1268 >~www.example.com</TT
1272 >~www.example.com/features/news.html</TT
1276 > Or, you can designate sites as <SPAN
1280 >trusted referrers</I
1283 prepending the name with a <TT
1286 > character. The effect is that
1287 access to untrusted sites will be granted -- but only if a link from this
1288 trusted referrer was used to get there. The link target will then be added
1292 > so that future, direct accesses will be
1293 granted. Sites added via this mechanism do not become trusted referrers
1294 themselves (i.e. they are added with a <TT
1298 There is a limit of 512 such entries, after which new entries will not be
1302 > If you use the <TT
1305 > operator in the trust file, it may grow
1306 considerably over time.
1309 > It is recommended that <SPAN
1315 >--disable-force</TT
1318 >--disable-toggle</TT
1322 > --disable-editor</TT
1323 > options, if this feature is to be
1327 > Possible applications include limiting Internet access for children.
1343 > These options are mainly useful when tracing a problem.
1344 Note that you might also want to invoke
1352 command line option when debugging.
1365 CLASS="VARIABLELIST"
1371 > Key values that determine what information gets logged to the
1373 HREF="config.html#LOGFILE"
1394 >12289 (i.e.: URLs plus informational and warning messages)</P
1397 >Effect if unset:</DT
1400 > Nothing gets logged.
1407 > The available debug levels are:
1417 CLASS="PROGRAMLISTING"
1418 > debug 1 # show each GET/POST/CONNECT request
1419 debug 2 # show each connection status
1420 debug 4 # show I/O status
1421 debug 8 # show header parsing
1422 debug 16 # log all data written to the network into the logfile
1423 debug 32 # debug force feature
1424 debug 64 # debug regular expression filters
1425 debug 128 # debug redirects
1426 debug 256 # debug GIF de-animation
1427 debug 512 # Common Log Format
1428 debug 1024 # debug kill pop-ups
1429 debug 2048 # CGI user interface
1430 debug 4096 # Startup banner and warnings.
1431 debug 8192 # Non-fatal errors</PRE
1438 > To select multiple debug levels, you can either add them or use
1445 > A debug level of 1 is informative because it will show you each request
1446 as it happens. <SPAN
1450 >1, 4096 and 8192 are highly recommended</I
1453 so that you will notice when things go wrong. The other levels are probably
1454 only of interest if you are hunting down a specific problem. They can produce
1455 a hell of an output (especially 16).
1459 > The reporting of <SPAN
1465 > errors (i.e. ones which causes
1469 > to exit) is always on and cannot be disabled.
1472 > If you want to use CLF (Common Log Format), you should set <SPAN
1482 > and not enable anything else.
1488 > has a hard-coded limit for the
1489 length of log messages. If it's reached, messages are logged truncated
1490 and marked with <SPAN
1492 >"... [too long, truncated]"</SPAN
1504 NAME="SINGLE-THREADED"
1506 >7.3.2. single-threaded</H4
1510 CLASS="VARIABLELIST"
1516 > Whether to run only one server thread
1544 >Effect if unset:</DT
1547 > Multi-threaded (or, where unavailable: forked) operation, i.e. the ability to
1548 serve multiple requests simultaneously.
1555 > This option is only there for debug purposes and you should never
1556 need to use it. <SPAN
1560 >It will drastically reduce performance.</I
1574 NAME="ACCESS-CONTROL"
1576 >7.4. Access Control and Security</H2
1578 > This section of the config file controls the security-relevant aspects
1589 NAME="LISTEN-ADDRESS"
1591 >7.4.1. listen-address</H4
1595 CLASS="VARIABLELIST"
1601 > The IP address and TCP port on which <SPAN
1605 listen for client requests.
1631 >Effect if unset:</DT
1634 > Bind to 127.0.0.1 (localhost), port 8118. This is suitable and recommended for
1635 home users who run <SPAN
1638 > on the same machine as
1646 > You will need to configure your browser(s) to this proxy address and port.
1649 > If you already have another service running on port 8118, or if you want to
1650 serve requests from other machines (e.g. on your local network) as well, you
1651 will need to override the default.
1654 > If you leave out the IP address, <SPAN
1658 bind to all interfaces (addresses) on your machine and may become reachable
1659 from the Internet. In that case, consider using <A
1660 HREF="config.html#ACLS"
1661 >access control lists</A
1662 > (ACL's, see below), and/or
1669 > to untrusted users, you will
1670 also want to turn off the <TT
1673 HREF="config.html#ENABLE-EDIT-ACTIONS"
1674 >enable-edit-actions</A
1680 HREF="config.html#ENABLE-REMOTE-TOGGLE"
1681 >enable-remote-toggle</A
1691 > Suppose you are running <SPAN
1695 a machine which has the address 192.168.0.1 on your local private network
1696 (192.168.0.0) and has another outside connection with a different address.
1697 You want it to serve requests from inside only:
1707 CLASS="PROGRAMLISTING"
1708 > listen-address 192.168.0.1:8118</PRE
1729 CLASS="VARIABLELIST"
1735 > Initial state of "toggle" status
1751 >Effect if unset:</DT
1754 > Act as if toggled on
1761 > If set to 0, <SPAN
1767 >"toggled off"</SPAN
1768 > mode, i.e. mostly behave like a normal,
1769 content-neutral proxy where all ad blocking, filtering, etc are disabled. See
1772 >enable-remote-toggle</TT
1773 > below. This is not really useful
1774 anymore, since toggling is much easier via <A
1775 HREF="http://config.privoxy.org/toggle"
1777 >the web interface</A
1785 > The windows version will only display the toggle icon in the system tray
1786 if this option is present.
1797 NAME="ENABLE-REMOTE-TOGGLE"
1799 >7.4.3. enable-remote-toggle</H4
1803 CLASS="VARIABLELIST"
1809 > Whether or not the <A
1810 HREF="http://config.privoxy.org/toggle"
1830 >Effect if unset:</DT
1833 > The web-based toggle feature is disabled.
1840 > When toggled off, <SPAN
1843 > mostly acts like a normal,
1844 content-neutral proxy, i.e. it acts as if none of the actions applied to
1848 > For the time being, access to the toggle feature can <SPAN
1855 controlled separately by <SPAN
1858 > or HTTP authentication,
1859 so that everybody who can access <SPAN
1870 toggle it for all users. So this option is <SPAN
1877 for multi-user environments with untrusted users.
1880 > Note that you must have compiled <SPAN
1884 support for this feature, otherwise this option has no effect.
1895 NAME="ENABLE-REMOTE-HTTP-TOGGLE"
1897 >7.4.4. enable-remote-http-toggle</H4
1901 CLASS="VARIABLELIST"
1907 > Whether or not Privoxy recognizes special HTTP headers to change its behaviour.
1923 >Effect if unset:</DT
1926 > Privoxy ignores special HTTP headers.
1933 > When toggled on, the client can change <SPAN
1937 behaviour by setting special HTTP headers. Currently the only supported
1938 special header is <SPAN
1940 >"X-Filter: No"</SPAN
1941 >, to disable filtering for
1942 the ongoing request, even if it is enabled in one of the action files.
1945 > If you are using <SPAN
1949 multi-user environment or with untrustworthy clients and want to
1950 enforce filtering, you will have to disable this option,
1951 otherwise you can ignore it.
1962 NAME="ENABLE-EDIT-ACTIONS"
1964 >7.4.5. enable-edit-actions</H4
1968 CLASS="VARIABLELIST"
1974 > Whether or not the <A
1975 HREF="http://config.privoxy.org/show-status"
1995 >Effect if unset:</DT
1998 > The web-based actions file editor is disabled.
2005 > For the time being, access to the editor can <SPAN
2012 controlled separately by <SPAN
2015 > or HTTP authentication,
2016 so that everybody who can access <SPAN
2027 modify its configuration for all users. So this option is <SPAN
2034 > for multi-user environments with untrusted users.
2037 > Note that you must have compiled <SPAN
2041 support for this feature, otherwise this option has no effect.
2052 NAME="ENFORCE-BLOCKS"
2054 >7.4.6. enforce-blocks</H4
2058 CLASS="VARIABLELIST"
2064 > Whether the user is allowed to ignore blocks and can <SPAN
2066 >"go there anyway"</SPAN
2095 >Effect if unset:</DT
2098 > Blocks are not enforced.
2108 > is mainly used to block and filter
2109 requests as a service to the user, for example to block ads and other
2110 junk that clogs the pipes. <SPAN
2114 isn't perfect and sometimes innocent pages are blocked. In this situation it
2115 makes sense to allow the user to enforce the request and have
2122 > In the default configuration <SPAN
2129 > page contains a <SPAN
2131 >"go there anyway"</SPAN
2133 link to adds a special string (the force prefix) to the request URL.
2134 If that link is used, <SPAN
2138 detect the force prefix, remove it again and let the request pass.
2144 > can also be used to enforce
2145 a network policy. In that case the user obviously should not be able to
2146 bypass any blocks, and that's what the <SPAN
2148 >"enforce-blocks"</SPAN
2150 option is for. If it's enabled, <SPAN
2156 >"go there anyway"</SPAN
2157 > link. If the user adds the force
2158 prefix by hand, it will not be accepted and the circumvention attempt
2179 >7.4.7. ACLs: permit-access and deny-access</H4
2181 NAME="PERMIT-ACCESS"
2189 CLASS="VARIABLELIST"
2195 > Who can access what.
2237 > are IP addresses in dotted decimal notation or valid
2249 > are subnet masks in CIDR notation, i.e. integer
2250 values from 2 to 30 representing the length (in bits) of the network address. The masks and the whole
2251 destination part are optional.
2267 >Effect if unset:</DT
2270 > Don't restrict access further than implied by <TT
2280 > Access controls are included at the request of ISPs and systems
2281 administrators, and <SPAN
2285 >are not usually needed by individual users</I
2288 For a typical home user, it will normally suffice to ensure that
2292 > only listens on the localhost
2293 (127.0.0.1) or internal (home) network address by means of the
2295 HREF="config.html#LISTEN-ADDRESS"
2307 > Please see the warnings in the FAQ that this proxy is not intended to be a substitute
2308 for a firewall or to encourage anyone to defer addressing basic security
2312 > Multiple ACL lines are OK.
2313 If any ACLs are specified, <SPAN
2317 to IP addresses that match at least one <TT
2321 and don't match any subsequent <TT
2324 > line. In other words, the
2325 last match wins, with the default being <TT
2334 > is using a forwarder (see <TT
2338 for a particular destination URL, the <TT
2344 that is examined is the address of the forwarder and <SPAN
2351 of the ultimate target. This is necessary because it may be impossible for the local
2355 > to determine the IP address of the
2356 ultimate target (that's often what gateways are used for).
2359 > You should prefer using IP addresses over DNS names, because the address lookups take
2360 time. All DNS names must resolve! You can <SPAN
2366 > use domain patterns
2370 > or partial domain names. If a DNS name resolves to multiple
2371 IP addresses, only the first one is used.
2374 > Denying access to particular sites by ACL may have undesired side effects
2375 if the site in question is hosted on a machine which also hosts other sites
2383 > Explicitly define the default behavior if no ACL and
2391 is OK. The absence of a <TT
2403 > destination addresses are OK:
2414 > permit-access localhost</PRE
2421 > Allow any host on the same class C subnet as www.privoxy.org access to
2422 nothing but www.example.com (or other domains hosted on the same system):
2433 > permit-access www.privoxy.org/24 www.example.com/32</PRE
2440 > Allow access from any host on the 26-bit subnet 192.168.45.64 to anywhere,
2441 with the exception that 192.168.45.73 may not access the IP address behind
2442 www.dirty-stuff.example.com:
2453 > permit-access 192.168.45.64/26
2454 deny-access 192.168.45.73 www.dirty-stuff.example.com</PRE
2471 >7.4.8. buffer-limit</H4
2475 CLASS="VARIABLELIST"
2481 > Maximum size of the buffer for content filtering.
2497 >Effect if unset:</DT
2500 > Use a 4MB (4096 KB) limit.
2507 > For content filtering, i.e. the <TT
2514 > actions, it is necessary that
2518 > buffers the entire document body.
2519 This can be potentially dangerous, since a server could just keep sending
2520 data indefinitely and wait for your RAM to exhaust -- with nasty consequences.
2524 > When a document buffer size reaches the <TT
2528 flushed to the client unfiltered and no further attempt to
2529 filter the rest of the document is made. Remember that there may be multiple threads
2530 running, which might require up to <TT
2540 >, unless you have enabled <SPAN
2542 >"single-threaded"</SPAN
2558 >7.5. Forwarding</H2
2560 > This feature allows routing of HTTP requests through a chain of
2561 multiple proxies.</P
2563 > Forwarding can be used to chain Privoxy with a caching proxy to speed
2564 up browsing. Using a parent proxy may also be necessary if the machine
2568 > runs on has no direct Internet access.</P
2570 > Note that parent proxies can severely decrease your privacy level.
2571 For example a parent proxy could add your IP address to the request
2572 headers and if it's a caching proxy it may add the <SPAN
2576 header to revalidation requests again, even though you configured Privoxy
2577 to remove it. It may also ignore Privoxy's header time randomization and use the
2578 original values which could be used by the server as cookie replacement
2579 to track your steps between visits.</P
2581 > Also specified here are SOCKS proxies. <SPAN
2585 supports the SOCKS 4 and SOCKS 4A protocols.</P
2597 CLASS="VARIABLELIST"
2603 > To which parent HTTP proxy specific requests should be routed.
2635 HREF="actions-file.html#AF-PATTERNS"
2638 that specifies to which requests (i.e. URLs) this forward rule shall apply. Use <TT
2657 is the DNS name or IP address of the parent HTTP proxy through which the requests should be forwarded,
2658 optionally followed by its listening port (default: 8080).
2659 Use a single dot (<TT
2664 >"no forwarding"</SPAN
2681 >Effect if unset:</DT
2684 > Don't use parent HTTP proxies.
2699 >, then requests are not
2700 forwarded to another HTTP proxy but are made directly to the web servers.
2703 > Multiple lines are OK, they are checked in sequence, and the last match wins.
2710 > Everything goes to an example parent proxy, except SSL on port 443 (which it doesn't handle):
2721 > forward / parent-proxy.example.org:8080
2729 > Everything goes to our example ISP's caching proxy, except for requests
2730 to that ISP's sites:
2741 > forward / caching-proxy.example-isp.net:8000
2742 forward .example-isp.net .</PRE
2759 >7.5.2. forward-socks4 and forward-socks4a</H4
2761 NAME="FORWARD-SOCKS4"
2764 NAME="FORWARD-SOCKS4A"
2769 CLASS="VARIABLELIST"
2775 > Through which SOCKS proxy (and optionally to which parent HTTP proxy) specific requests should be routed.
2818 HREF="actions-file.html#AF-PATTERNS"
2821 that specifies to which requests (i.e. URLs) this forward rule shall apply. Use <TT
2840 are IP addresses in dotted decimal notation or valid DNS names (<TT
2851 >"no HTTP forwarding"</SPAN
2852 >), and the optional
2858 > parameters are TCP ports, i.e. integer values from 1 to 64535
2874 >Effect if unset:</DT
2877 > Don't use SOCKS proxies.
2884 > Multiple lines are OK, they are checked in sequence, and the last match wins.
2887 > The difference between <TT
2892 >forward-socks4a</TT
2894 is that in the SOCKS 4A protocol, the DNS resolution of the target hostname happens on the SOCKS
2895 server, while in SOCKS 4 it happens locally.
2906 >, then requests are not
2907 forwarded to another HTTP proxy but are made (HTTP-wise) directly to the web servers, albeit through
2915 > From the company example.com, direct connections are made to all
2919 > domains, but everything outbound goes through
2920 their ISP's proxy by way of example.com's corporate SOCKS 4A gateway to
2932 > forward-socks4a / socks-gw.example.com:1080 www-cache.example-isp.net:8080
2933 forward .example.com .</PRE
2940 > A rule that uses a SOCKS 4 gateway for all destinations but no HTTP parent looks like this:
2951 > forward-socks4 / socks-gw.example.com:1080 .</PRE
2958 > To chain Privoxy and Tor, both running on the same system, you should use
2970 > forward-socks4 / 127.0.0.1:9050 .</PRE
2980 > network can't be used to reach your local network,
2981 therefore it's a good idea to make some exceptions:
2992 > forward 192.168.*.*/ .
2994 forward 127.*.*.*/ .</PRE
3001 > Unencrypted connections to systems in these address ranges will
3002 be as (un)secure as the local network is, but the alternative is that you
3003 can't reach the network at all.
3006 > If you also want to be able to reach servers in your local network by
3007 using their names, you will need additional exceptions that look like
3019 > forward localhost/ .</PRE
3034 NAME="ADVANCED-FORWARDING-EXAMPLES"
3036 >7.5.3. Advanced Forwarding Examples</H4
3038 > If you have links to multiple ISPs that provide various special content
3039 only to their subscribers, you can configure multiple <SPAN
3043 which have connections to the respective ISPs to act as forwarders to each other, so that
3050 > users can see the internal content of all ISPs.</P
3052 > Assume that host-a has a PPP connection to isp-a.net. And host-b has a PPP connection to
3053 isp-b.net. Both run <SPAN
3057 configuration can look like this:</P
3070 forward .isp-b.net host-b:8118</PRE
3087 forward .isp-a.net host-a:8118</PRE
3093 > Now, your users can set their browser's proxy to use either
3094 host-a or host-b and be able to browse the internal content
3095 of both isp-a and isp-b.</P
3097 > If you intend to chain <SPAN
3104 > locally, then chain as
3107 >browser -> squid -> privoxy</TT
3108 > is the recommended way. </P
3110 > Assuming that <SPAN
3117 run on the same box, your <SPAN
3120 > configuration could then look like this:</P
3130 > # Define Privoxy as parent proxy (without ICP)
3131 cache_peer 127.0.0.1 parent 8118 7 no-query
3133 # Define ACL for protocol FTP
3136 # Do not forward FTP requests to Privoxy
3137 always_direct allow ftp
3139 # Forward all the rest to Privoxy
3140 never_direct allow all</PRE
3146 > You would then need to change your browser's proxy settings to <SPAN
3149 >'s address and port.
3150 Squid normally uses port 3128. If unsure consult <TT
3158 > You could just as well decide to only forward requests for Windows executables through
3159 a virus-scanning parent proxy, say, on <TT
3161 >antivir.example.com</TT
3173 forward /.*\.(exe|com|dll|zip)$ antivir.example.com:8010</PRE
3184 NAME="FORWARDED-CONNECT-RETRIES"
3186 >7.5.4. forwarded-connect-retries</H4
3190 CLASS="VARIABLELIST"
3196 > How often Privoxy retries if a forwarded connection request fails.
3206 >Number of retries.</I
3224 >Effect if unset:</DT
3227 > Connections forwarded through other proxies are treated like direct connections and no retry attempts are made.
3237 >forwarded-connect-retries</I
3239 > is mainly interesting
3240 for socks4a connections, where <SPAN
3243 > can't detect why the connections failed.
3244 The connection might have failed because of a DNS timeout in which case a retry makes sense,
3245 but it might also have failed because the server doesn't exist or isn't reachable. In this
3246 case the retry will just delay the appearance of Privoxy's error message.
3249 > Note that in the context of this option, <SPAN
3251 >"forwarded connections"</SPAN
3252 > includes all connections
3253 that Privoxy forwards through other proxies. This option is not limited to the HTTP CONNECT method.
3256 > Only use this option, if you are getting many forwarding related error messages,
3257 that go away when you try again manually. Start with a small value and check Privoxy's
3258 logfile from time to time, to see how many retries are usually needed.
3265 > forwarded-connect-retries 1
3276 NAME="ACCEPT-INTERCEPTED-REQUESTS"
3278 >7.5.5. accept-intercepted-requests</H4
3282 CLASS="VARIABLELIST"
3288 > Whether intercepted requests should be treated as valid.
3316 >Effect if unset:</DT
3319 > Only proxy requests are accepted, intercepted requests are treated as invalid.
3326 > If you don't trust your clients and want to force them
3331 option and configure your packet filter to redirect outgoing
3332 HTTP connections into <SPAN
3338 > Make sure that <SPAN
3342 aren't redirected as well. Additionally take care that
3346 > can't intentionally connect
3347 to itself, otherwise you could run into redirection loops if
3351 > listening port is reachable
3352 by the outside or an attacker has access to the pages you visit.
3359 > accept-intercepted-requests 1
3370 NAME="SPLIT-LARGE-FORMS"
3372 >7.5.6. split-large-forms</H4
3376 CLASS="VARIABLELIST"
3382 > Whether the CGI interface should stay compatible with broken HTTP clients.
3410 >Effect if unset:</DT
3413 > The CGI form generate long GET URLs.
3423 > CGI forms can lead to
3424 rather long URLs. This isn't a problem as far as the HTTP
3425 standard is concerned, but it can confuse clients with arbitrary
3426 URL lenght limitations.
3429 > Enabling split-large-forms causes <SPAN
3433 to devide big forms into smaller ones to keep the URL length down.
3434 It makes editing a lot less convenient and you can no longer
3435 submit all changes at once, but at least it works around this
3439 > If you don't notice any editing problems, there is no reason
3440 to enable this option, but if one of the submit buttons appears
3441 to be broken, you should give it a try.
3448 > split-large-forms 1
3462 >7.6. Windows GUI Options</H2
3467 > has a number of options specific to the
3468 Windows GUI interface:</P
3470 NAME="ACTIVITY-ANIMATION"
3475 >"activity-animation"</SPAN
3480 > icon will animate when
3484 > is active. To turn off, set to 0.</P
3489 CLASS="LITERALLAYOUT"
3494 >activity-animation 1</I
3497 </P
3507 >"log-messages"</SPAN
3512 > will log messages to the console
3518 CLASS="LITERALLAYOUT"
3526 </P
3531 NAME="LOG-BUFFER-SIZE"
3537 >"log-buffer-size"</SPAN
3538 > is set to 1, the size of the log buffer,
3539 i.e. the amount of memory used for the log messages displayed in the
3540 console window, will be limited to <SPAN
3542 >"log-max-lines"</SPAN
3545 > Warning: Setting this to 0 will result in the buffer to grow infinitely and
3546 eat up all your memory!</P
3551 CLASS="LITERALLAYOUT"
3556 >log-buffer-size 1</I
3559 </P
3564 NAME="LOG-MAX-LINES"
3569 >log-max-lines</SPAN
3570 > is the maximum number of lines held
3571 in the log buffer. See above.</P
3576 CLASS="LITERALLAYOUT"
3581 >log-max-lines 200</I
3584 </P
3589 NAME="LOG-HIGHLIGHT-MESSAGES"
3594 >"log-highlight-messages"</SPAN
3599 > will highlight portions of the log
3600 messages with a bold-faced font:</P
3605 CLASS="LITERALLAYOUT"
3610 >log-highlight-messages 1</I
3613 </P
3618 NAME="LOG-FONT-NAME"
3621 > The font used in the console window:</P
3626 CLASS="LITERALLAYOUT"
3631 >log-font-name Comic Sans MS</I
3634 </P
3639 NAME="LOG-FONT-SIZE"
3642 > Font size used in the console window:</P
3647 CLASS="LITERALLAYOUT"
3655 </P
3660 NAME="SHOW-ON-TASK-BAR"
3666 >"show-on-task-bar"</SPAN
3667 > controls whether or not
3671 > will appear as a button on the Task bar
3677 CLASS="LITERALLAYOUT"
3682 >show-on-task-bar 0</I
3685 </P
3690 NAME="CLOSE-BUTTON-MINIMIZES"
3695 >"close-button-minimizes"</SPAN
3696 > is set to 1, the Windows close
3697 button will minimize <SPAN
3700 > instead of closing
3701 the program (close with the exit option on the File menu).</P
3706 CLASS="LITERALLAYOUT"
3711 >close-button-minimizes 1</I
3714 </P
3724 >"hide-console"</SPAN
3725 > option is specific to the MS-Win console
3729 >. If this option is used,
3733 > will disconnect from and hide the
3739 CLASS="LITERALLAYOUT"
3747 </P
3758 SUMMARY="Footer navigation table"
3769 HREF="configuration.html"
3787 HREF="actions-file.html"
3797 >Privoxy Configuration</TD