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.9 User Manual"
11 HREF="index.html"><LINK
13 TITLE="The Main Configuration File"
14 HREF="config.html"><LINK
17 HREF="filter-file.html"><LINK
20 HREF="../p_doc.css"><META
21 HTTP-EQUIV="Content-Type"
24 <LINK REL="STYLESHEET" TYPE="text/css" HREF="p_doc.css">
36 SUMMARY="Header navigation table"
45 >Privoxy 3.0.9 User Manual</TH
67 HREF="filter-file.html"
85 > The actions files are used to define what <SPAN
95 > takes for which URLs, and thus determines
96 how ad images, cookies and various other aspects of HTTP content and
97 transactions are handled, and on which sites (or even parts thereof).
98 There are a number of such actions, with a wide range of functionality.
99 Each action does something a little different.
100 These actions give us a veritable arsenal of tools with which to exert
101 our control, preferences and independence. Actions can be combined so that
102 their effects are aggregated when applied against a given set of URLs.</P
105 are three action files included with <SPAN
120 > - is the primary action file
121 that sets the initial values for all actions. It is intended to
122 provide a base level of functionality for
126 > array of features. So it is
127 a set of broad rules that should work reasonably well as-is for most users.
128 This is the file that the developers are keeping updated, and <A
129 HREF="installation.html#INSTALLATION-KEEPUPDATED"
130 >making available to users</A
132 The user's preferences as set in <TT
155 > - is intended to be for local site
156 preferences and exceptions. As an example, if your ISP or your bank
157 has specific requirements, and need special handling, this kind of
158 thing should go here. This file will not be upgraded.
166 > - is used only by the web based editor
168 HREF="http://config.privoxy.org/edit-actions-list?f=default"
170 > http://config.privoxy.org/edit-actions-list?f=default</A
172 to set various pre-defined sets of rules for the default actions section
184 >Set to Cautious</SPAN
190 >Set to Advanced</SPAN
194 > These have increasing levels of aggressiveness <SPAN
199 influence on your browsing unless you select them explicitly in the
202 >. A default installation should be pre-set to
206 > (versions prior to 3.0.5 were set to
210 >). New users should try this for a while before
211 adjusting the settings to more aggressive levels. The more aggressive
212 the settings, then the more likelihood there is of problems such as sites
213 not working as they should.
219 > button allows you to turn each
220 action on/off individually for fine-tuning. The <SPAN
224 button changes the actions list to low/safe settings which will activate
225 ad blocking and a minimal set of <SPAN
228 >'s features, and subsequently
229 there will be less of a chance for accidental problems. The
233 > button sets the list to a medium level of
234 other features and a low level set of privacy features. The
238 > button sets the list to a high level of
239 ad blocking and medium level of privacy. See the chart below. The latter
240 three buttons over-ride any changes via with the
244 > button. More fine-tuning can be done in the
245 lower sections of this internal page.
248 > It is not recommend to edit the <TT
255 > The default profiles, and their associated actions, as pre-defined in
269 >Table 1. Default Configurations</B
299 >Ad-blocking Aggressiveness</TD
309 >Ad-filtering by size</TD
319 >Ad-filtering by link</TD
339 >Privacy Features</TD
369 >GIF de-animation</TD
399 >JavaScript taming</TD
419 >Image tag reordering</TD
437 > The list of actions files to be used are defined in the main configuration
438 file, and are processed in the order they are defined (e.g.
442 > is typically processed before
446 >). The content of these can all be viewed and
448 HREF="http://config.privoxy.org/show-status"
450 >http://config.privoxy.org/show-status</A
452 The over-riding principle when applying actions, is that the last action that
453 matches a given URL wins. The broadest, most general rules go first
458 followed by any exceptions (typically also in
462 >), which are then followed lastly by any
463 local preferences (typically in <SPAN
479 > An actions file typically has multiple sections. If you want to use
483 > in an actions file, you have to place the (optional)
485 HREF="actions-file.html#ALIASES"
487 > at the top of that file.
488 Then comes the default set of rules which will apply universally to all
489 sites and pages (be <SPAN
499 > or any other actions file after
503 >, because it will override the result
504 from consulting any previous file). And then below that,
505 exceptions to the defined universal policies. You can regard
509 > as an appendix to <TT
513 with the advantage that it is a separate file, which makes preserving your
514 personal settings across <SPAN
517 > upgrades easier.</P
520 Actions can be used to block anything you want, including ads, banners, or
521 just some obnoxious URL whose content you would rather not see. Cookies can be accepted
522 or rejected, or accepted only during the current browser session (i.e. not
523 written to disk), content can be modified, some JavaScripts tamed, user-tracking
524 fooled, and much more. See below for a <A
525 HREF="actions-file.html#ACTIONS"
535 >8.1. Finding the Right Mix</A
539 HREF="actions-file.html#ACTIONS"
541 >, like cookie suppression
542 or script disabling, may render some sites unusable that rely on these
543 techniques to work properly. Finding the right mix of actions is not always easy and
544 certainly a matter of personal taste. And, things can always change, requiring
545 refinements in the configuration. In general, it can be said that the more
549 > your default settings (in the top section of the
550 actions file) are, the more exceptions for <SPAN
554 will have to make later. If, for example, you want to crunch all cookies per
555 default, you'll have to make exceptions from that rule for sites that you
556 regularly use and that require cookies for actually useful purposes, like maybe
557 your bank, favorite shop, or newspaper.</P
559 > We have tried to provide you with reasonable rules to start from in the
560 distribution actions files. But there is no general rule of thumb on these
561 things. There just are too many variables, and sites are constantly changing.
562 Sooner or later you will want to change the rules (and read this chapter again :).</P
573 > The easiest way to edit the actions files is with a browser by
574 using our browser-based editor, which can be reached from <A
575 HREF="http://config.privoxy.org/show-status"
577 >http://config.privoxy.org/show-status</A
579 Note: the config file option <A
580 HREF="config.html#ENABLE-EDIT-ACTIONS"
581 >enable-edit-actions</A
582 > must be enabled for
583 this to work. The editor allows both fine-grained control over every single
584 feature on a per-URL basis, and easy choosing from wholesale sets of defaults
595 >. Warning: the <SPAN
599 aggressive, and will be more likely to cause problems for some sites.
600 Experienced users only!
603 > If you prefer plain text editing to GUIs, you can of course also directly edit the
604 the actions files with your favorite text editor. Look at
608 > which is richly commented with many
617 >8.3. How Actions are Applied to Requests</A
620 > Actions files are divided into sections. There are special sections,
624 HREF="actions-file.html#ALIASES"
627 > sections which will
628 be discussed later. For now let's concentrate on regular sections: They have a
629 heading line (often split up to multiple lines for readability) which consist
630 of a list of actions, separated by whitespace and enclosed in curly braces.
631 Below that, there is a list of URL and tag patterns, each on a separate line.</P
633 > To determine which actions apply to a request, the URL of the request is
634 compared to all URL patterns in each <SPAN
638 Every time it matches, the list of applicable actions for the request is
639 incrementally updated, using the heading of the section in which the
640 pattern is located. The same is done again for tags and tag patterns later on.</P
642 > If multiple applying sections set the same action differently,
643 the last match wins. If not, the effects are aggregated.
644 E.g. a URL might match a regular section with a heading line of <TT
648 HREF="actions-file.html#HANDLE-AS-IMAGE"
652 then later another one with just <TT
656 HREF="actions-file.html#BLOCK"
666 > actions to apply. And there may well be
667 cases where you will want to combine actions together. Such a section then
685 # Block these as if they were images. Send no block page.
687 media.example.com/.*banners
688 .example.com/images/ads/</PRE
695 > You can trace this process for URL patterns and any given URL by visiting <A
696 HREF="http://config.privoxy.org/show-url-info"
698 >http://config.privoxy.org/show-url-info</A
701 > Examples and more detail on this is provided in the Appendix, <A
702 HREF="appendix.html#ACTIONSANAT"
703 > Troubleshooting: Anatomy of an Action</A
723 to determine what <SPAN
729 > might apply to which sites and
730 pages your browser attempts to access. These <SPAN
740 > matching to achieve a high degree of
741 flexibility. This allows one expression to be expanded and potentially match
742 against many similar patterns.</P
744 > Generally, an URL pattern has the form
747 ><domain>/<path></TT
751 ><domain></TT
756 optional. (This is why the special <TT
759 > pattern matches all
760 URLs). Note that the protocol portion of the URL pattern (e.g.
771 the pattern. This is assumed already!</P
773 > The pattern matching syntax is different for the domain and path parts of
774 the URL. The domain part uses a simple globbing type matching technique,
775 while the path part uses a more flexible
777 HREF="http://en.wikipedia.org/wiki/Regular_expressions"
782 Expressions (PCRE)"</SPAN
793 >www.example.com/</TT
797 > is a domain-only pattern and will match any request to <TT
801 regardless of which document on that server is requested. So ALL pages in
802 this domain would be covered by the scope of this action. Note that a
806 > is different and would NOT match.
816 > means exactly the same. For domain-only patterns, the trailing <TT
826 >www.example.com/index.html$</TT
830 > matches all the documents on <TT
834 whose name starts with <TT
843 >www.example.com/index.html$</TT
847 > matches only the single document <TT
864 > matches the document <TT
867 >, regardless of the domain,
874 > web server anywhere.
884 > matches nothing, since it would be interpreted as a domain name and
885 there is no top-level domain called <TT
900 >8.4.1. The Domain Pattern</A
903 > The matching of the domain part offers some flexible options: if the
904 domain starts or ends with a dot, it becomes unanchored at that end.
918 > matches any domain with first-level domain <TT
922 and second-level domain <TT
935 >foo.bar.baz.example.com</TT
937 Note that it wouldn't match if the second-level domain was <TT
950 > matches any domain that <SPAN
960 > (It also matches the domain
964 > but most of the time that doesn't matter.)
974 > matches any domain that <SPAN
984 And, by the way, also included would be any files or documents that exist
985 within that domain since no path limitations are specified. (Correctly
986 speaking: It matches any FQDN that contains <TT
990 a domain.) This might be <TT
1000 >www.example.net/cgi/testing.pl</TT
1001 > for instance. All these
1008 > Additionally, there are wild-cards that you can use in the domain names
1009 themselves. These work similarly to shell globbing type wild-cards:
1013 > represents zero or more arbitrary characters (this is
1016 HREF="http://en.wikipedia.org/wiki/Regular_expressions"
1023 > based syntax of <SPAN
1030 > represents any single character (this is equivalent to the
1031 regular expression syntax of a simple <SPAN
1034 >), and you can define
1037 >"character classes"</SPAN
1038 > in square brackets which is similar to
1039 the same regular expression technique. All of this can be freely mixed:</P
1043 CLASS="VARIABLELIST"
1048 >ad*.example.com</TT
1054 >"adserver.example.com"</SPAN
1058 >"ads.example.com"</SPAN
1059 >, etc but not <SPAN
1061 >"sfads.example.com"</SPAN
1068 >*ad*.example.com</TT
1072 > matches all of the above, and then some.
1088 >pictures.epix.com</TT
1091 >a.b.c.d.e.upix.com</TT
1098 >www[1-9a-ez].example.c*</TT
1104 >www1.example.com</TT
1108 >www4.example.cc</TT
1111 >wwwd.example.cy</TT
1115 >wwwz.example.com</TT
1125 >wwww.example.com</TT
1132 > While flexible, this is not the sophistication of full regular expression based syntax.</P
1140 >8.4.2. The Path Pattern</A
1146 > uses Perl compatible (PCRE)
1148 HREF="http://en.wikipedia.org/wiki/Regular_expressions"
1157 HREF="http://www.pcre.org/"
1161 matching the path portion (after the slash), and is thus more flexible.</P
1164 HREF="appendix.html#REGEX"
1166 > with a brief quick-start into regular
1167 expressions, and full (very technical) documentation on PCRE regex syntax is available on-line
1169 HREF="http://www.pcre.org/man.txt"
1171 >http://www.pcre.org/man.txt</A
1173 You might also find the Perl man page on regular expressions (<TT
1177 useful, which is available on-line at <A
1178 HREF="http://perldoc.perl.org/perlre.html"
1180 >http://perldoc.perl.org/perlre.html</A
1183 > Note that the path pattern is automatically left-anchored at the <SPAN
1187 i.e. it matches as if it would start with a <SPAN
1190 > (regular expression speak
1191 for the beginning of a line).</P
1193 > Please also note that matching in the path is <SPAN
1197 >CASE INSENSITIVE</I
1200 by default, but you can switch to case sensitive at any point in the pattern by using the
1206 >www.example.com/(?-i)PaTtErN.*</TT
1208 only documents whose path starts with <TT
1218 > this capitalization.</P
1222 CLASS="VARIABLELIST"
1227 >.example.com/.*</TT
1231 > Is equivalent to just <SPAN
1233 >".example.com"</SPAN
1234 >, since any documents
1235 within that domain are matched with or without the <SPAN
1239 regular expression. This is redundant
1245 >.example.com/.*/index.html$</TT
1249 > Will match any page in the domain of <SPAN
1251 >"example.com"</SPAN
1256 >, and that is part of some path. For
1257 example, it matches <SPAN
1259 >"www.example.com/testing/index.html"</SPAN
1263 >"www.example.com/index.html"</SPAN
1264 > because the regular
1265 expression called for at least two <SPAN
1269 requirement. It also would match
1272 >"www.example.com/testing/index_html"</SPAN
1274 special meta-character <SPAN
1283 >.example.com/(.*/)?index\.html$</TT
1287 > This regular expression is conditional so it will match any page
1291 > regardless of path which in this case can
1292 have one or more <SPAN
1295 >. And this one must contain exactly
1299 > (but does not have to end with that!).
1305 >.example.com/(.*/)(ads|banners?|junk)</TT
1309 > This regular expression will match any path of <SPAN
1311 >"example.com"</SPAN
1313 that contains any of the words <SPAN
1323 > (because of the <SPAN
1330 The path does not have to end in these words, just contain them.
1336 >.example.com/(.*/)(ads|banners?|junk)/.*\.(jpe?g|gif|png)$</TT
1340 > This is very much the same as above, except now it must end in either
1354 one is limited to common image formats.
1360 > There are many, many good examples to be found in <TT
1364 and more tutorials below in <A
1365 HREF="appendix.html#REGEX"
1366 >Appendix on regular expressions</A
1375 >8.4.3. The Tag Pattern</A
1378 > Tag patterns are used to change the applying actions based on the
1379 request's tags. Tags can be created with either the
1381 HREF="actions-file.html#CLIENT-HEADER-TAGGER"
1382 >client-header-tagger</A
1385 HREF="actions-file.html#SERVER-HEADER-TAGGER"
1386 >server-header-tagger</A
1389 > Tag patterns have to start with <SPAN
1396 can tell them apart from URL patterns. Everything after the colon
1397 including white space, is interpreted as a regular expression with
1398 path pattern syntax, except that tag patterns aren't left-anchored
1399 automatically (<SPAN
1402 > doesn't silently add a <SPAN
1406 you have to do it yourself if you need it).</P
1408 > To match all requests that are tagged with <SPAN
1412 your pattern line should be <SPAN
1419 > would work as well, but it would also
1420 match requests whose tags contain <SPAN
1427 > wouldn't work as it requires white space.</P
1429 > Sections can contain URL and tag patterns at the same time,
1430 but tag patterns are checked after the URL patterns and thus
1431 always overrule them, even if they are located before the URL patterns.</P
1433 > Once a new tag is added, Privoxy checks right away if it's matched by one
1434 of the tag patterns and updates the action settings accordingly. As a result
1435 tags can be used to activate other tagger actions, as long as these other
1436 taggers look for headers that haven't already be parsed.</P
1438 > For example you could tag client requests which use the
1443 then use this tag to activate another tagger that adds a tag if cookies
1444 are sent, and then use a block action based on the cookie tag. This allows
1445 the outcome of one action, to be input into a subsequent action. However if
1446 you'd reverse the position of the described taggers, and activated the
1447 method tagger based on the cookie tagger, no method tags would be created.
1448 The method tagger would look for the request line, but at the time
1449 the cookie tag is created, the request line has already been parsed.</P
1451 > While this is a limitation you should be aware of, this kind of
1452 indirection is seldom needed anyway and even the example doesn't
1453 make too much sense.</P
1465 > All actions are disabled by default, until they are explicitly enabled
1466 somewhere in an actions file. Actions are turned on if preceded with a
1470 >, and turned off if preceded with a <SPAN
1479 >"do that action"</SPAN
1486 >"please block URLs that match the
1487 following patterns"</SPAN
1494 block URLs that match the following patterns, even if <TT
1498 previously applied."</SPAN
1502 Again, actions are invoked by placing them on a line, enclosed in curly braces and
1503 separated by whitespace, like in
1506 >{+some-action -some-other-action{some-parameter}}</TT
1508 followed by a list of URL patterns, one per line, to which they apply.
1509 Together, the actions line and the following pattern lines make up a section
1510 of the actions file. </P
1513 Actions fall into three categories:</P
1521 Boolean, i.e the action can only be <SPAN
1544 > # enable action <TT
1555 > # disable action <TT
1577 Parameterized, where some value is required in order to enable this type of action.
1599 >} # enable action and set parameter to <TT
1605 # overwriting parameter from previous match if necessary
1611 > # disable action. The parameter can be omitted</PRE
1618 > Note that if the URL matches multiple positive forms of a parameterized action,
1619 the last match wins, i.e. the params from earlier matches are simply ignored.
1625 >+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
1632 Multi-value. These look exactly like parameterized actions,
1633 but they behave differently: If the action applies multiple times to the
1634 same URL, but with different parameters, <SPAN
1647 > matches are remembered. This is used for actions
1648 that can be executed for the same request repeatedly, like adding multiple
1649 headers, or filtering through multiple filters. Syntax:
1670 >} # enable action and add <TT
1675 > to the list of parameters
1686 >} # remove the parameter <TT
1691 > from the list of parameters
1692 # If it was the last one left, disable the action.
1698 > # disable this action completely and remove all parameters from the list</PRE
1708 >+add-header{X-Fun-Header: Some text}</TT
1712 >+filter{html-annoyances}</TT
1719 > If nothing is specified in any actions file, no <SPAN
1723 taken. So in this case <SPAN
1727 normal, non-blocking, non-filtering proxy. You must specifically enable the
1728 privacy and blocking features you need (although the provided default actions
1729 files will give a good starting point).</P
1731 > Later defined action sections always over-ride earlier ones of the same type.
1732 So exceptions to any rules you make, should come in the latter part of the file (or
1733 in a file that is processed later when using multiple actions files such
1737 >). For multi-valued actions, the actions
1738 are applied in the order they are specified. Actions files are processed in
1739 the order they are defined in <TT
1743 installation has three actions files). It also quite possible for any given
1744 URL to match more than one <SPAN
1747 > (because of wildcards and
1748 regular expressions), and thus to trigger more than one set of actions! Last
1751 > The list of valid <SPAN
1761 >8.5.1. add-header</A
1766 CLASS="VARIABLELIST"
1772 >Confuse log analysis, custom applications</P
1778 > Sends a user defined HTTP header to the web server.
1791 > Any string value is possible. Validity of the defined HTTP headers is not checked.
1792 It is recommended that you use the <SPAN
1806 > This action may be specified multiple times, in order to define multiple
1807 headers. This is rarely needed for the typical user. If you don't know what
1810 >"HTTP headers"</SPAN
1811 > are, you definitely don't need to worry about this
1827 >+add-header{X-User-Tracking: sucks}</PRE
1848 CLASS="VARIABLELIST"
1854 >Block ads or other unwanted content</P
1860 > Requests for URLs to which this action applies are blocked, i.e. the
1861 requests are trapped by <SPAN
1864 > and the requested URL is never retrieved,
1865 but is answered locally with a substitute page or image, as determined by
1869 HREF="actions-file.html#HANDLE-AS-IMAGE"
1876 HREF="actions-file.html#SET-IMAGE-BLOCKER"
1877 >set-image-blocker</A
1883 HREF="actions-file.html#HANDLE-AS-EMPTY-DOCUMENT"
1884 >handle-as-empty-document</A
1909 > sends a special <SPAN
1913 for requests to blocked pages. This page contains links to find out why the request
1914 was blocked, and a click-through to the blocked content (the latter only if compiled with the
1915 force feature enabled). The <SPAN
1918 > page adapts to the available
1919 screen space -- it displays full-blown if space allows, or miniaturized and text-only
1920 if loaded into a small frame or window. If you are using <SPAN
1924 right now, you can take a look at the
1926 HREF="http://ads.bannerserver.example.com/nasty-ads/sponsor.html"
1937 A very important exception occurs if <SPAN
1950 HREF="actions-file.html#HANDLE-AS-IMAGE"
1954 apply to the same request: it will then be replaced by an image. If
1958 HREF="actions-file.html#SET-IMAGE-BLOCKER"
1959 >set-image-blocker</A
1962 (see below) also applies, the type of image will be determined by its parameter,
1963 if not, the standard checkerboard pattern is sent.
1966 > It is important to understand this process, in order
1967 to understand how <SPAN
1971 ads and other unwanted content. Blocking is a core feature, and one
1972 upon which various other features depend.
1978 HREF="actions-file.html#FILTER"
1982 action can perform a very similar task, by <SPAN
1986 banner images and other content through rewriting the relevant URLs in the
1987 document's HTML source, so they don't get requested in the first place.
1988 Note that this is a totally different technique, and it's easy to confuse the two.
1992 >Example usage (section):</DT
2004 # Block and replace with "blocked" page
2005 .nasty-stuff.example.com
2007 {+block +handle-as-image}
2008 # Block and replace with image
2012 {+block +handle-as-empty-document}
2013 # Block and then ignore
2014 adserver.exampleclick.net/.*\.js$</PRE
2029 NAME="CLIENT-HEADER-FILTER"
2030 >8.5.3. client-header-filter</A
2035 CLASS="VARIABLELIST"
2041 > Rewrite or remove single client headers.
2048 > All client headers to which this action applies are filtered on-the-fly through
2049 the specified regular expression based substitutions.
2062 > The name of a client-header filter, as defined in one of the
2064 HREF="filter-file.html"
2073 > Client-header filters are applied to each header on its own, not to
2074 all at once. This makes it easier to diagnose problems, but on the downside
2075 you can't write filters that only change header x if header y's value is z.
2076 You can do that by using tags though.
2079 > Client-header filters are executed after the other header actions have finished
2080 and use their output as input.
2083 > If the request URL gets changed, <SPAN
2086 > will detect that and use the new
2087 one. This can be used to rewrite the request destination behind the client's
2088 back, for example to specify a Tor exit relay for certain requests.
2091 > Please refer to the <A
2092 HREF="filter-file.html"
2093 >filter file chapter</A
2095 to learn which client-header filters are available by default, and how to
2100 >Example usage (section):</DT
2111 ># Hide Tor exit notation in Host and Referer Headers
2112 {+client-header-filter{hide-tor-exit-notation}}
2129 NAME="CLIENT-HEADER-TAGGER"
2130 >8.5.4. client-header-tagger</A
2135 CLASS="VARIABLELIST"
2141 > Block requests based on their headers.
2148 > Client headers to which this action applies are filtered on-the-fly through
2149 the specified regular expression based substitutions, the result is used as
2163 > The name of a client-header tagger, as defined in one of the
2165 HREF="filter-file.html"
2174 > Client-header taggers are applied to each header on its own,
2175 and as the header isn't modified, each tagger <SPAN
2182 > Client-header taggers are the first actions that are executed
2183 and their tags can be used to control every other action.
2187 >Example usage (section):</DT
2198 ># Tag every request with the User-Agent header
2199 {+client-header-tagger{user-agent}}
2216 NAME="CONTENT-TYPE-OVERWRITE"
2217 >8.5.5. content-type-overwrite</A
2222 CLASS="VARIABLELIST"
2228 >Stop useless download menus from popping up, or change the browser's rendering mode</P
2234 > Replaces the <SPAN
2236 >"Content-Type:"</SPAN
2237 > HTTP server header.
2259 >"Content-Type:"</SPAN
2260 > HTTP server header is used by the
2261 browser to decide what to do with the document. The value of this
2262 header can cause the browser to open a download menu instead of
2263 displaying the document by itself, even if the document's format is
2264 supported by the browser.
2267 > The declared content type can also affect which rendering mode
2268 the browser chooses. If XHTML is delivered as <SPAN
2272 many browsers treat it as yet another broken HTML document.
2273 If it is send as <SPAN
2275 >"application/xml"</SPAN
2277 XHTML support will only display it, if the syntax is correct.
2280 > If you see a web site that proudly uses XHTML buttons, but sets
2283 >"Content-Type: text/html"</SPAN
2284 >, you can use <SPAN
2288 to overwrite it with <SPAN
2290 >"application/xml"</SPAN
2292 the web master's claim inside your XHTML-supporting browser.
2293 If the syntax is incorrect, the browser will complain loudly.
2296 > You can also go the opposite direction: if your browser prints
2297 error messages instead of rendering a document falsely declared
2298 as XHTML, you can overwrite the content type with
2302 > and have it rendered as broken HTML document.
2307 >content-type-overwrite</TT
2311 >"Content-Type:"</SPAN
2312 > headers that look like some kind of text.
2313 If you want to overwrite it unconditionally, you have to combine it with
2317 HREF="actions-file.html#FORCE-TEXT-MODE"
2321 This limitation exists for a reason, think twice before circumventing it.
2324 > Most of the time it's easier to replace this action with a custom
2328 HREF="actions-file.html#SERVER-HEADER-FILTER"
2329 >server-header filter</A
2332 It allows you to activate it for every document of a certain site and it will still
2333 only replace the content types you aimed at.
2336 > Of course you can apply <TT
2338 >content-type-overwrite</TT
2340 to a whole site and then make URL based exceptions, but it's a lot
2341 more work to get the same precision.
2345 >Example usage (sections):</DT
2356 ># Check if www.example.net/ really uses valid XHTML
2357 { +content-type-overwrite{application/xml} }
2360 # but leave the content type unmodified if the URL looks like a style sheet
2361 {-content-type-overwrite}
2362 www.example.net/.*\.css$
2363 www.example.net/.*style</PRE
2378 NAME="CRUNCH-CLIENT-HEADER"
2379 >8.5.6. crunch-client-header</A
2384 CLASS="VARIABLELIST"
2390 >Remove a client header <SPAN
2393 > has no dedicated action for.</P
2399 > Deletes every header sent by the client that contains the string the user supplied as parameter.
2419 > This action allows you to block client headers for which no dedicated
2427 > will remove every client header that
2428 contains the string you supplied as parameter.
2431 > Regular expressions are <SPAN
2438 use this action to block different headers in the same request, unless
2439 they contain the same string.
2444 >crunch-client-header</TT
2445 > is only meant for quick tests.
2446 If you have to block several different headers, or only want to modify
2447 parts of them, you should use a
2451 HREF="actions-file.html#CLIENT-HEADER-FILTER"
2452 >client-header filter</A
2475 > Don't block any header without understanding the consequences.
2483 >Example usage (section):</DT
2494 ># Block the non-existent "Privacy-Violation:" client header
2495 { +crunch-client-header{Privacy-Violation:} }
2512 NAME="CRUNCH-IF-NONE-MATCH"
2513 >8.5.7. crunch-if-none-match</A
2518 CLASS="VARIABLELIST"
2524 >Prevent yet another way to track the user's steps between sessions.</P
2532 >"If-None-Match:"</SPAN
2533 > HTTP client header.
2553 > Removing the <SPAN
2555 >"If-None-Match:"</SPAN
2556 > HTTP client header
2557 is useful for filter testing, where you want to force a real
2558 reload instead of getting status code <SPAN
2562 would cause the browser to use a cached copy of the page.
2565 > It is also useful to make sure the header isn't used as a cookie
2566 replacement (unlikely but possible).
2569 > Blocking the <SPAN
2571 >"If-None-Match:"</SPAN
2572 > header shouldn't cause any
2573 caching problems, as long as the <SPAN
2575 >"If-Modified-Since:"</SPAN
2577 isn't blocked or missing as well.
2580 > It is recommended to use this action together with
2584 HREF="actions-file.html#HIDE-IF-MODIFIED-SINCE"
2585 >hide-if-modified-since</A
2592 HREF="actions-file.html#OVERWRITE-LAST-MODIFIED"
2593 >overwrite-last-modified</A
2599 >Example usage (section):</DT
2610 ># Let the browser revalidate cached documents but don't
2611 # allow the server to use the revalidation headers for user tracking.
2612 {+hide-if-modified-since{-60} \
2613 +overwrite-last-modified{randomize} \
2614 +crunch-if-none-match}
2630 NAME="CRUNCH-INCOMING-COOKIES"
2631 >8.5.8. crunch-incoming-cookies</A
2636 CLASS="VARIABLELIST"
2642 > Prevent the web server from setting HTTP cookies on your system
2651 >"Set-Cookie:"</SPAN
2652 > HTTP headers from server replies.
2672 > This action is only concerned with <SPAN
2689 HREF="actions-file.html#CRUNCH-OUTGOING-COOKIES"
2690 >crunch-outgoing-cookies</A
2699 > to disable HTTP cookies completely.
2708 > to use this action in conjunction
2712 HREF="actions-file.html#SESSION-COOKIES-ONLY"
2713 >session-cookies-only</A
2716 since it would prevent the session cookies from being set. See also
2720 HREF="actions-file.html#FILTER-CONTENT-COOKIES"
2721 >filter-content-cookies</A
2738 >+crunch-incoming-cookies</PRE
2753 NAME="CRUNCH-SERVER-HEADER"
2754 >8.5.9. crunch-server-header</A
2759 CLASS="VARIABLELIST"
2765 >Remove a server header <SPAN
2768 > has no dedicated action for.</P
2774 > Deletes every header sent by the server that contains the string the user supplied as parameter.
2794 > This action allows you to block server headers for which no dedicated
2798 > action exists. <SPAN
2802 will remove every server header that contains the string you supplied as parameter.
2805 > Regular expressions are <SPAN
2812 use this action to block different headers in the same request, unless
2813 they contain the same string.
2818 >crunch-server-header</TT
2819 > is only meant for quick tests.
2820 If you have to block several different headers, or only want to modify
2821 parts of them, you should use a custom
2825 HREF="actions-file.html#SERVER-HEADER-FILTER"
2826 >server-header filter</A
2849 > Don't block any header without understanding the consequences.
2857 >Example usage (section):</DT
2868 ># Crunch server headers that try to prevent caching
2869 { +crunch-server-header{no-cache} }
2885 NAME="CRUNCH-OUTGOING-COOKIES"
2886 >8.5.10. crunch-outgoing-cookies</A
2891 CLASS="VARIABLELIST"
2897 > Prevent the web server from reading any HTTP cookies from your system
2907 > HTTP headers from client requests.
2927 > This action is only concerned with <SPAN
2944 HREF="actions-file.html#CRUNCH-INCOMING-COOKIES"
2945 >crunch-incoming-cookies</A
2954 > to disable HTTP cookies completely.
2963 > to use this action in conjunction
2967 HREF="actions-file.html#SESSION-COOKIES-ONLY"
2968 >session-cookies-only</A
2971 since it would prevent the session cookies from being read.
2986 >+crunch-outgoing-cookies</PRE
3001 NAME="DEANIMATE-GIFS"
3002 >8.5.11. deanimate-gifs</A
3007 CLASS="VARIABLELIST"
3013 >Stop those annoying, distracting animated GIF images.</P
3019 > De-animate GIF animations, i.e. reduce them to their first or last image.
3045 > This will also shrink the images considerably (in bytes, not pixels!). If
3049 > is given, the first frame of the animation
3050 is used as the replacement. If <SPAN
3053 > is given, the last
3054 frame of the animation is used instead, which probably makes more sense for
3055 most banner animations, but also has the risk of not showing the entire
3056 last frame (if it is only a delta to an earlier frame).
3059 > You can safely use this action with patterns that will also match non-GIF
3060 objects, because no attempt will be made at anything that doesn't look like
3076 >+deanimate-gifs{last}</PRE
3091 NAME="DOWNGRADE-HTTP-VERSION"
3092 >8.5.12. downgrade-http-version</A
3097 CLASS="VARIABLELIST"
3103 >Work around (very rare) problems with HTTP/1.1</P
3109 > Downgrades HTTP/1.1 client requests and server replies to HTTP/1.0.
3129 > This is a left-over from the time when <SPAN
3133 didn't support important HTTP/1.1 features well. It is left here for the
3134 unlikely case that you experience HTTP/1.1 related problems with some server
3135 out there. Not all HTTP/1.1 features and requirements are supported yet,
3136 so there is a chance you might need this action.
3140 >Example usage (section):</DT
3151 >{+downgrade-http-version}
3152 problem-host.example.com</PRE
3167 NAME="FAST-REDIRECTS"
3168 >8.5.13. fast-redirects</A
3173 CLASS="VARIABLELIST"
3179 >Fool some click-tracking scripts and speed up indirect links.</P
3185 > Detects redirection URLs and redirects the browser without contacting
3186 the redirection server first.
3205 >"simple-check"</SPAN
3206 > to just search for the string <SPAN
3210 to detect redirection URLs.
3217 >"check-decoded-url"</SPAN
3218 > to decode URLs (if necessary) before searching
3219 for redirection URLs.
3229 Many sites, like yahoo.com, don't just link to other sites. Instead, they
3230 will link to some script on their own servers, giving the destination as a
3231 parameter, which will then redirect you to the final target. URLs
3232 resulting from this scheme typically look like:
3235 >"http://www.example.org/click-tracker.cgi?target=http%3a//www.example.net/"</SPAN
3239 > Sometimes, there are even multiple consecutive redirects encoded in the
3240 URL. These redirections via scripts make your web browsing more traceable,
3241 since the server from which you follow such a link can see where you go
3242 to. Apart from that, valuable bandwidth and time is wasted, while your
3243 browser asks the server for one redirect after the other. Plus, it feeds
3247 > This feature is currently not very smart and is scheduled for improvement.
3248 If it is enabled by default, you will have to create some exceptions to
3249 this action. It can lead to failures in several ways:
3252 > Not every URLs with other URLs as parameters is evil.
3253 Some sites offer a real service that requires this information to work.
3254 For example a validation service needs to know, which document to validate.
3258 > assumes that every URL parameter that
3259 looks like another URL is a redirection target, and will always redirect to
3260 the last one. Most of the time the assumption is correct, but if it isn't,
3261 the user gets redirected anyway.
3264 > Another failure occurs if the URL contains other parameters after the URL parameter.
3268 >"http://www.example.org/?redirect=http%3a//www.example.net/&foo=bar"</SPAN
3270 contains the redirection URL <SPAN
3272 >"http://www.example.net/"</SPAN
3274 followed by another parameter. <TT
3278 and will cause a redirect to <SPAN
3280 >"http://www.example.net/&foo=bar"</SPAN
3282 Depending on the target server configuration, the parameter will be silently ignored
3285 >"page not found"</SPAN
3286 > error. You can prevent this problem by
3290 HREF="actions-file.html#REDIRECT"
3294 to remove the last part of the URL, but it requires a little effort.
3297 > To detect a redirection URL, <TT
3301 looks for the string <SPAN
3304 >, either in plain text
3305 (invalid but often used) or encoded as <SPAN
3309 Some sites use their own URL encoding scheme, encrypt the address
3310 of the target server or replace it with a database id. In theses cases
3314 > is fooled and the request reaches the
3315 redirection server where it probably gets logged.
3330 > { +fast-redirects{simple-check} }
3333 { +fast-redirects{check-decoded-url} }
3334 another.example.com/testing</PRE
3355 CLASS="VARIABLELIST"
3361 >Get rid of HTML and JavaScript annoyances, banner advertisements (by size),
3362 do fun text replacements, add personalized effects, etc.</P
3368 > All instances of text-based type, most notably HTML and JavaScript, to which
3369 this action applies, can be filtered on-the-fly through the specified regular
3370 expression based substitutions. (Note: as of version 3.0.3 plain text documents
3371 are exempted from filtering, because web servers often use the
3375 > MIME type for all files whose type they don't know.)
3388 > The name of a content filter, as defined in the <A
3389 HREF="filter-file.html"
3392 Filters can be defined in one or more files as defined by the
3396 HREF="config.html#FILTERFILE"
3407 > is the collection of filters
3408 supplied by the developers. Locally defined filters should go
3409 in their own file, such as <TT
3415 > When used in its negative form,
3416 and without parameters, <SPAN
3422 > filtering is completely disabled.
3429 > For your convenience, there are a number of pre-defined filters available
3430 in the distribution filter file that you can use. See the examples below for
3434 > Filtering requires buffering the page content, which may appear to
3435 slow down page rendering since nothing is displayed until all content has
3436 passed the filters. (It does not really take longer, but seems that way
3437 since the page is not incrementally displayed.) This effect will be more
3438 noticeable on slower connections.
3443 >"Rolling your own"</SPAN
3445 filters requires a knowledge of
3447 HREF="http://en.wikipedia.org/wiki/Regular_expressions"
3456 HREF="http://en.wikipedia.org/wiki/Html"
3463 This is very powerful feature, and potentially very intrusive.
3464 Filters should be used with caution, and where an equivalent
3471 > The amount of data that can be filtered is limited to the
3475 HREF="config.html#BUFFER-LIMIT"
3479 option in the main <A
3483 default is 4096 KB (4 Megs). Once this limit is exceeded, the buffered
3484 data, and all pending data, is passed through unfiltered.
3487 > Inappropriate MIME types, such as zipped files, are not filtered at all.
3488 (Again, only text-based types except plain text). Encrypted SSL data
3489 (from HTTPS servers) cannot be filtered either, since this would violate
3490 the integrity of the secure transaction. In some situations it might
3491 be necessary to protect certain text, like source code, from filtering
3492 by defining appropriate <TT
3498 > Compressed content can't be filtered either, unless <SPAN
3502 is compiled with zlib support (requires at least <SPAN
3509 > will decompress the content before filtering
3513 > If you use a <SPAN
3516 > version without zlib support, but want filtering to work on
3517 as much documents as possible, even those that would normally be sent compressed,
3518 you must use the <TT
3521 HREF="actions-file.html#PREVENT-COMPRESSION"
3522 >prevent-compression</A
3525 action in conjunction with <TT
3531 > Content filtering can achieve some of the same effects as the
3535 HREF="actions-file.html#BLOCK"
3539 action, i.e. it can be used to block ads and banners. But the mechanism
3540 works quite differently. One effective use, is to block ad banners
3541 based on their size (see below), since many of these seem to be somewhat
3548 > with suggestions for new or
3549 improved filters is particularly welcome!
3552 > The below list has only the names and a one-line description of each
3553 predefined filter. There are <A
3554 HREF="filter-file.html#PREDEFINED-FILTERS"
3556 verbose explanations</A
3557 > of what these filters do in the <A
3558 HREF="filter-file.html"
3559 >filter file chapter</A
3564 >Example usage (with filters from the distribution <TT
3569 HREF="filter-file.html#PREDEFINED-FILTERS"
3570 >the Predefined Filters section</A
3572 more explanation on each:</DT
3576 NAME="FILTER-JS-ANNOYANCES"
3587 >+filter{js-annoyances} # Get rid of particularly annoying JavaScript abuse</PRE
3595 NAME="FILTER-JS-EVENTS"
3606 >+filter{js-events} # Kill all JS event bindings (Radically destructive! Only for extra nasty sites)</PRE
3614 NAME="FILTER-HTML-ANNOYANCES"
3625 >+filter{html-annoyances} # Get rid of particularly annoying HTML abuse</PRE
3633 NAME="FILTER-CONTENT-COOKIES"
3644 >+filter{content-cookies} # Kill cookies that come in the HTML or JS content</PRE
3652 NAME="FILTER-REFRESH-TAGS"
3663 >+filter{refresh-tags} # Kill automatic refresh tags (for dial-on-demand setups)</PRE
3671 NAME="FILTER-UNSOLICITED-POPUPS"
3682 >+filter{unsolicited-popups} # Disable only unsolicited pop-up windows. Useful if your browser lacks this ability.</PRE
3690 NAME="FILTER-ALL-POPUPS"
3701 >+filter{all-popups} # Kill all popups in JavaScript and HTML. Useful if your browser lacks this ability.</PRE
3709 NAME="FILTER-IMG-REORDER"
3720 >+filter{img-reorder} # Reorder attributes in <img> tags to make the banners-by-* filters more effective</PRE
3728 NAME="FILTER-BANNERS-BY-SIZE"
3739 >+filter{banners-by-size} # Kill banners by size</PRE
3747 NAME="FILTER-BANNERS-BY-LINK"
3758 >+filter{banners-by-link} # Kill banners by their links to known clicktrackers</PRE
3766 NAME="FILTER-WEBBUGS"
3777 >+filter{webbugs} # Squish WebBugs (1x1 invisible GIFs used for user tracking)</PRE
3785 NAME="FILTER-TINY-TEXTFORMS"
3796 >+filter{tiny-textforms} # Extend those tiny textareas up to 40x80 and kill the hard wrap</PRE
3804 NAME="FILTER-JUMPING-WINDOWS"
3815 >+filter{jumping-windows} # Prevent windows from resizing and moving themselves</PRE
3823 NAME="FILTER-FRAMESET-BORDERS"
3834 >+filter{frameset-borders} # Give frames a border and make them resizeable</PRE
3842 NAME="FILTER-DEMORONIZER"
3853 >+filter{demoronizer} # Fix MS's non-standard use of standard charsets</PRE
3861 NAME="FILTER-SHOCKWAVE-FLASH"
3872 >+filter{shockwave-flash} # Kill embedded Shockwave Flash objects</PRE
3880 NAME="FILTER-QUICKTIME-KIOSKMODE"
3891 >+filter{quicktime-kioskmode} # Make Quicktime movies savable</PRE
3910 >+filter{fun} # Text replacements for subversive browsing fun!</PRE
3918 NAME="FILTER-CRUDE-PARENTAL"
3929 >+filter{crude-parental} # Crude parental filtering (demo only)</PRE
3937 NAME="FILTER-IE-EXPLOITS"
3948 >+filter{ie-exploits} # Disable a known Internet Explorer bug exploits</PRE
3956 NAME="FILTER-SITE-SPECIFICS"
3967 >+filter{site-specifics} # Custom filters for specific site related problems</PRE
3975 NAME="FILTER-GOOGLE"
3986 >+filter{google} # Removes text ads and other Google specific improvements</PRE
4005 >+filter{yahoo} # Removes text ads and other Yahoo specific improvements</PRE
4024 >+filter{msn} # Removes text ads and other MSN specific improvements</PRE
4032 NAME="FILTER-BLOGSPOT"
4043 >+filter{blogspot} # Cleans up Blogspot blogs</PRE
4051 NAME="FILTER-NO-PING"
4062 >+filter{no-ping} # Removes non-standard ping attributes from anchor and area tags</PRE
4077 NAME="FORCE-TEXT-MODE"
4078 >8.5.15. force-text-mode</A
4083 CLASS="VARIABLELIST"
4092 > to treat a document as if it was in some kind of <SPAN
4104 > Declares a document as text, even if the <SPAN
4106 >"Content-Type:"</SPAN
4107 > isn't detected as such.
4130 HREF="actions-file.html#FILTER"
4137 > tries to only filter files that are
4138 in some kind of text format. The same restrictions apply to
4142 HREF="actions-file.html#CONTENT-TYPE-OVERWRITE"
4143 >content-type-overwrite</A
4148 >force-text-mode</TT
4149 > declares a document as text,
4150 without looking at the <SPAN
4152 >"Content-Type:"</SPAN
4174 > Think twice before activating this action. Filtering binary data
4175 with regular expressions can cause file damage.
4210 NAME="FORWARD-OVERRIDE"
4211 >8.5.16. forward-override</A
4216 CLASS="VARIABLELIST"
4222 >Change the forwarding settings based on User-Agent or request origin</P
4228 > Overrules the forward directives in the configuration file.
4248 > to use a direct connection without any additional proxies.</P
4254 >"forward 127.0.0.1:8123"</SPAN
4255 > to use the HTTP proxy listening at 127.0.0.1 port 8123.
4262 >"forward-socks4a 127.0.0.1:9050 ."</SPAN
4263 > to use the socks4a proxy listening at
4264 127.0.0.1 port 9050. Replace <SPAN
4266 >"forward-socks4a"</SPAN
4269 >"forward-socks4"</SPAN
4271 to use a socks4 connection (with local DNS resolution) instead, use <SPAN
4273 >"forward-socks5"</SPAN
4275 for socks5 connections (with remote DNS resolution).
4282 >"forward-socks4a 127.0.0.1:9050 proxy.example.org:8000"</SPAN
4283 > to use the socks4a proxy
4284 listening at 127.0.0.1 port 9050 to reach the HTTP proxy listening at proxy.example.org port 8000.
4287 >"forward-socks4a"</SPAN
4290 >"forward-socks4"</SPAN
4291 > to use a socks4 connection
4292 (with local DNS resolution) instead, use <SPAN
4294 >"forward-socks5"</SPAN
4296 for socks5 connections (with remote DNS resolution).
4305 > This action takes parameters similar to the
4307 HREF="config.html#FORWARDING"
4309 > directives in the configuration
4310 file, but without the URL pattern. It can be used as replacement, but normally it's only
4311 used in cases where matching based on the request URL isn't sufficient.
4332 > Please read the description for the <A
4333 HREF="config.html#FORWARDING"
4336 using this action. Forwarding to the wrong people will reduce your privacy and increase the
4337 chances of man-in-the-middle attacks.
4340 > If the ports are missing or invalid, default values will be used. This might change
4341 in the future and you shouldn't rely on it. Otherwise incorrect syntax causes Privoxy
4346 HREF="http://config.privoxy.org/show-url-info"
4348 >show-url-info CGI page</A
4350 to verify that your forward settings do what you thought the do.
4369 ># Always use direct connections for requests previously tagged as
4372 >"User-Agent: fetch libfetch/2.0"</SPAN
4374 # resuming downloads continues to work.
4375 # This way you can continue to use Tor for your normal browsing,
4376 # without overloading the Tor network with your FreeBSD ports updates
4377 # or downloads of bigger files like ISOs.
4378 # Note that HTTP headers are easy to fake and therefore their
4379 # values are as (un)trustworthy as your clients and users.
4380 {+forward-override{forward .} \
4381 -hide-if-modified-since \
4382 -overwrite-last-modified \
4384 TAG:^User-Agent: fetch libfetch/2\.0$
4400 NAME="HANDLE-AS-EMPTY-DOCUMENT"
4401 >8.5.17. handle-as-empty-document</A
4406 CLASS="VARIABLELIST"
4412 >Mark URLs that should be replaced by empty documents <SPAN
4416 >if they get blocked</I
4424 > This action alone doesn't do anything noticeable. It just marks URLs.
4428 HREF="actions-file.html#BLOCK"
4438 the presence or absence of this mark decides whether an HTML <SPAN
4442 page, or an empty document will be sent to the client as a substitute for the blocked content.
4449 > document isn't literally empty, but actually contains a single space.
4469 > Some browsers complain about syntax errors if JavaScript documents
4470 are blocked with <SPAN
4474 default HTML page; this option can be used to silence them.
4475 And of course this action can also be used to eliminate the <SPAN
4479 BLOCKED message in frames.
4482 > The content type for the empty document can be specified with
4486 HREF="actions-file.html#CONTENT-TYPE-OVERWRITE"
4487 >content-type-overwrite{}</A
4490 but usually this isn't necessary.
4505 ># Block all documents on example.org that end with ".js",
4506 # but send an empty document instead of the usual HTML message.
4507 {+block +handle-as-empty-document}
4524 NAME="HANDLE-AS-IMAGE"
4525 >8.5.18. handle-as-image</A
4530 CLASS="VARIABLELIST"
4536 >Mark URLs as belonging to images (so they'll be replaced by images <SPAN
4540 >if they do get blocked</I
4542 >, rather than HTML pages)</P
4548 > This action alone doesn't do anything noticeable. It just marks URLs as images.
4552 HREF="actions-file.html#BLOCK"
4562 the presence or absence of this mark decides whether an HTML <SPAN
4566 page, or a replacement image (as determined by the <TT
4569 HREF="actions-file.html#SET-IMAGE-BLOCKER"
4570 >set-image-blocker</A
4572 > action) will be sent to the
4573 client as a substitute for the blocked content.
4593 > The below generic example section is actually part of <TT
4597 It marks all URLs with well-known image file name extensions as images and should
4601 > Users will probably only want to use the handle-as-image action in conjunction with
4605 HREF="actions-file.html#BLOCK"
4608 >, to block sources of banners, whose URLs don't
4609 reflect the file type, like in the second example section.
4612 > Note that you cannot treat HTML pages as images in most cases. For instance, (in-line) ad
4613 frames require an HTML page to be sent, or they won't display properly.
4616 >handle-as-image</TT
4617 > in this situation will not replace the
4618 ad frame with an image, but lead to error messages.
4622 >Example usage (sections):</DT
4633 ># Generic image extensions:
4636 /.*\.(gif|jpg|jpeg|png|bmp|ico)$
4638 # These don't look like images, but they're banners and should be
4639 # blocked as images:
4641 {+block +handle-as-image}
4642 some.nasty-banner-server.com/junk.cgi\?output=trash
4644 # Banner source! Who cares if they also have non-image content?
4645 ad.doubleclick.net </PRE
4660 NAME="HIDE-ACCEPT-LANGUAGE"
4661 >8.5.19. hide-accept-language</A
4666 CLASS="VARIABLELIST"
4672 >Pretend to use different language settings.</P
4678 > Deletes or replaces the <SPAN
4680 >"Accept-Language:"</SPAN
4681 > HTTP header in client requests.
4697 >, or any user defined value.
4704 > Faking the browser's language settings can be useful to make a
4705 foreign User-Agent set with
4709 HREF="actions-file.html#HIDE-USER-AGENT"
4716 > However some sites with content in different languages check the
4719 >"Accept-Language:"</SPAN
4720 > to decide which one to take by default.
4721 Sometimes it isn't possible to later switch to another language without
4724 >"Accept-Language:"</SPAN
4728 > Therefore it's a good idea to either only change the
4731 >"Accept-Language:"</SPAN
4732 > header to languages you understand,
4733 or to languages that aren't wide spread.
4736 > Before setting the <SPAN
4738 >"Accept-Language:"</SPAN
4740 to a rare language, you should consider that it helps to
4741 make your requests unique and thus easier to trace.
4742 If you don't plan to change this header frequently,
4743 you should stick to a common language.
4747 >Example usage (section):</DT
4758 ># Pretend to use Canadian language settings.
4759 {+hide-accept-language{en-ca} \
4760 +hide-user-agent{Mozilla/5.0 (X11; U; OpenBSD i386; en-CA; rv:1.8.0.4) Gecko/20060628 Firefox/1.5.0.4} \
4777 NAME="HIDE-CONTENT-DISPOSITION"
4778 >8.5.20. hide-content-disposition</A
4783 CLASS="VARIABLELIST"
4789 >Prevent download menus for content you prefer to view inside the browser.</P
4795 > Deletes or replaces the <SPAN
4797 >"Content-Disposition:"</SPAN
4798 > HTTP header set by some servers.
4814 >, or any user defined value.
4821 > Some servers set the <SPAN
4823 >"Content-Disposition:"</SPAN
4825 documents they assume you want to save locally before viewing them.
4828 >"Content-Disposition:"</SPAN
4829 > header contains the file name
4830 the browser is supposed to use by default.
4833 > In most browsers that understand this header, it makes it impossible to
4840 > the document, without downloading it first,
4841 even if it's just a simple text file or an image.
4844 > Removing the <SPAN
4846 >"Content-Disposition:"</SPAN
4848 to prevent this annoyance, but some browsers additionally check the
4851 >"Content-Type:"</SPAN
4852 > header, before they decide if they can
4853 display a document without saving it first. In these cases, you have
4854 to change this header as well, before the browser stops displaying
4858 > It is also possible to change the server's file name suggestion
4859 to another one, but in most cases it isn't worth the time to set
4863 > This action will probably be removed in the future,
4864 use server-header filters instead.
4879 ># Disarm the download link in Sourceforge's patch tracker
4881 +content-type-overwrite{text/plain}\
4882 +hide-content-disposition{block} }
4883 .sourceforge.net/tracker/download\.php</PRE
4898 NAME="HIDE-IF-MODIFIED-SINCE"
4899 >8.5.21. hide-if-modified-since</A
4904 CLASS="VARIABLELIST"
4910 >Prevent yet another way to track the user's steps between sessions.</P
4918 >"If-Modified-Since:"</SPAN
4919 > HTTP client header or modifies its value.
4935 >, or a user defined value that specifies a range of hours.
4942 > Removing this header is useful for filter testing, where you want to force a real
4943 reload instead of getting status code <SPAN
4946 >, which would cause the
4947 browser to use a cached copy of the page.
4950 > Instead of removing the header, <TT
4952 >hide-if-modified-since</TT
4954 also add or subtract a random amount of time to/from the header's value.
4955 You specify a range of minutes where the random factor should be chosen from and
4959 > does the rest. A negative value means
4960 subtracting, a positive value adding.
4963 > Randomizing the value of the <SPAN
4965 >"If-Modified-Since:"</SPAN
4967 it less likely that the server can use the time as a cookie replacement,
4968 but you will run into caching problems if the random range is too high.
4971 > It is a good idea to only use a small negative value and let
4975 HREF="actions-file.html#OVERWRITE-LAST-MODIFIED"
4976 >overwrite-last-modified</A
4979 handle the greater changes.
4982 > It is also recommended to use this action together with
4986 HREF="actions-file.html#CRUNCH-IF-NONE-MATCH"
4987 >crunch-if-none-match</A
4990 otherwise it's more or less pointless.
4994 >Example usage (section):</DT
5005 ># Let the browser revalidate but make tracking based on the time less likely.
5006 {+hide-if-modified-since{-60} \
5007 +overwrite-last-modified{randomize} \
5008 +crunch-if-none-match}
5024 NAME="HIDE-FORWARDED-FOR-HEADERS"
5025 >8.5.22. hide-forwarded-for-headers</A
5030 CLASS="VARIABLELIST"
5036 >Improve privacy by not forwarding the source of the request in the HTTP headers.</P
5042 > Deletes any existing <SPAN
5044 >"X-Forwarded-for:"</SPAN
5045 > HTTP header from client requests.
5065 > It is safe and recommended to leave this on.
5080 >+hide-forwarded-for-headers</PRE
5095 NAME="HIDE-FROM-HEADER"
5096 >8.5.23. hide-from-header</A
5101 CLASS="VARIABLELIST"
5107 >Keep your (old and ill) browser from telling web servers your email address</P
5113 > Deletes any existing <SPAN
5116 > HTTP header, or replaces it with the
5133 >, or any user defined value.
5143 > will completely remove the header
5144 (not to be confused with the <TT
5147 HREF="actions-file.html#BLOCK"
5154 > Alternately, you can specify any value you prefer to be sent to the web
5155 server. If you do, it is a matter of fairness not to use any address that
5156 is actually used by a real person.
5159 > This action is rarely needed, as modern web browsers don't send
5178 >+hide-from-header{block}</PRE
5191 >+hide-from-header{spam-me-senseless@sittingduck.example.com}</PRE
5206 NAME="HIDE-REFERRER"
5207 >8.5.24. hide-referrer</A
5215 CLASS="VARIABLELIST"
5221 >Conceal which link you followed to get to a particular site</P
5230 > (sic) HTTP header from the client request,
5231 or replaces it with a forged one.
5250 >"conditional-block"</SPAN
5251 > to delete the header completely if the host has changed.</P
5257 >"conditional-forge"</SPAN
5258 > to forge the header if the host has changed.</P
5265 > to delete the header unconditionally.</P
5272 > to pretend to be coming from the homepage of the server we are talking to.</P
5276 >Any other string to set a user defined referrer.</P
5286 >conditional-block</TT
5287 > is the only parameter,
5288 that isn't easily detected in the server's log file. If it blocks the
5289 referrer, the request will look like the visitor used a bookmark or
5290 typed in the address directly.
5293 > Leaving the referrer unmodified for requests on the same host
5294 allows the server owner to see the visitor's <SPAN
5298 but in most cases she could also get that information by comparing
5299 other parts of the log file: for example the User-Agent if it isn't
5300 a very common one, or the user's IP address if it doesn't change between
5304 > Always blocking the referrer, or using a custom one, can lead to
5305 failures on servers that check the referrer before they answer any
5306 requests, in an attempt to prevent their content from being
5307 embedded or linked to elsewhere.
5312 >conditional-block</TT
5317 will work with referrer checks, as long as content and valid referring page
5318 are on the same host. Most of the time that's the case.
5325 > is an alternate spelling of
5329 > and the two can be can be freely
5330 substituted with each other. (<SPAN
5334 correct English spelling, however the HTTP specification has a bug - it
5335 requires it to be spelled as <SPAN
5353 >+hide-referrer{forge}</PRE
5366 >+hide-referrer{http://www.yahoo.com/}</PRE
5381 NAME="HIDE-USER-AGENT"
5382 >8.5.25. hide-user-agent</A
5387 CLASS="VARIABLELIST"
5393 >Try to conceal your type of browser and client operating system</P
5399 > Replaces the value of the <SPAN
5401 >"User-Agent:"</SPAN
5403 in client requests with the specified value.
5416 > Any user-defined string.
5441 > This can lead to problems on web sites that depend on looking at this header in
5442 order to customize their content for different browsers (which, by the
5449 > the right thing to do: good web sites
5450 work browser-independently).
5457 > Using this action in multi-user setups or wherever different types of
5458 browsers will access the same <SPAN
5468 >. In single-user, single-browser
5469 setups, you might use it to delete your OS version information from
5470 the headers, because it is an invitation to exploit known bugs for your
5471 OS. It is also occasionally useful to forge this in order to access
5472 sites that won't let you in otherwise (though there may be a good
5473 reason in some cases). Example of this: some MSN sites will not
5477 > enter, yet forging to a
5481 > user-agent works just fine.
5482 (Must be just a silly MS goof, I'm sure :-).
5485 > More information on known user-agent strings can be found at
5487 HREF="http://www.user-agents.org/"
5489 >http://www.user-agents.org/</A
5493 HREF="http://en.wikipedia.org/wiki/User_agent"
5495 >http://en.wikipedia.org/wiki/User_agent</A
5511 >+hide-user-agent{Netscape 6.1 (X11; I; Linux 2.4.18 i686)}</PRE
5526 NAME="INSPECT-JPEGS"
5527 >8.5.26. inspect-jpegs</A
5532 CLASS="VARIABLELIST"
5538 >Try to protect against a MS buffer over-run in JPEG processing</P
5544 > Protect against a known exploit
5564 > See Microsoft Security Bulletin MS04-028. JPEG images are one of the most
5565 common image types found across the Internet. The exploit as described can
5566 allow execution of code on the target system, giving an attacker access
5567 to the system in question by merely planting an altered JPEG image, which
5568 would have no obvious indications of what lurks inside. This action
5569 tries to prevent this exploit if delivered through unencrypted HTTP.
5572 > Note that the exploit mentioned is several years old
5573 and it's unlikely that your client is still vulnerable
5574 against it. This action may be removed in one of the
5590 >+inspect-jpegs</PRE
5605 >8.5.27. kill-popups<A
5613 CLASS="VARIABLELIST"
5619 >Eliminate those annoying pop-up windows (deprecated)</P
5625 > While loading the document, replace JavaScript code that opens
5626 pop-up windows with (syntactically neutral) dummy code on the fly.
5646 > This action is basically a built-in, hardwired special-purpose filter
5647 action, but there are important differences: For <TT
5651 the document need not be buffered, so it can be incrementally rendered while
5652 downloading. But <TT
5655 > doesn't catch as many pop-ups as
5659 HREF="actions-file.html#FILTER-ALL-POPUPS"
5668 does and is not as smart as <TT
5671 HREF="actions-file.html#FILTER-UNSOLICITED-POPUPS"
5675 >unsolicited-popups</I
5683 > Think of it as a fast and efficient replacement for a filter that you
5684 can use if you don't want any filtering at all. Note that it doesn't make
5685 sense to combine it with any <TT
5688 HREF="actions-file.html#FILTER"
5692 since as soon as one <TT
5695 HREF="actions-file.html#FILTER"
5699 the whole document needs to be buffered anyway, which destroys the advantage of
5703 > action over its filter equivalent.
5706 > Killing all pop-ups unconditionally is problematic. Many shops and banks rely on
5707 pop-ups to display forms, shopping carts etc, and the <TT
5710 HREF="actions-file.html#FILTER-UNSOLICITED-POPUPS"
5714 >unsolicited-popups</I
5719 > does a better job of catching only the unwanted ones.
5722 > If the only kind of pop-ups that you want to kill are exit consoles (those
5729 > windows that appear when you close an other
5730 one), you might want to use
5734 HREF="actions-file.html#FILTER"
5746 > This action is most appropriate for browsers that don't have any controls
5747 for unwanted pop-ups. Not recommended for general usage.
5750 > This action doesn't work very reliable and may be removed in future releases.
5779 NAME="LIMIT-CONNECT"
5780 >8.5.28. limit-connect</A
5785 CLASS="VARIABLELIST"
5791 >Prevent abuse of <SPAN
5794 > as a TCP proxy relay or disable SSL for untrusted sites</P
5800 > Specifies to which ports HTTP CONNECT requests are allowable.
5813 > A comma-separated list of ports or port ranges (the latter using dashes, with the minimum
5814 defaulting to 0 and the maximum to 65K).
5821 > By default, i.e. if no <TT
5828 > only allows HTTP CONNECT
5829 requests to port 443 (the standard, secure HTTPS port). Use
5833 > if more fine-grained control is desired
5834 for some or all destinations.
5837 > The CONNECT methods exists in HTTP to allow access to secure websites
5841 > URLs) through proxies. It works very simply:
5842 the proxy connects to the server on the specified port, and then
5843 short-circuits its connections to the client and to the remote server.
5844 This means CONNECT-enabled proxies can be used as TCP relays very easily.
5850 > relays HTTPS traffic without seeing
5851 the decoded content. Websites can leverage this limitation to circumvent <SPAN
5855 filters. By specifying an invalid port range you can disable HTTPS entirely.
5856 If you plan to disable SSL by default, consider enabling
5860 HREF="actions-file.html#TREAT-FORBIDDEN-CONNECTS-LIKE-BLOCKS"
5861 >treat-forbidden-connects-like-blocks</A
5864 as well, to be able to quickly create exceptions.
5868 >Example usages:</DT
5879 >+limit-connect{443} # This is the default and need not be specified.
5880 +limit-connect{80,443} # Ports 80 and 443 are OK.
5881 +limit-connect{-3, 7, 20-100, 500-} # Ports less than 3, 7, 20 to 100 and above 500 are OK.
5882 +limit-connect{-} # All ports are OK
5883 +limit-connect{,} # No HTTPS/SSL traffic is allowed</PRE
5898 NAME="PREVENT-COMPRESSION"
5899 >8.5.29. prevent-compression</A
5904 CLASS="VARIABLELIST"
5910 > Ensure that servers send the content uncompressed, so it can be
5914 HREF="actions-file.html#FILTER"
5924 > Removes the Accept-Encoding header which can be used to ask for compressed transfer.
5944 > More and more websites send their content compressed by default, which
5945 is generally a good idea and saves bandwidth. But the <TT
5948 HREF="actions-file.html#FILTER"
5954 HREF="actions-file.html#DEANIMATE-GIFS"
5961 HREF="actions-file.html#KILL-POPUPS"
5965 access to the uncompressed data.
5968 > When compiled with zlib support (available since <SPAN
5971 > 3.0.7), content that should be
5972 filtered is decompressed on-the-fly and you don't have to worry about this action.
5973 If you are using an older <SPAN
5976 > version, or one that hasn't been compiled with zlib
5977 support, this action can be used to convince the server to send the content uncompressed.
5980 > Most text-based instances compress very well, the size is seldom decreased by less than 50%,
5981 for markup-heavy instances like news feeds saving more than 90% of the original size isn't
5985 > Not using compression will therefore slow down the transfer, and you should only
5986 enable this action if you really need it. As of <SPAN
5989 > 3.0.7 it's disabled in all
5990 predefined action settings.
5993 > Note that some (rare) ill-configured sites don't handle requests for uncompressed
5994 documents correctly. Broken PHP applications tend to send an empty document body,
5995 some IIS versions only send the beginning of the content. If you enable
5998 >prevent-compression</TT
5999 > per default, you might want to add
6000 exceptions for those sites. See the example for how to do that.
6004 >Example usage (sections):</DT
6015 ># Selectively turn off compression, and enable a filter
6017 { +filter{tiny-textforms} +prevent-compression }
6018 # Match only these sites
6023 # Or instead, we could set a universal default:
6025 { +prevent-compression }
6028 # Then maybe make exceptions for broken sites:
6030 { -prevent-compression }
6046 NAME="OVERWRITE-LAST-MODIFIED"
6047 >8.5.30. overwrite-last-modified</A
6052 CLASS="VARIABLELIST"
6058 >Prevent yet another way to track the user's steps between sessions.</P
6066 >"Last-Modified:"</SPAN
6067 > HTTP server header or modifies its value.
6080 > One of the keywords: <SPAN
6085 >"reset-to-request-time"</SPAN
6097 > Removing the <SPAN
6099 >"Last-Modified:"</SPAN
6100 > header is useful for filter
6101 testing, where you want to force a real reload instead of getting status
6105 >, which would cause the browser to reuse the old
6106 version of the page.
6112 > option overwrites the value of the
6115 >"Last-Modified:"</SPAN
6116 > header with a randomly chosen time
6117 between the original value and the current time. In theory the server
6118 could send each document with a different <SPAN
6120 >"Last-Modified:"</SPAN
6122 header to track visits without using cookies. <SPAN
6126 makes it impossible and the browser can still revalidate cached documents.
6131 >"reset-to-request-time"</SPAN
6132 > overwrites the value of the
6135 >"Last-Modified:"</SPAN
6136 > header with the current time. You could use
6137 this option together with
6141 HREF="actions-file.html#HIDE-IF-MODIFIED-SINCE"
6142 >hided-if-modified-since</A
6145 to further customize your random range.
6148 > The preferred parameter here is <SPAN
6152 to use, as long as the time settings are more or less correct.
6153 If the server sets the <SPAN
6155 >"Last-Modified:"</SPAN
6156 > header to the time
6157 of the request, the random range becomes zero and the value stays the same.
6158 Therefore you should later randomize it a second time with
6162 HREF="actions-file.html#HIDE-IF-MODIFIED-SINCE"
6163 >hided-if-modified-since</A
6169 > It is also recommended to use this action together with
6173 HREF="actions-file.html#CRUNCH-IF-NONE-MATCH"
6174 >crunch-if-none-match</A
6191 ># Let the browser revalidate without being tracked across sessions
6192 { +hide-if-modified-since{-60} \
6193 +overwrite-last-modified{randomize} \
6194 +crunch-if-none-match}
6211 >8.5.31. redirect</A
6216 CLASS="VARIABLELIST"
6222 > Redirect requests to other sites.
6229 > Convinces the browser that the requested document has been moved
6230 to another location and the browser should get it from there.
6243 > An absolute URL or a single pcrs command.
6250 > Requests to which this action applies are answered with a
6251 HTTP redirect to URLs of your choosing. The new URL is
6252 either provided as parameter, or derived by applying a
6253 single pcrs command to the original URL.
6256 > This action will be ignored if you use it together with
6260 HREF="actions-file.html#BLOCK"
6264 It can be combined with
6268 HREF="actions-file.html#FAST-REDIRECTS"
6269 >fast-redirects{check-decoded-url}</A
6272 to redirect to a decoded version of a rewritten URL.
6275 > Use this action carefully, make sure not to create redirection loops
6276 and be aware that using your own redirects might make it
6277 possible to fingerprint your requests.
6281 >Example usages:</DT
6292 ># Replace example.com's style sheet with another one
6293 { +redirect{http://localhost/css-replacements/example.com.css} }
6294 example.com/stylesheet\.css
6296 # Create a short, easy to remember nickname for a favorite site
6297 # (relies on the browser accept and forward invalid URLs to <SPAN
6301 { +redirect{http://www.privoxy.org/user-manual/actions-file.html} }
6304 # Always use the expanded view for Undeadly.org articles
6305 # (Note the $ at the end of the URL pattern to make sure
6306 # the request for the rewritten URL isn't redirected as well)
6307 {+redirect{s@$@&mode=expanded@}}
6308 undeadly.org/cgi\?action=article&sid=\d*$</PRE
6323 NAME="SEND-VANILLA-WAFER"
6324 >8.5.32. send-vanilla-wafer</A
6329 CLASS="VARIABLELIST"
6335 > Feed log analysis scripts with useless data.
6342 > Sends a cookie with each request stating that you do not accept any copyright
6343 on cookies sent to you, and asking the site operator not to track you.
6363 > The vanilla wafer is a (relatively) unique header and could conceivably be used to track you.
6366 > This action is rarely used and not enabled in the default configuration.
6381 >+send-vanilla-wafer</PRE
6397 >8.5.33. send-wafer</A
6402 CLASS="VARIABLELIST"
6408 > Send custom cookies or feed log analysis scripts with even more useless data.
6415 > Sends a custom, user-defined cookie with each request.
6428 > A string of the form <SPAN
6448 > Being multi-valued, multiple instances of this action can apply to the same request,
6449 resulting in multiple cookies being sent.
6452 > This action is rarely used and not enabled in the default configuration.
6456 >Example usage (section):</DT
6467 >{+send-wafer{UsingPrivoxy=true}}
6468 my-internal-testing-server.void</PRE
6483 NAME="SERVER-HEADER-FILTER"
6484 >8.5.34. server-header-filter</A
6489 CLASS="VARIABLELIST"
6495 > Rewrite or remove single server headers.
6502 > All server headers to which this action applies are filtered on-the-fly
6503 through the specified regular expression based substitutions.
6516 > The name of a server-header filter, as defined in one of the
6518 HREF="filter-file.html"
6527 > Server-header filters are applied to each header on its own, not to
6528 all at once. This makes it easier to diagnose problems, but on the downside
6529 you can't write filters that only change header x if header y's value is z.
6530 You can do that by using tags though.
6533 > Server-header filters are executed after the other header actions have finished
6534 and use their output as input.
6537 > Please refer to the <A
6538 HREF="filter-file.html"
6539 >filter file chapter</A
6541 to learn which server-header filters are available by default, and how to
6546 >Example usage (section):</DT
6557 >{+server-header-filter{html-to-xml}}
6558 example.org/xml-instance-that-is-delivered-as-html
6560 {+server-header-filter{xml-to-html}}
6561 example.org/instance-that-is-delivered-as-xml-but-is-not
6577 NAME="SERVER-HEADER-TAGGER"
6578 >8.5.35. server-header-tagger</A
6583 CLASS="VARIABLELIST"
6589 > Enable or disable filters based on the Content-Type header.
6596 > Server headers to which this action applies are filtered on-the-fly through
6597 the specified regular expression based substitutions, the result is used as
6611 > The name of a server-header tagger, as defined in one of the
6613 HREF="filter-file.html"
6622 > Server-header taggers are applied to each header on its own,
6623 and as the header isn't modified, each tagger <SPAN
6630 > Server-header taggers are executed before all other header actions
6631 that modify server headers. Their tags can be used to control
6632 all of the other server-header actions, the content filters
6633 and the crunch actions (<A
6634 HREF="actions-file.html#REDIRECT"
6638 HREF="actions-file.html#BLOCK"
6643 > Obviously crunching based on tags created by server-header taggers
6644 doesn't prevent the request from showing up in the server's log file.
6648 >Example usage (section):</DT
6659 ># Tag every request with the content type declared by the server
6660 {+server-header-tagger{content-type}}
6677 NAME="SESSION-COOKIES-ONLY"
6678 >8.5.36. session-cookies-only</A
6683 CLASS="VARIABLELIST"
6689 > Allow only temporary <SPAN
6692 > cookies (for the current
6693 browser session <SPAN
6711 >"Set-Cookie:"</SPAN
6713 server headers. Most browsers will not store such cookies permanently and
6714 forget them in between sessions.
6734 > This is less strict than <TT
6737 HREF="actions-file.html#CRUNCH-INCOMING-COOKIES"
6738 >crunch-incoming-cookies</A
6744 HREF="actions-file.html#CRUNCH-OUTGOING-COOKIES"
6745 >crunch-outgoing-cookies</A
6747 > and allows you to browse
6748 websites that insist or rely on setting cookies, without compromising your privacy too badly.
6751 > Most browsers will not permanently store cookies that have been processed by
6754 >session-cookies-only</TT
6755 > and will forget about them between sessions.
6756 This makes profiling cookies useless, but won't break sites which require cookies so
6757 that you can log in for transactions. This is generally turned on for all
6758 sites, and is the recommended setting.
6769 >session-cookies-only</TT
6774 HREF="actions-file.html#CRUNCH-INCOMING-COOKIES"
6775 >crunch-incoming-cookies</A
6781 HREF="actions-file.html#CRUNCH-OUTGOING-COOKIES"
6782 >crunch-outgoing-cookies</A
6784 >. If you do, cookies
6785 will be plainly killed.
6788 > Note that it is up to the browser how it handles such cookies without an <SPAN
6792 field. If you use an exotic browser, you might want to try it out to be sure.
6795 > This setting also has no effect on cookies that may have been stored
6796 previously by the browser before starting <SPAN
6800 These would have to be removed manually.
6808 HREF="actions-file.html#FILTER-CONTENT-COOKIES"
6809 >content-cookies filter</A
6811 to block some types of cookies. Content cookies are not effected by
6814 >session-cookies-only</TT
6830 >+session-cookies-only</PRE
6845 NAME="SET-IMAGE-BLOCKER"
6846 >8.5.37. set-image-blocker</A
6851 CLASS="VARIABLELIST"
6857 >Choose the replacement for blocked images</P
6863 > This action alone doesn't do anything noticeable. If <SPAN
6873 HREF="actions-file.html#BLOCK"
6885 HREF="actions-file.html#HANDLE-AS-IMAGE"
6895 apply, i.e. if the request is to be blocked as an image,
6902 > the parameter of this action decides what will be
6903 sent as a replacement.
6923 > to send a built-in checkerboard pattern image. The image is visually
6924 decent, scales very well, and makes it obvious where banners were busted.
6932 > to send a built-in transparent image. This makes banners disappear
6933 completely, but makes it hard to detect where <SPAN
6937 images on a given page and complicates troubleshooting if <SPAN
6941 has blocked innocent images, like navigation icons.
6955 send a redirect to <TT
6961 to any image anywhere, even in your local filesystem via <SPAN
6965 (But note that not all browsers support redirecting to a local file system).
6968 > A good application of redirects is to use special <SPAN
6972 URLs, which send the built-in images, as <TT
6978 This has the same visual effect as specifying <SPAN
6985 the first place, but enables your browser to cache the replacement image, instead of requesting
6986 it over and over again.
6995 > The URLs for the built-in images are <SPAN
6997 >"http://config.privoxy.org/send-banner?type=<TT
7018 > There is a third (advanced) type, called <SPAN
7030 >set-image-blocker</TT
7031 >, but meant for use from <A
7032 HREF="filter-file.html"
7035 Auto will select the type of image that would have applied to the referring page, had it been an image.
7053 >+set-image-blocker{pattern}</PRE
7060 > Redirect to the BSD daemon:
7071 >+set-image-blocker{http://www.freebsd.org/gifs/dae_up3.gif}</PRE
7078 > Redirect to the built-in pattern for better caching:
7089 >+set-image-blocker{http://config.privoxy.org/send-banner?type=pattern}</PRE
7104 NAME="TREAT-FORBIDDEN-CONNECTS-LIKE-BLOCKS"
7105 >8.5.38. treat-forbidden-connects-like-blocks</A
7110 CLASS="VARIABLELIST"
7116 >Block forbidden connects with an easy to find error message.</P
7122 > If this action is enabled, <SPAN
7126 makes a difference between forbidden connects and ordinary blocks.
7150 HREF="actions-file.html#LIMIT-CONNECT"
7156 with a short error message inside the headers. If the browser doesn't display
7157 headers (most don't), you just see an empty page.
7160 > With this action enabled, <SPAN
7164 the message that is used for ordinary blocks instead. If you decide
7165 to make an exception for the page in question, you can do so by
7175 > requests the clients tell
7179 > which host they are interested
7180 in, but not which document they plan to get later. As a result, the
7183 >"Go there anyway"</SPAN
7184 > wouldn't work and is therefore suppressed.
7199 >+treat-forbidden-connects-like-blocks</PRE
7218 > Note that many of these actions have the potential to cause a page to
7219 misbehave, possibly even not to display at all. There are many ways
7220 a site designer may choose to design his site, and what HTTP header
7221 content, and other criteria, he may depend on. There is no way to have hard
7222 and fast rules for all sites. See the <A
7223 HREF="appendix.html#ACTIONSANAT"
7225 > for a brief example on troubleshooting
7248 >, can be defined by combining other actions.
7249 These can in turn be invoked just like the built-in actions.
7250 Currently, an alias name can contain any character except space, tab,
7268 > that you only use <SPAN
7288 Alias names are not case sensitive, and are not required to start with a
7295 > sign, since they are merely textually
7298 > Aliases can be used throughout the actions file, but they <SPAN
7303 defined in a special section at the top of the file!</I
7306 And there can only be one such section per actions file. Each actions file may
7307 have its own alias section, and the aliases defined in it are only visible
7308 within that file.</P
7310 > There are two main reasons to use aliases: One is to save typing for frequently
7311 used combinations of actions, the other one is a gain in flexibility: If you
7312 decide once how you want to handle shops by defining an alias called
7316 >, you can later change your policy on shops in
7323 > place, and your changes will take effect everywhere
7324 in the actions file where the <SPAN
7327 > alias is used. Calling aliases
7328 by their purpose also makes your actions files more readable.</P
7330 > Currently, there is one big drawback to using aliases, though:
7334 >'s built-in web-based action file
7335 editor honors aliases when reading the actions files, but it expands
7336 them before writing. So the effects of your aliases are of course preserved,
7337 but the aliases themselves are lost when you edit sections that use aliases
7340 > Now let's define some aliases...</P
7350 > # Useful custom aliases we can use later.
7352 # Note the (required!) section header line and that this section
7353 # must be at the top of the actions file!
7357 # These aliases just save typing later:
7358 # (Note that some already use other aliases!)
7360 +crunch-all-cookies = +<A
7361 HREF="actions-file.html#CRUNCH-INCOMING-COOKIES"
7362 >crunch-incoming-cookies</A
7364 HREF="actions-file.html#CRUNCH-OUTGOING-COOKIES"
7365 >crunch-outgoing-cookies</A
7367 -crunch-all-cookies = -<A
7368 HREF="actions-file.html#CRUNCH-INCOMING-COOKIES"
7369 >crunch-incoming-cookies</A
7371 HREF="actions-file.html#CRUNCH-OUTGOING-COOKIES"
7372 >crunch-outgoing-cookies</A
7374 +block-as-image = +block +handle-as-image
7375 allow-all-cookies = -crunch-all-cookies -<A
7376 HREF="actions-file.html#SESSION-COOKIES-ONLY"
7377 >session-cookies-only</A
7379 HREF="actions-file.html#FILTER-CONTENT-COOKIES"
7380 >filter{content-cookies}</A
7383 # These aliases define combinations of actions
7384 # that are useful for certain types of sites:
7387 HREF="actions-file.html#BLOCK"
7390 HREF="actions-file.html#FILTER"
7392 > -crunch-all-cookies -<A
7393 HREF="actions-file.html#FAST-REDIRECTS"
7396 HREF="actions-file.html#HIDE-REFERER"
7399 HREF="actions-file.html#KILL-POPUPS"
7402 HREF="actions-file.html#PREVENT-COMPRESSION"
7403 >prevent-compression</A
7406 shop = -crunch-all-cookies -<A
7407 HREF="actions-file.html#FILTER-ALL-POPUPS"
7408 >filter{all-popups}</A
7410 HREF="actions-file.html#KILL-POPUPS"
7414 # Short names for other aliases, for really lazy people ;-)
7416 c0 = +crunch-all-cookies
7417 c1 = -crunch-all-cookies</PRE
7423 > ...and put them to use. These sections would appear in the lower part of an
7424 actions file and define exceptions to the default actions (as specified further
7438 > # These sites are either very complex or very keen on
7439 # user data and require minimal interference to work:
7442 .office.microsoft.com
7443 .windowsupdate.microsoft.com
7444 # Gmail is really mail.google.com, not gmail.com
7448 # Allow cookies (for setting and retrieving your customer data)
7452 .worldpay.com # for quietpc.com
7455 # These shops require pop-ups:
7457 {-kill-popups -filter{all-popups} -filter{unsolicited-popups}}
7459 .overclockers.co.uk</PRE
7465 > Aliases like <SPAN
7471 > are typically used for
7475 > sites that require more than one action to be disabled
7476 in order to function properly.</P
7484 >8.7. Actions Files Tutorial</A
7487 > The above chapters have shown <A
7488 HREF="actions-file.html"
7489 >which actions files
7490 there are and how they are organized</A
7491 >, how actions are <A
7492 HREF="actions-file.html#ACTIONS"
7495 HREF="actions-file.html#ACTIONS-APPLY"
7499 HREF="actions-file.html#AF-PATTERNS"
7503 HREF="actions-file.html#ALIASES"
7505 >. Now, let's look at an
7513 file and see how all these pieces come together:</P
7520 >8.7.1. default.action</A
7523 >Every config file should start with a short comment stating its purpose:</P
7533 ># Sample default.action file <ijbswa-developers@lists.sourceforge.net></PRE
7539 >Then, since this is the <TT
7543 first section is a special section for internal use that you needn't
7544 change or worry about:</P
7554 >##########################################################################
7555 # Settings -- Don't change! For internal Privoxy use ONLY.
7556 ##########################################################################
7559 for-privoxy-version=3.0</PRE
7565 >After that comes the (optional) alias section. We'll use the example
7566 section from the above <A
7567 HREF="actions-file.html#ALIASES"
7568 >chapter on aliases</A
7570 that also explains why and how aliases are used:</P
7580 >##########################################################################
7582 ##########################################################################
7585 # These aliases just save typing later:
7586 # (Note that some already use other aliases!)
7588 +crunch-all-cookies = +<A
7589 HREF="actions-file.html#CRUNCH-INCOMING-COOKIES"
7590 >crunch-incoming-cookies</A
7592 HREF="actions-file.html#CRUNCH-OUTGOING-COOKIES"
7593 >crunch-outgoing-cookies</A
7595 -crunch-all-cookies = -<A
7596 HREF="actions-file.html#CRUNCH-INCOMING-COOKIES"
7597 >crunch-incoming-cookies</A
7599 HREF="actions-file.html#CRUNCH-OUTGOING-COOKIES"
7600 >crunch-outgoing-cookies</A
7602 +block-as-image = +block +handle-as-image
7603 mercy-for-cookies = -crunch-all-cookies -<A
7604 HREF="actions-file.html#SESSION-COOKIES-ONLY"
7605 >session-cookies-only</A
7607 HREF="actions-file.html#FILTER-CONTENT-COOKIES"
7608 >filter{content-cookies}</A
7611 # These aliases define combinations of actions
7612 # that are useful for certain types of sites:
7615 HREF="actions-file.html#BLOCK"
7618 HREF="actions-file.html#FILTER"
7620 > -crunch-all-cookies -<A
7621 HREF="actions-file.html#FAST-REDIRECTS"
7624 HREF="actions-file.html#HIDE-REFERER"
7627 HREF="actions-file.html#KILL-POPUPS"
7630 shop = -crunch-all-cookies -<A
7631 HREF="actions-file.html#FILTER-ALL-POPUPS"
7632 >filter{all-popups}</A
7634 HREF="actions-file.html#KILL-POPUPS"
7642 > Now come the regular sections, i.e. sets of actions, accompanied
7643 by URL patterns to which they apply. Remember <SPAN
7648 are disabled when matching starts</I
7650 >, so we have to explicitly
7651 enable the ones we want.</P
7653 > The first regular section is probably the most important. It has only
7662 HREF="actions-file.html#AF-PATTERNS"
7663 >matches all URLs</A
7665 set of actions used in this <SPAN
7673 be applied to all requests as a start</I
7675 >. It can be partly or
7676 wholly overridden by later matches further down this file, or in user.action,
7677 but it will still be largely responsible for your overall browsing
7680 > Again, at the start of matching, all actions are disabled, so there is
7681 no need to disable any actions here. (Remember: a <SPAN
7685 preceding the action name enables the action, a <SPAN
7689 Also note how this long line has been made more readable by splitting it into
7690 multiple lines with line continuation.</P
7700 >##########################################################################
7701 # "Defaults" section:
7702 ##########################################################################
7705 HREF="actions-file.html#DEANIMATE-GIFS"
7709 HREF="actions-file.html#FILTER-HTML-ANNOYANCES"
7710 >filter{html-annoyances}</A
7713 HREF="actions-file.html#FILTER-REFRESH-TAGS"
7714 >filter{refresh-tags}</A
7717 HREF="actions-file.html#FILTER-WEBBUGS"
7721 HREF="actions-file.html#FILTER-IE-EXPLOITS"
7722 >filter{ie-exploits}</A
7725 HREF="actions-file.html#HIDE-FORWARDED-FOR-HEADERS"
7726 >hide-forwarded-for-headers</A
7729 HREF="actions-file.html#HIDE-FROM-HEADER"
7730 >hide-from-header{block}</A
7733 HREF="actions-file.html#HIDE-REFERER"
7734 >hide-referrer{forge}</A
7737 HREF="actions-file.html#PREVENT-COMPRESSION"
7738 >prevent-compression</A
7741 HREF="actions-file.html#SESSION-COOKIES-ONLY"
7742 >session-cookies-only</A
7745 HREF="actions-file.html#SET-IMAGE-BLOCKER"
7746 >set-image-blocker{pattern}</A
7749 / # forward slash will match *all* potential URL patterns.</PRE
7755 > The default behavior is now set.
7758 > The first of our specialized sections is concerned with <SPAN
7762 sites, i.e. sites that require minimum interference, because they are either
7763 very complex or very keen on tracking you (and have mechanisms in place that
7764 make them unusable for people who avoid being tracked). We will simply use
7768 > alias instead of stating the list
7769 of actions explicitly:</P
7779 >##########################################################################
7780 # Exceptions for sites that'll break under the default action set:
7781 ##########################################################################
7783 # "Fragile" Use a minimum set of actions for these sites (see alias above):
7786 .office.microsoft.com # surprise, surprise!
7787 .windowsupdate.microsoft.com
7788 mail.google.com</PRE
7794 > Shopping sites are not as fragile, but they typically
7795 require cookies to log in, and pop-up windows for shopping
7796 carts or item details. Again, we'll use a pre-defined alias:</P
7810 .worldpay.com # for quietpc.com
7821 HREF="actions-file.html#FAST-REDIRECTS"
7825 action, which we enabled per default above, breaks some sites. So disable
7826 it for popular sites where we know it misbehaves:</P
7837 HREF="actions-file.html#FAST-REDIRECTS"
7843 .altavista.com/.*(like|url|link):http
7844 .altavista.com/trans.*urltext=http
7851 > It is important that <SPAN
7855 URLs belong to images, so that <SPAN
7862 be blocked, a substitute image can be sent, rather than an HTML page.
7863 Contacting the remote site to find out is not an option, since it
7864 would destroy the loading time advantage of banner blocking, and it
7865 would feed the advertisers (in terms of money <SPAN
7872 information). We can mark any URL as an image with the <TT
7875 HREF="actions-file.html#HANDLE-AS-IMAGE"
7879 and marking all URLs that end in a known image file extension is a
7890 >##########################################################################
7892 ##########################################################################
7894 # Define which file types will be treated as images, in case they get
7895 # blocked further down this file:
7898 HREF="actions-file.html#HANDLE-AS-IMAGE"
7901 /.*\.(gif|jpe?g|png|bmp|ico)$</PRE
7907 > And then there are known banner sources. They often use scripts to
7908 generate the banners, so it won't be visible from the URL that the
7909 request is for an image. Hence we block them <SPAN
7916 mark them as images in one go, with the help of our
7919 >+block-as-image</TT
7920 > alias defined above. (We could of
7921 course just as well use <TT
7924 HREF="actions-file.html#BLOCK"
7928 HREF="actions-file.html#HANDLE-AS-IMAGE"
7932 Remember that the type of the replacement image is chosen by the
7936 HREF="actions-file.html#SET-IMAGE-BLOCKER"
7937 >set-image-blocker</A
7940 action. Since all URLs have matched the default section with its
7944 HREF="actions-file.html#SET-IMAGE-BLOCKER"
7945 >set-image-blocker</A
7948 action before, it still applies and needn't be repeated:</P
7958 ># Known ad generators:
7963 .ad.*.doubleclick.net
7964 .a.yimg.com/(?:(?!/i/).)*$
7965 .a[0-9].yimg.com/(?:(?!/i/).)*$
7973 > One of the most important jobs of <SPAN
7977 is to block banners. Many of these can be <SPAN
7984 HREF="actions-file.html#FILTER"
7986 >{banners-by-size}</TT
7988 action, which we enabled above, and which deletes the references to banner
7989 images from the pages while they are loaded, so the browser doesn't request
7990 them anymore, and hence they don't need to be blocked here. But this naturally
7991 doesn't catch all banners, and some people choose not to use filters, so we
7992 need a comprehensive list of patterns for banner URLs here, and apply the
7996 HREF="actions-file.html#BLOCK"
7999 > action to them.</P
8001 > First comes many generic patterns, which do most of the work, by
8002 matching typical domain and path name components of banners. Then comes
8003 a list of individual patterns for specific sites, which is omitted here
8004 to keep the example short:</P
8014 >##########################################################################
8015 # Block these fine banners:
8016 ##########################################################################
8018 HREF="actions-file.html#BLOCK"
8028 /.*count(er)?\.(pl|cgi|exe|dll|asp|php[34]?)
8029 /(?:.*/)?(publicite|werbung|rekla(ma|me|am)|annonse|maino(kset|nta|s)?)/
8031 # Site-specific patterns (abbreviated):
8039 > It's quite remarkable how many advertisers actually call their banner
8045 >.com, or call the directory
8046 in which the banners are stored simply <SPAN
8050 generic patterns are surprisingly effective.</P
8052 > But being very generic, they necessarily also catch URLs that we don't want
8053 to block. The pattern <TT
8065 >.nasty-corp.com"</SPAN
8075 >.sourcefroge.net"</SPAN
8085 >l.some-provider.net."</SPAN
8087 well-known exceptions to the <TT
8090 HREF="actions-file.html#BLOCK"
8096 > Note that these are exceptions to exceptions from the default! Consider the URL
8099 >"downloads.sourcefroge.net"</SPAN
8100 >: Initially, all actions are deactivated,
8101 so it wouldn't get blocked. Then comes the defaults section, which matches the
8102 URL, but just deactivates the <TT
8105 HREF="actions-file.html#BLOCK"
8109 action once again. Then it matches <TT
8112 >, an exception to the
8113 general non-blocking policy, and suddenly
8117 HREF="actions-file.html#BLOCK"
8120 > applies. And now, it'll match
8127 HREF="actions-file.html#BLOCK"
8131 applies, so (unless it matches <SPAN
8137 > further down) it ends up
8141 HREF="actions-file.html#BLOCK"
8144 > action applying.</P
8154 >##########################################################################
8155 # Save some innocent victims of the above generic block patterns:
8156 ##########################################################################
8161 HREF="actions-file.html#BLOCK"
8164 adv[io]*. # (for advogato.org and advice.*)
8165 adsl. # (has nothing to do with ads)
8166 adobe. # (has nothing to do with ads either)
8167 ad[ud]*. # (adult.* and add.*)
8168 .edu # (universities don't host banners (yet!))
8169 .*loads. # (downloads, uploads etc)
8177 www.globalintersec.com/adv # (adv = advanced)
8178 www.ugu.com/sui/ugu/adv</PRE
8184 > Filtering source code can have nasty side effects,
8185 so make an exception for our friends at sourceforge.net,
8186 and all paths with <SPAN
8189 > in them. Note that
8193 HREF="actions-file.html#FILTER"
8203 > filters in one fell swoop!</P
8213 ># Don't filter code!
8216 HREF="actions-file.html#FILTER"
8223 .sourceforge.net</PRE
8232 > is of course much more
8233 comprehensive, but we hope this example made clear how it works.</P
8241 >8.7.2. user.action</A
8244 > So far we are painting with a broad brush by setting general policies,
8245 which would be a reasonable starting point for many people. Now,
8246 you might want to be more specific and have customized rules that
8247 are more suitable to your personal habits and preferences. These would
8248 be for narrowly defined situations like your ISP or your bank, and should
8252 >, which is parsed after all other
8253 actions files and hence has the last word, over-riding any previously
8254 defined actions. <TT
8264 > place for your personal settings, since
8268 > is actively maintained by the
8272 > developers and you'll probably want
8273 to install updated versions from time to time.</P
8275 > So let's look at a few examples of things that one might typically do in
8289 ># My user.action file. <fred@example.com></PRE
8296 HREF="actions-file.html#ALIASES"
8298 > are local to the actions
8299 file that they are defined in, you can't use the ones from
8303 >, unless you repeat them here:</P
8313 ># Aliases are local to the file they are defined in.
8314 # (Re-)define aliases for this file:
8318 # These aliases just save typing later, and the alias names should
8319 # be self explanatory.
8321 +crunch-all-cookies = +crunch-incoming-cookies +crunch-outgoing-cookies
8322 -crunch-all-cookies = -crunch-incoming-cookies -crunch-outgoing-cookies
8323 allow-all-cookies = -crunch-all-cookies -session-cookies-only
8324 allow-popups = -filter{all-popups} -kill-popups
8325 +block-as-image = +block +handle-as-image
8326 -block-as-image = -block
8328 # These aliases define combinations of actions that are useful for
8329 # certain types of sites:
8331 fragile = -block -crunch-all-cookies -filter -fast-redirects -hide-referrer -kill-popups
8332 shop = -crunch-all-cookies allow-popups
8334 # Allow ads for selected useful free sites:
8336 allow-ads = -block -filter{banners-by-size} -filter{banners-by-link}
8338 # Alias for specific file types that are text, but might have conflicting
8339 # MIME types. We want the browser to force these to be text documents.
8340 handle-as-text = -<A
8341 HREF="actions-file.html#FILTER"
8344 HREF="actions-file.html#CONTENT-TYPE-OVERWRITE"
8345 >content-type-overwrite{text/plain}</A
8347 HREF="actions-file.html#FORCE-TEXT-MODE"
8350 HREF="actions-file.html#HIDE-CONTENT-DISPOSITION"
8351 >hide-content-disposition</A
8358 > Say you have accounts on some sites that you visit regularly, and
8359 you don't want to have to log in manually each time. So you'd like
8360 to allow persistent cookies for these sites. The
8363 >allow-all-cookies</TT
8364 > alias defined above does exactly
8365 that, i.e. it disables crunching of cookies in any direction, and the
8366 processing of cookies to make them only temporary.</P
8376 >{ allow-all-cookies }
8386 > Your bank is allergic to some filter, but you don't know which, so you disable them all:</P
8397 HREF="actions-file.html#FILTER"
8400 .your-home-banking-site.com</PRE
8406 > Some file types you may not want to filter for various reasons:</P
8416 ># Technical documentation is likely to contain strings that might
8417 # erroneously get altered by the JavaScript-oriented filters:
8422 # And this stupid host sends streaming video with a wrong MIME type,
8423 # so that Privoxy thinks it is getting HTML and starts filtering:
8425 stupid-server.example.com/</PRE
8431 > Example of a simple <A
8432 HREF="actions-file.html#BLOCK"
8434 > action. Say you've
8435 seen an ad on your favourite page on example.com that you want to get rid of.
8436 You have right-clicked the image, selected <SPAN
8438 >"copy image location"</SPAN
8440 and pasted the URL below while removing the leading http://, into a
8444 > section. Note that <TT
8448 > need not be specified, since all URLs ending in
8452 > will be tagged as images by the general rules as set
8453 in default.action anyway:</P
8464 HREF="actions-file.html#BLOCK"
8467 www.example.com/nasty-ads/sponsor\.gif
8468 another.example.net/more/junk/here/</PRE
8474 > The URLs of dynamically generated banners, especially from large banner
8475 farms, often don't use the well-known image file name extensions, which
8476 makes it impossible for <SPAN
8480 the file type just by looking at the URL.
8483 >+block-as-image</TT
8484 > alias defined above for
8486 Note that objects which match this rule but then turn out NOT to be an
8487 image are typically rendered as a <SPAN
8489 >"broken image"</SPAN
8491 browser. Use cautiously.</P
8501 >{ +block-as-image }
8511 > Now you noticed that the default configuration breaks Forbes Magazine,
8512 but you were too lazy to find out which action is the culprit, and you
8513 were again too lazy to give <A
8517 you just used the <TT
8520 > alias on the site, and
8527 > -- it worked. The <TT
8531 aliases disables those actions that are most likely to break a site. Also,
8532 good for testing purposes to see if it is <SPAN
8536 that is causing the problem or not. We later find other regular sites
8537 that misbehave, and add those to our personalized list of troublemakers:</P
8556 > You like the <SPAN
8559 > text replacements in <TT
8563 but it is disabled in the distributed actions file.
8564 So you'd like to turn it on in your private,
8565 update-safe config, once and for all:</P
8576 HREF="actions-file.html#FILTER-FUN"
8579 / # For ALL sites!</PRE
8585 > Note that the above is not really a good idea: There are exceptions
8586 to the filters in <TT
8590 really shouldn't be filtered, like code on CVS->Web interfaces. Since
8594 > has the last word, these exceptions
8595 won't be valid for the <SPAN
8598 > filtering specified here.</P
8600 > You might also worry about how your favourite free websites are
8601 funded, and find that they rely on displaying banner advertisements
8602 to survive. So you might want to specifically allow banners for those
8603 sites that you feel provide value to you:</P
8625 > has been aliased to
8629 HREF="actions-file.html#BLOCK"
8636 HREF="actions-file.html#FILTER-BANNERS-BY-SIZE"
8637 >filter{banners-by-size}</A
8643 HREF="actions-file.html#FILTER-BANNERS-BY-LINK"
8644 >filter{banners-by-link}</A
8648 > Invoke another alias here to force an over-ride of the MIME type <TT
8650 > application/x-sh</TT
8651 > which typically would open a download type
8652 dialog. In my case, I want to look at the shell script, and then I can save
8653 it should I choose to.</P
8673 > is generally the best place to define
8674 exceptions and additions to the default policies of
8678 >. Some actions are safe to have their
8679 default policies set here though. So let's set a default policy to have a
8683 > image as opposed to the checkerboard pattern for
8693 > of course matches all URL
8694 paths and patterns:</P
8705 HREF="actions-file.html#SET-IMAGE-BLOCKER"
8706 >set-image-blocker{blank}</A
8721 SUMMARY="Footer navigation table"
8750 HREF="filter-file.html"
8760 >The Main Configuration File</TD
projects / privoxy.git / blob