1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
8 CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
10 TITLE="Privoxy 3.0.7 User Manual"
11 HREF="index.html"><LINK
13 TITLE="The Main Configuration File"
14 HREF="config.html"><LINK
17 HREF="filter-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
64 HREF="filter-file.html"
82 > The actions files are used to define what <SPAN
92 > takes for which URLs, and thus determines
93 how ad images, cookies and various other aspects of HTTP content and
94 transactions are handled, and on which sites (or even parts thereof).
95 There are a number of such actions, with a wide range of functionality.
96 Each action does something a little different.
97 These actions give us a veritable arsenal of tools with which to exert
98 our control, preferences and independence. Actions can be combined so that
99 their effects are aggregated when applied against a given set of URLs.</P
102 are three action files included with <SPAN
117 > - is the primary action file
118 that sets the initial values for all actions. It is intended to
119 provide a base level of functionality for
123 > array of features. So it is
124 a set of broad rules that should work reasonably well as-is for most users.
125 This is the file that the developers are keeping updated, and <A
126 HREF="installation.html#INSTALLATION-KEEPUPDATED"
127 >making available to users</A
129 The user's preferences as set in <TT
152 > - is intended to be for local site
153 preferences and exceptions. As an example, if your ISP or your bank
154 has specific requirements, and need special handling, this kind of
155 thing should go here. This file will not be upgraded.
163 > - is used only by the web based editor
165 HREF="http://config.privoxy.org/edit-actions-list?f=default"
167 > http://config.privoxy.org/edit-actions-list?f=default</A
169 to set various pre-defined sets of rules for the default actions section
181 >Set to Cautious</SPAN
187 >Set to Advanced</SPAN
191 > These have increasing levels of aggressiveness <SPAN
196 influence on your browsing unless you select them explicitly in the
199 >. A default installation should be pre-set to
203 > (versions prior to 3.0.5 were set to
207 >). New users should try this for a while before
208 adjusting the settings to more aggressive levels. The more aggressive
209 the settings, then the more likelihood there is of problems such as sites
210 not working as they should.
216 > button allows you to turn each
217 action on/off individually for fine-tuning. The <SPAN
221 button changes the actions list to low/safe settings which will activate
222 ad blocking and a minimal set of <SPAN
225 >'s features, and subsequently
226 there will be less of a chance for accidental problems. The
230 > button sets the list to a medium level of
231 other features and a low level set of privacy features. The
235 > button sets the list to a high level of
236 ad blocking and medium level of privacy. See the chart below. The latter
237 three buttons over-ride any changes via with the
241 > button. More fine-tuning can be done in the
242 lower sections of this internal page.
245 > It is not recommend to edit the <TT
252 > The default profiles, and their associated actions, as pre-defined in
266 >Table 1. Default Configurations</B
296 >Ad-blocking Aggressiveness</TD
306 >Ad-filtering by size</TD
316 >Ad-filtering by link</TD
336 >Privacy Features</TD
366 >GIF de-animation</TD
396 >JavaScript taming</TD
416 >Image tag reordering</TD
434 > The list of actions files to be used are defined in the main configuration
435 file, and are processed in the order they are defined (e.g.
439 > is typically processed before
443 >). The content of these can all be viewed and
445 HREF="http://config.privoxy.org/show-status"
447 >http://config.privoxy.org/show-status</A
449 The over-riding principle when applying actions, is that the last action that
450 matches a given URL wins. The broadest, most general rules go first
455 followed by any exceptions (typically also in
459 >), which are then followed lastly by any
460 local preferences (typically in <SPAN
476 > An actions file typically has multiple sections. If you want to use
480 > in an actions file, you have to place the (optional)
482 HREF="actions-file.html#ALIASES"
484 > at the top of that file.
485 Then comes the default set of rules which will apply universally to all
486 sites and pages (be <SPAN
496 > or any other actions file after
500 >, because it will override the result
501 from consulting any previous file). And then below that,
502 exceptions to the defined universal policies. You can regard
506 > as an appendix to <TT
510 with the advantage that it is a separate file, which makes preserving your
511 personal settings across <SPAN
514 > upgrades easier.</P
517 Actions can be used to block anything you want, including ads, banners, or
518 just some obnoxious URL whose content you would rather not see. Cookies can be accepted
519 or rejected, or accepted only during the current browser session (i.e. not
520 written to disk), content can be modified, some JavaScripts tamed, user-tracking
521 fooled, and much more. See below for a <A
522 HREF="actions-file.html#ACTIONS"
532 >8.1. Finding the Right Mix</A
536 HREF="actions-file.html#ACTIONS"
538 >, like cookie suppression
539 or script disabling, may render some sites unusable that rely on these
540 techniques to work properly. Finding the right mix of actions is not always easy and
541 certainly a matter of personal taste. And, things can always change, requiring
542 refinements in the configuration. In general, it can be said that the more
546 > your default settings (in the top section of the
547 actions file) are, the more exceptions for <SPAN
551 will have to make later. If, for example, you want to crunch all cookies per
552 default, you'll have to make exceptions from that rule for sites that you
553 regularly use and that require cookies for actually useful purposes, like maybe
554 your bank, favorite shop, or newspaper.</P
556 > We have tried to provide you with reasonable rules to start from in the
557 distribution actions files. But there is no general rule of thumb on these
558 things. There just are too many variables, and sites are constantly changing.
559 Sooner or later you will want to change the rules (and read this chapter again :).</P
570 > The easiest way to edit the actions files is with a browser by
571 using our browser-based editor, which can be reached from <A
572 HREF="http://config.privoxy.org/show-status"
574 >http://config.privoxy.org/show-status</A
576 Note: the config file option <A
577 HREF="config.html#ENABLE-EDIT-ACTIONS"
578 >enable-edit-actions</A
579 > must be enabled for
580 this to work. The editor allows both fine-grained control over every single
581 feature on a per-URL basis, and easy choosing from wholesale sets of defaults
592 >. Warning: the <SPAN
596 aggressive, and will be more likely to cause problems for some sites.
597 Experienced users only!
600 > If you prefer plain text editing to GUIs, you can of course also directly edit the
601 the actions files with your favorite text editor. Look at
605 > which is richly commented with many
614 >8.3. How Actions are Applied to Requests</A
617 > Actions files are divided into sections. There are special sections,
621 HREF="actions-file.html#ALIASES"
624 > sections which will
625 be discussed later. For now let's concentrate on regular sections: They have a
626 heading line (often split up to multiple lines for readability) which consist
627 of a list of actions, separated by whitespace and enclosed in curly braces.
628 Below that, there is a list of URL and tag patterns, each on a separate line.</P
630 > To determine which actions apply to a request, the URL of the request is
631 compared to all URL patterns in each <SPAN
635 Every time it matches, the list of applicable actions for the request is
636 incrementally updated, using the heading of the section in which the
637 pattern is located. The same is done again for tags and tag patterns later on.</P
639 > If multiple applying sections set the same action differently,
640 the last match wins. If not, the effects are aggregated.
641 E.g. a URL might match a regular section with a heading line of <TT
645 HREF="actions-file.html#HANDLE-AS-IMAGE"
649 then later another one with just <TT
653 HREF="actions-file.html#BLOCK"
663 > actions to apply. And there may well be
664 cases where you will want to combine actions together. Such a section then
682 # Block these as if they were images. Send no block page.
684 media.example.com/.*banners
685 .example.com/images/ads/</PRE
692 > You can trace this process for URL patterns and any given URL by visiting <A
693 HREF="http://config.privoxy.org/show-url-info"
695 >http://config.privoxy.org/show-url-info</A
698 > Examples and more detail on this is provided in the Appendix, <A
699 HREF="appendix.html#ACTIONSANAT"
700 > Troubleshooting: Anatomy of an Action</A
720 to determine what <SPAN
726 > might apply to which sites and
727 pages your browser attempts to access. These <SPAN
737 > matching to achieve a high degree of
738 flexibility. This allows one expression to be expanded and potentially match
739 against many similar patterns.</P
741 > Generally, an URL pattern has the form
744 ><domain>/<path></TT
748 ><domain></TT
753 optional. (This is why the special <TT
756 > pattern matches all
757 URLs). Note that the protocol portion of the URL pattern (e.g.
768 the pattern. This is assumed already!</P
770 > The pattern matching syntax is different for the domain and path parts of
771 the URL. The domain part uses a simple globbing type matching technique,
772 while the path part uses a more flexible
774 HREF="http://en.wikipedia.org/wiki/Regular_expressions"
779 Expressions (PCRE)"</SPAN
790 >www.example.com/</TT
794 > is a domain-only pattern and will match any request to <TT
798 regardless of which document on that server is requested. So ALL pages in
799 this domain would be covered by the scope of this action. Note that a
803 > is different and would NOT match.
813 > means exactly the same. For domain-only patterns, the trailing <TT
823 >www.example.com/index.html$</TT
827 > matches all the documents on <TT
831 whose name starts with <TT
840 >www.example.com/index.html$</TT
844 > matches only the single document <TT
861 > matches the document <TT
864 >, regardless of the domain,
871 > web server anywhere.
881 > matches nothing, since it would be interpreted as a domain name and
882 there is no top-level domain called <TT
897 >8.4.1. The Domain Pattern</A
900 > The matching of the domain part offers some flexible options: if the
901 domain starts or ends with a dot, it becomes unanchored at that end.
915 > matches any domain that <SPAN
935 > matches any domain that <SPAN
955 > matches any domain that <SPAN
965 And, by the way, also included would be any files or documents that exist
966 within that domain since no path limitations are specified. (Correctly
967 speaking: It matches any FQDN that contains <TT
971 a domain.) This might be <TT
981 >www.example.net/cgi/testing.pl</TT
982 > for instance. All these
989 > Additionally, there are wild-cards that you can use in the domain names
990 themselves. These work similarly to shell globbing type wild-cards:
994 > represents zero or more arbitrary characters (this is
997 HREF="http://en.wikipedia.org/wiki/Regular_expressions"
1004 > based syntax of <SPAN
1011 > represents any single character (this is equivalent to the
1012 regular expression syntax of a simple <SPAN
1015 >), and you can define
1018 >"character classes"</SPAN
1019 > in square brackets which is similar to
1020 the same regular expression technique. All of this can be freely mixed:</P
1024 CLASS="VARIABLELIST"
1029 >ad*.example.com</TT
1035 >"adserver.example.com"</SPAN
1039 >"ads.example.com"</SPAN
1040 >, etc but not <SPAN
1042 >"sfads.example.com"</SPAN
1049 >*ad*.example.com</TT
1053 > matches all of the above, and then some.
1069 >pictures.epix.com</TT
1072 >a.b.c.d.e.upix.com</TT
1079 >www[1-9a-ez].example.c*</TT
1085 >www1.example.com</TT
1089 >www4.example.cc</TT
1092 >wwwd.example.cy</TT
1096 >wwwz.example.com</TT
1106 >wwww.example.com</TT
1113 > While flexible, this is not the sophistication of full regular expression based syntax.</P
1121 >8.4.2. The Path Pattern</A
1127 > uses Perl compatible (PCRE)
1129 HREF="http://en.wikipedia.org/wiki/Regular_expressions"
1138 HREF="http://www.pcre.org/"
1142 matching the path portion (after the slash), and is thus more flexible.</P
1145 HREF="appendix.html#REGEX"
1147 > with a brief quick-start into regular
1148 expressions, and full (very technical) documentation on PCRE regex syntax is available on-line
1150 HREF="http://www.pcre.org/man.txt"
1152 >http://www.pcre.org/man.txt</A
1154 You might also find the Perl man page on regular expressions (<TT
1158 useful, which is available on-line at <A
1159 HREF="http://perldoc.perl.org/perlre.html"
1161 >http://perldoc.perl.org/perlre.html</A
1164 > Note that the path pattern is automatically left-anchored at the <SPAN
1168 i.e. it matches as if it would start with a <SPAN
1171 > (regular expression speak
1172 for the beginning of a line).</P
1174 > Please also note that matching in the path is <SPAN
1178 >CASE INSENSITIVE</I
1181 by default, but you can switch to case sensitive at any point in the pattern by using the
1187 >www.example.com/(?-i)PaTtErN.*</TT
1189 only documents whose path starts with <TT
1199 > this capitalization.</P
1203 CLASS="VARIABLELIST"
1208 >.example.com/.*</TT
1212 > Is equivalent to just <SPAN
1214 >".example.com"</SPAN
1215 >, since any documents
1216 within that domain are matched with or without the <SPAN
1220 regular expression. This is redundant
1226 >.example.com/.*/index.html$</TT
1230 > Will match any page in the domain of <SPAN
1232 >"example.com"</SPAN
1237 >, and that is part of some path. For
1238 example, it matches <SPAN
1240 >"www.example.com/testing/index.html"</SPAN
1244 >"www.example.com/index.html"</SPAN
1245 > because the regular
1246 expression called for at least two <SPAN
1250 requirement. It also would match
1253 >"www.example.com/testing/index_html"</SPAN
1255 special meta-character <SPAN
1264 >.example.com/(.*/)?index\.html$</TT
1268 > This regular expression is conditional so it will match any page
1272 > regardless of path which in this case can
1273 have one or more <SPAN
1276 >. And this one must contain exactly
1280 > (but does not have to end with that!).
1286 >.example.com/(.*/)(ads|banners?|junk)</TT
1290 > This regular expression will match any path of <SPAN
1292 >"example.com"</SPAN
1294 that contains any of the words <SPAN
1304 > (because of the <SPAN
1311 The path does not have to end in these words, just contain them.
1317 >.example.com/(.*/)(ads|banners?|junk)/.*\.(jpe?g|gif|png)$</TT
1321 > This is very much the same as above, except now it must end in either
1335 one is limited to common image formats.
1341 > There are many, many good examples to be found in <TT
1345 and more tutorials below in <A
1346 HREF="appendix.html#REGEX"
1347 >Appendix on regular expressions</A
1356 >8.4.3. The Tag Pattern</A
1359 > Tag patterns are used to change the applying actions based on the
1360 request's tags. Tags can be created with either the
1362 HREF="actions-file.html#CLIENT-HEADER-TAGGER"
1363 >client-header-tagger</A
1366 HREF="actions-file.html#SERVER-HEADER-TAGGER"
1367 >server-header-tagger</A
1370 > Tag patterns have to start with <SPAN
1377 can tell them apart from URL patterns. Everything after the colon
1378 including white space, is interpreted as a regular expression with
1379 path pattern syntax, except that tag patterns aren't left-anchored
1380 automatically (<SPAN
1383 > doesn't silently add a <SPAN
1387 you have to do it yourself if you need it).</P
1389 > To match all requests that are tagged with <SPAN
1393 your pattern line should be <SPAN
1400 > would work as well, but it would also
1401 match requests whose tags contain <SPAN
1408 > wouldn't work as it requires white space.</P
1410 > Sections can contain URL and tag patterns at the same time,
1411 but tag patterns are checked after the URL patterns and thus
1412 always overrule them, even if they are located before the URL patterns.</P
1414 > Once a new tag is added, Privoxy checks right away if it's matched by one
1415 of the tag patterns and updates the action settings accordingly. As a result
1416 tags can be used to activate other tagger actions, as long as these other
1417 taggers look for headers that haven't already be parsed.</P
1419 > For example you could tag client requests which use the
1424 then use this tag to activate another tagger that adds a tag if cookies
1425 are sent, and then use a block action based on the cookie tag. This allows
1426 the outcome of one action, to be input into a subsequent action. However if
1427 you'd reverse the position of the described taggers, and activated the
1428 method tagger based on the cookie tagger, no method tags would be created.
1429 The method tagger would look for the request line, but at the time
1430 the cookie tag is created, the request line has already been parsed.</P
1432 > While this is a limitation you should be aware of, this kind of
1433 indirection is seldom needed anyway and even the example doesn't
1434 make too much sense.</P
1446 > All actions are disabled by default, until they are explicitly enabled
1447 somewhere in an actions file. Actions are turned on if preceded with a
1451 >, and turned off if preceded with a <SPAN
1460 >"do that action"</SPAN
1467 >"please block URLs that match the
1468 following patterns"</SPAN
1475 block URLs that match the following patterns, even if <TT
1479 previously applied."</SPAN
1483 Again, actions are invoked by placing them on a line, enclosed in curly braces and
1484 separated by whitespace, like in
1487 >{+some-action -some-other-action{some-parameter}}</TT
1489 followed by a list of URL patterns, one per line, to which they apply.
1490 Together, the actions line and the following pattern lines make up a section
1491 of the actions file. </P
1494 Actions fall into three categories:</P
1502 Boolean, i.e the action can only be <SPAN
1525 > # enable action <TT
1536 > # disable action <TT
1558 Parameterized, where some value is required in order to enable this type of action.
1580 >} # enable action and set parameter to <TT
1586 # overwriting parameter from previous match if necessary
1592 > # disable action. The parameter can be omitted</PRE
1599 > Note that if the URL matches multiple positive forms of a parameterized action,
1600 the last match wins, i.e. the params from earlier matches are simply ignored.
1606 >+hide-user-agent{Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8.1.4) Gecko/20070602 Firefox/2.0.0.4}</TT
1613 Multi-value. These look exactly like parameterized actions,
1614 but they behave differently: If the action applies multiple times to the
1615 same URL, but with different parameters, <SPAN
1628 > matches are remembered. This is used for actions
1629 that can be executed for the same request repeatedly, like adding multiple
1630 headers, or filtering through multiple filters. Syntax:
1651 >} # enable action and add <TT
1656 > to the list of parameters
1667 >} # remove the parameter <TT
1672 > from the list of parameters
1673 # If it was the last one left, disable the action.
1679 > # disable this action completely and remove all parameters from the list</PRE
1689 >+add-header{X-Fun-Header: Some text}</TT
1693 >+filter{html-annoyances}</TT
1700 > If nothing is specified in any actions file, no <SPAN
1704 taken. So in this case <SPAN
1708 normal, non-blocking, non-filtering proxy. You must specifically enable the
1709 privacy and blocking features you need (although the provided default actions
1710 files will give a good starting point).</P
1712 > Later defined action sections always over-ride earlier ones of the same type.
1713 So exceptions to any rules you make, should come in the latter part of the file (or
1714 in a file that is processed later when using multiple actions files such
1718 >). For multi-valued actions, the actions
1719 are applied in the order they are specified. Actions files are processed in
1720 the order they are defined in <TT
1724 installation has three actions files). It also quite possible for any given
1725 URL to match more than one <SPAN
1728 > (because of wildcards and
1729 regular expressions), and thus to trigger more than one set of actions! Last
1732 > The list of valid <SPAN
1742 >8.5.1. add-header</A
1747 CLASS="VARIABLELIST"
1753 >Confuse log analysis, custom applications</P
1759 > Sends a user defined HTTP header to the web server.
1772 > Any string value is possible. Validity of the defined HTTP headers is not checked.
1773 It is recommended that you use the <SPAN
1787 > This action may be specified multiple times, in order to define multiple
1788 headers. This is rarely needed for the typical user. If you don't know what
1791 >"HTTP headers"</SPAN
1792 > are, you definitely don't need to worry about this
1808 >+add-header{X-User-Tracking: sucks}</PRE
1829 CLASS="VARIABLELIST"
1835 >Block ads or other unwanted content</P
1841 > Requests for URLs to which this action applies are blocked, i.e. the
1842 requests are trapped by <SPAN
1845 > and the requested URL is never retrieved,
1846 but is answered locally with a substitute page or image, as determined by
1850 HREF="actions-file.html#HANDLE-AS-IMAGE"
1857 HREF="actions-file.html#SET-IMAGE-BLOCKER"
1858 >set-image-blocker</A
1864 HREF="actions-file.html#HANDLE-AS-EMPTY-DOCUMENT"
1865 >handle-as-empty-document</A
1890 > sends a special <SPAN
1894 for requests to blocked pages. This page contains links to find out why the request
1895 was blocked, and a click-through to the blocked content (the latter only if compiled with the
1896 force feature enabled). The <SPAN
1899 > page adapts to the available
1900 screen space -- it displays full-blown if space allows, or miniaturized and text-only
1901 if loaded into a small frame or window. If you are using <SPAN
1905 right now, you can take a look at the
1907 HREF="http://ads.bannerserver.example.com/nasty-ads/sponsor.html"
1918 A very important exception occurs if <SPAN
1931 HREF="actions-file.html#HANDLE-AS-IMAGE"
1935 apply to the same request: it will then be replaced by an image. If
1939 HREF="actions-file.html#SET-IMAGE-BLOCKER"
1940 >set-image-blocker</A
1943 (see below) also applies, the type of image will be determined by its parameter,
1944 if not, the standard checkerboard pattern is sent.
1947 > It is important to understand this process, in order
1948 to understand how <SPAN
1952 ads and other unwanted content. Blocking is a core feature, and one
1953 upon which various other features depend.
1959 HREF="actions-file.html#FILTER"
1963 action can perform a very similar task, by <SPAN
1967 banner images and other content through rewriting the relevant URLs in the
1968 document's HTML source, so they don't get requested in the first place.
1969 Note that this is a totally different technique, and it's easy to confuse the two.
1973 >Example usage (section):</DT
1985 # Block and replace with "blocked" page
1986 .nasty-stuff.example.com
1988 {+block +handle-as-image}
1989 # Block and replace with image
1993 {+block +handle-as-empty-document}
1994 # Block and then ignore
1995 adserver.exampleclick.net/.*\.js$</PRE
2010 NAME="CLIENT-HEADER-FILTER"
2011 >8.5.3. client-header-filter</A
2016 CLASS="VARIABLELIST"
2022 > Rewrite or remove single client headers.
2029 > All client headers to which this action applies are filtered on-the-fly through
2030 the specified regular expression based substitutions.
2043 > The name of a client-header filter, as defined in one of the
2045 HREF="filter-file.html"
2054 > Client-header filters are applied to each header on its own, not to
2055 all at once. This makes it easier to diagnose problems, but on the downside
2056 you can't write filters that only change header x if header y's value is z.
2057 You can do that by using tags though.
2060 > Client-header filters are executed after the other header actions have finished
2061 and use their output as input.
2064 > If the request URL gets changed, <SPAN
2067 > will detect that and use the new
2068 one. This can be used to rewrite the request destination behind the client's
2069 back, for example to specify a Tor exit relay for certain requests.
2072 > Please refer to the <A
2073 HREF="filter-file.html"
2074 >filter file chapter</A
2076 to learn which client-header filters are available by default, and how to
2081 >Example usage (section):</DT
2092 >{+client-header-filter{hide-tor-exit-notation}}
2109 NAME="CLIENT-HEADER-TAGGER"
2110 >8.5.4. client-header-tagger</A
2115 CLASS="VARIABLELIST"
2121 > Block requests based on their headers.
2128 > Client headers to which this action applies are filtered on-the-fly through
2129 the specified regular expression based substitutions, the result is used as
2143 > The name of a client-header tagger, as defined in one of the
2145 HREF="filter-file.html"
2154 > Client-header taggers are applied to each header on its own,
2155 and as the header isn't modified, each tagger <SPAN
2162 > Client-header taggers are the first actions that are executed
2163 and their tags can be used to control every other action.
2167 >Example usage (section):</DT
2178 ># Tag every request with the User-Agent header
2179 {+client-header-tagger{user-agent}}
2196 NAME="CONTENT-TYPE-OVERWRITE"
2197 >8.5.5. content-type-overwrite</A
2202 CLASS="VARIABLELIST"
2208 >Stop useless download menus from popping up, or change the browser's rendering mode</P
2214 > Replaces the <SPAN
2216 >"Content-Type:"</SPAN
2217 > HTTP server header.
2239 >"Content-Type:"</SPAN
2240 > HTTP server header is used by the
2241 browser to decide what to do with the document. The value of this
2242 header can cause the browser to open a download menu instead of
2243 displaying the document by itself, even if the document's format is
2244 supported by the browser.
2247 > The declared content type can also affect which rendering mode
2248 the browser chooses. If XHTML is delivered as <SPAN
2252 many browsers treat it as yet another broken HTML document.
2253 If it is send as <SPAN
2255 >"application/xml"</SPAN
2257 XHTML support will only display it, if the syntax is correct.
2260 > If you see a web site that proudly uses XHTML buttons, but sets
2263 >"Content-Type: text/html"</SPAN
2264 >, you can use <SPAN
2268 to overwrite it with <SPAN
2270 >"application/xml"</SPAN
2272 the web master's claim inside your XHTML-supporting browser.
2273 If the syntax is incorrect, the browser will complain loudly.
2276 > You can also go the opposite direction: if your browser prints
2277 error messages instead of rendering a document falsely declared
2278 as XHTML, you can overwrite the content type with
2282 > and have it rendered as broken HTML document.
2287 >content-type-overwrite</TT
2291 >"Content-Type:"</SPAN
2292 > headers that look like some kind of text.
2293 If you want to overwrite it unconditionally, you have to combine it with
2297 HREF="actions-file.html#FORCE-TEXT-MODE"
2301 This limitation exists for a reason, think twice before circumventing it.
2304 > Most of the time it's easier to replace this action with a custom
2308 HREF="actions-file.html#SERVER-HEADER-FILTER"
2309 >server-header filter</A
2312 It allows you to activate it for every document of a certain site and it will still
2313 only replace the content types you aimed at.
2316 > Of course you can apply <TT
2318 >content-type-overwrite</TT
2320 to a whole site and then make URL based exceptions, but it's a lot
2321 more work to get the same precision.
2325 >Example usage (sections):</DT
2336 ># Check if www.example.net/ really uses valid XHTML
2337 { +content-type-overwrite{application/xml} }
2340 # but leave the content type unmodified if the URL looks like a style sheet
2341 {-content-type-overwrite}
2342 www.example.net/.*\.css$
2343 www.example.net/.*style</PRE
2358 NAME="CRUNCH-CLIENT-HEADER"
2359 >8.5.6. crunch-client-header</A
2364 CLASS="VARIABLELIST"
2370 >Remove a client header <SPAN
2373 > has no dedicated action for.</P
2379 > Deletes every header sent by the client that contains the string the user supplied as parameter.
2399 > This action allows you to block client headers for which no dedicated
2407 > will remove every client header that
2408 contains the string you supplied as parameter.
2411 > Regular expressions are <SPAN
2418 use this action to block different headers in the same request, unless
2419 they contain the same string.
2424 >crunch-client-header</TT
2425 > is only meant for quick tests.
2426 If you have to block several different headers, or only want to modify
2427 parts of them, you should use a
2431 HREF="actions-file.html#CLIENT-HEADER-FILTER"
2432 >client-header filter</A
2455 > Don't block any header without understanding the consequences.
2463 >Example usage (section):</DT
2474 ># Block the non-existent "Privacy-Violation:" client header
2475 { +crunch-client-header{Privacy-Violation:} }
2492 NAME="CRUNCH-IF-NONE-MATCH"
2493 >8.5.7. crunch-if-none-match</A
2498 CLASS="VARIABLELIST"
2504 >Prevent yet another way to track the user's steps between sessions.</P
2512 >"If-None-Match:"</SPAN
2513 > HTTP client header.
2533 > Removing the <SPAN
2535 >"If-None-Match:"</SPAN
2536 > HTTP client header
2537 is useful for filter testing, where you want to force a real
2538 reload instead of getting status code <SPAN
2542 would cause the browser to use a cached copy of the page.
2545 > It is also useful to make sure the header isn't used as a cookie
2546 replacement (unlikely but possible).
2549 > Blocking the <SPAN
2551 >"If-None-Match:"</SPAN
2552 > header shouldn't cause any
2553 caching problems, as long as the <SPAN
2555 >"If-Modified-Since:"</SPAN
2557 isn't blocked or missing as well.
2560 > It is recommended to use this action together with
2564 HREF="actions-file.html#HIDE-IF-MODIFIED-SINCE"
2565 >hide-if-modified-since</A
2572 HREF="actions-file.html#OVERWRITE-LAST-MODIFIED"
2573 >overwrite-last-modified</A
2579 >Example usage (section):</DT
2590 ># Let the browser revalidate cached documents but don't
2591 # allow the server to use the revalidation headers for user tracking.
2592 {+hide-if-modified-since{-60} \
2593 +overwrite-last-modified{randomize} \
2594 +crunch-if-none-match}
2610 NAME="CRUNCH-INCOMING-COOKIES"
2611 >8.5.8. crunch-incoming-cookies</A
2616 CLASS="VARIABLELIST"
2622 > Prevent the web server from setting HTTP cookies on your system
2631 >"Set-Cookie:"</SPAN
2632 > HTTP headers from server replies.
2652 > This action is only concerned with <SPAN
2669 HREF="actions-file.html#CRUNCH-OUTGOING-COOKIES"
2670 >crunch-outgoing-cookies</A
2679 > to disable HTTP cookies completely.
2688 > to use this action in conjunction
2692 HREF="actions-file.html#SESSION-COOKIES-ONLY"
2693 >session-cookies-only</A
2696 since it would prevent the session cookies from being set. See also
2700 HREF="actions-file.html#FILTER-CONTENT-COOKIES"
2701 >filter-content-cookies</A
2718 >+crunch-incoming-cookies</PRE
2733 NAME="CRUNCH-SERVER-HEADER"
2734 >8.5.9. crunch-server-header</A
2739 CLASS="VARIABLELIST"
2745 >Remove a server header <SPAN
2748 > has no dedicated action for.</P
2754 > Deletes every header sent by the server that contains the string the user supplied as parameter.
2774 > This action allows you to block server headers for which no dedicated
2778 > action exists. <SPAN
2782 will remove every server header that contains the string you supplied as parameter.
2785 > Regular expressions are <SPAN
2792 use this action to block different headers in the same request, unless
2793 they contain the same string.
2798 >crunch-server-header</TT
2799 > is only meant for quick tests.
2800 If you have to block several different headers, or only want to modify
2801 parts of them, you should use a custom
2805 HREF="actions-file.html#SERVER-HEADER-FILTER"
2806 >server-header filter</A
2829 > Don't block any header without understanding the consequences.
2837 >Example usage (section):</DT
2848 ># Crunch server headers that try to prevent caching
2849 { +crunch-server-header{no-cache} }
2865 NAME="CRUNCH-OUTGOING-COOKIES"
2866 >8.5.10. crunch-outgoing-cookies</A
2871 CLASS="VARIABLELIST"
2877 > Prevent the web server from reading any HTTP cookies from your system
2887 > HTTP headers from client requests.
2907 > This action is only concerned with <SPAN
2924 HREF="actions-file.html#CRUNCH-INCOMING-COOKIES"
2925 >crunch-incoming-cookies</A
2934 > to disable HTTP cookies completely.
2943 > to use this action in conjunction
2947 HREF="actions-file.html#SESSION-COOKIES-ONLY"
2948 >session-cookies-only</A
2951 since it would prevent the session cookies from being read.
2966 >+crunch-outgoing-cookies</PRE
2981 NAME="DEANIMATE-GIFS"
2982 >8.5.11. deanimate-gifs</A
2987 CLASS="VARIABLELIST"
2993 >Stop those annoying, distracting animated GIF images.</P
2999 > De-animate GIF animations, i.e. reduce them to their first or last image.
3025 > This will also shrink the images considerably (in bytes, not pixels!). If
3029 > is given, the first frame of the animation
3030 is used as the replacement. If <SPAN
3033 > is given, the last
3034 frame of the animation is used instead, which probably makes more sense for
3035 most banner animations, but also has the risk of not showing the entire
3036 last frame (if it is only a delta to an earlier frame).
3039 > You can safely use this action with patterns that will also match non-GIF
3040 objects, because no attempt will be made at anything that doesn't look like
3056 >+deanimate-gifs{last}</PRE
3071 NAME="DOWNGRADE-HTTP-VERSION"
3072 >8.5.12. downgrade-http-version</A
3077 CLASS="VARIABLELIST"
3083 >Work around (very rare) problems with HTTP/1.1</P
3089 > Downgrades HTTP/1.1 client requests and server replies to HTTP/1.0.
3109 > This is a left-over from the time when <SPAN
3113 didn't support important HTTP/1.1 features well. It is left here for the
3114 unlikely case that you experience HTTP/1.1 related problems with some server
3115 out there. Not all HTTP/1.1 features and requirements are supported yet,
3116 so there is a chance you might need this action.
3120 >Example usage (section):</DT
3131 >{+downgrade-http-version}
3132 problem-host.example.com</PRE
3147 NAME="FAST-REDIRECTS"
3148 >8.5.13. fast-redirects</A
3153 CLASS="VARIABLELIST"
3159 >Fool some click-tracking scripts and speed up indirect links.</P
3165 > Detects redirection URLs and redirects the browser without contacting
3166 the redirection server first.
3185 >"simple-check"</SPAN
3186 > to just search for the string <SPAN
3190 to detect redirection URLs.
3197 >"check-decoded-url"</SPAN
3198 > to decode URLs (if necessary) before searching
3199 for redirection URLs.
3209 Many sites, like yahoo.com, don't just link to other sites. Instead, they
3210 will link to some script on their own servers, giving the destination as a
3211 parameter, which will then redirect you to the final target. URLs
3212 resulting from this scheme typically look like:
3215 >"http://www.example.org/click-tracker.cgi?target=http%3a//www.example.net/"</SPAN
3219 > Sometimes, there are even multiple consecutive redirects encoded in the
3220 URL. These redirections via scripts make your web browsing more traceable,
3221 since the server from which you follow such a link can see where you go
3222 to. Apart from that, valuable bandwidth and time is wasted, while your
3223 browser asks the server for one redirect after the other. Plus, it feeds
3227 > This feature is currently not very smart and is scheduled for improvement.
3228 If it is enabled by default, you will have to create some exceptions to
3229 this action. It can lead to failures in several ways:
3232 > Not every URLs with other URLs as parameters is evil.
3233 Some sites offer a real service that requires this information to work.
3234 For example a validation service needs to know, which document to validate.
3238 > assumes that every URL parameter that
3239 looks like another URL is a redirection target, and will always redirect to
3240 the last one. Most of the time the assumption is correct, but if it isn't,
3241 the user gets redirected anyway.
3244 > Another failure occurs if the URL contains other parameters after the URL parameter.
3248 >"http://www.example.org/?redirect=http%3a//www.example.net/&foo=bar"</SPAN
3250 contains the redirection URL <SPAN
3252 >"http://www.example.net/"</SPAN
3254 followed by another parameter. <TT
3258 and will cause a redirect to <SPAN
3260 >"http://www.example.net/&foo=bar"</SPAN
3262 Depending on the target server configuration, the parameter will be silently ignored
3265 >"page not found"</SPAN
3266 > error. You can prevent this problem by
3270 HREF="actions-file.html#REDIRECT"
3274 to remove the last part of the URL, but it requires a little effort.
3277 > To detect a redirection URL, <TT
3281 looks for the string <SPAN
3284 >, either in plain text
3285 (invalid but often used) or encoded as <SPAN
3289 Some sites use their own URL encoding scheme, encrypt the address
3290 of the target server or replace it with a database id. In theses cases
3294 > is fooled and the request reaches the
3295 redirection server where it probably gets logged.
3310 > { +fast-redirects{simple-check} }
3313 { +fast-redirects{check-decoded-url} }
3314 another.example.com/testing</PRE
3335 CLASS="VARIABLELIST"
3341 >Get rid of HTML and JavaScript annoyances, banner advertisements (by size),
3342 do fun text replacements, add personalized effects, etc.</P
3348 > All instances of text-based type, most notably HTML and JavaScript, to which
3349 this action applies, can be filtered on-the-fly through the specified regular
3350 expression based substitutions. (Note: as of version 3.0.3 plain text documents
3351 are exempted from filtering, because web servers often use the
3355 > MIME type for all files whose type they don't know.)
3368 > The name of a content filter, as defined in the <A
3369 HREF="filter-file.html"
3372 Filters can be defined in one or more files as defined by the
3376 HREF="config.html#FILTERFILE"
3387 > is the collection of filters
3388 supplied by the developers. Locally defined filters should go
3389 in their own file, such as <TT
3395 > When used in its negative form,
3396 and without parameters, <SPAN
3402 > filtering is completely disabled.
3409 > For your convenience, there are a number of pre-defined filters available
3410 in the distribution filter file that you can use. See the examples below for
3414 > Filtering requires buffering the page content, which may appear to
3415 slow down page rendering since nothing is displayed until all content has
3416 passed the filters. (It does not really take longer, but seems that way
3417 since the page is not incrementally displayed.) This effect will be more
3418 noticeable on slower connections.
3423 >"Rolling your own"</SPAN
3425 filters requires a knowledge of
3427 HREF="http://en.wikipedia.org/wiki/Regular_expressions"
3436 HREF="http://en.wikipedia.org/wiki/Html"
3443 This is very powerful feature, and potentially very intrusive.
3444 Filters should be used with caution, and where an equivalent
3451 > The amount of data that can be filtered is limited to the
3455 HREF="config.html#BUFFER-LIMIT"
3459 option in the main <A
3463 default is 4096 KB (4 Megs). Once this limit is exceeded, the buffered
3464 data, and all pending data, is passed through unfiltered.
3467 > Inappropriate MIME types, such as zipped files, are not filtered at all.
3468 (Again, only text-based types except plain text). Encrypted SSL data
3469 (from HTTPS servers) cannot be filtered either, since this would violate
3470 the integrity of the secure transaction. In some situations it might
3471 be necessary to protect certain text, like source code, from filtering
3472 by defining appropriate <TT
3478 > Compressed content can't be filtered either, unless <SPAN
3482 is compiled with zlib support (requires at least <SPAN
3489 > will decompress the content before filtering
3493 > If you use a <SPAN
3496 > version without zlib support, but want filtering to work on
3497 as much documents as possible, even those that would normally be sent compressed,
3498 you must use the <TT
3501 HREF="actions-file.html#PREVENT-COMPRESSION"
3502 >prevent-compression</A
3505 action in conjunction with <TT
3511 > Content filtering can achieve some of the same effects as the
3515 HREF="actions-file.html#BLOCK"
3519 action, i.e. it can be used to block ads and banners. But the mechanism
3520 works quite differently. One effective use, is to block ad banners
3521 based on their size (see below), since many of these seem to be somewhat
3528 > with suggestions for new or
3529 improved filters is particularly welcome!
3532 > The below list has only the names and a one-line description of each
3533 predefined filter. There are <A
3534 HREF="filter-file.html#PREDEFINED-FILTERS"
3536 verbose explanations</A
3537 > of what these filters do in the <A
3538 HREF="filter-file.html"
3539 >filter file chapter</A
3544 >Example usage (with filters from the distribution <TT
3549 HREF="filter-file.html#PREDEFINED-FILTERS"
3550 >the Predefined Filters section</A
3552 more explanation on each:</DT
3556 NAME="FILTER-JS-ANNOYANCES"
3567 >+filter{js-annoyances} # Get rid of particularly annoying JavaScript abuse</PRE
3575 NAME="FILTER-JS-EVENTS"
3586 >+filter{js-events} # Kill all JS event bindings (Radically destructive! Only for extra nasty sites)</PRE
3594 NAME="FILTER-HTML-ANNOYANCES"
3605 >+filter{html-annoyances} # Get rid of particularly annoying HTML abuse</PRE
3613 NAME="FILTER-CONTENT-COOKIES"
3624 >+filter{content-cookies} # Kill cookies that come in the HTML or JS content</PRE
3632 NAME="FILTER-REFRESH-TAGS"
3643 >+filter{refresh-tags} # Kill automatic refresh tags (for dial-on-demand setups)</PRE
3651 NAME="FILTER-UNSOLICITED-POPUPS"
3662 >+filter{unsolicited-popups} # Disable only unsolicited pop-up windows. Useful if your browser lacks this ability.</PRE
3670 NAME="FILTER-ALL-POPUPS"
3681 >+filter{all-popups} # Kill all popups in JavaScript and HTML. Useful if your browser lacks this ability.</PRE
3689 NAME="FILTER-IMG-REORDER"
3700 >+filter{img-reorder} # Reorder attributes in <img> tags to make the banners-by-* filters more effective</PRE
3708 NAME="FILTER-BANNERS-BY-SIZE"
3719 >+filter{banners-by-size} # Kill banners by size</PRE
3727 NAME="FILTER-BANNERS-BY-LINK"
3738 >+filter{banners-by-link} # Kill banners by their links to known clicktrackers</PRE
3746 NAME="FILTER-WEBBUGS"
3757 >+filter{webbugs} # Squish WebBugs (1x1 invisible GIFs used for user tracking)</PRE
3765 NAME="FILTER-TINY-TEXTFORMS"
3776 >+filter{tiny-textforms} # Extend those tiny textareas up to 40x80 and kill the hard wrap</PRE
3784 NAME="FILTER-JUMPING-WINDOWS"
3795 >+filter{jumping-windows} # Prevent windows from resizing and moving themselves</PRE
3803 NAME="FILTER-FRAMESET-BORDERS"
3814 >+filter{frameset-borders} # Give frames a border and make them resizeable</PRE
3822 NAME="FILTER-DEMORONIZER"
3833 >+filter{demoronizer} # Fix MS's non-standard use of standard charsets</PRE
3841 NAME="FILTER-SHOCKWAVE-FLASH"
3852 >+filter{shockwave-flash} # Kill embedded Shockwave Flash objects</PRE
3860 NAME="FILTER-QUICKTIME-KIOSKMODE"
3871 >+filter{quicktime-kioskmode} # Make Quicktime movies savable</PRE
3890 >+filter{fun} # Text replacements for subversive browsing fun!</PRE
3898 NAME="FILTER-CRUDE-PARENTAL"
3909 >+filter{crude-parental} # Crude parental filtering (demo only)</PRE
3917 NAME="FILTER-IE-EXPLOITS"
3928 >+filter{ie-exploits} # Disable a known Internet Explorer bug exploits</PRE
3936 NAME="FILTER-SITE-SPECIFICS"
3947 >+filter{site-specifics} # Custom filters for specific site related problems</PRE
3955 NAME="FILTER-GOOGLE"
3966 >+filter{google} # Removes text ads and other Google specific improvements</PRE
3985 >+filter{yahoo} # Removes text ads and other Yahoo specific improvements</PRE
4004 >+filter{msn} # Removes text ads and other MSN specific improvements</PRE
4012 NAME="FILTER-BLOGSPOT"
4023 >+filter{blogspot} # Cleans up Blogspot blogs</PRE
4031 NAME="FILTER-NO-PING"
4042 >+filter{no-ping} # Removes non-standard ping attributes from anchor and area tags</PRE
4057 NAME="FORCE-TEXT-MODE"
4058 >8.5.15. force-text-mode</A
4063 CLASS="VARIABLELIST"
4072 > to treat a document as if it was in some kind of <SPAN
4084 > Declares a document as text, even if the <SPAN
4086 >"Content-Type:"</SPAN
4087 > isn't detected as such.
4110 HREF="actions-file.html#FILTER"
4117 > tries to only filter files that are
4118 in some kind of text format. The same restrictions apply to
4122 HREF="actions-file.html#CONTENT-TYPE-OVERWRITE"
4123 >content-type-overwrite</A
4128 >force-text-mode</TT
4129 > declares a document as text,
4130 without looking at the <SPAN
4132 >"Content-Type:"</SPAN
4154 > Think twice before activating this action. Filtering binary data
4155 with regular expressions can cause file damage.
4190 NAME="FORWARD-OVERRIDE"
4191 >8.5.16. forward-override</A
4196 CLASS="VARIABLELIST"
4202 >Change the forwarding settings based on User-Agent or request origin</P
4208 > Overrules the forward directives in the configuration file.
4228 > to use a direct connection without any additional proxies.</P
4234 >"forward 127.0.0.1:8123"</SPAN
4235 > to use the HTTP proxy listening at 127.0.0.1 port 8123.
4242 >"forward-socks4a 127.0.0.1:9050 ."</SPAN
4243 > to use the socks4a proxy listening at
4244 127.0.0.1 port 9050. Replace <SPAN
4246 >"forward-socks4a"</SPAN
4249 >"forward-socks4"</SPAN
4251 to use a socks4 connection (with local DNS resolution) instead.
4258 >"forward-socks4a 127.0.0.1:9050 proxy.example.org:8000"</SPAN
4259 > to use the socks4a proxy
4260 listening at 127.0.0.1 port 9050 to reach the HTTP proxy listening at proxy.example.org port 8000.
4263 >"forward-socks4a"</SPAN
4266 >"forward-socks4"</SPAN
4267 > to use a socks4 connection
4268 (with local DNS resolution) instead.
4277 > This action takes parameters similar to the
4279 HREF="config.html#FORWARDING"
4281 > directives in the configuration
4282 file, but without the URL pattern. It can be used as replacement, but normally it's only
4283 used in cases where matching based on the request URL isn't sufficient.
4304 > Please read the description for the <A
4305 HREF="config.html#FORWARDING"
4308 using this action. Forwarding to the wrong people will reduce your privacy and increase the
4309 chances of man-in-the-middle attacks.
4312 > If the ports are missing or invalid, default values will be used. This might change
4313 in the future and you shouldn't rely on it. Otherwise incorrect syntax causes Privoxy
4318 HREF="http://config.privoxy.org/show-url-info"
4320 >show-url-info CGI page</A
4322 to verify that your forward settings do what you thought the do.
4341 ># Always use direct connections for requests previously tagged as
4344 >"User-Agent: fetch libfetch/2.0"</SPAN
4346 # resuming downloads continues to work.
4347 # This way you can continue to use Tor for your normal browsing,
4348 # without overloading the Tor network with your FreeBSD ports updates
4349 # or downloads of bigger files like ISOs.
4350 # Note that HTTP headers are easy to fake and therefore their
4351 # values are as (un)trustworthy as your clients and users.
4352 {+forward-override{forward .} \
4353 -hide-if-modified-since \
4354 -overwrite-last-modified \
4356 TAG:^User-Agent: fetch libfetch/2\.0$
4372 NAME="HANDLE-AS-EMPTY-DOCUMENT"
4373 >8.5.17. handle-as-empty-document</A
4378 CLASS="VARIABLELIST"
4384 >Mark URLs that should be replaced by empty documents <SPAN
4388 >if they get blocked</I
4396 > This action alone doesn't do anything noticeable. It just marks URLs.
4400 HREF="actions-file.html#BLOCK"
4410 the presence or absence of this mark decides whether an HTML <SPAN
4414 page, or an empty document will be sent to the client as a substitute for the blocked content.
4421 > document isn't literally empty, but actually contains a single space.
4441 > Some browsers complain about syntax errors if JavaScript documents
4442 are blocked with <SPAN
4446 default HTML page; this option can be used to silence them.
4447 And of course this action can also be used to eliminate the <SPAN
4451 BLOCKED message in frames.
4454 > The content type for the empty document can be specified with
4458 HREF="actions-file.html#CONTENT-TYPE-OVERWRITE"
4459 >content-type-overwrite{}</A
4462 but usually this isn't necessary.
4477 ># Block all documents on example.org that end with ".js",
4478 # but send an empty document instead of the usual HTML message.
4479 {+block +handle-as-empty-document}
4496 NAME="HANDLE-AS-IMAGE"
4497 >8.5.18. handle-as-image</A
4502 CLASS="VARIABLELIST"
4508 >Mark URLs as belonging to images (so they'll be replaced by images <SPAN
4512 >if they do get blocked</I
4514 >, rather than HTML pages)</P
4520 > This action alone doesn't do anything noticeable. It just marks URLs as images.
4524 HREF="actions-file.html#BLOCK"
4534 the presence or absence of this mark decides whether an HTML <SPAN
4538 page, or a replacement image (as determined by the <TT
4541 HREF="actions-file.html#SET-IMAGE-BLOCKER"
4542 >set-image-blocker</A
4544 > action) will be sent to the
4545 client as a substitute for the blocked content.
4565 > The below generic example section is actually part of <TT
4569 It marks all URLs with well-known image file name extensions as images and should
4573 > Users will probably only want to use the handle-as-image action in conjunction with
4577 HREF="actions-file.html#BLOCK"
4580 >, to block sources of banners, whose URLs don't
4581 reflect the file type, like in the second example section.
4584 > Note that you cannot treat HTML pages as images in most cases. For instance, (in-line) ad
4585 frames require an HTML page to be sent, or they won't display properly.
4588 >handle-as-image</TT
4589 > in this situation will not replace the
4590 ad frame with an image, but lead to error messages.
4594 >Example usage (sections):</DT
4605 ># Generic image extensions:
4608 /.*\.(gif|jpg|jpeg|png|bmp|ico)$
4610 # These don't look like images, but they're banners and should be
4611 # blocked as images:
4613 {+block +handle-as-image}
4614 some.nasty-banner-server.com/junk.cgi\?output=trash
4616 # Banner source! Who cares if they also have non-image content?
4617 ad.doubleclick.net </PRE
4632 NAME="HIDE-ACCEPT-LANGUAGE"
4633 >8.5.19. hide-accept-language</A
4638 CLASS="VARIABLELIST"
4644 >Pretend to use different language settings.</P
4650 > Deletes or replaces the <SPAN
4652 >"Accept-Language:"</SPAN
4653 > HTTP header in client requests.
4669 >, or any user defined value.
4676 > Faking the browser's language settings can be useful to make a
4677 foreign User-Agent set with
4681 HREF="actions-file.html#HIDE-USER-AGENT"
4688 > However some sites with content in different languages check the
4691 >"Accept-Language:"</SPAN
4692 > to decide which one to take by default.
4693 Sometimes it isn't possible to later switch to another language without
4696 >"Accept-Language:"</SPAN
4700 > Therefore it's a good idea to either only change the
4703 >"Accept-Language:"</SPAN
4704 > header to languages you understand,
4705 or to languages that aren't wide spread.
4708 > Before setting the <SPAN
4710 >"Accept-Language:"</SPAN
4712 to a rare language, you should consider that it helps to
4713 make your requests unique and thus easier to trace.
4714 If you don't plan to change this header frequently,
4715 you should stick to a common language.
4719 >Example usage (section):</DT
4730 ># Pretend to use Canadian language settings.
4731 {+hide-accept-language{en-ca} \
4732 +hide-user-agent{Mozilla/5.0 (X11; U; OpenBSD i386; en-CA; rv:1.8.0.4) Gecko/20060628 Firefox/1.5.0.4} \
4749 NAME="HIDE-CONTENT-DISPOSITION"
4750 >8.5.20. hide-content-disposition</A
4755 CLASS="VARIABLELIST"
4761 >Prevent download menus for content you prefer to view inside the browser.</P
4767 > Deletes or replaces the <SPAN
4769 >"Content-Disposition:"</SPAN
4770 > HTTP header set by some servers.
4786 >, or any user defined value.
4793 > Some servers set the <SPAN
4795 >"Content-Disposition:"</SPAN
4797 documents they assume you want to save locally before viewing them.
4800 >"Content-Disposition:"</SPAN
4801 > header contains the file name
4802 the browser is supposed to use by default.
4805 > In most browsers that understand this header, it makes it impossible to
4812 > the document, without downloading it first,
4813 even if it's just a simple text file or an image.
4816 > Removing the <SPAN
4818 >"Content-Disposition:"</SPAN
4820 to prevent this annoyance, but some browsers additionally check the
4823 >"Content-Type:"</SPAN
4824 > header, before they decide if they can
4825 display a document without saving it first. In these cases, you have
4826 to change this header as well, before the browser stops displaying
4830 > It is also possible to change the server's file name suggestion
4831 to another one, but in most cases it isn't worth the time to set
4835 > This action will probably be removed in the future,
4836 use server-header filters instead.
4851 ># Disarm the download link in Sourceforge's patch tracker
4853 +content-type-overwrite{text/plain}\
4854 +hide-content-disposition{block} }
4855 .sourceforge.net/tracker/download\.php</PRE
4870 NAME="HIDE-IF-MODIFIED-SINCE"
4871 >8.5.21. hide-if-modified-since</A
4876 CLASS="VARIABLELIST"
4882 >Prevent yet another way to track the user's steps between sessions.</P
4890 >"If-Modified-Since:"</SPAN
4891 > HTTP client header or modifies its value.
4907 >, or a user defined value that specifies a range of hours.
4914 > Removing this header is useful for filter testing, where you want to force a real
4915 reload instead of getting status code <SPAN
4918 >, which would cause the
4919 browser to use a cached copy of the page.
4922 > Instead of removing the header, <TT
4924 >hide-if-modified-since</TT
4926 also add or subtract a random amount of time to/from the header's value.
4927 You specify a range of minutes where the random factor should be chosen from and
4931 > does the rest. A negative value means
4932 subtracting, a positive value adding.
4935 > Randomizing the value of the <SPAN
4937 >"If-Modified-Since:"</SPAN
4939 it less likely that the server can use the time as a cookie replacement,
4940 but you will run into caching problems if the random range is too high.
4943 > It is a good idea to only use a small negative value and let
4947 HREF="actions-file.html#OVERWRITE-LAST-MODIFIED"
4948 >overwrite-last-modified</A
4951 handle the greater changes.
4954 > It is also recommended to use this action together with
4958 HREF="actions-file.html#CRUNCH-IF-NONE-MATCH"
4959 >crunch-if-none-match</A
4962 otherwise it's more or less pointless.
4966 >Example usage (section):</DT
4977 ># Let the browser revalidate but make tracking based on the time less likely.
4978 {+hide-if-modified-since{-60} \
4979 +overwrite-last-modified{randomize} \
4980 +crunch-if-none-match}
4996 NAME="HIDE-FORWARDED-FOR-HEADERS"
4997 >8.5.22. hide-forwarded-for-headers</A
5002 CLASS="VARIABLELIST"
5008 >Improve privacy by not forwarding the source of the request in the HTTP headers.</P
5014 > Deletes any existing <SPAN
5016 >"X-Forwarded-for:"</SPAN
5017 > HTTP header from client requests.
5037 > It is safe and recommended to leave this on.
5052 >+hide-forwarded-for-headers</PRE
5067 NAME="HIDE-FROM-HEADER"
5068 >8.5.23. hide-from-header</A
5073 CLASS="VARIABLELIST"
5079 >Keep your (old and ill) browser from telling web servers your email address</P
5085 > Deletes any existing <SPAN
5088 > HTTP header, or replaces it with the
5105 >, or any user defined value.
5115 > will completely remove the header
5116 (not to be confused with the <TT
5119 HREF="actions-file.html#BLOCK"
5126 > Alternately, you can specify any value you prefer to be sent to the web
5127 server. If you do, it is a matter of fairness not to use any address that
5128 is actually used by a real person.
5131 > This action is rarely needed, as modern web browsers don't send
5150 >+hide-from-header{block}</PRE
5163 >+hide-from-header{spam-me-senseless@sittingduck.example.com}</PRE
5178 NAME="HIDE-REFERRER"
5179 >8.5.24. hide-referrer</A
5187 CLASS="VARIABLELIST"
5193 >Conceal which link you followed to get to a particular site</P
5202 > (sic) HTTP header from the client request,
5203 or replaces it with a forged one.
5222 >"conditional-block"</SPAN
5223 > to delete the header completely if the host has changed.</P
5229 >"conditional-forge"</SPAN
5230 > to forge the header if the host has changed.</P
5237 > to delete the header unconditionally.</P
5244 > to pretend to be coming from the homepage of the server we are talking to.</P
5248 >Any other string to set a user defined referrer.</P
5258 >conditional-block</TT
5259 > is the only parameter,
5260 that isn't easily detected in the server's log file. If it blocks the
5261 referrer, the request will look like the visitor used a bookmark or
5262 typed in the address directly.
5265 > Leaving the referrer unmodified for requests on the same host
5266 allows the server owner to see the visitor's <SPAN
5270 but in most cases she could also get that information by comparing
5271 other parts of the log file: for example the User-Agent if it isn't
5272 a very common one, or the user's IP address if it doesn't change between
5276 > Always blocking the referrer, or using a custom one, can lead to
5277 failures on servers that check the referrer before they answer any
5278 requests, in an attempt to prevent their content from being
5279 embedded or linked to elsewhere.
5284 >conditional-block</TT
5289 will work with referrer checks, as long as content and valid referring page
5290 are on the same host. Most of the time that's the case.
5297 > is an alternate spelling of
5301 > and the two can be can be freely
5302 substituted with each other. (<SPAN
5306 correct English spelling, however the HTTP specification has a bug - it
5307 requires it to be spelled as <SPAN
5325 >+hide-referrer{forge}</PRE
5338 >+hide-referrer{http://www.yahoo.com/}</PRE
5353 NAME="HIDE-USER-AGENT"
5354 >8.5.25. hide-user-agent</A
5359 CLASS="VARIABLELIST"
5365 >Try to conceal your type of browser and client operating system</P
5371 > Replaces the value of the <SPAN
5373 >"User-Agent:"</SPAN
5375 in client requests with the specified value.
5388 > Any user-defined string.
5413 > This can lead to problems on web sites that depend on looking at this header in
5414 order to customize their content for different browsers (which, by the
5421 > the right thing to do: good web sites
5422 work browser-independently).
5429 > Using this action in multi-user setups or wherever different types of
5430 browsers will access the same <SPAN
5440 >. In single-user, single-browser
5441 setups, you might use it to delete your OS version information from
5442 the headers, because it is an invitation to exploit known bugs for your
5443 OS. It is also occasionally useful to forge this in order to access
5444 sites that won't let you in otherwise (though there may be a good
5445 reason in some cases). Example of this: some MSN sites will not
5449 > enter, yet forging to a
5453 > user-agent works just fine.
5454 (Must be just a silly MS goof, I'm sure :-).
5457 > More information on known user-agent strings can be found at
5459 HREF="http://www.user-agents.org/"
5461 >http://www.user-agents.org/</A
5465 HREF="http://en.wikipedia.org/wiki/User_agent"
5467 >http://en.wikipedia.org/wiki/User_agent</A
5483 >+hide-user-agent{Netscape 6.1 (X11; I; Linux 2.4.18 i686)}</PRE
5498 NAME="INSPECT-JPEGS"
5499 >8.5.26. inspect-jpegs</A
5504 CLASS="VARIABLELIST"
5510 >Try to protect against a MS buffer over-run in JPEG processing</P
5516 > Protect against a known exploit
5536 > See Microsoft Security Bulletin MS04-028. JPEG images are one of the most
5537 common image types found across the Internet. The exploit as described can
5538 allow execution of code on the target system, giving an attacker access
5539 to the system in question by merely planting an altered JPEG image, which
5540 would have no obvious indications of what lurks inside. This action
5541 tries to prevent this exploit if delivered through unencrypted HTTP.
5544 > Note that the exploit mentioned is several years old
5545 and it's unlikely that your client is still vulnerable
5546 against it. This action may be removed in one of the
5562 >+inspect-jpegs</PRE
5577 >8.5.27. kill-popups<A
5585 CLASS="VARIABLELIST"
5591 >Eliminate those annoying pop-up windows (deprecated)</P
5597 > While loading the document, replace JavaScript code that opens
5598 pop-up windows with (syntactically neutral) dummy code on the fly.
5618 > This action is basically a built-in, hardwired special-purpose filter
5619 action, but there are important differences: For <TT
5623 the document need not be buffered, so it can be incrementally rendered while
5624 downloading. But <TT
5627 > doesn't catch as many pop-ups as
5631 HREF="actions-file.html#FILTER-ALL-POPUPS"
5640 does and is not as smart as <TT
5643 HREF="actions-file.html#FILTER-UNSOLICITED-POPUPS"
5647 >unsolicited-popups</I
5655 > Think of it as a fast and efficient replacement for a filter that you
5656 can use if you don't want any filtering at all. Note that it doesn't make
5657 sense to combine it with any <TT
5660 HREF="actions-file.html#FILTER"
5664 since as soon as one <TT
5667 HREF="actions-file.html#FILTER"
5671 the whole document needs to be buffered anyway, which destroys the advantage of
5675 > action over its filter equivalent.
5678 > Killing all pop-ups unconditionally is problematic. Many shops and banks rely on
5679 pop-ups to display forms, shopping carts etc, and the <TT
5682 HREF="actions-file.html#FILTER-UNSOLICITED-POPUPS"
5686 >unsolicited-popups</I
5691 > does a better job of catching only the unwanted ones.
5694 > If the only kind of pop-ups that you want to kill are exit consoles (those
5701 > windows that appear when you close an other
5702 one), you might want to use
5706 HREF="actions-file.html#FILTER"
5718 > This action is most appropriate for browsers that don't have any controls
5719 for unwanted pop-ups. Not recommended for general usage.
5722 > This action doesn't work very reliable and may be removed in future releases.
5751 NAME="LIMIT-CONNECT"
5752 >8.5.28. limit-connect</A
5757 CLASS="VARIABLELIST"
5763 >Prevent abuse of <SPAN
5766 > as a TCP proxy relay or disable SSL for untrusted sites</P
5772 > Specifies to which ports HTTP CONNECT requests are allowable.
5785 > A comma-separated list of ports or port ranges (the latter using dashes, with the minimum
5786 defaulting to 0 and the maximum to 65K).
5793 > By default, i.e. if no <TT
5800 > only allows HTTP CONNECT
5801 requests to port 443 (the standard, secure HTTPS port). Use
5805 > if more fine-grained control is desired
5806 for some or all destinations.
5809 > The CONNECT methods exists in HTTP to allow access to secure websites
5813 > URLs) through proxies. It works very simply:
5814 the proxy connects to the server on the specified port, and then
5815 short-circuits its connections to the client and to the remote server.
5816 This means CONNECT-enabled proxies can be used as TCP relays very easily.
5822 > relays HTTPS traffic without seeing
5823 the decoded content. Websites can leverage this limitation to circumvent <SPAN
5827 filters. By specifying an invalid port range you can disable HTTPS entirely.
5828 If you plan to disable SSL by default, consider enabling
5832 HREF="actions-file.html#TREAT-FORBIDDEN-CONNECTS-LIKE-BLOCKS"
5833 >treat-forbidden-connects-like-blocks</A
5836 as well, to be able to quickly create exceptions.
5840 >Example usages:</DT
5851 >+limit-connect{443} # This is the default and need not be specified.
5852 +limit-connect{80,443} # Ports 80 and 443 are OK.
5853 +limit-connect{-3, 7, 20-100, 500-} # Ports less than 3, 7, 20 to 100 and above 500 are OK.
5854 +limit-connect{-} # All ports are OK
5855 +limit-connect{,} # No HTTPS/SSL traffic is allowed</PRE
5870 NAME="PREVENT-COMPRESSION"
5871 >8.5.29. prevent-compression</A
5876 CLASS="VARIABLELIST"
5882 > Ensure that servers send the content uncompressed, so it can be
5886 HREF="actions-file.html#FILTER"
5896 > Removes the Accept-Encoding header which can be used to ask for compressed transfer.
5916 > More and more websites send their content compressed by default, which
5917 is generally a good idea and saves bandwidth. But the <TT
5920 HREF="actions-file.html#FILTER"
5926 HREF="actions-file.html#DEANIMATE-GIFS"
5933 HREF="actions-file.html#KILL-POPUPS"
5937 access to the uncompressed data.
5940 > When compiled with zlib support (available since <SPAN
5943 > 3.0.7), content that should be
5944 filtered is decompressed on-the-fly and you don't have to worry about this action.
5945 If you are using an older <SPAN
5948 > version, or one that hasn't been compiled with zlib
5949 support, this action can be used to convince the server to send the content uncompressed.
5952 > Most text-based instances compress very well, the size is seldom decreased by less than 50%,
5953 for markup-heavy instances like news feeds saving more than 90% of the original size isn't
5957 > Not using compression will therefore slow down the transfer, and you should only
5958 enable this action if you really need it. As of <SPAN
5961 > 3.0.7 it's disabled in all
5962 predefined action settings.
5965 > Note that some (rare) ill-configured sites don't handle requests for uncompressed
5966 documents correctly. Broken PHP applications tend to send an empty document body,
5967 some IIS versions only send the beginning of the content. If you enable
5970 >prevent-compression</TT
5971 > per default, you might want to add
5972 exceptions for those sites. See the example for how to do that.
5976 >Example usage (sections):</DT
5987 ># Selectively turn off compression, and enable a filter
5989 { +filter{tiny-textforms} +prevent-compression }
5990 # Match only these sites
5995 # Or instead, we could set a universal default:
5997 { +prevent-compression }
6000 # Then maybe make exceptions for broken sites:
6002 { -prevent-compression }
6018 NAME="OVERWRITE-LAST-MODIFIED"
6019 >8.5.30. overwrite-last-modified</A
6024 CLASS="VARIABLELIST"
6030 >Prevent yet another way to track the user's steps between sessions.</P
6038 >"Last-Modified:"</SPAN
6039 > HTTP server header or modifies its value.
6052 > One of the keywords: <SPAN
6057 >"reset-to-request-time"</SPAN
6069 > Removing the <SPAN
6071 >"Last-Modified:"</SPAN
6072 > header is useful for filter
6073 testing, where you want to force a real reload instead of getting status
6077 >, which would cause the browser to reuse the old
6078 version of the page.
6084 > option overwrites the value of the
6087 >"Last-Modified:"</SPAN
6088 > header with a randomly chosen time
6089 between the original value and the current time. In theory the server
6090 could send each document with a different <SPAN
6092 >"Last-Modified:"</SPAN
6094 header to track visits without using cookies. <SPAN
6098 makes it impossible and the browser can still revalidate cached documents.
6103 >"reset-to-request-time"</SPAN
6104 > overwrites the value of the
6107 >"Last-Modified:"</SPAN
6108 > header with the current time. You could use
6109 this option together with
6113 HREF="actions-file.html#HIDE-IF-MODIFIED-SINCE"
6114 >hided-if-modified-since</A
6117 to further customize your random range.
6120 > The preferred parameter here is <SPAN
6124 to use, as long as the time settings are more or less correct.
6125 If the server sets the <SPAN
6127 >"Last-Modified:"</SPAN
6128 > header to the time
6129 of the request, the random range becomes zero and the value stays the same.
6130 Therefore you should later randomize it a second time with
6134 HREF="actions-file.html#HIDE-IF-MODIFIED-SINCE"
6135 >hided-if-modified-since</A
6141 > It is also recommended to use this action together with
6145 HREF="actions-file.html#CRUNCH-IF-NONE-MATCH"
6146 >crunch-if-none-match</A
6163 ># Let the browser revalidate without being tracked across sessions
6164 { +hide-if-modified-since{-60} \
6165 +overwrite-last-modified{randomize} \
6166 +crunch-if-none-match}
6183 >8.5.31. redirect</A
6188 CLASS="VARIABLELIST"
6194 > Redirect requests to other sites.
6201 > Convinces the browser that the requested document has been moved
6202 to another location and the browser should get it from there.
6215 > An absolute URL or a single pcrs command.
6222 > Requests to which this action applies are answered with a
6223 HTTP redirect to URLs of your choosing. The new URL is
6224 either provided as parameter, or derived by applying a
6225 single pcrs command to the original URL.
6228 > This action will be ignored if you use it together with
6232 HREF="actions-file.html#BLOCK"
6236 It can be combined with
6240 HREF="actions-file.html#FAST-REDIRECTS"
6241 >fast-redirects{check-decoded-url}</A
6244 to redirect to a decoded version of a rewritten URL.
6247 > Use this action carefully, make sure not to create redirection loops
6248 and be aware that using your own redirects might make it
6249 possible to fingerprint your requests.
6253 >Example usages:</DT
6264 ># Replace example.com's style sheet with another one
6265 { +redirect{http://localhost/css-replacements/example.com.css} }
6266 example.com/stylesheet\.css
6268 # Create a short, easy to remember nickname for a favorite site
6269 # (relies on the browser accept and forward invalid URLs to <SPAN
6273 { +redirect{http://www.privoxy.org/user-manual/actions-file.html} }
6276 # Always use the expanded view for Undeadly.org articles
6277 # (Note the $ at the end of the URL pattern to make sure
6278 # the request for the rewritten URL isn't redirected as well)
6279 {+redirect{s@$@&mode=expanded@}}
6280 undeadly.org/cgi\?action=article&sid=\d*$</PRE
6295 NAME="SEND-VANILLA-WAFER"
6296 >8.5.32. send-vanilla-wafer</A
6301 CLASS="VARIABLELIST"
6307 > Feed log analysis scripts with useless data.
6314 > Sends a cookie with each request stating that you do not accept any copyright
6315 on cookies sent to you, and asking the site operator not to track you.
6335 > The vanilla wafer is a (relatively) unique header and could conceivably be used to track you.
6338 > This action is rarely used and not enabled in the default configuration.
6353 >+send-vanilla-wafer</PRE
6369 >8.5.33. send-wafer</A
6374 CLASS="VARIABLELIST"
6380 > Send custom cookies or feed log analysis scripts with even more useless data.
6387 > Sends a custom, user-defined cookie with each request.
6400 > A string of the form <SPAN
6420 > Being multi-valued, multiple instances of this action can apply to the same request,
6421 resulting in multiple cookies being sent.
6424 > This action is rarely used and not enabled in the default configuration.
6428 >Example usage (section):</DT
6439 >{+send-wafer{UsingPrivoxy=true}}
6440 my-internal-testing-server.void</PRE
6455 NAME="SERVER-HEADER-FILTER"
6456 >8.5.34. server-header-filter</A
6461 CLASS="VARIABLELIST"
6467 > Rewrite or remove single server headers.
6474 > All server headers to which this action applies are filtered on-the-fly
6475 through the specified regular expression based substitutions.
6488 > The name of a server-header filter, as defined in one of the
6490 HREF="filter-file.html"
6499 > Server-header filters are applied to each header on its own, not to
6500 all at once. This makes it easier to diagnose problems, but on the downside
6501 you can't write filters that only change header x if header y's value is z.
6502 You can do that by using tags though.
6505 > Server-header filters are executed after the other header actions have finished
6506 and use their output as input.
6509 > Please refer to the <A
6510 HREF="filter-file.html"
6511 >filter file chapter</A
6513 to learn which server-header filters are available by default, and how to
6518 >Example usage (section):</DT
6529 >{+server-header-filter{html-to-xml}}
6530 example.org/xml-instance-that-is-delivered-as-html
6532 {+server-header-filter{xml-to-html}}
6533 example.org/instance-that-is-delivered-as-xml-but-is-not
6549 NAME="SERVER-HEADER-TAGGER"
6550 >8.5.35. server-header-tagger</A
6555 CLASS="VARIABLELIST"
6561 > Enable or disable filters based on the Content-Type header.
6568 > Server headers to which this action applies are filtered on-the-fly through
6569 the specified regular expression based substitutions, the result is used as
6583 > The name of a server-header tagger, as defined in one of the
6585 HREF="filter-file.html"
6594 > Server-header taggers are applied to each header on its own,
6595 and as the header isn't modified, each tagger <SPAN
6602 > Server-header taggers are executed before all other header actions
6603 that modify server headers. Their tags can be used to control
6604 all of the other server-header actions, the content filters
6605 and the crunch actions (<A
6606 HREF="actions-file.html#REDIRECT"
6610 HREF="actions-file.html#BLOCK"
6615 > Obviously crunching based on tags created by server-header taggers
6616 doesn't prevent the request from showing up in the server's log file.
6620 >Example usage (section):</DT
6631 ># Tag every request with the content type declared by the server
6632 {+server-header-tagger{content-type}}
6649 NAME="SESSION-COOKIES-ONLY"
6650 >8.5.36. session-cookies-only</A
6655 CLASS="VARIABLELIST"
6661 > Allow only temporary <SPAN
6664 > cookies (for the current
6665 browser session <SPAN
6683 >"Set-Cookie:"</SPAN
6685 server headers. Most browsers will not store such cookies permanently and
6686 forget them in between sessions.
6706 > This is less strict than <TT
6709 HREF="actions-file.html#CRUNCH-INCOMING-COOKIES"
6710 >crunch-incoming-cookies</A
6716 HREF="actions-file.html#CRUNCH-OUTGOING-COOKIES"
6717 >crunch-outgoing-cookies</A
6719 > and allows you to browse
6720 websites that insist or rely on setting cookies, without compromising your privacy too badly.
6723 > Most browsers will not permanently store cookies that have been processed by
6726 >session-cookies-only</TT
6727 > and will forget about them between sessions.
6728 This makes profiling cookies useless, but won't break sites which require cookies so
6729 that you can log in for transactions. This is generally turned on for all
6730 sites, and is the recommended setting.
6741 >session-cookies-only</TT
6746 HREF="actions-file.html#CRUNCH-INCOMING-COOKIES"
6747 >crunch-incoming-cookies</A
6753 HREF="actions-file.html#CRUNCH-OUTGOING-COOKIES"
6754 >crunch-outgoing-cookies</A
6756 >. If you do, cookies
6757 will be plainly killed.
6760 > Note that it is up to the browser how it handles such cookies without an <SPAN
6764 field. If you use an exotic browser, you might want to try it out to be sure.
6767 > This setting also has no effect on cookies that may have been stored
6768 previously by the browser before starting <SPAN
6772 These would have to be removed manually.
6780 HREF="actions-file.html#FILTER-CONTENT-COOKIES"
6781 >content-cookies filter</A
6783 to block some types of cookies. Content cookies are not effected by
6786 >session-cookies-only</TT
6802 >+session-cookies-only</PRE
6817 NAME="SET-IMAGE-BLOCKER"
6818 >8.5.37. set-image-blocker</A
6823 CLASS="VARIABLELIST"
6829 >Choose the replacement for blocked images</P
6835 > This action alone doesn't do anything noticeable. If <SPAN
6845 HREF="actions-file.html#BLOCK"
6857 HREF="actions-file.html#HANDLE-AS-IMAGE"
6867 apply, i.e. if the request is to be blocked as an image,
6874 > the parameter of this action decides what will be
6875 sent as a replacement.
6895 > to send a built-in checkerboard pattern image. The image is visually
6896 decent, scales very well, and makes it obvious where banners were busted.
6904 > to send a built-in transparent image. This makes banners disappear
6905 completely, but makes it hard to detect where <SPAN
6909 images on a given page and complicates troubleshooting if <SPAN
6913 has blocked innocent images, like navigation icons.
6927 send a redirect to <TT
6933 to any image anywhere, even in your local filesystem via <SPAN
6937 (But note that not all browsers support redirecting to a local file system).
6940 > A good application of redirects is to use special <SPAN
6944 URLs, which send the built-in images, as <TT
6950 This has the same visual effect as specifying <SPAN
6957 the first place, but enables your browser to cache the replacement image, instead of requesting
6958 it over and over again.
6967 > The URLs for the built-in images are <SPAN
6969 >"http://config.privoxy.org/send-banner?type=<TT
6990 > There is a third (advanced) type, called <SPAN
7002 >set-image-blocker</TT
7003 >, but meant for use from <A
7004 HREF="filter-file.html"
7007 Auto will select the type of image that would have applied to the referring page, had it been an image.
7025 >+set-image-blocker{pattern}</PRE
7032 > Redirect to the BSD daemon:
7043 >+set-image-blocker{http://www.freebsd.org/gifs/dae_up3.gif}</PRE
7050 > Redirect to the built-in pattern for better caching:
7061 >+set-image-blocker{http://config.privoxy.org/send-banner?type=pattern}</PRE
7076 NAME="TREAT-FORBIDDEN-CONNECTS-LIKE-BLOCKS"
7077 >8.5.38. treat-forbidden-connects-like-blocks</A
7082 CLASS="VARIABLELIST"
7088 >Block forbidden connects with an easy to find error message.</P
7094 > If this action is enabled, <SPAN
7098 makes a difference between forbidden connects and ordinary blocks.
7122 HREF="actions-file.html#LIMIT-CONNECT"
7128 with a short error message inside the headers. If the browser doesn't display
7129 headers (most don't), you just see an empty page.
7132 > With this action enabled, <SPAN
7136 the message that is used for ordinary blocks instead. If you decide
7137 to make an exception for the page in question, you can do so by
7147 > requests the clients tell
7151 > which host they are interested
7152 in, but not which document they plan to get later. As a result, the
7155 >"Go there anyway"</SPAN
7156 > wouldn't work and is therefore suppressed.
7171 >+treat-forbidden-connects-like-blocks</PRE
7190 > Note that many of these actions have the potential to cause a page to
7191 misbehave, possibly even not to display at all. There are many ways
7192 a site designer may choose to design his site, and what HTTP header
7193 content, and other criteria, he may depend on. There is no way to have hard
7194 and fast rules for all sites. See the <A
7195 HREF="appendix.html#ACTIONSANAT"
7197 > for a brief example on troubleshooting
7220 >, can be defined by combining other actions.
7221 These can in turn be invoked just like the built-in actions.
7222 Currently, an alias name can contain any character except space, tab,
7240 > that you only use <SPAN
7260 Alias names are not case sensitive, and are not required to start with a
7267 > sign, since they are merely textually
7270 > Aliases can be used throughout the actions file, but they <SPAN
7275 defined in a special section at the top of the file!</I
7278 And there can only be one such section per actions file. Each actions file may
7279 have its own alias section, and the aliases defined in it are only visible
7280 within that file.</P
7282 > There are two main reasons to use aliases: One is to save typing for frequently
7283 used combinations of actions, the other one is a gain in flexibility: If you
7284 decide once how you want to handle shops by defining an alias called
7288 >, you can later change your policy on shops in
7295 > place, and your changes will take effect everywhere
7296 in the actions file where the <SPAN
7299 > alias is used. Calling aliases
7300 by their purpose also makes your actions files more readable.</P
7302 > Currently, there is one big drawback to using aliases, though:
7306 >'s built-in web-based action file
7307 editor honors aliases when reading the actions files, but it expands
7308 them before writing. So the effects of your aliases are of course preserved,
7309 but the aliases themselves are lost when you edit sections that use aliases
7312 > Now let's define some aliases...</P
7322 > # Useful custom aliases we can use later.
7324 # Note the (required!) section header line and that this section
7325 # must be at the top of the actions file!
7329 # These aliases just save typing later:
7330 # (Note that some already use other aliases!)
7332 +crunch-all-cookies = +<A
7333 HREF="actions-file.html#CRUNCH-INCOMING-COOKIES"
7334 >crunch-incoming-cookies</A
7336 HREF="actions-file.html#CRUNCH-OUTGOING-COOKIES"
7337 >crunch-outgoing-cookies</A
7339 -crunch-all-cookies = -<A
7340 HREF="actions-file.html#CRUNCH-INCOMING-COOKIES"
7341 >crunch-incoming-cookies</A
7343 HREF="actions-file.html#CRUNCH-OUTGOING-COOKIES"
7344 >crunch-outgoing-cookies</A
7346 +block-as-image = +block +handle-as-image
7347 allow-all-cookies = -crunch-all-cookies -<A
7348 HREF="actions-file.html#SESSION-COOKIES-ONLY"
7349 >session-cookies-only</A
7351 HREF="actions-file.html#FILTER-CONTENT-COOKIES"
7352 >filter{content-cookies}</A
7355 # These aliases define combinations of actions
7356 # that are useful for certain types of sites:
7359 HREF="actions-file.html#BLOCK"
7362 HREF="actions-file.html#FILTER"
7364 > -crunch-all-cookies -<A
7365 HREF="actions-file.html#FAST-REDIRECTS"
7368 HREF="actions-file.html#HIDE-REFERER"
7371 HREF="actions-file.html#KILL-POPUPS"
7374 HREF="actions-file.html#PREVENT-COMPRESSION"
7375 >prevent-compression</A
7378 shop = -crunch-all-cookies -<A
7379 HREF="actions-file.html#FILTER-ALL-POPUPS"
7380 >filter{all-popups}</A
7382 HREF="actions-file.html#KILL-POPUPS"
7386 # Short names for other aliases, for really lazy people ;-)
7388 c0 = +crunch-all-cookies
7389 c1 = -crunch-all-cookies</PRE
7395 > ...and put them to use. These sections would appear in the lower part of an
7396 actions file and define exceptions to the default actions (as specified further
7410 > # These sites are either very complex or very keen on
7411 # user data and require minimal interference to work:
7414 .office.microsoft.com
7415 .windowsupdate.microsoft.com
7416 # Gmail is really mail.google.com, not gmail.com
7420 # Allow cookies (for setting and retrieving your customer data)
7424 .worldpay.com # for quietpc.com
7427 # These shops require pop-ups:
7429 {-kill-popups -filter{all-popups} -filter{unsolicited-popups}}
7431 .overclockers.co.uk</PRE
7437 > Aliases like <SPAN
7443 > are typically used for
7447 > sites that require more than one action to be disabled
7448 in order to function properly.</P
7456 >8.7. Actions Files Tutorial</A
7459 > The above chapters have shown <A
7460 HREF="actions-file.html"
7461 >which actions files
7462 there are and how they are organized</A
7463 >, how actions are <A
7464 HREF="actions-file.html#ACTIONS"
7467 HREF="actions-file.html#ACTIONS-APPLY"
7471 HREF="actions-file.html#AF-PATTERNS"
7475 HREF="actions-file.html#ALIASES"
7477 >. Now, let's look at an
7485 file and see how all these pieces come together:</P
7492 >8.7.1. default.action</A
7495 >Every config file should start with a short comment stating its purpose:</P
7505 ># Sample default.action file <ijbswa-developers@lists.sourceforge.net></PRE
7511 >Then, since this is the <TT
7515 first section is a special section for internal use that you needn't
7516 change or worry about:</P
7526 >##########################################################################
7527 # Settings -- Don't change! For internal Privoxy use ONLY.
7528 ##########################################################################
7531 for-privoxy-version=3.0</PRE
7537 >After that comes the (optional) alias section. We'll use the example
7538 section from the above <A
7539 HREF="actions-file.html#ALIASES"
7540 >chapter on aliases</A
7542 that also explains why and how aliases are used:</P
7552 >##########################################################################
7554 ##########################################################################
7557 # These aliases just save typing later:
7558 # (Note that some already use other aliases!)
7560 +crunch-all-cookies = +<A
7561 HREF="actions-file.html#CRUNCH-INCOMING-COOKIES"
7562 >crunch-incoming-cookies</A
7564 HREF="actions-file.html#CRUNCH-OUTGOING-COOKIES"
7565 >crunch-outgoing-cookies</A
7567 -crunch-all-cookies = -<A
7568 HREF="actions-file.html#CRUNCH-INCOMING-COOKIES"
7569 >crunch-incoming-cookies</A
7571 HREF="actions-file.html#CRUNCH-OUTGOING-COOKIES"
7572 >crunch-outgoing-cookies</A
7574 +block-as-image = +block +handle-as-image
7575 mercy-for-cookies = -crunch-all-cookies -<A
7576 HREF="actions-file.html#SESSION-COOKIES-ONLY"
7577 >session-cookies-only</A
7579 HREF="actions-file.html#FILTER-CONTENT-COOKIES"
7580 >filter{content-cookies}</A
7583 # These aliases define combinations of actions
7584 # that are useful for certain types of sites:
7587 HREF="actions-file.html#BLOCK"
7590 HREF="actions-file.html#FILTER"
7592 > -crunch-all-cookies -<A
7593 HREF="actions-file.html#FAST-REDIRECTS"
7596 HREF="actions-file.html#HIDE-REFERER"
7599 HREF="actions-file.html#KILL-POPUPS"
7602 shop = -crunch-all-cookies -<A
7603 HREF="actions-file.html#FILTER-ALL-POPUPS"
7604 >filter{all-popups}</A
7606 HREF="actions-file.html#KILL-POPUPS"
7614 > Now come the regular sections, i.e. sets of actions, accompanied
7615 by URL patterns to which they apply. Remember <SPAN
7620 are disabled when matching starts</I
7622 >, so we have to explicitly
7623 enable the ones we want.</P
7625 > The first regular section is probably the most important. It has only
7634 HREF="actions-file.html#AF-PATTERNS"
7635 >matches all URLs</A
7637 set of actions used in this <SPAN
7645 be applied to all requests as a start</I
7647 >. It can be partly or
7648 wholly overridden by later matches further down this file, or in user.action,
7649 but it will still be largely responsible for your overall browsing
7652 > Again, at the start of matching, all actions are disabled, so there is
7653 no need to disable any actions here. (Remember: a <SPAN
7657 preceding the action name enables the action, a <SPAN
7661 Also note how this long line has been made more readable by splitting it into
7662 multiple lines with line continuation.</P
7672 >##########################################################################
7673 # "Defaults" section:
7674 ##########################################################################
7677 HREF="actions-file.html#DEANIMATE-GIFS"
7681 HREF="actions-file.html#FILTER-HTML-ANNOYANCES"
7682 >filter{html-annoyances}</A
7685 HREF="actions-file.html#FILTER-REFRESH-TAGS"
7686 >filter{refresh-tags}</A
7689 HREF="actions-file.html#FILTER-WEBBUGS"
7693 HREF="actions-file.html#FILTER-IE-EXPLOITS"
7694 >filter{ie-exploits}</A
7697 HREF="actions-file.html#HIDE-FORWARDED-FOR-HEADERS"
7698 >hide-forwarded-for-headers</A
7701 HREF="actions-file.html#HIDE-FROM-HEADER"
7702 >hide-from-header{block}</A
7705 HREF="actions-file.html#HIDE-REFERER"
7706 >hide-referrer{forge}</A
7709 HREF="actions-file.html#PREVENT-COMPRESSION"
7710 >prevent-compression</A
7713 HREF="actions-file.html#SESSION-COOKIES-ONLY"
7714 >session-cookies-only</A
7717 HREF="actions-file.html#SET-IMAGE-BLOCKER"
7718 >set-image-blocker{pattern}</A
7721 / # forward slash will match *all* potential URL patterns.</PRE
7727 > The default behavior is now set.
7730 > The first of our specialized sections is concerned with <SPAN
7734 sites, i.e. sites that require minimum interference, because they are either
7735 very complex or very keen on tracking you (and have mechanisms in place that
7736 make them unusable for people who avoid being tracked). We will simply use
7740 > alias instead of stating the list
7741 of actions explicitly:</P
7751 >##########################################################################
7752 # Exceptions for sites that'll break under the default action set:
7753 ##########################################################################
7755 # "Fragile" Use a minimum set of actions for these sites (see alias above):
7758 .office.microsoft.com # surprise, surprise!
7759 .windowsupdate.microsoft.com
7760 mail.google.com</PRE
7766 > Shopping sites are not as fragile, but they typically
7767 require cookies to log in, and pop-up windows for shopping
7768 carts or item details. Again, we'll use a pre-defined alias:</P
7782 .worldpay.com # for quietpc.com
7793 HREF="actions-file.html#FAST-REDIRECTS"
7797 action, which we enabled per default above, breaks some sites. So disable
7798 it for popular sites where we know it misbehaves:</P
7809 HREF="actions-file.html#FAST-REDIRECTS"
7815 .altavista.com/.*(like|url|link):http
7816 .altavista.com/trans.*urltext=http
7823 > It is important that <SPAN
7827 URLs belong to images, so that <SPAN
7834 be blocked, a substitute image can be sent, rather than an HTML page.
7835 Contacting the remote site to find out is not an option, since it
7836 would destroy the loading time advantage of banner blocking, and it
7837 would feed the advertisers (in terms of money <SPAN
7844 information). We can mark any URL as an image with the <TT
7847 HREF="actions-file.html#HANDLE-AS-IMAGE"
7851 and marking all URLs that end in a known image file extension is a
7862 >##########################################################################
7864 ##########################################################################
7866 # Define which file types will be treated as images, in case they get
7867 # blocked further down this file:
7870 HREF="actions-file.html#HANDLE-AS-IMAGE"
7873 /.*\.(gif|jpe?g|png|bmp|ico)$</PRE
7879 > And then there are known banner sources. They often use scripts to
7880 generate the banners, so it won't be visible from the URL that the
7881 request is for an image. Hence we block them <SPAN
7888 mark them as images in one go, with the help of our
7891 >+block-as-image</TT
7892 > alias defined above. (We could of
7893 course just as well use <TT
7896 HREF="actions-file.html#BLOCK"
7900 HREF="actions-file.html#HANDLE-AS-IMAGE"
7904 Remember that the type of the replacement image is chosen by the
7908 HREF="actions-file.html#SET-IMAGE-BLOCKER"
7909 >set-image-blocker</A
7912 action. Since all URLs have matched the default section with its
7916 HREF="actions-file.html#SET-IMAGE-BLOCKER"
7917 >set-image-blocker</A
7920 action before, it still applies and needn't be repeated:</P
7930 ># Known ad generators:
7935 .ad.*.doubleclick.net
7936 .a.yimg.com/(?:(?!/i/).)*$
7937 .a[0-9].yimg.com/(?:(?!/i/).)*$
7945 > One of the most important jobs of <SPAN
7949 is to block banners. Many of these can be <SPAN
7956 HREF="actions-file.html#FILTER"
7958 >{banners-by-size}</TT
7960 action, which we enabled above, and which deletes the references to banner
7961 images from the pages while they are loaded, so the browser doesn't request
7962 them anymore, and hence they don't need to be blocked here. But this naturally
7963 doesn't catch all banners, and some people choose not to use filters, so we
7964 need a comprehensive list of patterns for banner URLs here, and apply the
7968 HREF="actions-file.html#BLOCK"
7971 > action to them.</P
7973 > First comes many generic patterns, which do most of the work, by
7974 matching typical domain and path name components of banners. Then comes
7975 a list of individual patterns for specific sites, which is omitted here
7976 to keep the example short:</P
7986 >##########################################################################
7987 # Block these fine banners:
7988 ##########################################################################
7990 HREF="actions-file.html#BLOCK"
8000 /.*count(er)?\.(pl|cgi|exe|dll|asp|php[34]?)
8001 /(?:.*/)?(publicite|werbung|rekla(ma|me|am)|annonse|maino(kset|nta|s)?)/
8003 # Site-specific patterns (abbreviated):
8011 > It's quite remarkable how many advertisers actually call their banner
8017 >.com, or call the directory
8018 in which the banners are stored simply <SPAN
8022 generic patterns are surprisingly effective.</P
8024 > But being very generic, they necessarily also catch URLs that we don't want
8025 to block. The pattern <TT
8037 >.nasty-corp.com"</SPAN
8047 >.sourcefroge.net"</SPAN
8057 >l.some-provider.net."</SPAN
8059 well-known exceptions to the <TT
8062 HREF="actions-file.html#BLOCK"
8068 > Note that these are exceptions to exceptions from the default! Consider the URL
8071 >"downloads.sourcefroge.net"</SPAN
8072 >: Initially, all actions are deactivated,
8073 so it wouldn't get blocked. Then comes the defaults section, which matches the
8074 URL, but just deactivates the <TT
8077 HREF="actions-file.html#BLOCK"
8081 action once again. Then it matches <TT
8084 >, an exception to the
8085 general non-blocking policy, and suddenly
8089 HREF="actions-file.html#BLOCK"
8092 > applies. And now, it'll match
8099 HREF="actions-file.html#BLOCK"
8103 applies, so (unless it matches <SPAN
8109 > further down) it ends up
8113 HREF="actions-file.html#BLOCK"
8116 > action applying.</P
8126 >##########################################################################
8127 # Save some innocent victims of the above generic block patterns:
8128 ##########################################################################
8133 HREF="actions-file.html#BLOCK"
8136 adv[io]*. # (for advogato.org and advice.*)
8137 adsl. # (has nothing to do with ads)
8138 adobe. # (has nothing to do with ads either)
8139 ad[ud]*. # (adult.* and add.*)
8140 .edu # (universities don't host banners (yet!))
8141 .*loads. # (downloads, uploads etc)
8149 www.globalintersec.com/adv # (adv = advanced)
8150 www.ugu.com/sui/ugu/adv</PRE
8156 > Filtering source code can have nasty side effects,
8157 so make an exception for our friends at sourceforge.net,
8158 and all paths with <SPAN
8161 > in them. Note that
8165 HREF="actions-file.html#FILTER"
8175 > filters in one fell swoop!</P
8185 ># Don't filter code!
8188 HREF="actions-file.html#FILTER"
8195 .sourceforge.net</PRE
8204 > is of course much more
8205 comprehensive, but we hope this example made clear how it works.</P
8213 >8.7.2. user.action</A
8216 > So far we are painting with a broad brush by setting general policies,
8217 which would be a reasonable starting point for many people. Now,
8218 you might want to be more specific and have customized rules that
8219 are more suitable to your personal habits and preferences. These would
8220 be for narrowly defined situations like your ISP or your bank, and should
8224 >, which is parsed after all other
8225 actions files and hence has the last word, over-riding any previously
8226 defined actions. <TT
8236 > place for your personal settings, since
8240 > is actively maintained by the
8244 > developers and you'll probably want
8245 to install updated versions from time to time.</P
8247 > So let's look at a few examples of things that one might typically do in
8261 ># My user.action file. <fred@example.com></PRE
8268 HREF="actions-file.html#ALIASES"
8270 > are local to the actions
8271 file that they are defined in, you can't use the ones from
8275 >, unless you repeat them here:</P
8285 ># Aliases are local to the file they are defined in.
8286 # (Re-)define aliases for this file:
8290 # These aliases just save typing later, and the alias names should
8291 # be self explanatory.
8293 +crunch-all-cookies = +crunch-incoming-cookies +crunch-outgoing-cookies
8294 -crunch-all-cookies = -crunch-incoming-cookies -crunch-outgoing-cookies
8295 allow-all-cookies = -crunch-all-cookies -session-cookies-only
8296 allow-popups = -filter{all-popups} -kill-popups
8297 +block-as-image = +block +handle-as-image
8298 -block-as-image = -block
8300 # These aliases define combinations of actions that are useful for
8301 # certain types of sites:
8303 fragile = -block -crunch-all-cookies -filter -fast-redirects -hide-referrer -kill-popups
8304 shop = -crunch-all-cookies allow-popups
8306 # Allow ads for selected useful free sites:
8308 allow-ads = -block -filter{banners-by-size} -filter{banners-by-link}
8310 # Alias for specific file types that are text, but might have conflicting
8311 # MIME types. We want the browser to force these to be text documents.
8312 handle-as-text = -<A
8313 HREF="actions-file.html#FILTER"
8316 HREF="actions-file.html#CONTENT-TYPE-OVERWRITE"
8317 >content-type-overwrite{text/plain}</A
8319 HREF="actions-file.html#FORCE-TEXT-MODE"
8322 HREF="actions-file.html#HIDE-CONTENT-DISPOSITION"
8323 >hide-content-disposition</A
8330 > Say you have accounts on some sites that you visit regularly, and
8331 you don't want to have to log in manually each time. So you'd like
8332 to allow persistent cookies for these sites. The
8335 >allow-all-cookies</TT
8336 > alias defined above does exactly
8337 that, i.e. it disables crunching of cookies in any direction, and the
8338 processing of cookies to make them only temporary.</P
8348 >{ allow-all-cookies }
8358 > Your bank is allergic to some filter, but you don't know which, so you disable them all:</P
8369 HREF="actions-file.html#FILTER"
8372 .your-home-banking-site.com</PRE
8378 > Some file types you may not want to filter for various reasons:</P
8388 ># Technical documentation is likely to contain strings that might
8389 # erroneously get altered by the JavaScript-oriented filters:
8394 # And this stupid host sends streaming video with a wrong MIME type,
8395 # so that Privoxy thinks it is getting HTML and starts filtering:
8397 stupid-server.example.com/</PRE
8403 > Example of a simple <A
8404 HREF="actions-file.html#BLOCK"
8406 > action. Say you've
8407 seen an ad on your favourite page on example.com that you want to get rid of.
8408 You have right-clicked the image, selected <SPAN
8410 >"copy image location"</SPAN
8412 and pasted the URL below while removing the leading http://, into a
8416 > section. Note that <TT
8420 > need not be specified, since all URLs ending in
8424 > will be tagged as images by the general rules as set
8425 in default.action anyway:</P
8436 HREF="actions-file.html#BLOCK"
8439 www.example.com/nasty-ads/sponsor\.gif
8440 another.example.net/more/junk/here/</PRE
8446 > The URLs of dynamically generated banners, especially from large banner
8447 farms, often don't use the well-known image file name extensions, which
8448 makes it impossible for <SPAN
8452 the file type just by looking at the URL.
8455 >+block-as-image</TT
8456 > alias defined above for
8458 Note that objects which match this rule but then turn out NOT to be an
8459 image are typically rendered as a <SPAN
8461 >"broken image"</SPAN
8463 browser. Use cautiously.</P
8473 >{ +block-as-image }
8483 > Now you noticed that the default configuration breaks Forbes Magazine,
8484 but you were too lazy to find out which action is the culprit, and you
8485 were again too lazy to give <A
8489 you just used the <TT
8492 > alias on the site, and
8499 > -- it worked. The <TT
8503 aliases disables those actions that are most likely to break a site. Also,
8504 good for testing purposes to see if it is <SPAN
8508 that is causing the problem or not. We later find other regular sites
8509 that misbehave, and add those to our personalized list of troublemakers:</P
8528 > You like the <SPAN
8531 > text replacements in <TT
8535 but it is disabled in the distributed actions file.
8536 So you'd like to turn it on in your private,
8537 update-safe config, once and for all:</P
8548 HREF="actions-file.html#FILTER-FUN"
8551 / # For ALL sites!</PRE
8557 > Note that the above is not really a good idea: There are exceptions
8558 to the filters in <TT
8562 really shouldn't be filtered, like code on CVS->Web interfaces. Since
8566 > has the last word, these exceptions
8567 won't be valid for the <SPAN
8570 > filtering specified here.</P
8572 > You might also worry about how your favourite free websites are
8573 funded, and find that they rely on displaying banner advertisements
8574 to survive. So you might want to specifically allow banners for those
8575 sites that you feel provide value to you:</P
8597 > has been aliased to
8601 HREF="actions-file.html#BLOCK"
8608 HREF="actions-file.html#FILTER-BANNERS-BY-SIZE"
8609 >filter{banners-by-size}</A
8615 HREF="actions-file.html#FILTER-BANNERS-BY-LINK"
8616 >filter{banners-by-link}</A
8620 > Invoke another alias here to force an over-ride of the MIME type <TT
8622 > application/x-sh</TT
8623 > which typically would open a download type
8624 dialog. In my case, I want to look at the shell script, and then I can save
8625 it should I choose to.</P
8645 > is generally the best place to define
8646 exceptions and additions to the default policies of
8650 >. Some actions are safe to have their
8651 default policies set here though. So let's set a default policy to have a
8655 > image as opposed to the checkerboard pattern for
8665 > of course matches all URL
8666 paths and patterns:</P
8677 HREF="actions-file.html#SET-IMAGE-BLOCKER"
8678 >set-image-blocker{blank}</A
8693 SUMMARY="Footer navigation table"
8722 HREF="filter-file.html"
8732 >The Main Configuration File</TD
projects / privoxy.git / blob