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.8 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.8 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 with first-level domain <TT
919 and second-level domain <TT
932 >foo.bar.baz.example.com</TT
934 Note that it wouldn't match if the second-level domain was <TT
947 > matches any domain that <SPAN
957 > (It also matches the domain
961 > but most of the time that doesn't matter.)
971 > matches any domain that <SPAN
981 And, by the way, also included would be any files or documents that exist
982 within that domain since no path limitations are specified. (Correctly
983 speaking: It matches any FQDN that contains <TT
987 a domain.) This might be <TT
997 >www.example.net/cgi/testing.pl</TT
998 > for instance. All these
1005 > Additionally, there are wild-cards that you can use in the domain names
1006 themselves. These work similarly to shell globbing type wild-cards:
1010 > represents zero or more arbitrary characters (this is
1013 HREF="http://en.wikipedia.org/wiki/Regular_expressions"
1020 > based syntax of <SPAN
1027 > represents any single character (this is equivalent to the
1028 regular expression syntax of a simple <SPAN
1031 >), and you can define
1034 >"character classes"</SPAN
1035 > in square brackets which is similar to
1036 the same regular expression technique. All of this can be freely mixed:</P
1040 CLASS="VARIABLELIST"
1045 >ad*.example.com</TT
1051 >"adserver.example.com"</SPAN
1055 >"ads.example.com"</SPAN
1056 >, etc but not <SPAN
1058 >"sfads.example.com"</SPAN
1065 >*ad*.example.com</TT
1069 > matches all of the above, and then some.
1085 >pictures.epix.com</TT
1088 >a.b.c.d.e.upix.com</TT
1095 >www[1-9a-ez].example.c*</TT
1101 >www1.example.com</TT
1105 >www4.example.cc</TT
1108 >wwwd.example.cy</TT
1112 >wwwz.example.com</TT
1122 >wwww.example.com</TT
1129 > While flexible, this is not the sophistication of full regular expression based syntax.</P
1137 >8.4.2. The Path Pattern</A
1143 > uses Perl compatible (PCRE)
1145 HREF="http://en.wikipedia.org/wiki/Regular_expressions"
1154 HREF="http://www.pcre.org/"
1158 matching the path portion (after the slash), and is thus more flexible.</P
1161 HREF="appendix.html#REGEX"
1163 > with a brief quick-start into regular
1164 expressions, and full (very technical) documentation on PCRE regex syntax is available on-line
1166 HREF="http://www.pcre.org/man.txt"
1168 >http://www.pcre.org/man.txt</A
1170 You might also find the Perl man page on regular expressions (<TT
1174 useful, which is available on-line at <A
1175 HREF="http://perldoc.perl.org/perlre.html"
1177 >http://perldoc.perl.org/perlre.html</A
1180 > Note that the path pattern is automatically left-anchored at the <SPAN
1184 i.e. it matches as if it would start with a <SPAN
1187 > (regular expression speak
1188 for the beginning of a line).</P
1190 > Please also note that matching in the path is <SPAN
1194 >CASE INSENSITIVE</I
1197 by default, but you can switch to case sensitive at any point in the pattern by using the
1203 >www.example.com/(?-i)PaTtErN.*</TT
1205 only documents whose path starts with <TT
1215 > this capitalization.</P
1219 CLASS="VARIABLELIST"
1224 >.example.com/.*</TT
1228 > Is equivalent to just <SPAN
1230 >".example.com"</SPAN
1231 >, since any documents
1232 within that domain are matched with or without the <SPAN
1236 regular expression. This is redundant
1242 >.example.com/.*/index.html$</TT
1246 > Will match any page in the domain of <SPAN
1248 >"example.com"</SPAN
1253 >, and that is part of some path. For
1254 example, it matches <SPAN
1256 >"www.example.com/testing/index.html"</SPAN
1260 >"www.example.com/index.html"</SPAN
1261 > because the regular
1262 expression called for at least two <SPAN
1266 requirement. It also would match
1269 >"www.example.com/testing/index_html"</SPAN
1271 special meta-character <SPAN
1280 >.example.com/(.*/)?index\.html$</TT
1284 > This regular expression is conditional so it will match any page
1288 > regardless of path which in this case can
1289 have one or more <SPAN
1292 >. And this one must contain exactly
1296 > (but does not have to end with that!).
1302 >.example.com/(.*/)(ads|banners?|junk)</TT
1306 > This regular expression will match any path of <SPAN
1308 >"example.com"</SPAN
1310 that contains any of the words <SPAN
1320 > (because of the <SPAN
1327 The path does not have to end in these words, just contain them.
1333 >.example.com/(.*/)(ads|banners?|junk)/.*\.(jpe?g|gif|png)$</TT
1337 > This is very much the same as above, except now it must end in either
1351 one is limited to common image formats.
1357 > There are many, many good examples to be found in <TT
1361 and more tutorials below in <A
1362 HREF="appendix.html#REGEX"
1363 >Appendix on regular expressions</A
1372 >8.4.3. The Tag Pattern</A
1375 > Tag patterns are used to change the applying actions based on the
1376 request's tags. Tags can be created with either the
1378 HREF="actions-file.html#CLIENT-HEADER-TAGGER"
1379 >client-header-tagger</A
1382 HREF="actions-file.html#SERVER-HEADER-TAGGER"
1383 >server-header-tagger</A
1386 > Tag patterns have to start with <SPAN
1393 can tell them apart from URL patterns. Everything after the colon
1394 including white space, is interpreted as a regular expression with
1395 path pattern syntax, except that tag patterns aren't left-anchored
1396 automatically (<SPAN
1399 > doesn't silently add a <SPAN
1403 you have to do it yourself if you need it).</P
1405 > To match all requests that are tagged with <SPAN
1409 your pattern line should be <SPAN
1416 > would work as well, but it would also
1417 match requests whose tags contain <SPAN
1424 > wouldn't work as it requires white space.</P
1426 > Sections can contain URL and tag patterns at the same time,
1427 but tag patterns are checked after the URL patterns and thus
1428 always overrule them, even if they are located before the URL patterns.</P
1430 > Once a new tag is added, Privoxy checks right away if it's matched by one
1431 of the tag patterns and updates the action settings accordingly. As a result
1432 tags can be used to activate other tagger actions, as long as these other
1433 taggers look for headers that haven't already be parsed.</P
1435 > For example you could tag client requests which use the
1440 then use this tag to activate another tagger that adds a tag if cookies
1441 are sent, and then use a block action based on the cookie tag. This allows
1442 the outcome of one action, to be input into a subsequent action. However if
1443 you'd reverse the position of the described taggers, and activated the
1444 method tagger based on the cookie tagger, no method tags would be created.
1445 The method tagger would look for the request line, but at the time
1446 the cookie tag is created, the request line has already been parsed.</P
1448 > While this is a limitation you should be aware of, this kind of
1449 indirection is seldom needed anyway and even the example doesn't
1450 make too much sense.</P
1462 > All actions are disabled by default, until they are explicitly enabled
1463 somewhere in an actions file. Actions are turned on if preceded with a
1467 >, and turned off if preceded with a <SPAN
1476 >"do that action"</SPAN
1483 >"please block URLs that match the
1484 following patterns"</SPAN
1491 block URLs that match the following patterns, even if <TT
1495 previously applied."</SPAN
1499 Again, actions are invoked by placing them on a line, enclosed in curly braces and
1500 separated by whitespace, like in
1503 >{+some-action -some-other-action{some-parameter}}</TT
1505 followed by a list of URL patterns, one per line, to which they apply.
1506 Together, the actions line and the following pattern lines make up a section
1507 of the actions file. </P
1510 Actions fall into three categories:</P
1518 Boolean, i.e the action can only be <SPAN
1541 > # enable action <TT
1552 > # disable action <TT
1574 Parameterized, where some value is required in order to enable this type of action.
1596 >} # enable action and set parameter to <TT
1602 # overwriting parameter from previous match if necessary
1608 > # disable action. The parameter can be omitted</PRE
1615 > Note that if the URL matches multiple positive forms of a parameterized action,
1616 the last match wins, i.e. the params from earlier matches are simply ignored.
1622 >+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
1629 Multi-value. These look exactly like parameterized actions,
1630 but they behave differently: If the action applies multiple times to the
1631 same URL, but with different parameters, <SPAN
1644 > matches are remembered. This is used for actions
1645 that can be executed for the same request repeatedly, like adding multiple
1646 headers, or filtering through multiple filters. Syntax:
1667 >} # enable action and add <TT
1672 > to the list of parameters
1683 >} # remove the parameter <TT
1688 > from the list of parameters
1689 # If it was the last one left, disable the action.
1695 > # disable this action completely and remove all parameters from the list</PRE
1705 >+add-header{X-Fun-Header: Some text}</TT
1709 >+filter{html-annoyances}</TT
1716 > If nothing is specified in any actions file, no <SPAN
1720 taken. So in this case <SPAN
1724 normal, non-blocking, non-filtering proxy. You must specifically enable the
1725 privacy and blocking features you need (although the provided default actions
1726 files will give a good starting point).</P
1728 > Later defined action sections always over-ride earlier ones of the same type.
1729 So exceptions to any rules you make, should come in the latter part of the file (or
1730 in a file that is processed later when using multiple actions files such
1734 >). For multi-valued actions, the actions
1735 are applied in the order they are specified. Actions files are processed in
1736 the order they are defined in <TT
1740 installation has three actions files). It also quite possible for any given
1741 URL to match more than one <SPAN
1744 > (because of wildcards and
1745 regular expressions), and thus to trigger more than one set of actions! Last
1748 > The list of valid <SPAN
1758 >8.5.1. add-header</A
1763 CLASS="VARIABLELIST"
1769 >Confuse log analysis, custom applications</P
1775 > Sends a user defined HTTP header to the web server.
1788 > Any string value is possible. Validity of the defined HTTP headers is not checked.
1789 It is recommended that you use the <SPAN
1803 > This action may be specified multiple times, in order to define multiple
1804 headers. This is rarely needed for the typical user. If you don't know what
1807 >"HTTP headers"</SPAN
1808 > are, you definitely don't need to worry about this
1824 >+add-header{X-User-Tracking: sucks}</PRE
1845 CLASS="VARIABLELIST"
1851 >Block ads or other unwanted content</P
1857 > Requests for URLs to which this action applies are blocked, i.e. the
1858 requests are trapped by <SPAN
1861 > and the requested URL is never retrieved,
1862 but is answered locally with a substitute page or image, as determined by
1866 HREF="actions-file.html#HANDLE-AS-IMAGE"
1873 HREF="actions-file.html#SET-IMAGE-BLOCKER"
1874 >set-image-blocker</A
1880 HREF="actions-file.html#HANDLE-AS-EMPTY-DOCUMENT"
1881 >handle-as-empty-document</A
1906 > sends a special <SPAN
1910 for requests to blocked pages. This page contains links to find out why the request
1911 was blocked, and a click-through to the blocked content (the latter only if compiled with the
1912 force feature enabled). The <SPAN
1915 > page adapts to the available
1916 screen space -- it displays full-blown if space allows, or miniaturized and text-only
1917 if loaded into a small frame or window. If you are using <SPAN
1921 right now, you can take a look at the
1923 HREF="http://ads.bannerserver.example.com/nasty-ads/sponsor.html"
1934 A very important exception occurs if <SPAN
1947 HREF="actions-file.html#HANDLE-AS-IMAGE"
1951 apply to the same request: it will then be replaced by an image. If
1955 HREF="actions-file.html#SET-IMAGE-BLOCKER"
1956 >set-image-blocker</A
1959 (see below) also applies, the type of image will be determined by its parameter,
1960 if not, the standard checkerboard pattern is sent.
1963 > It is important to understand this process, in order
1964 to understand how <SPAN
1968 ads and other unwanted content. Blocking is a core feature, and one
1969 upon which various other features depend.
1975 HREF="actions-file.html#FILTER"
1979 action can perform a very similar task, by <SPAN
1983 banner images and other content through rewriting the relevant URLs in the
1984 document's HTML source, so they don't get requested in the first place.
1985 Note that this is a totally different technique, and it's easy to confuse the two.
1989 >Example usage (section):</DT
2001 # Block and replace with "blocked" page
2002 .nasty-stuff.example.com
2004 {+block +handle-as-image}
2005 # Block and replace with image
2009 {+block +handle-as-empty-document}
2010 # Block and then ignore
2011 adserver.exampleclick.net/.*\.js$</PRE
2026 NAME="CLIENT-HEADER-FILTER"
2027 >8.5.3. client-header-filter</A
2032 CLASS="VARIABLELIST"
2038 > Rewrite or remove single client headers.
2045 > All client headers to which this action applies are filtered on-the-fly through
2046 the specified regular expression based substitutions.
2059 > The name of a client-header filter, as defined in one of the
2061 HREF="filter-file.html"
2070 > Client-header filters are applied to each header on its own, not to
2071 all at once. This makes it easier to diagnose problems, but on the downside
2072 you can't write filters that only change header x if header y's value is z.
2073 You can do that by using tags though.
2076 > Client-header filters are executed after the other header actions have finished
2077 and use their output as input.
2080 > If the request URL gets changed, <SPAN
2083 > will detect that and use the new
2084 one. This can be used to rewrite the request destination behind the client's
2085 back, for example to specify a Tor exit relay for certain requests.
2088 > Please refer to the <A
2089 HREF="filter-file.html"
2090 >filter file chapter</A
2092 to learn which client-header filters are available by default, and how to
2097 >Example usage (section):</DT
2108 >{+client-header-filter{hide-tor-exit-notation}}
2125 NAME="CLIENT-HEADER-TAGGER"
2126 >8.5.4. client-header-tagger</A
2131 CLASS="VARIABLELIST"
2137 > Block requests based on their headers.
2144 > Client headers to which this action applies are filtered on-the-fly through
2145 the specified regular expression based substitutions, the result is used as
2159 > The name of a client-header tagger, as defined in one of the
2161 HREF="filter-file.html"
2170 > Client-header taggers are applied to each header on its own,
2171 and as the header isn't modified, each tagger <SPAN
2178 > Client-header taggers are the first actions that are executed
2179 and their tags can be used to control every other action.
2183 >Example usage (section):</DT
2194 ># Tag every request with the User-Agent header
2195 {+client-header-tagger{user-agent}}
2212 NAME="CONTENT-TYPE-OVERWRITE"
2213 >8.5.5. content-type-overwrite</A
2218 CLASS="VARIABLELIST"
2224 >Stop useless download menus from popping up, or change the browser's rendering mode</P
2230 > Replaces the <SPAN
2232 >"Content-Type:"</SPAN
2233 > HTTP server header.
2255 >"Content-Type:"</SPAN
2256 > HTTP server header is used by the
2257 browser to decide what to do with the document. The value of this
2258 header can cause the browser to open a download menu instead of
2259 displaying the document by itself, even if the document's format is
2260 supported by the browser.
2263 > The declared content type can also affect which rendering mode
2264 the browser chooses. If XHTML is delivered as <SPAN
2268 many browsers treat it as yet another broken HTML document.
2269 If it is send as <SPAN
2271 >"application/xml"</SPAN
2273 XHTML support will only display it, if the syntax is correct.
2276 > If you see a web site that proudly uses XHTML buttons, but sets
2279 >"Content-Type: text/html"</SPAN
2280 >, you can use <SPAN
2284 to overwrite it with <SPAN
2286 >"application/xml"</SPAN
2288 the web master's claim inside your XHTML-supporting browser.
2289 If the syntax is incorrect, the browser will complain loudly.
2292 > You can also go the opposite direction: if your browser prints
2293 error messages instead of rendering a document falsely declared
2294 as XHTML, you can overwrite the content type with
2298 > and have it rendered as broken HTML document.
2303 >content-type-overwrite</TT
2307 >"Content-Type:"</SPAN
2308 > headers that look like some kind of text.
2309 If you want to overwrite it unconditionally, you have to combine it with
2313 HREF="actions-file.html#FORCE-TEXT-MODE"
2317 This limitation exists for a reason, think twice before circumventing it.
2320 > Most of the time it's easier to replace this action with a custom
2324 HREF="actions-file.html#SERVER-HEADER-FILTER"
2325 >server-header filter</A
2328 It allows you to activate it for every document of a certain site and it will still
2329 only replace the content types you aimed at.
2332 > Of course you can apply <TT
2334 >content-type-overwrite</TT
2336 to a whole site and then make URL based exceptions, but it's a lot
2337 more work to get the same precision.
2341 >Example usage (sections):</DT
2352 ># Check if www.example.net/ really uses valid XHTML
2353 { +content-type-overwrite{application/xml} }
2356 # but leave the content type unmodified if the URL looks like a style sheet
2357 {-content-type-overwrite}
2358 www.example.net/.*\.css$
2359 www.example.net/.*style</PRE
2374 NAME="CRUNCH-CLIENT-HEADER"
2375 >8.5.6. crunch-client-header</A
2380 CLASS="VARIABLELIST"
2386 >Remove a client header <SPAN
2389 > has no dedicated action for.</P
2395 > Deletes every header sent by the client that contains the string the user supplied as parameter.
2415 > This action allows you to block client headers for which no dedicated
2423 > will remove every client header that
2424 contains the string you supplied as parameter.
2427 > Regular expressions are <SPAN
2434 use this action to block different headers in the same request, unless
2435 they contain the same string.
2440 >crunch-client-header</TT
2441 > is only meant for quick tests.
2442 If you have to block several different headers, or only want to modify
2443 parts of them, you should use a
2447 HREF="actions-file.html#CLIENT-HEADER-FILTER"
2448 >client-header filter</A
2471 > Don't block any header without understanding the consequences.
2479 >Example usage (section):</DT
2490 ># Block the non-existent "Privacy-Violation:" client header
2491 { +crunch-client-header{Privacy-Violation:} }
2508 NAME="CRUNCH-IF-NONE-MATCH"
2509 >8.5.7. crunch-if-none-match</A
2514 CLASS="VARIABLELIST"
2520 >Prevent yet another way to track the user's steps between sessions.</P
2528 >"If-None-Match:"</SPAN
2529 > HTTP client header.
2549 > Removing the <SPAN
2551 >"If-None-Match:"</SPAN
2552 > HTTP client header
2553 is useful for filter testing, where you want to force a real
2554 reload instead of getting status code <SPAN
2558 would cause the browser to use a cached copy of the page.
2561 > It is also useful to make sure the header isn't used as a cookie
2562 replacement (unlikely but possible).
2565 > Blocking the <SPAN
2567 >"If-None-Match:"</SPAN
2568 > header shouldn't cause any
2569 caching problems, as long as the <SPAN
2571 >"If-Modified-Since:"</SPAN
2573 isn't blocked or missing as well.
2576 > It is recommended to use this action together with
2580 HREF="actions-file.html#HIDE-IF-MODIFIED-SINCE"
2581 >hide-if-modified-since</A
2588 HREF="actions-file.html#OVERWRITE-LAST-MODIFIED"
2589 >overwrite-last-modified</A
2595 >Example usage (section):</DT
2606 ># Let the browser revalidate cached documents but don't
2607 # allow the server to use the revalidation headers for user tracking.
2608 {+hide-if-modified-since{-60} \
2609 +overwrite-last-modified{randomize} \
2610 +crunch-if-none-match}
2626 NAME="CRUNCH-INCOMING-COOKIES"
2627 >8.5.8. crunch-incoming-cookies</A
2632 CLASS="VARIABLELIST"
2638 > Prevent the web server from setting HTTP cookies on your system
2647 >"Set-Cookie:"</SPAN
2648 > HTTP headers from server replies.
2668 > This action is only concerned with <SPAN
2685 HREF="actions-file.html#CRUNCH-OUTGOING-COOKIES"
2686 >crunch-outgoing-cookies</A
2695 > to disable HTTP cookies completely.
2704 > to use this action in conjunction
2708 HREF="actions-file.html#SESSION-COOKIES-ONLY"
2709 >session-cookies-only</A
2712 since it would prevent the session cookies from being set. See also
2716 HREF="actions-file.html#FILTER-CONTENT-COOKIES"
2717 >filter-content-cookies</A
2734 >+crunch-incoming-cookies</PRE
2749 NAME="CRUNCH-SERVER-HEADER"
2750 >8.5.9. crunch-server-header</A
2755 CLASS="VARIABLELIST"
2761 >Remove a server header <SPAN
2764 > has no dedicated action for.</P
2770 > Deletes every header sent by the server that contains the string the user supplied as parameter.
2790 > This action allows you to block server headers for which no dedicated
2794 > action exists. <SPAN
2798 will remove every server header that contains the string you supplied as parameter.
2801 > Regular expressions are <SPAN
2808 use this action to block different headers in the same request, unless
2809 they contain the same string.
2814 >crunch-server-header</TT
2815 > is only meant for quick tests.
2816 If you have to block several different headers, or only want to modify
2817 parts of them, you should use a custom
2821 HREF="actions-file.html#SERVER-HEADER-FILTER"
2822 >server-header filter</A
2845 > Don't block any header without understanding the consequences.
2853 >Example usage (section):</DT
2864 ># Crunch server headers that try to prevent caching
2865 { +crunch-server-header{no-cache} }
2881 NAME="CRUNCH-OUTGOING-COOKIES"
2882 >8.5.10. crunch-outgoing-cookies</A
2887 CLASS="VARIABLELIST"
2893 > Prevent the web server from reading any HTTP cookies from your system
2903 > HTTP headers from client requests.
2923 > This action is only concerned with <SPAN
2940 HREF="actions-file.html#CRUNCH-INCOMING-COOKIES"
2941 >crunch-incoming-cookies</A
2950 > to disable HTTP cookies completely.
2959 > to use this action in conjunction
2963 HREF="actions-file.html#SESSION-COOKIES-ONLY"
2964 >session-cookies-only</A
2967 since it would prevent the session cookies from being read.
2982 >+crunch-outgoing-cookies</PRE
2997 NAME="DEANIMATE-GIFS"
2998 >8.5.11. deanimate-gifs</A
3003 CLASS="VARIABLELIST"
3009 >Stop those annoying, distracting animated GIF images.</P
3015 > De-animate GIF animations, i.e. reduce them to their first or last image.
3041 > This will also shrink the images considerably (in bytes, not pixels!). If
3045 > is given, the first frame of the animation
3046 is used as the replacement. If <SPAN
3049 > is given, the last
3050 frame of the animation is used instead, which probably makes more sense for
3051 most banner animations, but also has the risk of not showing the entire
3052 last frame (if it is only a delta to an earlier frame).
3055 > You can safely use this action with patterns that will also match non-GIF
3056 objects, because no attempt will be made at anything that doesn't look like
3072 >+deanimate-gifs{last}</PRE
3087 NAME="DOWNGRADE-HTTP-VERSION"
3088 >8.5.12. downgrade-http-version</A
3093 CLASS="VARIABLELIST"
3099 >Work around (very rare) problems with HTTP/1.1</P
3105 > Downgrades HTTP/1.1 client requests and server replies to HTTP/1.0.
3125 > This is a left-over from the time when <SPAN
3129 didn't support important HTTP/1.1 features well. It is left here for the
3130 unlikely case that you experience HTTP/1.1 related problems with some server
3131 out there. Not all HTTP/1.1 features and requirements are supported yet,
3132 so there is a chance you might need this action.
3136 >Example usage (section):</DT
3147 >{+downgrade-http-version}
3148 problem-host.example.com</PRE
3163 NAME="FAST-REDIRECTS"
3164 >8.5.13. fast-redirects</A
3169 CLASS="VARIABLELIST"
3175 >Fool some click-tracking scripts and speed up indirect links.</P
3181 > Detects redirection URLs and redirects the browser without contacting
3182 the redirection server first.
3201 >"simple-check"</SPAN
3202 > to just search for the string <SPAN
3206 to detect redirection URLs.
3213 >"check-decoded-url"</SPAN
3214 > to decode URLs (if necessary) before searching
3215 for redirection URLs.
3225 Many sites, like yahoo.com, don't just link to other sites. Instead, they
3226 will link to some script on their own servers, giving the destination as a
3227 parameter, which will then redirect you to the final target. URLs
3228 resulting from this scheme typically look like:
3231 >"http://www.example.org/click-tracker.cgi?target=http%3a//www.example.net/"</SPAN
3235 > Sometimes, there are even multiple consecutive redirects encoded in the
3236 URL. These redirections via scripts make your web browsing more traceable,
3237 since the server from which you follow such a link can see where you go
3238 to. Apart from that, valuable bandwidth and time is wasted, while your
3239 browser asks the server for one redirect after the other. Plus, it feeds
3243 > This feature is currently not very smart and is scheduled for improvement.
3244 If it is enabled by default, you will have to create some exceptions to
3245 this action. It can lead to failures in several ways:
3248 > Not every URLs with other URLs as parameters is evil.
3249 Some sites offer a real service that requires this information to work.
3250 For example a validation service needs to know, which document to validate.
3254 > assumes that every URL parameter that
3255 looks like another URL is a redirection target, and will always redirect to
3256 the last one. Most of the time the assumption is correct, but if it isn't,
3257 the user gets redirected anyway.
3260 > Another failure occurs if the URL contains other parameters after the URL parameter.
3264 >"http://www.example.org/?redirect=http%3a//www.example.net/&foo=bar"</SPAN
3266 contains the redirection URL <SPAN
3268 >"http://www.example.net/"</SPAN
3270 followed by another parameter. <TT
3274 and will cause a redirect to <SPAN
3276 >"http://www.example.net/&foo=bar"</SPAN
3278 Depending on the target server configuration, the parameter will be silently ignored
3281 >"page not found"</SPAN
3282 > error. You can prevent this problem by
3286 HREF="actions-file.html#REDIRECT"
3290 to remove the last part of the URL, but it requires a little effort.
3293 > To detect a redirection URL, <TT
3297 looks for the string <SPAN
3300 >, either in plain text
3301 (invalid but often used) or encoded as <SPAN
3305 Some sites use their own URL encoding scheme, encrypt the address
3306 of the target server or replace it with a database id. In theses cases
3310 > is fooled and the request reaches the
3311 redirection server where it probably gets logged.
3326 > { +fast-redirects{simple-check} }
3329 { +fast-redirects{check-decoded-url} }
3330 another.example.com/testing</PRE
3351 CLASS="VARIABLELIST"
3357 >Get rid of HTML and JavaScript annoyances, banner advertisements (by size),
3358 do fun text replacements, add personalized effects, etc.</P
3364 > All instances of text-based type, most notably HTML and JavaScript, to which
3365 this action applies, can be filtered on-the-fly through the specified regular
3366 expression based substitutions. (Note: as of version 3.0.3 plain text documents
3367 are exempted from filtering, because web servers often use the
3371 > MIME type for all files whose type they don't know.)
3384 > The name of a content filter, as defined in the <A
3385 HREF="filter-file.html"
3388 Filters can be defined in one or more files as defined by the
3392 HREF="config.html#FILTERFILE"
3403 > is the collection of filters
3404 supplied by the developers. Locally defined filters should go
3405 in their own file, such as <TT
3411 > When used in its negative form,
3412 and without parameters, <SPAN
3418 > filtering is completely disabled.
3425 > For your convenience, there are a number of pre-defined filters available
3426 in the distribution filter file that you can use. See the examples below for
3430 > Filtering requires buffering the page content, which may appear to
3431 slow down page rendering since nothing is displayed until all content has
3432 passed the filters. (It does not really take longer, but seems that way
3433 since the page is not incrementally displayed.) This effect will be more
3434 noticeable on slower connections.
3439 >"Rolling your own"</SPAN
3441 filters requires a knowledge of
3443 HREF="http://en.wikipedia.org/wiki/Regular_expressions"
3452 HREF="http://en.wikipedia.org/wiki/Html"
3459 This is very powerful feature, and potentially very intrusive.
3460 Filters should be used with caution, and where an equivalent
3467 > The amount of data that can be filtered is limited to the
3471 HREF="config.html#BUFFER-LIMIT"
3475 option in the main <A
3479 default is 4096 KB (4 Megs). Once this limit is exceeded, the buffered
3480 data, and all pending data, is passed through unfiltered.
3483 > Inappropriate MIME types, such as zipped files, are not filtered at all.
3484 (Again, only text-based types except plain text). Encrypted SSL data
3485 (from HTTPS servers) cannot be filtered either, since this would violate
3486 the integrity of the secure transaction. In some situations it might
3487 be necessary to protect certain text, like source code, from filtering
3488 by defining appropriate <TT
3494 > Compressed content can't be filtered either, unless <SPAN
3498 is compiled with zlib support (requires at least <SPAN
3505 > will decompress the content before filtering
3509 > If you use a <SPAN
3512 > version without zlib support, but want filtering to work on
3513 as much documents as possible, even those that would normally be sent compressed,
3514 you must use the <TT
3517 HREF="actions-file.html#PREVENT-COMPRESSION"
3518 >prevent-compression</A
3521 action in conjunction with <TT
3527 > Content filtering can achieve some of the same effects as the
3531 HREF="actions-file.html#BLOCK"
3535 action, i.e. it can be used to block ads and banners. But the mechanism
3536 works quite differently. One effective use, is to block ad banners
3537 based on their size (see below), since many of these seem to be somewhat
3544 > with suggestions for new or
3545 improved filters is particularly welcome!
3548 > The below list has only the names and a one-line description of each
3549 predefined filter. There are <A
3550 HREF="filter-file.html#PREDEFINED-FILTERS"
3552 verbose explanations</A
3553 > of what these filters do in the <A
3554 HREF="filter-file.html"
3555 >filter file chapter</A
3560 >Example usage (with filters from the distribution <TT
3565 HREF="filter-file.html#PREDEFINED-FILTERS"
3566 >the Predefined Filters section</A
3568 more explanation on each:</DT
3572 NAME="FILTER-JS-ANNOYANCES"
3583 >+filter{js-annoyances} # Get rid of particularly annoying JavaScript abuse</PRE
3591 NAME="FILTER-JS-EVENTS"
3602 >+filter{js-events} # Kill all JS event bindings (Radically destructive! Only for extra nasty sites)</PRE
3610 NAME="FILTER-HTML-ANNOYANCES"
3621 >+filter{html-annoyances} # Get rid of particularly annoying HTML abuse</PRE
3629 NAME="FILTER-CONTENT-COOKIES"
3640 >+filter{content-cookies} # Kill cookies that come in the HTML or JS content</PRE
3648 NAME="FILTER-REFRESH-TAGS"
3659 >+filter{refresh-tags} # Kill automatic refresh tags (for dial-on-demand setups)</PRE
3667 NAME="FILTER-UNSOLICITED-POPUPS"
3678 >+filter{unsolicited-popups} # Disable only unsolicited pop-up windows. Useful if your browser lacks this ability.</PRE
3686 NAME="FILTER-ALL-POPUPS"
3697 >+filter{all-popups} # Kill all popups in JavaScript and HTML. Useful if your browser lacks this ability.</PRE
3705 NAME="FILTER-IMG-REORDER"
3716 >+filter{img-reorder} # Reorder attributes in <img> tags to make the banners-by-* filters more effective</PRE
3724 NAME="FILTER-BANNERS-BY-SIZE"
3735 >+filter{banners-by-size} # Kill banners by size</PRE
3743 NAME="FILTER-BANNERS-BY-LINK"
3754 >+filter{banners-by-link} # Kill banners by their links to known clicktrackers</PRE
3762 NAME="FILTER-WEBBUGS"
3773 >+filter{webbugs} # Squish WebBugs (1x1 invisible GIFs used for user tracking)</PRE
3781 NAME="FILTER-TINY-TEXTFORMS"
3792 >+filter{tiny-textforms} # Extend those tiny textareas up to 40x80 and kill the hard wrap</PRE
3800 NAME="FILTER-JUMPING-WINDOWS"
3811 >+filter{jumping-windows} # Prevent windows from resizing and moving themselves</PRE
3819 NAME="FILTER-FRAMESET-BORDERS"
3830 >+filter{frameset-borders} # Give frames a border and make them resizeable</PRE
3838 NAME="FILTER-DEMORONIZER"
3849 >+filter{demoronizer} # Fix MS's non-standard use of standard charsets</PRE
3857 NAME="FILTER-SHOCKWAVE-FLASH"
3868 >+filter{shockwave-flash} # Kill embedded Shockwave Flash objects</PRE
3876 NAME="FILTER-QUICKTIME-KIOSKMODE"
3887 >+filter{quicktime-kioskmode} # Make Quicktime movies savable</PRE
3906 >+filter{fun} # Text replacements for subversive browsing fun!</PRE
3914 NAME="FILTER-CRUDE-PARENTAL"
3925 >+filter{crude-parental} # Crude parental filtering (demo only)</PRE
3933 NAME="FILTER-IE-EXPLOITS"
3944 >+filter{ie-exploits} # Disable a known Internet Explorer bug exploits</PRE
3952 NAME="FILTER-SITE-SPECIFICS"
3963 >+filter{site-specifics} # Custom filters for specific site related problems</PRE
3971 NAME="FILTER-GOOGLE"
3982 >+filter{google} # Removes text ads and other Google specific improvements</PRE
4001 >+filter{yahoo} # Removes text ads and other Yahoo specific improvements</PRE
4020 >+filter{msn} # Removes text ads and other MSN specific improvements</PRE
4028 NAME="FILTER-BLOGSPOT"
4039 >+filter{blogspot} # Cleans up Blogspot blogs</PRE
4047 NAME="FILTER-NO-PING"
4058 >+filter{no-ping} # Removes non-standard ping attributes from anchor and area tags</PRE
4073 NAME="FORCE-TEXT-MODE"
4074 >8.5.15. force-text-mode</A
4079 CLASS="VARIABLELIST"
4088 > to treat a document as if it was in some kind of <SPAN
4100 > Declares a document as text, even if the <SPAN
4102 >"Content-Type:"</SPAN
4103 > isn't detected as such.
4126 HREF="actions-file.html#FILTER"
4133 > tries to only filter files that are
4134 in some kind of text format. The same restrictions apply to
4138 HREF="actions-file.html#CONTENT-TYPE-OVERWRITE"
4139 >content-type-overwrite</A
4144 >force-text-mode</TT
4145 > declares a document as text,
4146 without looking at the <SPAN
4148 >"Content-Type:"</SPAN
4170 > Think twice before activating this action. Filtering binary data
4171 with regular expressions can cause file damage.
4206 NAME="FORWARD-OVERRIDE"
4207 >8.5.16. forward-override</A
4212 CLASS="VARIABLELIST"
4218 >Change the forwarding settings based on User-Agent or request origin</P
4224 > Overrules the forward directives in the configuration file.
4244 > to use a direct connection without any additional proxies.</P
4250 >"forward 127.0.0.1:8123"</SPAN
4251 > to use the HTTP proxy listening at 127.0.0.1 port 8123.
4258 >"forward-socks4a 127.0.0.1:9050 ."</SPAN
4259 > to use the socks4a proxy listening at
4260 127.0.0.1 port 9050. Replace <SPAN
4262 >"forward-socks4a"</SPAN
4265 >"forward-socks4"</SPAN
4267 to use a socks4 connection (with local DNS resolution) instead.
4274 >"forward-socks4a 127.0.0.1:9050 proxy.example.org:8000"</SPAN
4275 > to use the socks4a proxy
4276 listening at 127.0.0.1 port 9050 to reach the HTTP proxy listening at proxy.example.org port 8000.
4279 >"forward-socks4a"</SPAN
4282 >"forward-socks4"</SPAN
4283 > to use a socks4 connection
4284 (with local DNS resolution) instead.
4293 > This action takes parameters similar to the
4295 HREF="config.html#FORWARDING"
4297 > directives in the configuration
4298 file, but without the URL pattern. It can be used as replacement, but normally it's only
4299 used in cases where matching based on the request URL isn't sufficient.
4320 > Please read the description for the <A
4321 HREF="config.html#FORWARDING"
4324 using this action. Forwarding to the wrong people will reduce your privacy and increase the
4325 chances of man-in-the-middle attacks.
4328 > If the ports are missing or invalid, default values will be used. This might change
4329 in the future and you shouldn't rely on it. Otherwise incorrect syntax causes Privoxy
4334 HREF="http://config.privoxy.org/show-url-info"
4336 >show-url-info CGI page</A
4338 to verify that your forward settings do what you thought the do.
4357 ># Always use direct connections for requests previously tagged as
4360 >"User-Agent: fetch libfetch/2.0"</SPAN
4362 # resuming downloads continues to work.
4363 # This way you can continue to use Tor for your normal browsing,
4364 # without overloading the Tor network with your FreeBSD ports updates
4365 # or downloads of bigger files like ISOs.
4366 # Note that HTTP headers are easy to fake and therefore their
4367 # values are as (un)trustworthy as your clients and users.
4368 {+forward-override{forward .} \
4369 -hide-if-modified-since \
4370 -overwrite-last-modified \
4372 TAG:^User-Agent: fetch libfetch/2\.0$
4388 NAME="HANDLE-AS-EMPTY-DOCUMENT"
4389 >8.5.17. handle-as-empty-document</A
4394 CLASS="VARIABLELIST"
4400 >Mark URLs that should be replaced by empty documents <SPAN
4404 >if they get blocked</I
4412 > This action alone doesn't do anything noticeable. It just marks URLs.
4416 HREF="actions-file.html#BLOCK"
4426 the presence or absence of this mark decides whether an HTML <SPAN
4430 page, or an empty document will be sent to the client as a substitute for the blocked content.
4437 > document isn't literally empty, but actually contains a single space.
4457 > Some browsers complain about syntax errors if JavaScript documents
4458 are blocked with <SPAN
4462 default HTML page; this option can be used to silence them.
4463 And of course this action can also be used to eliminate the <SPAN
4467 BLOCKED message in frames.
4470 > The content type for the empty document can be specified with
4474 HREF="actions-file.html#CONTENT-TYPE-OVERWRITE"
4475 >content-type-overwrite{}</A
4478 but usually this isn't necessary.
4493 ># Block all documents on example.org that end with ".js",
4494 # but send an empty document instead of the usual HTML message.
4495 {+block +handle-as-empty-document}
4512 NAME="HANDLE-AS-IMAGE"
4513 >8.5.18. handle-as-image</A
4518 CLASS="VARIABLELIST"
4524 >Mark URLs as belonging to images (so they'll be replaced by images <SPAN
4528 >if they do get blocked</I
4530 >, rather than HTML pages)</P
4536 > This action alone doesn't do anything noticeable. It just marks URLs as images.
4540 HREF="actions-file.html#BLOCK"
4550 the presence or absence of this mark decides whether an HTML <SPAN
4554 page, or a replacement image (as determined by the <TT
4557 HREF="actions-file.html#SET-IMAGE-BLOCKER"
4558 >set-image-blocker</A
4560 > action) will be sent to the
4561 client as a substitute for the blocked content.
4581 > The below generic example section is actually part of <TT
4585 It marks all URLs with well-known image file name extensions as images and should
4589 > Users will probably only want to use the handle-as-image action in conjunction with
4593 HREF="actions-file.html#BLOCK"
4596 >, to block sources of banners, whose URLs don't
4597 reflect the file type, like in the second example section.
4600 > Note that you cannot treat HTML pages as images in most cases. For instance, (in-line) ad
4601 frames require an HTML page to be sent, or they won't display properly.
4604 >handle-as-image</TT
4605 > in this situation will not replace the
4606 ad frame with an image, but lead to error messages.
4610 >Example usage (sections):</DT
4621 ># Generic image extensions:
4624 /.*\.(gif|jpg|jpeg|png|bmp|ico)$
4626 # These don't look like images, but they're banners and should be
4627 # blocked as images:
4629 {+block +handle-as-image}
4630 some.nasty-banner-server.com/junk.cgi\?output=trash
4632 # Banner source! Who cares if they also have non-image content?
4633 ad.doubleclick.net </PRE
4648 NAME="HIDE-ACCEPT-LANGUAGE"
4649 >8.5.19. hide-accept-language</A
4654 CLASS="VARIABLELIST"
4660 >Pretend to use different language settings.</P
4666 > Deletes or replaces the <SPAN
4668 >"Accept-Language:"</SPAN
4669 > HTTP header in client requests.
4685 >, or any user defined value.
4692 > Faking the browser's language settings can be useful to make a
4693 foreign User-Agent set with
4697 HREF="actions-file.html#HIDE-USER-AGENT"
4704 > However some sites with content in different languages check the
4707 >"Accept-Language:"</SPAN
4708 > to decide which one to take by default.
4709 Sometimes it isn't possible to later switch to another language without
4712 >"Accept-Language:"</SPAN
4716 > Therefore it's a good idea to either only change the
4719 >"Accept-Language:"</SPAN
4720 > header to languages you understand,
4721 or to languages that aren't wide spread.
4724 > Before setting the <SPAN
4726 >"Accept-Language:"</SPAN
4728 to a rare language, you should consider that it helps to
4729 make your requests unique and thus easier to trace.
4730 If you don't plan to change this header frequently,
4731 you should stick to a common language.
4735 >Example usage (section):</DT
4746 ># Pretend to use Canadian language settings.
4747 {+hide-accept-language{en-ca} \
4748 +hide-user-agent{Mozilla/5.0 (X11; U; OpenBSD i386; en-CA; rv:1.8.0.4) Gecko/20060628 Firefox/1.5.0.4} \
4765 NAME="HIDE-CONTENT-DISPOSITION"
4766 >8.5.20. hide-content-disposition</A
4771 CLASS="VARIABLELIST"
4777 >Prevent download menus for content you prefer to view inside the browser.</P
4783 > Deletes or replaces the <SPAN
4785 >"Content-Disposition:"</SPAN
4786 > HTTP header set by some servers.
4802 >, or any user defined value.
4809 > Some servers set the <SPAN
4811 >"Content-Disposition:"</SPAN
4813 documents they assume you want to save locally before viewing them.
4816 >"Content-Disposition:"</SPAN
4817 > header contains the file name
4818 the browser is supposed to use by default.
4821 > In most browsers that understand this header, it makes it impossible to
4828 > the document, without downloading it first,
4829 even if it's just a simple text file or an image.
4832 > Removing the <SPAN
4834 >"Content-Disposition:"</SPAN
4836 to prevent this annoyance, but some browsers additionally check the
4839 >"Content-Type:"</SPAN
4840 > header, before they decide if they can
4841 display a document without saving it first. In these cases, you have
4842 to change this header as well, before the browser stops displaying
4846 > It is also possible to change the server's file name suggestion
4847 to another one, but in most cases it isn't worth the time to set
4851 > This action will probably be removed in the future,
4852 use server-header filters instead.
4867 ># Disarm the download link in Sourceforge's patch tracker
4869 +content-type-overwrite{text/plain}\
4870 +hide-content-disposition{block} }
4871 .sourceforge.net/tracker/download\.php</PRE
4886 NAME="HIDE-IF-MODIFIED-SINCE"
4887 >8.5.21. hide-if-modified-since</A
4892 CLASS="VARIABLELIST"
4898 >Prevent yet another way to track the user's steps between sessions.</P
4906 >"If-Modified-Since:"</SPAN
4907 > HTTP client header or modifies its value.
4923 >, or a user defined value that specifies a range of hours.
4930 > Removing this header is useful for filter testing, where you want to force a real
4931 reload instead of getting status code <SPAN
4934 >, which would cause the
4935 browser to use a cached copy of the page.
4938 > Instead of removing the header, <TT
4940 >hide-if-modified-since</TT
4942 also add or subtract a random amount of time to/from the header's value.
4943 You specify a range of minutes where the random factor should be chosen from and
4947 > does the rest. A negative value means
4948 subtracting, a positive value adding.
4951 > Randomizing the value of the <SPAN
4953 >"If-Modified-Since:"</SPAN
4955 it less likely that the server can use the time as a cookie replacement,
4956 but you will run into caching problems if the random range is too high.
4959 > It is a good idea to only use a small negative value and let
4963 HREF="actions-file.html#OVERWRITE-LAST-MODIFIED"
4964 >overwrite-last-modified</A
4967 handle the greater changes.
4970 > It is also recommended to use this action together with
4974 HREF="actions-file.html#CRUNCH-IF-NONE-MATCH"
4975 >crunch-if-none-match</A
4978 otherwise it's more or less pointless.
4982 >Example usage (section):</DT
4993 ># Let the browser revalidate but make tracking based on the time less likely.
4994 {+hide-if-modified-since{-60} \
4995 +overwrite-last-modified{randomize} \
4996 +crunch-if-none-match}
5012 NAME="HIDE-FORWARDED-FOR-HEADERS"
5013 >8.5.22. hide-forwarded-for-headers</A
5018 CLASS="VARIABLELIST"
5024 >Improve privacy by not forwarding the source of the request in the HTTP headers.</P
5030 > Deletes any existing <SPAN
5032 >"X-Forwarded-for:"</SPAN
5033 > HTTP header from client requests.
5053 > It is safe and recommended to leave this on.
5068 >+hide-forwarded-for-headers</PRE
5083 NAME="HIDE-FROM-HEADER"
5084 >8.5.23. hide-from-header</A
5089 CLASS="VARIABLELIST"
5095 >Keep your (old and ill) browser from telling web servers your email address</P
5101 > Deletes any existing <SPAN
5104 > HTTP header, or replaces it with the
5121 >, or any user defined value.
5131 > will completely remove the header
5132 (not to be confused with the <TT
5135 HREF="actions-file.html#BLOCK"
5142 > Alternately, you can specify any value you prefer to be sent to the web
5143 server. If you do, it is a matter of fairness not to use any address that
5144 is actually used by a real person.
5147 > This action is rarely needed, as modern web browsers don't send
5166 >+hide-from-header{block}</PRE
5179 >+hide-from-header{spam-me-senseless@sittingduck.example.com}</PRE
5194 NAME="HIDE-REFERRER"
5195 >8.5.24. hide-referrer</A
5203 CLASS="VARIABLELIST"
5209 >Conceal which link you followed to get to a particular site</P
5218 > (sic) HTTP header from the client request,
5219 or replaces it with a forged one.
5238 >"conditional-block"</SPAN
5239 > to delete the header completely if the host has changed.</P
5245 >"conditional-forge"</SPAN
5246 > to forge the header if the host has changed.</P
5253 > to delete the header unconditionally.</P
5260 > to pretend to be coming from the homepage of the server we are talking to.</P
5264 >Any other string to set a user defined referrer.</P
5274 >conditional-block</TT
5275 > is the only parameter,
5276 that isn't easily detected in the server's log file. If it blocks the
5277 referrer, the request will look like the visitor used a bookmark or
5278 typed in the address directly.
5281 > Leaving the referrer unmodified for requests on the same host
5282 allows the server owner to see the visitor's <SPAN
5286 but in most cases she could also get that information by comparing
5287 other parts of the log file: for example the User-Agent if it isn't
5288 a very common one, or the user's IP address if it doesn't change between
5292 > Always blocking the referrer, or using a custom one, can lead to
5293 failures on servers that check the referrer before they answer any
5294 requests, in an attempt to prevent their content from being
5295 embedded or linked to elsewhere.
5300 >conditional-block</TT
5305 will work with referrer checks, as long as content and valid referring page
5306 are on the same host. Most of the time that's the case.
5313 > is an alternate spelling of
5317 > and the two can be can be freely
5318 substituted with each other. (<SPAN
5322 correct English spelling, however the HTTP specification has a bug - it
5323 requires it to be spelled as <SPAN
5341 >+hide-referrer{forge}</PRE
5354 >+hide-referrer{http://www.yahoo.com/}</PRE
5369 NAME="HIDE-USER-AGENT"
5370 >8.5.25. hide-user-agent</A
5375 CLASS="VARIABLELIST"
5381 >Try to conceal your type of browser and client operating system</P
5387 > Replaces the value of the <SPAN
5389 >"User-Agent:"</SPAN
5391 in client requests with the specified value.
5404 > Any user-defined string.
5429 > This can lead to problems on web sites that depend on looking at this header in
5430 order to customize their content for different browsers (which, by the
5437 > the right thing to do: good web sites
5438 work browser-independently).
5445 > Using this action in multi-user setups or wherever different types of
5446 browsers will access the same <SPAN
5456 >. In single-user, single-browser
5457 setups, you might use it to delete your OS version information from
5458 the headers, because it is an invitation to exploit known bugs for your
5459 OS. It is also occasionally useful to forge this in order to access
5460 sites that won't let you in otherwise (though there may be a good
5461 reason in some cases). Example of this: some MSN sites will not
5465 > enter, yet forging to a
5469 > user-agent works just fine.
5470 (Must be just a silly MS goof, I'm sure :-).
5473 > More information on known user-agent strings can be found at
5475 HREF="http://www.user-agents.org/"
5477 >http://www.user-agents.org/</A
5481 HREF="http://en.wikipedia.org/wiki/User_agent"
5483 >http://en.wikipedia.org/wiki/User_agent</A
5499 >+hide-user-agent{Netscape 6.1 (X11; I; Linux 2.4.18 i686)}</PRE
5514 NAME="INSPECT-JPEGS"
5515 >8.5.26. inspect-jpegs</A
5520 CLASS="VARIABLELIST"
5526 >Try to protect against a MS buffer over-run in JPEG processing</P
5532 > Protect against a known exploit
5552 > See Microsoft Security Bulletin MS04-028. JPEG images are one of the most
5553 common image types found across the Internet. The exploit as described can
5554 allow execution of code on the target system, giving an attacker access
5555 to the system in question by merely planting an altered JPEG image, which
5556 would have no obvious indications of what lurks inside. This action
5557 tries to prevent this exploit if delivered through unencrypted HTTP.
5560 > Note that the exploit mentioned is several years old
5561 and it's unlikely that your client is still vulnerable
5562 against it. This action may be removed in one of the
5578 >+inspect-jpegs</PRE
5593 >8.5.27. kill-popups<A
5601 CLASS="VARIABLELIST"
5607 >Eliminate those annoying pop-up windows (deprecated)</P
5613 > While loading the document, replace JavaScript code that opens
5614 pop-up windows with (syntactically neutral) dummy code on the fly.
5634 > This action is basically a built-in, hardwired special-purpose filter
5635 action, but there are important differences: For <TT
5639 the document need not be buffered, so it can be incrementally rendered while
5640 downloading. But <TT
5643 > doesn't catch as many pop-ups as
5647 HREF="actions-file.html#FILTER-ALL-POPUPS"
5656 does and is not as smart as <TT
5659 HREF="actions-file.html#FILTER-UNSOLICITED-POPUPS"
5663 >unsolicited-popups</I
5671 > Think of it as a fast and efficient replacement for a filter that you
5672 can use if you don't want any filtering at all. Note that it doesn't make
5673 sense to combine it with any <TT
5676 HREF="actions-file.html#FILTER"
5680 since as soon as one <TT
5683 HREF="actions-file.html#FILTER"
5687 the whole document needs to be buffered anyway, which destroys the advantage of
5691 > action over its filter equivalent.
5694 > Killing all pop-ups unconditionally is problematic. Many shops and banks rely on
5695 pop-ups to display forms, shopping carts etc, and the <TT
5698 HREF="actions-file.html#FILTER-UNSOLICITED-POPUPS"
5702 >unsolicited-popups</I
5707 > does a better job of catching only the unwanted ones.
5710 > If the only kind of pop-ups that you want to kill are exit consoles (those
5717 > windows that appear when you close an other
5718 one), you might want to use
5722 HREF="actions-file.html#FILTER"
5734 > This action is most appropriate for browsers that don't have any controls
5735 for unwanted pop-ups. Not recommended for general usage.
5738 > This action doesn't work very reliable and may be removed in future releases.
5767 NAME="LIMIT-CONNECT"
5768 >8.5.28. limit-connect</A
5773 CLASS="VARIABLELIST"
5779 >Prevent abuse of <SPAN
5782 > as a TCP proxy relay or disable SSL for untrusted sites</P
5788 > Specifies to which ports HTTP CONNECT requests are allowable.
5801 > A comma-separated list of ports or port ranges (the latter using dashes, with the minimum
5802 defaulting to 0 and the maximum to 65K).
5809 > By default, i.e. if no <TT
5816 > only allows HTTP CONNECT
5817 requests to port 443 (the standard, secure HTTPS port). Use
5821 > if more fine-grained control is desired
5822 for some or all destinations.
5825 > The CONNECT methods exists in HTTP to allow access to secure websites
5829 > URLs) through proxies. It works very simply:
5830 the proxy connects to the server on the specified port, and then
5831 short-circuits its connections to the client and to the remote server.
5832 This means CONNECT-enabled proxies can be used as TCP relays very easily.
5838 > relays HTTPS traffic without seeing
5839 the decoded content. Websites can leverage this limitation to circumvent <SPAN
5843 filters. By specifying an invalid port range you can disable HTTPS entirely.
5844 If you plan to disable SSL by default, consider enabling
5848 HREF="actions-file.html#TREAT-FORBIDDEN-CONNECTS-LIKE-BLOCKS"
5849 >treat-forbidden-connects-like-blocks</A
5852 as well, to be able to quickly create exceptions.
5856 >Example usages:</DT
5867 >+limit-connect{443} # This is the default and need not be specified.
5868 +limit-connect{80,443} # Ports 80 and 443 are OK.
5869 +limit-connect{-3, 7, 20-100, 500-} # Ports less than 3, 7, 20 to 100 and above 500 are OK.
5870 +limit-connect{-} # All ports are OK
5871 +limit-connect{,} # No HTTPS/SSL traffic is allowed</PRE
5886 NAME="PREVENT-COMPRESSION"
5887 >8.5.29. prevent-compression</A
5892 CLASS="VARIABLELIST"
5898 > Ensure that servers send the content uncompressed, so it can be
5902 HREF="actions-file.html#FILTER"
5912 > Removes the Accept-Encoding header which can be used to ask for compressed transfer.
5932 > More and more websites send their content compressed by default, which
5933 is generally a good idea and saves bandwidth. But the <TT
5936 HREF="actions-file.html#FILTER"
5942 HREF="actions-file.html#DEANIMATE-GIFS"
5949 HREF="actions-file.html#KILL-POPUPS"
5953 access to the uncompressed data.
5956 > When compiled with zlib support (available since <SPAN
5959 > 3.0.7), content that should be
5960 filtered is decompressed on-the-fly and you don't have to worry about this action.
5961 If you are using an older <SPAN
5964 > version, or one that hasn't been compiled with zlib
5965 support, this action can be used to convince the server to send the content uncompressed.
5968 > Most text-based instances compress very well, the size is seldom decreased by less than 50%,
5969 for markup-heavy instances like news feeds saving more than 90% of the original size isn't
5973 > Not using compression will therefore slow down the transfer, and you should only
5974 enable this action if you really need it. As of <SPAN
5977 > 3.0.7 it's disabled in all
5978 predefined action settings.
5981 > Note that some (rare) ill-configured sites don't handle requests for uncompressed
5982 documents correctly. Broken PHP applications tend to send an empty document body,
5983 some IIS versions only send the beginning of the content. If you enable
5986 >prevent-compression</TT
5987 > per default, you might want to add
5988 exceptions for those sites. See the example for how to do that.
5992 >Example usage (sections):</DT
6003 ># Selectively turn off compression, and enable a filter
6005 { +filter{tiny-textforms} +prevent-compression }
6006 # Match only these sites
6011 # Or instead, we could set a universal default:
6013 { +prevent-compression }
6016 # Then maybe make exceptions for broken sites:
6018 { -prevent-compression }
6034 NAME="OVERWRITE-LAST-MODIFIED"
6035 >8.5.30. overwrite-last-modified</A
6040 CLASS="VARIABLELIST"
6046 >Prevent yet another way to track the user's steps between sessions.</P
6054 >"Last-Modified:"</SPAN
6055 > HTTP server header or modifies its value.
6068 > One of the keywords: <SPAN
6073 >"reset-to-request-time"</SPAN
6085 > Removing the <SPAN
6087 >"Last-Modified:"</SPAN
6088 > header is useful for filter
6089 testing, where you want to force a real reload instead of getting status
6093 >, which would cause the browser to reuse the old
6094 version of the page.
6100 > option overwrites the value of the
6103 >"Last-Modified:"</SPAN
6104 > header with a randomly chosen time
6105 between the original value and the current time. In theory the server
6106 could send each document with a different <SPAN
6108 >"Last-Modified:"</SPAN
6110 header to track visits without using cookies. <SPAN
6114 makes it impossible and the browser can still revalidate cached documents.
6119 >"reset-to-request-time"</SPAN
6120 > overwrites the value of the
6123 >"Last-Modified:"</SPAN
6124 > header with the current time. You could use
6125 this option together with
6129 HREF="actions-file.html#HIDE-IF-MODIFIED-SINCE"
6130 >hided-if-modified-since</A
6133 to further customize your random range.
6136 > The preferred parameter here is <SPAN
6140 to use, as long as the time settings are more or less correct.
6141 If the server sets the <SPAN
6143 >"Last-Modified:"</SPAN
6144 > header to the time
6145 of the request, the random range becomes zero and the value stays the same.
6146 Therefore you should later randomize it a second time with
6150 HREF="actions-file.html#HIDE-IF-MODIFIED-SINCE"
6151 >hided-if-modified-since</A
6157 > It is also recommended to use this action together with
6161 HREF="actions-file.html#CRUNCH-IF-NONE-MATCH"
6162 >crunch-if-none-match</A
6179 ># Let the browser revalidate without being tracked across sessions
6180 { +hide-if-modified-since{-60} \
6181 +overwrite-last-modified{randomize} \
6182 +crunch-if-none-match}
6199 >8.5.31. redirect</A
6204 CLASS="VARIABLELIST"
6210 > Redirect requests to other sites.
6217 > Convinces the browser that the requested document has been moved
6218 to another location and the browser should get it from there.
6231 > An absolute URL or a single pcrs command.
6238 > Requests to which this action applies are answered with a
6239 HTTP redirect to URLs of your choosing. The new URL is
6240 either provided as parameter, or derived by applying a
6241 single pcrs command to the original URL.
6244 > This action will be ignored if you use it together with
6248 HREF="actions-file.html#BLOCK"
6252 It can be combined with
6256 HREF="actions-file.html#FAST-REDIRECTS"
6257 >fast-redirects{check-decoded-url}</A
6260 to redirect to a decoded version of a rewritten URL.
6263 > Use this action carefully, make sure not to create redirection loops
6264 and be aware that using your own redirects might make it
6265 possible to fingerprint your requests.
6269 >Example usages:</DT
6280 ># Replace example.com's style sheet with another one
6281 { +redirect{http://localhost/css-replacements/example.com.css} }
6282 example.com/stylesheet\.css
6284 # Create a short, easy to remember nickname for a favorite site
6285 # (relies on the browser accept and forward invalid URLs to <SPAN
6289 { +redirect{http://www.privoxy.org/user-manual/actions-file.html} }
6292 # Always use the expanded view for Undeadly.org articles
6293 # (Note the $ at the end of the URL pattern to make sure
6294 # the request for the rewritten URL isn't redirected as well)
6295 {+redirect{s@$@&mode=expanded@}}
6296 undeadly.org/cgi\?action=article&sid=\d*$</PRE
6311 NAME="SEND-VANILLA-WAFER"
6312 >8.5.32. send-vanilla-wafer</A
6317 CLASS="VARIABLELIST"
6323 > Feed log analysis scripts with useless data.
6330 > Sends a cookie with each request stating that you do not accept any copyright
6331 on cookies sent to you, and asking the site operator not to track you.
6351 > The vanilla wafer is a (relatively) unique header and could conceivably be used to track you.
6354 > This action is rarely used and not enabled in the default configuration.
6369 >+send-vanilla-wafer</PRE
6385 >8.5.33. send-wafer</A
6390 CLASS="VARIABLELIST"
6396 > Send custom cookies or feed log analysis scripts with even more useless data.
6403 > Sends a custom, user-defined cookie with each request.
6416 > A string of the form <SPAN
6436 > Being multi-valued, multiple instances of this action can apply to the same request,
6437 resulting in multiple cookies being sent.
6440 > This action is rarely used and not enabled in the default configuration.
6444 >Example usage (section):</DT
6455 >{+send-wafer{UsingPrivoxy=true}}
6456 my-internal-testing-server.void</PRE
6471 NAME="SERVER-HEADER-FILTER"
6472 >8.5.34. server-header-filter</A
6477 CLASS="VARIABLELIST"
6483 > Rewrite or remove single server headers.
6490 > All server headers to which this action applies are filtered on-the-fly
6491 through the specified regular expression based substitutions.
6504 > The name of a server-header filter, as defined in one of the
6506 HREF="filter-file.html"
6515 > Server-header filters are applied to each header on its own, not to
6516 all at once. This makes it easier to diagnose problems, but on the downside
6517 you can't write filters that only change header x if header y's value is z.
6518 You can do that by using tags though.
6521 > Server-header filters are executed after the other header actions have finished
6522 and use their output as input.
6525 > Please refer to the <A
6526 HREF="filter-file.html"
6527 >filter file chapter</A
6529 to learn which server-header filters are available by default, and how to
6534 >Example usage (section):</DT
6545 >{+server-header-filter{html-to-xml}}
6546 example.org/xml-instance-that-is-delivered-as-html
6548 {+server-header-filter{xml-to-html}}
6549 example.org/instance-that-is-delivered-as-xml-but-is-not
6565 NAME="SERVER-HEADER-TAGGER"
6566 >8.5.35. server-header-tagger</A
6571 CLASS="VARIABLELIST"
6577 > Enable or disable filters based on the Content-Type header.
6584 > Server headers to which this action applies are filtered on-the-fly through
6585 the specified regular expression based substitutions, the result is used as
6599 > The name of a server-header tagger, as defined in one of the
6601 HREF="filter-file.html"
6610 > Server-header taggers are applied to each header on its own,
6611 and as the header isn't modified, each tagger <SPAN
6618 > Server-header taggers are executed before all other header actions
6619 that modify server headers. Their tags can be used to control
6620 all of the other server-header actions, the content filters
6621 and the crunch actions (<A
6622 HREF="actions-file.html#REDIRECT"
6626 HREF="actions-file.html#BLOCK"
6631 > Obviously crunching based on tags created by server-header taggers
6632 doesn't prevent the request from showing up in the server's log file.
6636 >Example usage (section):</DT
6647 ># Tag every request with the content type declared by the server
6648 {+server-header-tagger{content-type}}
6665 NAME="SESSION-COOKIES-ONLY"
6666 >8.5.36. session-cookies-only</A
6671 CLASS="VARIABLELIST"
6677 > Allow only temporary <SPAN
6680 > cookies (for the current
6681 browser session <SPAN
6699 >"Set-Cookie:"</SPAN
6701 server headers. Most browsers will not store such cookies permanently and
6702 forget them in between sessions.
6722 > This is less strict than <TT
6725 HREF="actions-file.html#CRUNCH-INCOMING-COOKIES"
6726 >crunch-incoming-cookies</A
6732 HREF="actions-file.html#CRUNCH-OUTGOING-COOKIES"
6733 >crunch-outgoing-cookies</A
6735 > and allows you to browse
6736 websites that insist or rely on setting cookies, without compromising your privacy too badly.
6739 > Most browsers will not permanently store cookies that have been processed by
6742 >session-cookies-only</TT
6743 > and will forget about them between sessions.
6744 This makes profiling cookies useless, but won't break sites which require cookies so
6745 that you can log in for transactions. This is generally turned on for all
6746 sites, and is the recommended setting.
6757 >session-cookies-only</TT
6762 HREF="actions-file.html#CRUNCH-INCOMING-COOKIES"
6763 >crunch-incoming-cookies</A
6769 HREF="actions-file.html#CRUNCH-OUTGOING-COOKIES"
6770 >crunch-outgoing-cookies</A
6772 >. If you do, cookies
6773 will be plainly killed.
6776 > Note that it is up to the browser how it handles such cookies without an <SPAN
6780 field. If you use an exotic browser, you might want to try it out to be sure.
6783 > This setting also has no effect on cookies that may have been stored
6784 previously by the browser before starting <SPAN
6788 These would have to be removed manually.
6796 HREF="actions-file.html#FILTER-CONTENT-COOKIES"
6797 >content-cookies filter</A
6799 to block some types of cookies. Content cookies are not effected by
6802 >session-cookies-only</TT
6818 >+session-cookies-only</PRE
6833 NAME="SET-IMAGE-BLOCKER"
6834 >8.5.37. set-image-blocker</A
6839 CLASS="VARIABLELIST"
6845 >Choose the replacement for blocked images</P
6851 > This action alone doesn't do anything noticeable. If <SPAN
6861 HREF="actions-file.html#BLOCK"
6873 HREF="actions-file.html#HANDLE-AS-IMAGE"
6883 apply, i.e. if the request is to be blocked as an image,
6890 > the parameter of this action decides what will be
6891 sent as a replacement.
6911 > to send a built-in checkerboard pattern image. The image is visually
6912 decent, scales very well, and makes it obvious where banners were busted.
6920 > to send a built-in transparent image. This makes banners disappear
6921 completely, but makes it hard to detect where <SPAN
6925 images on a given page and complicates troubleshooting if <SPAN
6929 has blocked innocent images, like navigation icons.
6943 send a redirect to <TT
6949 to any image anywhere, even in your local filesystem via <SPAN
6953 (But note that not all browsers support redirecting to a local file system).
6956 > A good application of redirects is to use special <SPAN
6960 URLs, which send the built-in images, as <TT
6966 This has the same visual effect as specifying <SPAN
6973 the first place, but enables your browser to cache the replacement image, instead of requesting
6974 it over and over again.
6983 > The URLs for the built-in images are <SPAN
6985 >"http://config.privoxy.org/send-banner?type=<TT
7006 > There is a third (advanced) type, called <SPAN
7018 >set-image-blocker</TT
7019 >, but meant for use from <A
7020 HREF="filter-file.html"
7023 Auto will select the type of image that would have applied to the referring page, had it been an image.
7041 >+set-image-blocker{pattern}</PRE
7048 > Redirect to the BSD daemon:
7059 >+set-image-blocker{http://www.freebsd.org/gifs/dae_up3.gif}</PRE
7066 > Redirect to the built-in pattern for better caching:
7077 >+set-image-blocker{http://config.privoxy.org/send-banner?type=pattern}</PRE
7092 NAME="TREAT-FORBIDDEN-CONNECTS-LIKE-BLOCKS"
7093 >8.5.38. treat-forbidden-connects-like-blocks</A
7098 CLASS="VARIABLELIST"
7104 >Block forbidden connects with an easy to find error message.</P
7110 > If this action is enabled, <SPAN
7114 makes a difference between forbidden connects and ordinary blocks.
7138 HREF="actions-file.html#LIMIT-CONNECT"
7144 with a short error message inside the headers. If the browser doesn't display
7145 headers (most don't), you just see an empty page.
7148 > With this action enabled, <SPAN
7152 the message that is used for ordinary blocks instead. If you decide
7153 to make an exception for the page in question, you can do so by
7163 > requests the clients tell
7167 > which host they are interested
7168 in, but not which document they plan to get later. As a result, the
7171 >"Go there anyway"</SPAN
7172 > wouldn't work and is therefore suppressed.
7187 >+treat-forbidden-connects-like-blocks</PRE
7206 > Note that many of these actions have the potential to cause a page to
7207 misbehave, possibly even not to display at all. There are many ways
7208 a site designer may choose to design his site, and what HTTP header
7209 content, and other criteria, he may depend on. There is no way to have hard
7210 and fast rules for all sites. See the <A
7211 HREF="appendix.html#ACTIONSANAT"
7213 > for a brief example on troubleshooting
7236 >, can be defined by combining other actions.
7237 These can in turn be invoked just like the built-in actions.
7238 Currently, an alias name can contain any character except space, tab,
7256 > that you only use <SPAN
7276 Alias names are not case sensitive, and are not required to start with a
7283 > sign, since they are merely textually
7286 > Aliases can be used throughout the actions file, but they <SPAN
7291 defined in a special section at the top of the file!</I
7294 And there can only be one such section per actions file. Each actions file may
7295 have its own alias section, and the aliases defined in it are only visible
7296 within that file.</P
7298 > There are two main reasons to use aliases: One is to save typing for frequently
7299 used combinations of actions, the other one is a gain in flexibility: If you
7300 decide once how you want to handle shops by defining an alias called
7304 >, you can later change your policy on shops in
7311 > place, and your changes will take effect everywhere
7312 in the actions file where the <SPAN
7315 > alias is used. Calling aliases
7316 by their purpose also makes your actions files more readable.</P
7318 > Currently, there is one big drawback to using aliases, though:
7322 >'s built-in web-based action file
7323 editor honors aliases when reading the actions files, but it expands
7324 them before writing. So the effects of your aliases are of course preserved,
7325 but the aliases themselves are lost when you edit sections that use aliases
7328 > Now let's define some aliases...</P
7338 > # Useful custom aliases we can use later.
7340 # Note the (required!) section header line and that this section
7341 # must be at the top of the actions file!
7345 # These aliases just save typing later:
7346 # (Note that some already use other aliases!)
7348 +crunch-all-cookies = +<A
7349 HREF="actions-file.html#CRUNCH-INCOMING-COOKIES"
7350 >crunch-incoming-cookies</A
7352 HREF="actions-file.html#CRUNCH-OUTGOING-COOKIES"
7353 >crunch-outgoing-cookies</A
7355 -crunch-all-cookies = -<A
7356 HREF="actions-file.html#CRUNCH-INCOMING-COOKIES"
7357 >crunch-incoming-cookies</A
7359 HREF="actions-file.html#CRUNCH-OUTGOING-COOKIES"
7360 >crunch-outgoing-cookies</A
7362 +block-as-image = +block +handle-as-image
7363 allow-all-cookies = -crunch-all-cookies -<A
7364 HREF="actions-file.html#SESSION-COOKIES-ONLY"
7365 >session-cookies-only</A
7367 HREF="actions-file.html#FILTER-CONTENT-COOKIES"
7368 >filter{content-cookies}</A
7371 # These aliases define combinations of actions
7372 # that are useful for certain types of sites:
7375 HREF="actions-file.html#BLOCK"
7378 HREF="actions-file.html#FILTER"
7380 > -crunch-all-cookies -<A
7381 HREF="actions-file.html#FAST-REDIRECTS"
7384 HREF="actions-file.html#HIDE-REFERER"
7387 HREF="actions-file.html#KILL-POPUPS"
7390 HREF="actions-file.html#PREVENT-COMPRESSION"
7391 >prevent-compression</A
7394 shop = -crunch-all-cookies -<A
7395 HREF="actions-file.html#FILTER-ALL-POPUPS"
7396 >filter{all-popups}</A
7398 HREF="actions-file.html#KILL-POPUPS"
7402 # Short names for other aliases, for really lazy people ;-)
7404 c0 = +crunch-all-cookies
7405 c1 = -crunch-all-cookies</PRE
7411 > ...and put them to use. These sections would appear in the lower part of an
7412 actions file and define exceptions to the default actions (as specified further
7426 > # These sites are either very complex or very keen on
7427 # user data and require minimal interference to work:
7430 .office.microsoft.com
7431 .windowsupdate.microsoft.com
7432 # Gmail is really mail.google.com, not gmail.com
7436 # Allow cookies (for setting and retrieving your customer data)
7440 .worldpay.com # for quietpc.com
7443 # These shops require pop-ups:
7445 {-kill-popups -filter{all-popups} -filter{unsolicited-popups}}
7447 .overclockers.co.uk</PRE
7453 > Aliases like <SPAN
7459 > are typically used for
7463 > sites that require more than one action to be disabled
7464 in order to function properly.</P
7472 >8.7. Actions Files Tutorial</A
7475 > The above chapters have shown <A
7476 HREF="actions-file.html"
7477 >which actions files
7478 there are and how they are organized</A
7479 >, how actions are <A
7480 HREF="actions-file.html#ACTIONS"
7483 HREF="actions-file.html#ACTIONS-APPLY"
7487 HREF="actions-file.html#AF-PATTERNS"
7491 HREF="actions-file.html#ALIASES"
7493 >. Now, let's look at an
7501 file and see how all these pieces come together:</P
7508 >8.7.1. default.action</A
7511 >Every config file should start with a short comment stating its purpose:</P
7521 ># Sample default.action file <ijbswa-developers@lists.sourceforge.net></PRE
7527 >Then, since this is the <TT
7531 first section is a special section for internal use that you needn't
7532 change or worry about:</P
7542 >##########################################################################
7543 # Settings -- Don't change! For internal Privoxy use ONLY.
7544 ##########################################################################
7547 for-privoxy-version=3.0</PRE
7553 >After that comes the (optional) alias section. We'll use the example
7554 section from the above <A
7555 HREF="actions-file.html#ALIASES"
7556 >chapter on aliases</A
7558 that also explains why and how aliases are used:</P
7568 >##########################################################################
7570 ##########################################################################
7573 # These aliases just save typing later:
7574 # (Note that some already use other aliases!)
7576 +crunch-all-cookies = +<A
7577 HREF="actions-file.html#CRUNCH-INCOMING-COOKIES"
7578 >crunch-incoming-cookies</A
7580 HREF="actions-file.html#CRUNCH-OUTGOING-COOKIES"
7581 >crunch-outgoing-cookies</A
7583 -crunch-all-cookies = -<A
7584 HREF="actions-file.html#CRUNCH-INCOMING-COOKIES"
7585 >crunch-incoming-cookies</A
7587 HREF="actions-file.html#CRUNCH-OUTGOING-COOKIES"
7588 >crunch-outgoing-cookies</A
7590 +block-as-image = +block +handle-as-image
7591 mercy-for-cookies = -crunch-all-cookies -<A
7592 HREF="actions-file.html#SESSION-COOKIES-ONLY"
7593 >session-cookies-only</A
7595 HREF="actions-file.html#FILTER-CONTENT-COOKIES"
7596 >filter{content-cookies}</A
7599 # These aliases define combinations of actions
7600 # that are useful for certain types of sites:
7603 HREF="actions-file.html#BLOCK"
7606 HREF="actions-file.html#FILTER"
7608 > -crunch-all-cookies -<A
7609 HREF="actions-file.html#FAST-REDIRECTS"
7612 HREF="actions-file.html#HIDE-REFERER"
7615 HREF="actions-file.html#KILL-POPUPS"
7618 shop = -crunch-all-cookies -<A
7619 HREF="actions-file.html#FILTER-ALL-POPUPS"
7620 >filter{all-popups}</A
7622 HREF="actions-file.html#KILL-POPUPS"
7630 > Now come the regular sections, i.e. sets of actions, accompanied
7631 by URL patterns to which they apply. Remember <SPAN
7636 are disabled when matching starts</I
7638 >, so we have to explicitly
7639 enable the ones we want.</P
7641 > The first regular section is probably the most important. It has only
7650 HREF="actions-file.html#AF-PATTERNS"
7651 >matches all URLs</A
7653 set of actions used in this <SPAN
7661 be applied to all requests as a start</I
7663 >. It can be partly or
7664 wholly overridden by later matches further down this file, or in user.action,
7665 but it will still be largely responsible for your overall browsing
7668 > Again, at the start of matching, all actions are disabled, so there is
7669 no need to disable any actions here. (Remember: a <SPAN
7673 preceding the action name enables the action, a <SPAN
7677 Also note how this long line has been made more readable by splitting it into
7678 multiple lines with line continuation.</P
7688 >##########################################################################
7689 # "Defaults" section:
7690 ##########################################################################
7693 HREF="actions-file.html#DEANIMATE-GIFS"
7697 HREF="actions-file.html#FILTER-HTML-ANNOYANCES"
7698 >filter{html-annoyances}</A
7701 HREF="actions-file.html#FILTER-REFRESH-TAGS"
7702 >filter{refresh-tags}</A
7705 HREF="actions-file.html#FILTER-WEBBUGS"
7709 HREF="actions-file.html#FILTER-IE-EXPLOITS"
7710 >filter{ie-exploits}</A
7713 HREF="actions-file.html#HIDE-FORWARDED-FOR-HEADERS"
7714 >hide-forwarded-for-headers</A
7717 HREF="actions-file.html#HIDE-FROM-HEADER"
7718 >hide-from-header{block}</A
7721 HREF="actions-file.html#HIDE-REFERER"
7722 >hide-referrer{forge}</A
7725 HREF="actions-file.html#PREVENT-COMPRESSION"
7726 >prevent-compression</A
7729 HREF="actions-file.html#SESSION-COOKIES-ONLY"
7730 >session-cookies-only</A
7733 HREF="actions-file.html#SET-IMAGE-BLOCKER"
7734 >set-image-blocker{pattern}</A
7737 / # forward slash will match *all* potential URL patterns.</PRE
7743 > The default behavior is now set.
7746 > The first of our specialized sections is concerned with <SPAN
7750 sites, i.e. sites that require minimum interference, because they are either
7751 very complex or very keen on tracking you (and have mechanisms in place that
7752 make them unusable for people who avoid being tracked). We will simply use
7756 > alias instead of stating the list
7757 of actions explicitly:</P
7767 >##########################################################################
7768 # Exceptions for sites that'll break under the default action set:
7769 ##########################################################################
7771 # "Fragile" Use a minimum set of actions for these sites (see alias above):
7774 .office.microsoft.com # surprise, surprise!
7775 .windowsupdate.microsoft.com
7776 mail.google.com</PRE
7782 > Shopping sites are not as fragile, but they typically
7783 require cookies to log in, and pop-up windows for shopping
7784 carts or item details. Again, we'll use a pre-defined alias:</P
7798 .worldpay.com # for quietpc.com
7809 HREF="actions-file.html#FAST-REDIRECTS"
7813 action, which we enabled per default above, breaks some sites. So disable
7814 it for popular sites where we know it misbehaves:</P
7825 HREF="actions-file.html#FAST-REDIRECTS"
7831 .altavista.com/.*(like|url|link):http
7832 .altavista.com/trans.*urltext=http
7839 > It is important that <SPAN
7843 URLs belong to images, so that <SPAN
7850 be blocked, a substitute image can be sent, rather than an HTML page.
7851 Contacting the remote site to find out is not an option, since it
7852 would destroy the loading time advantage of banner blocking, and it
7853 would feed the advertisers (in terms of money <SPAN
7860 information). We can mark any URL as an image with the <TT
7863 HREF="actions-file.html#HANDLE-AS-IMAGE"
7867 and marking all URLs that end in a known image file extension is a
7878 >##########################################################################
7880 ##########################################################################
7882 # Define which file types will be treated as images, in case they get
7883 # blocked further down this file:
7886 HREF="actions-file.html#HANDLE-AS-IMAGE"
7889 /.*\.(gif|jpe?g|png|bmp|ico)$</PRE
7895 > And then there are known banner sources. They often use scripts to
7896 generate the banners, so it won't be visible from the URL that the
7897 request is for an image. Hence we block them <SPAN
7904 mark them as images in one go, with the help of our
7907 >+block-as-image</TT
7908 > alias defined above. (We could of
7909 course just as well use <TT
7912 HREF="actions-file.html#BLOCK"
7916 HREF="actions-file.html#HANDLE-AS-IMAGE"
7920 Remember that the type of the replacement image is chosen by the
7924 HREF="actions-file.html#SET-IMAGE-BLOCKER"
7925 >set-image-blocker</A
7928 action. Since all URLs have matched the default section with its
7932 HREF="actions-file.html#SET-IMAGE-BLOCKER"
7933 >set-image-blocker</A
7936 action before, it still applies and needn't be repeated:</P
7946 ># Known ad generators:
7951 .ad.*.doubleclick.net
7952 .a.yimg.com/(?:(?!/i/).)*$
7953 .a[0-9].yimg.com/(?:(?!/i/).)*$
7961 > One of the most important jobs of <SPAN
7965 is to block banners. Many of these can be <SPAN
7972 HREF="actions-file.html#FILTER"
7974 >{banners-by-size}</TT
7976 action, which we enabled above, and which deletes the references to banner
7977 images from the pages while they are loaded, so the browser doesn't request
7978 them anymore, and hence they don't need to be blocked here. But this naturally
7979 doesn't catch all banners, and some people choose not to use filters, so we
7980 need a comprehensive list of patterns for banner URLs here, and apply the
7984 HREF="actions-file.html#BLOCK"
7987 > action to them.</P
7989 > First comes many generic patterns, which do most of the work, by
7990 matching typical domain and path name components of banners. Then comes
7991 a list of individual patterns for specific sites, which is omitted here
7992 to keep the example short:</P
8002 >##########################################################################
8003 # Block these fine banners:
8004 ##########################################################################
8006 HREF="actions-file.html#BLOCK"
8016 /.*count(er)?\.(pl|cgi|exe|dll|asp|php[34]?)
8017 /(?:.*/)?(publicite|werbung|rekla(ma|me|am)|annonse|maino(kset|nta|s)?)/
8019 # Site-specific patterns (abbreviated):
8027 > It's quite remarkable how many advertisers actually call their banner
8033 >.com, or call the directory
8034 in which the banners are stored simply <SPAN
8038 generic patterns are surprisingly effective.</P
8040 > But being very generic, they necessarily also catch URLs that we don't want
8041 to block. The pattern <TT
8053 >.nasty-corp.com"</SPAN
8063 >.sourcefroge.net"</SPAN
8073 >l.some-provider.net."</SPAN
8075 well-known exceptions to the <TT
8078 HREF="actions-file.html#BLOCK"
8084 > Note that these are exceptions to exceptions from the default! Consider the URL
8087 >"downloads.sourcefroge.net"</SPAN
8088 >: Initially, all actions are deactivated,
8089 so it wouldn't get blocked. Then comes the defaults section, which matches the
8090 URL, but just deactivates the <TT
8093 HREF="actions-file.html#BLOCK"
8097 action once again. Then it matches <TT
8100 >, an exception to the
8101 general non-blocking policy, and suddenly
8105 HREF="actions-file.html#BLOCK"
8108 > applies. And now, it'll match
8115 HREF="actions-file.html#BLOCK"
8119 applies, so (unless it matches <SPAN
8125 > further down) it ends up
8129 HREF="actions-file.html#BLOCK"
8132 > action applying.</P
8142 >##########################################################################
8143 # Save some innocent victims of the above generic block patterns:
8144 ##########################################################################
8149 HREF="actions-file.html#BLOCK"
8152 adv[io]*. # (for advogato.org and advice.*)
8153 adsl. # (has nothing to do with ads)
8154 adobe. # (has nothing to do with ads either)
8155 ad[ud]*. # (adult.* and add.*)
8156 .edu # (universities don't host banners (yet!))
8157 .*loads. # (downloads, uploads etc)
8165 www.globalintersec.com/adv # (adv = advanced)
8166 www.ugu.com/sui/ugu/adv</PRE
8172 > Filtering source code can have nasty side effects,
8173 so make an exception for our friends at sourceforge.net,
8174 and all paths with <SPAN
8177 > in them. Note that
8181 HREF="actions-file.html#FILTER"
8191 > filters in one fell swoop!</P
8201 ># Don't filter code!
8204 HREF="actions-file.html#FILTER"
8211 .sourceforge.net</PRE
8220 > is of course much more
8221 comprehensive, but we hope this example made clear how it works.</P
8229 >8.7.2. user.action</A
8232 > So far we are painting with a broad brush by setting general policies,
8233 which would be a reasonable starting point for many people. Now,
8234 you might want to be more specific and have customized rules that
8235 are more suitable to your personal habits and preferences. These would
8236 be for narrowly defined situations like your ISP or your bank, and should
8240 >, which is parsed after all other
8241 actions files and hence has the last word, over-riding any previously
8242 defined actions. <TT
8252 > place for your personal settings, since
8256 > is actively maintained by the
8260 > developers and you'll probably want
8261 to install updated versions from time to time.</P
8263 > So let's look at a few examples of things that one might typically do in
8277 ># My user.action file. <fred@example.com></PRE
8284 HREF="actions-file.html#ALIASES"
8286 > are local to the actions
8287 file that they are defined in, you can't use the ones from
8291 >, unless you repeat them here:</P
8301 ># Aliases are local to the file they are defined in.
8302 # (Re-)define aliases for this file:
8306 # These aliases just save typing later, and the alias names should
8307 # be self explanatory.
8309 +crunch-all-cookies = +crunch-incoming-cookies +crunch-outgoing-cookies
8310 -crunch-all-cookies = -crunch-incoming-cookies -crunch-outgoing-cookies
8311 allow-all-cookies = -crunch-all-cookies -session-cookies-only
8312 allow-popups = -filter{all-popups} -kill-popups
8313 +block-as-image = +block +handle-as-image
8314 -block-as-image = -block
8316 # These aliases define combinations of actions that are useful for
8317 # certain types of sites:
8319 fragile = -block -crunch-all-cookies -filter -fast-redirects -hide-referrer -kill-popups
8320 shop = -crunch-all-cookies allow-popups
8322 # Allow ads for selected useful free sites:
8324 allow-ads = -block -filter{banners-by-size} -filter{banners-by-link}
8326 # Alias for specific file types that are text, but might have conflicting
8327 # MIME types. We want the browser to force these to be text documents.
8328 handle-as-text = -<A
8329 HREF="actions-file.html#FILTER"
8332 HREF="actions-file.html#CONTENT-TYPE-OVERWRITE"
8333 >content-type-overwrite{text/plain}</A
8335 HREF="actions-file.html#FORCE-TEXT-MODE"
8338 HREF="actions-file.html#HIDE-CONTENT-DISPOSITION"
8339 >hide-content-disposition</A
8346 > Say you have accounts on some sites that you visit regularly, and
8347 you don't want to have to log in manually each time. So you'd like
8348 to allow persistent cookies for these sites. The
8351 >allow-all-cookies</TT
8352 > alias defined above does exactly
8353 that, i.e. it disables crunching of cookies in any direction, and the
8354 processing of cookies to make them only temporary.</P
8364 >{ allow-all-cookies }
8374 > Your bank is allergic to some filter, but you don't know which, so you disable them all:</P
8385 HREF="actions-file.html#FILTER"
8388 .your-home-banking-site.com</PRE
8394 > Some file types you may not want to filter for various reasons:</P
8404 ># Technical documentation is likely to contain strings that might
8405 # erroneously get altered by the JavaScript-oriented filters:
8410 # And this stupid host sends streaming video with a wrong MIME type,
8411 # so that Privoxy thinks it is getting HTML and starts filtering:
8413 stupid-server.example.com/</PRE
8419 > Example of a simple <A
8420 HREF="actions-file.html#BLOCK"
8422 > action. Say you've
8423 seen an ad on your favourite page on example.com that you want to get rid of.
8424 You have right-clicked the image, selected <SPAN
8426 >"copy image location"</SPAN
8428 and pasted the URL below while removing the leading http://, into a
8432 > section. Note that <TT
8436 > need not be specified, since all URLs ending in
8440 > will be tagged as images by the general rules as set
8441 in default.action anyway:</P
8452 HREF="actions-file.html#BLOCK"
8455 www.example.com/nasty-ads/sponsor\.gif
8456 another.example.net/more/junk/here/</PRE
8462 > The URLs of dynamically generated banners, especially from large banner
8463 farms, often don't use the well-known image file name extensions, which
8464 makes it impossible for <SPAN
8468 the file type just by looking at the URL.
8471 >+block-as-image</TT
8472 > alias defined above for
8474 Note that objects which match this rule but then turn out NOT to be an
8475 image are typically rendered as a <SPAN
8477 >"broken image"</SPAN
8479 browser. Use cautiously.</P
8489 >{ +block-as-image }
8499 > Now you noticed that the default configuration breaks Forbes Magazine,
8500 but you were too lazy to find out which action is the culprit, and you
8501 were again too lazy to give <A
8505 you just used the <TT
8508 > alias on the site, and
8515 > -- it worked. The <TT
8519 aliases disables those actions that are most likely to break a site. Also,
8520 good for testing purposes to see if it is <SPAN
8524 that is causing the problem or not. We later find other regular sites
8525 that misbehave, and add those to our personalized list of troublemakers:</P
8544 > You like the <SPAN
8547 > text replacements in <TT
8551 but it is disabled in the distributed actions file.
8552 So you'd like to turn it on in your private,
8553 update-safe config, once and for all:</P
8564 HREF="actions-file.html#FILTER-FUN"
8567 / # For ALL sites!</PRE
8573 > Note that the above is not really a good idea: There are exceptions
8574 to the filters in <TT
8578 really shouldn't be filtered, like code on CVS->Web interfaces. Since
8582 > has the last word, these exceptions
8583 won't be valid for the <SPAN
8586 > filtering specified here.</P
8588 > You might also worry about how your favourite free websites are
8589 funded, and find that they rely on displaying banner advertisements
8590 to survive. So you might want to specifically allow banners for those
8591 sites that you feel provide value to you:</P
8613 > has been aliased to
8617 HREF="actions-file.html#BLOCK"
8624 HREF="actions-file.html#FILTER-BANNERS-BY-SIZE"
8625 >filter{banners-by-size}</A
8631 HREF="actions-file.html#FILTER-BANNERS-BY-LINK"
8632 >filter{banners-by-link}</A
8636 > Invoke another alias here to force an over-ride of the MIME type <TT
8638 > application/x-sh</TT
8639 > which typically would open a download type
8640 dialog. In my case, I want to look at the shell script, and then I can save
8641 it should I choose to.</P
8661 > is generally the best place to define
8662 exceptions and additions to the default policies of
8666 >. Some actions are safe to have their
8667 default policies set here though. So let's set a default policy to have a
8671 > image as opposed to the checkerboard pattern for
8681 > of course matches all URL
8682 paths and patterns:</P
8693 HREF="actions-file.html#SET-IMAGE-BLOCKER"
8694 >set-image-blocker{blank}</A
8709 SUMMARY="Footer navigation table"
8738 HREF="filter-file.html"
8748 >The Main Configuration File</TD
projects / privoxy.git / blob