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.27 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.27 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
109 differing purposes:</P
117 >match-all.action</TT
118 > - is used to define which
122 > relating to banner-blocking, images, pop-ups,
123 content modification, cookie handling etc should be applied by default.
124 It should be the first actions file loaded
132 > - defines many exceptions (both
133 positive and negative) from the default set of actions that's configured
136 >match-all.action</TT
137 >. It is a set of rules that should
138 work reasonably well as-is for most users. This file is only supposed to
139 be edited by the developers. It should be the second actions file loaded.
147 > - is intended to be for local site
148 preferences and exceptions. As an example, if your ISP or your bank
149 has specific requirements, and need special handling, this kind of
150 thing should go here. This file will not be upgraded.
160 >Set to Cautious</SPAN
166 >Set to Advanced</SPAN
170 > These have increasing levels of aggressiveness <SPAN
175 influence on your browsing unless you select them explicitly in the
178 >. A default installation should be pre-set to
182 >. New users should try this for a while before
183 adjusting the settings to more aggressive levels. The more aggressive
184 the settings, then the more likelihood there is of problems such as sites
185 not working as they should.
191 > button allows you to turn each
192 action on/off individually for fine-tuning. The <SPAN
196 button changes the actions list to low/safe settings which will activate
197 ad blocking and a minimal set of <SPAN
200 >'s features, and subsequently
201 there will be less of a chance for accidental problems. The
205 > button sets the list to a medium level of
206 other features and a low level set of privacy features. The
210 > button sets the list to a high level of
211 ad blocking and medium level of privacy. See the chart below. The latter
212 three buttons over-ride any changes via with the
216 > button. More fine-tuning can be done in the
217 lower sections of this internal page.
220 > While the actions file editor allows to enable these settings in all
221 actions files, they are only supposed to be enabled in the first one
222 to make sure you don't unintentionally overrule earlier rules.
225 > The default profiles, and their associated actions, as pre-defined in
238 >Table 1. Default Configurations</B
268 >Ad-blocking Aggressiveness</TD
278 >Ad-filtering by size</TD
288 >Ad-filtering by link</TD
308 >Privacy Features</TD
338 >GIF de-animation</TD
368 >JavaScript taming</TD
388 >Image tag reordering</TD
402 > The list of actions files to be used are defined in the main configuration
403 file, and are processed in the order they are defined (e.g.
407 > is typically processed before
411 >). The content of these can all be viewed and
413 HREF="http://config.privoxy.org/show-status"
415 >http://config.privoxy.org/show-status</A
417 The over-riding principle when applying actions, is that the last action that
418 matches a given URL wins. The broadest, most general rules go first
423 followed by any exceptions (typically also in
427 >), which are then followed lastly by any
428 local preferences (typically in <SPAN
444 > An actions file typically has multiple sections. If you want to use
448 > in an actions file, you have to place the (optional)
450 HREF="actions-file.html#ALIASES"
452 > at the top of that file.
453 Then comes the default set of rules which will apply universally to all
454 sites and pages (be <SPAN
464 > or any other actions file after
468 >, because it will override the result
469 from consulting any previous file). And then below that,
470 exceptions to the defined universal policies. You can regard
474 > as an appendix to <TT
478 with the advantage that it is a separate file, which makes preserving your
479 personal settings across <SPAN
482 > upgrades easier.</P
484 > Actions can be used to block anything you want, including ads, banners, or
485 just some obnoxious URL whose content you would rather not see. Cookies can be accepted
486 or rejected, or accepted only during the current browser session (i.e. not
487 written to disk), content can be modified, some JavaScripts tamed, user-tracking
488 fooled, and much more. See below for a <A
489 HREF="actions-file.html#ACTIONS"
499 >8.1. Finding the Right Mix</A
503 HREF="actions-file.html#ACTIONS"
505 >, like cookie suppression
506 or script disabling, may render some sites unusable that rely on these
507 techniques to work properly. Finding the right mix of actions is not always easy and
508 certainly a matter of personal taste. And, things can always change, requiring
509 refinements in the configuration. In general, it can be said that the more
513 > your default settings (in the top section of the
514 actions file) are, the more exceptions for <SPAN
518 will have to make later. If, for example, you want to crunch all cookies per
519 default, you'll have to make exceptions from that rule for sites that you
520 regularly use and that require cookies for actually useful purposes, like maybe
521 your bank, favorite shop, or newspaper.</P
523 > We have tried to provide you with reasonable rules to start from in the
524 distribution actions files. But there is no general rule of thumb on these
525 things. There just are too many variables, and sites are constantly changing.
526 Sooner or later you will want to change the rules (and read this chapter again :).</P
537 > The easiest way to edit the actions files is with a browser by
538 using our browser-based editor, which can be reached from <A
539 HREF="http://config.privoxy.org/show-status"
541 >http://config.privoxy.org/show-status</A
543 Note: the config file option <A
544 HREF="config.html#ENABLE-EDIT-ACTIONS"
545 >enable-edit-actions</A
546 > must be enabled for
547 this to work. The editor allows both fine-grained control over every single
548 feature on a per-URL basis, and easy choosing from wholesale sets of defaults
559 >. Warning: the <SPAN
563 aggressive, and will be more likely to cause problems for some sites.
564 Experienced users only!
567 > If you prefer plain text editing to GUIs, you can of course also directly edit the
568 the actions files with your favorite text editor. Look at
572 > which is richly commented with many
581 >8.3. How Actions are Applied to Requests</A
584 > Actions files are divided into sections. There are special sections,
588 HREF="actions-file.html#ALIASES"
591 > sections which will
592 be discussed later. For now let's concentrate on regular sections: They have a
593 heading line (often split up to multiple lines for readability) which consist
594 of a list of actions, separated by whitespace and enclosed in curly braces.
595 Below that, there is a list of URL and tag patterns, each on a separate line.</P
597 > To determine which actions apply to a request, the URL of the request is
598 compared to all URL patterns in each <SPAN
602 Every time it matches, the list of applicable actions for the request is
603 incrementally updated, using the heading of the section in which the
604 pattern is located. The same is done again for tags and tag patterns later on.</P
606 > If multiple applying sections set the same action differently,
607 the last match wins. If not, the effects are aggregated.
608 E.g. a URL might match a regular section with a heading line of <TT
612 HREF="actions-file.html#HANDLE-AS-IMAGE"
616 then later another one with just <TT
620 HREF="actions-file.html#BLOCK"
630 > actions to apply. And there may well be
631 cases where you will want to combine actions together. Such a section then
646 >block{Banner ads.}</TT
648 # Block these as if they were images. Send no block page.
650 media.example.com/.*banners
651 .example.com/images/ads/</PRE
656 > You can trace this process for URL patterns and any given URL by visiting <A
657 HREF="http://config.privoxy.org/show-url-info"
659 >http://config.privoxy.org/show-url-info</A
662 > Examples and more detail on this is provided in the Appendix, <A
663 HREF="appendix.html#ACTIONSANAT"
664 > Troubleshooting: Anatomy of an Action</A
676 > As mentioned, <SPAN
683 to determine what <SPAN
689 > might apply to which sites and
690 pages your browser attempts to access. These <SPAN
700 > matching to achieve a high degree of
701 flexibility. This allows one expression to be expanded and potentially match
702 against many similar patterns.</P
704 > Generally, an URL pattern has the form
707 ><host><port>/<path></TT
719 > are optional. (This is why the special
723 > pattern matches all URLs). Note that the protocol
724 portion of the URL pattern (e.g. <TT
734 > be included in the pattern. This is assumed already!</P
736 > The pattern matching syntax is different for the host and path parts of
737 the URL. The host part uses a simple globbing type matching technique,
738 while the path part uses more flexible
740 HREF="http://en.wikipedia.org/wiki/Regular_expressions"
749 > The port part of a pattern is a decimal port number preceded by a colon
753 >). If the host part contains a numerical IPv6 address,
754 it has to be put into angle brackets
770 >www.example.com/</TT
774 > is a host-only pattern and will match any request to <TT
778 regardless of which document on that server is requested. So ALL pages in
779 this domain would be covered by the scope of this action. Note that a
783 > is different and would NOT match.
793 > means exactly the same. For host-only patterns, the trailing <TT
803 >www.example.com/index.html</TT
807 > matches all the documents on <TT
811 whose name starts with <TT
820 >www.example.com/index.html$</TT
824 > matches only the single document <TT
841 > matches the document <TT
844 >, regardless of the domain,
851 > web server anywhere.
861 > Matches any URL because there's no requirement for either the
862 domain or the path to match anything.
872 > Matches any URL pointing to TCP port 8000.
882 > Matches any URL with the host address <TT
886 (Note that the real URL uses plain brackets, not angle brackets.)
892 ><2001:db8::1>/</TT
896 > Matches any URL with the host address <TT
900 (Note that the real URL uses plain brackets, not angle brackets.)
910 > matches nothing, since it would be interpreted as a domain name and
911 there is no top-level domain called <TT
926 >8.4.1. The Host Pattern</A
929 > The matching of the host part offers some flexible options: if the
930 host pattern starts or ends with a dot, it becomes unanchored at that end.
931 The host pattern is often referred to as domain pattern as it is usually
932 used to match domain names and not IP addresses.
946 > matches any domain with first-level domain <TT
950 and second-level domain <TT
963 >foo.bar.baz.example.com</TT
965 Note that it wouldn't match if the second-level domain was <TT
978 > matches any domain that <SPAN
988 > (It also matches the domain
992 > but most of the time that doesn't matter.)
1002 > matches any domain that <SPAN
1012 And, by the way, also included would be any files or documents that exist
1013 within that domain since no path limitations are specified. (Correctly
1014 speaking: It matches any FQDN that contains <TT
1018 a domain.) This might be <TT
1020 >www.example.com</TT
1024 >news.example.de</TT
1028 >www.example.net/cgi/testing.pl</TT
1029 > for instance. All these
1036 > Additionally, there are wild-cards that you can use in the domain names
1037 themselves. These work similarly to shell globbing type wild-cards:
1041 > represents zero or more arbitrary characters (this is
1044 HREF="http://en.wikipedia.org/wiki/Regular_expressions"
1051 > based syntax of <SPAN
1058 > represents any single character (this is equivalent to the
1059 regular expression syntax of a simple <SPAN
1062 >), and you can define
1065 >"character classes"</SPAN
1066 > in square brackets which is similar to
1067 the same regular expression technique. All of this can be freely mixed:</P
1071 CLASS="VARIABLELIST"
1076 >ad*.example.com</TT
1082 >"adserver.example.com"</SPAN
1086 >"ads.example.com"</SPAN
1087 >, etc but not <SPAN
1089 >"sfads.example.com"</SPAN
1096 >*ad*.example.com</TT
1100 > matches all of the above, and then some.
1116 >pictures.epix.com</TT
1119 >a.b.c.d.e.upix.com</TT
1126 >www[1-9a-ez].example.c*</TT
1132 >www1.example.com</TT
1136 >www4.example.cc</TT
1139 >wwwd.example.cy</TT
1143 >wwwz.example.com</TT
1153 >wwww.example.com</TT
1160 > While flexible, this is not the sophistication of full regular expression based syntax.</P
1168 >8.4.2. The Path Pattern</A
1179 HREF="http://en.wikipedia.org/wiki/Regular_expressions"
1186 > for matching the path portion (after the slash),
1187 and is thus more flexible.</P
1190 HREF="appendix.html#REGEX"
1192 > with a brief quick-start into regular
1193 expressions, you also might want to have a look at your operating system's documentation
1194 on regular expressions (try <TT
1199 > Note that the path pattern is automatically left-anchored at the <SPAN
1203 i.e. it matches as if it would start with a <SPAN
1206 > (regular expression speak
1207 for the beginning of a line).</P
1209 > Please also note that matching in the path is <SPAN
1213 >CASE INSENSITIVE</I
1216 by default, but you can switch to case sensitive at any point in the pattern by using the
1222 >www.example.com/(?-i)PaTtErN.*</TT
1224 only documents whose path starts with <TT
1234 > this capitalization.</P
1238 CLASS="VARIABLELIST"
1243 >.example.com/.*</TT
1247 > Is equivalent to just <SPAN
1249 >".example.com"</SPAN
1250 >, since any documents
1251 within that domain are matched with or without the <SPAN
1255 regular expression. This is redundant
1261 >.example.com/.*/index.html$</TT
1265 > Will match any page in the domain of <SPAN
1267 >"example.com"</SPAN
1272 >, and that is part of some path. For
1273 example, it matches <SPAN
1275 >"www.example.com/testing/index.html"</SPAN
1279 >"www.example.com/index.html"</SPAN
1280 > because the regular
1281 expression called for at least two <SPAN
1285 requirement. It also would match
1288 >"www.example.com/testing/index_html"</SPAN
1290 special meta-character <SPAN
1299 >.example.com/(.*/)?index\.html$</TT
1303 > This regular expression is conditional so it will match any page
1307 > regardless of path which in this case can
1308 have one or more <SPAN
1311 >. And this one must contain exactly
1315 > (and end with that!).
1321 >.example.com/(.*/)(ads|banners?|junk)</TT
1325 > This regular expression will match any path of <SPAN
1327 >"example.com"</SPAN
1329 that contains any of the words <SPAN
1339 > (because of the <SPAN
1346 The path does not have to end in these words, just contain them.
1347 The path has to contain at least two slashes (including the one at the beginning).
1353 >.example.com/(.*/)(ads|banners?|junk)/.*\.(jpe?g|gif|png)$</TT
1357 > This is very much the same as above, except now it must end in either
1371 one is limited to common image formats.
1377 > There are many, many good examples to be found in <TT
1381 and more tutorials below in <A
1382 HREF="appendix.html#REGEX"
1383 >Appendix on regular expressions</A
1392 >8.4.3. The Request Tag Pattern</A
1395 > Request tag patterns are used to change the applying actions based on the
1396 request's tags. Tags can be created based on HTTP headers with either
1398 HREF="actions-file.html#CLIENT-HEADER-TAGGER"
1399 >client-header-tagger</A
1402 HREF="actions-file.html#SERVER-HEADER-TAGGER"
1403 >server-header-tagger</A
1406 > Request tag patterns have to start with <SPAN
1413 can tell them apart from other patterns. Everything after the colon
1414 including white space, is interpreted as a regular expression with
1415 path pattern syntax, except that tag patterns aren't left-anchored
1416 automatically (<SPAN
1419 > doesn't silently add a <SPAN
1423 you have to do it yourself if you need it).</P
1425 > To match all requests that are tagged with <SPAN
1429 your pattern line should be <SPAN
1436 > would work as well, but it would also
1437 match requests whose tags contain <SPAN
1444 > wouldn't work as it requires white space.</P
1446 > Sections can contain URL and request tag patterns at the same time,
1447 but request tag patterns are checked after the URL patterns and thus
1448 always overrule them, even if they are located before the URL patterns.</P
1450 > Once a new request tag is added, Privoxy checks right away if it's matched by one
1451 of the request tag patterns and updates the action settings accordingly. As a result
1452 request tags can be used to activate other tagger actions, as long as these other
1453 taggers look for headers that haven't already be parsed.</P
1455 > For example you could tag client requests which use the
1460 then use this tag to activate another tagger that adds a tag if cookies
1461 are sent, and then use a block action based on the cookie tag. This allows
1462 the outcome of one action, to be input into a subsequent action. However if
1463 you'd reverse the position of the described taggers, and activated the
1464 method tagger based on the cookie tagger, no method tags would be created.
1465 The method tagger would look for the request line, but at the time
1466 the cookie tag is created, the request line has already been parsed.</P
1468 > While this is a limitation you should be aware of, this kind of
1469 indirection is seldom needed anyway and even the example doesn't
1470 make too much sense.</P
1477 NAME="NEGATIVE-TAG-PATTERNS"
1478 >8.4.4. The Negative Request Tag Patterns</A
1481 > To match requests that do not have a certain request tag, specify a negative tag pattern
1482 by prefixing the tag pattern line with either <SPAN
1484 >"NO-REQUEST-TAG:"</SPAN
1488 >"NO-RESPONSE-TAG:"</SPAN
1494 > Negative request tag patterns created with <SPAN
1496 >"NO-REQUEST-TAG:"</SPAN
1498 after all client headers are scanned, the ones created with <SPAN
1500 >"NO-RESPONSE-TAG:"</SPAN
1502 are checked after all server headers are scanned. In both cases all the created
1503 tags are considered.</P
1510 NAME="CLIENT-TAG-PATTERN"
1511 >8.4.5. The Client Tag Pattern</A
1532 > This is an experimental feature. The syntax is likely to change in future versions.</P
1538 > Client tag patterns are not set based on HTTP headers but based on
1539 the client's IP address. Users can enable them themselves, but the
1540 Privoxy admin controls which tags are available and what their effect
1543 > After a client-specific tag has been defined with the
1545 HREF="config.html#CLIENT-SPECIFIC-TAG"
1546 >client-specific-tag</A
1548 directive, action sections can be activated based on the tag by using a
1549 CLIENT-TAG pattern. The CLIENT-TAG pattern is evaluated at the same priority
1550 as URL patterns, as a result the last matching pattern wins. Tags that
1551 are created based on client or server headers are evaluated later on
1552 and can overrule CLIENT-TAG and URL patterns!</P
1554 > The tag is set for all requests that come from clients that requested
1555 it to be set. Note that "clients" are differentiated by IP address,
1556 if the IP address changes the tag has to be requested again.</P
1558 > Clients can request tags to be set by using the CGI interface <A
1559 HREF="http://config.privoxy.org/client-tags"
1561 >http://config.privoxy.org/client-tags</A
1573 ># If the admin defined the client-specific-tag circumvent-blocks,
1574 # and the request comes from a client that previously requested
1575 # the tag to be set, overrule all previous +block actions that
1576 # are enabled based on URL to CLIENT-TAG patterns.
1578 CLIENT-TAG:^circumvent-blocks$
1580 # This section is not overruled because it's located after
1582 {+block{Nobody is supposed to request this.}}
1583 example.org/blocked-example-page</PRE
1598 > All actions are disabled by default, until they are explicitly enabled
1599 somewhere in an actions file. Actions are turned on if preceded with a
1603 >, and turned off if preceded with a <SPAN
1612 >"do that action"</SPAN
1619 >"please block URLs that match the
1620 following patterns"</SPAN
1627 block URLs that match the following patterns, even if <TT
1631 previously applied."</SPAN
1634 > Again, actions are invoked by placing them on a line, enclosed in curly braces and
1635 separated by whitespace, like in
1638 >{+some-action -some-other-action{some-parameter}}</TT
1640 followed by a list of URL patterns, one per line, to which they apply.
1641 Together, the actions line and the following pattern lines make up a section
1642 of the actions file.</P
1644 > Actions fall into three categories:</P
1650 > Boolean, i.e the action can only be <SPAN
1672 > # enable action <TT
1683 > # disable action <TT
1695 >+handle-as-image</TT
1701 > Parameterized, where some value is required in order to enable this type of action.
1722 >} # enable action and set parameter to <TT
1728 # overwriting parameter from previous match if necessary
1734 > # disable action. The parameter can be omitted</PRE
1739 > Note that if the URL matches multiple positive forms of a parameterized action,
1740 the last match wins, i.e. the params from earlier matches are simply ignored.
1745 >+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
1751 > Multi-value. These look exactly like parameterized actions,
1752 but they behave differently: If the action applies multiple times to the
1753 same URL, but with different parameters, <SPAN
1766 > matches are remembered. This is used for actions
1767 that can be executed for the same request repeatedly, like adding multiple
1768 headers, or filtering through multiple filters. Syntax:
1788 >} # enable action and add <TT
1793 > to the list of parameters
1804 >} # remove the parameter <TT
1809 > from the list of parameters
1810 # If it was the last one left, disable the action.
1816 > # disable this action completely and remove all parameters from the list</PRE
1823 >+add-header{X-Fun-Header: Some text}</TT
1827 >+filter{html-annoyances}</TT
1833 > If nothing is specified in any actions file, no <SPAN
1837 taken. So in this case <SPAN
1841 normal, non-blocking, non-filtering proxy. You must specifically enable the
1842 privacy and blocking features you need (although the provided default actions
1843 files will give a good starting point).</P
1845 > Later defined action sections always over-ride earlier ones of the same type.
1846 So exceptions to any rules you make, should come in the latter part of the file (or
1847 in a file that is processed later when using multiple actions files such
1851 >). For multi-valued actions, the actions
1852 are applied in the order they are specified. Actions files are processed in
1853 the order they are defined in <TT
1857 installation has three actions files). It also quite possible for any given
1858 URL to match more than one <SPAN
1861 > (because of wildcards and
1862 regular expressions), and thus to trigger more than one set of actions! Last
1865 > The list of valid <SPAN
1875 >8.5.1. add-header</A
1880 CLASS="VARIABLELIST"
1886 >Confuse log analysis, custom applications</P
1892 > Sends a user defined HTTP header to the web server.
1905 > Any string value is possible. Validity of the defined HTTP headers is not checked.
1906 It is recommended that you use the <SPAN
1920 > This action may be specified multiple times, in order to define multiple
1921 headers. This is rarely needed for the typical user. If you don't know what
1924 >"HTTP headers"</SPAN
1925 > are, you definitely don't need to worry about this
1929 > Headers added by this action are not modified by other actions.
1943 ># Add a DNT ("Do not track") header to all requests,
1944 # event to those that already have one.
1946 # This is just an example, not a recommendation.
1948 # There is no reason to believe that user-tracking websites care
1949 # about the DNT header and depending on the User-Agent, adding the
1950 # header may make user-tracking easier.
1951 {+add-header{DNT: 1}}
1971 CLASS="VARIABLELIST"
1977 >Block ads or other unwanted content</P
1983 > Requests for URLs to which this action applies are blocked, i.e. the
1984 requests are trapped by <SPAN
1987 > and the requested URL is never retrieved,
1988 but is answered locally with a substitute page or image, as determined by
1992 HREF="actions-file.html#HANDLE-AS-IMAGE"
1999 HREF="actions-file.html#SET-IMAGE-BLOCKER"
2000 >set-image-blocker</A
2006 HREF="actions-file.html#HANDLE-AS-EMPTY-DOCUMENT"
2007 >handle-as-empty-document</A
2023 >A block reason that should be given to the user.</P
2032 > sends a special <SPAN
2036 for requests to blocked pages. This page contains the block reason given as
2037 parameter, a link to find out why the block action applies, and a click-through
2038 to the blocked content (the latter only if the force feature is available and
2042 > A very important exception occurs if <SPAN
2055 HREF="actions-file.html#HANDLE-AS-IMAGE"
2059 apply to the same request: it will then be replaced by an image. If
2063 HREF="actions-file.html#SET-IMAGE-BLOCKER"
2064 >set-image-blocker</A
2067 (see below) also applies, the type of image will be determined by its parameter,
2068 if not, the standard checkerboard pattern is sent.
2071 > It is important to understand this process, in order
2072 to understand how <SPAN
2076 ads and other unwanted content. Blocking is a core feature, and one
2077 upon which various other features depend.
2083 HREF="actions-file.html#FILTER"
2087 action can perform a very similar task, by <SPAN
2091 banner images and other content through rewriting the relevant URLs in the
2092 document's HTML source, so they don't get requested in the first place.
2093 Note that this is a totally different technique, and it's easy to confuse the two.
2097 >Example usage (section):</DT
2107 >{+block{No nasty stuff for you.}}
2108 # Block and replace with "blocked" page
2109 .nasty-stuff.example.com
2111 {+block{Doubleclick banners.} +handle-as-image}
2112 # Block and replace with image
2116 {+block{Layered ads.} +handle-as-empty-document}
2117 # Block and then ignore
2118 adserver.example.net/.*\.js$</PRE
2131 NAME="CHANGE-X-FORWARDED-FOR"
2132 >8.5.3. change-x-forwarded-for</A
2137 CLASS="VARIABLELIST"
2143 >Improve privacy by not forwarding the source of the request in the HTTP headers.</P
2151 >"X-Forwarded-For:"</SPAN
2152 > HTTP header from the client request,
2173 > to delete the header.</P
2180 > to create the header (or append
2181 the client's IP address to an already existing one).
2190 > It is safe and recommended to use <TT
2196 > Forwarding the source address of the request may make
2197 sense in some multi-user setups but is also a privacy risk.
2211 >+change-x-forwarded-for{block}</PRE
2224 NAME="CLIENT-HEADER-FILTER"
2225 >8.5.4. client-header-filter</A
2230 CLASS="VARIABLELIST"
2236 > Rewrite or remove single client headers.
2243 > All client headers to which this action applies are filtered on-the-fly through
2244 the specified regular expression based substitutions.
2257 > The name of a client-header filter, as defined in one of the
2259 HREF="filter-file.html"
2268 > Client-header filters are applied to each header on its own, not to
2269 all at once. This makes it easier to diagnose problems, but on the downside
2270 you can't write filters that only change header x if header y's value is z.
2271 You can do that by using tags though.
2274 > Client-header filters are executed after the other header actions have finished
2275 and use their output as input.
2278 > If the request URI gets changed, <SPAN
2281 > will detect that and use the new
2282 one. This can be used to rewrite the request destination behind the client's
2283 back, for example to specify a Tor exit relay for certain requests.
2286 > Please refer to the <A
2287 HREF="filter-file.html"
2288 >filter file chapter</A
2290 to learn which client-header filters are available by default, and how to
2295 >Example usage (section):</DT
2305 ># Hide Tor exit notation in Host and Referer Headers
2306 {+client-header-filter{hide-tor-exit-notation}}
2320 NAME="CLIENT-HEADER-TAGGER"
2321 >8.5.5. client-header-tagger</A
2326 CLASS="VARIABLELIST"
2332 > Block requests based on their headers.
2339 > Client headers to which this action applies are filtered on-the-fly through
2340 the specified regular expression based substitutions, the result is used as
2354 > The name of a client-header tagger, as defined in one of the
2356 HREF="filter-file.html"
2365 > Client-header taggers are applied to each header on its own,
2366 and as the header isn't modified, each tagger <SPAN
2373 > Client-header taggers are the first actions that are executed
2374 and their tags can be used to control every other action.
2378 >Example usage (section):</DT
2388 ># Tag every request with the User-Agent header
2389 {+client-header-tagger{user-agent}}
2392 # Tagging itself doesn't change the action
2393 # settings, sections with TAG patterns do:
2395 # If it's a download agent, use a different forwarding proxy,
2396 # show the real User-Agent and make sure resume works.
2397 {+forward-override{forward-socks5 10.0.0.2:2222 .} \
2398 -hide-if-modified-since \
2399 -overwrite-last-modified \
2404 TAG:^User-Agent: NetBSD-ftp/
2405 TAG:^User-Agent: Novell ZYPP Installer
2406 TAG:^User-Agent: RPM APT-HTTP/
2407 TAG:^User-Agent: fetch libfetch/
2408 TAG:^User-Agent: Ubuntu APT-HTTP/
2409 TAG:^User-Agent: MPlayer/</PRE
2421 ># Tag all requests with the Range header set
2422 {+client-header-tagger{range-requests}}
2425 # Disable filtering for the tagged requests.
2427 # With filtering enabled Privoxy would remove the Range headers
2428 # to be able to filter the whole response. The downside is that
2429 # it prevents clients from resuming downloads or skipping over
2430 # parts of multimedia files.
2431 {-filter -deanimate-gifs}
2432 TAG:^RANGE-REQUEST$</PRE
2444 ># Tag all requests with the client IP address
2446 # (Technically the client IP address isn't included in the
2447 # client headers but client-header taggers can set it anyway.
2448 # For details see the tagger in default.filter)
2449 {+client-header-tagger{client-ip-address}}
2452 # Change forwarding settings for requests coming from address 10.0.0.1
2453 {+forward-override{forward-socks5 127.0.1.2:2222 .}}
2454 TAG:^IP-ADDRESS: 10\.0\.0\.1$</PRE
2467 NAME="CONTENT-TYPE-OVERWRITE"
2468 >8.5.6. content-type-overwrite</A
2473 CLASS="VARIABLELIST"
2479 >Stop useless download menus from popping up, or change the browser's rendering mode</P
2485 > Replaces the <SPAN
2487 >"Content-Type:"</SPAN
2488 > HTTP server header.
2510 >"Content-Type:"</SPAN
2511 > HTTP server header is used by the
2512 browser to decide what to do with the document. The value of this
2513 header can cause the browser to open a download menu instead of
2514 displaying the document by itself, even if the document's format is
2515 supported by the browser.
2518 > The declared content type can also affect which rendering mode
2519 the browser chooses. If XHTML is delivered as <SPAN
2523 many browsers treat it as yet another broken HTML document.
2524 If it is send as <SPAN
2526 >"application/xml"</SPAN
2528 XHTML support will only display it, if the syntax is correct.
2531 > If you see a web site that proudly uses XHTML buttons, but sets
2534 >"Content-Type: text/html"</SPAN
2535 >, you can use <SPAN
2539 to overwrite it with <SPAN
2541 >"application/xml"</SPAN
2543 the web master's claim inside your XHTML-supporting browser.
2544 If the syntax is incorrect, the browser will complain loudly.
2547 > You can also go the opposite direction: if your browser prints
2548 error messages instead of rendering a document falsely declared
2549 as XHTML, you can overwrite the content type with
2553 > and have it rendered as broken HTML document.
2558 >content-type-overwrite</TT
2562 >"Content-Type:"</SPAN
2563 > headers that look like some kind of text.
2564 If you want to overwrite it unconditionally, you have to combine it with
2568 HREF="actions-file.html#FORCE-TEXT-MODE"
2572 This limitation exists for a reason, think twice before circumventing it.
2575 > Most of the time it's easier to replace this action with a custom
2579 HREF="actions-file.html#SERVER-HEADER-FILTER"
2580 >server-header filter</A
2583 It allows you to activate it for every document of a certain site and it will still
2584 only replace the content types you aimed at.
2587 > Of course you can apply <TT
2589 >content-type-overwrite</TT
2591 to a whole site and then make URL based exceptions, but it's a lot
2592 more work to get the same precision.
2596 >Example usage (sections):</DT
2606 ># Check if www.example.net/ really uses valid XHTML
2607 { +content-type-overwrite{application/xml} }
2610 # but leave the content type unmodified if the URL looks like a style sheet
2611 {-content-type-overwrite}
2612 www.example.net/.*\.css$
2613 www.example.net/.*style</PRE
2626 NAME="CRUNCH-CLIENT-HEADER"
2627 >8.5.7. crunch-client-header</A
2632 CLASS="VARIABLELIST"
2638 >Remove a client header <SPAN
2641 > has no dedicated action for.</P
2647 > Deletes every header sent by the client that contains the string the user supplied as parameter.
2667 > This action allows you to block client headers for which no dedicated
2675 > will remove every client header that
2676 contains the string you supplied as parameter.
2679 > Regular expressions are <SPAN
2686 use this action to block different headers in the same request, unless
2687 they contain the same string.
2692 >crunch-client-header</TT
2693 > is only meant for quick tests.
2694 If you have to block several different headers, or only want to modify
2695 parts of them, you should use a
2699 HREF="actions-file.html#CLIENT-HEADER-FILTER"
2700 >client-header filter</A
2723 > Don't block any header without understanding the consequences.
2731 >Example usage (section):</DT
2741 ># Block the non-existent "Privacy-Violation:" client header
2742 { +crunch-client-header{Privacy-Violation:} }
2756 NAME="CRUNCH-IF-NONE-MATCH"
2757 >8.5.8. crunch-if-none-match</A
2762 CLASS="VARIABLELIST"
2768 >Prevent yet another way to track the user's steps between sessions.</P
2776 >"If-None-Match:"</SPAN
2777 > HTTP client header.
2797 > Removing the <SPAN
2799 >"If-None-Match:"</SPAN
2800 > HTTP client header
2801 is useful for filter testing, where you want to force a real
2802 reload instead of getting status code <SPAN
2806 would cause the browser to use a cached copy of the page.
2809 > It is also useful to make sure the header isn't used as a cookie
2810 replacement (unlikely but possible).
2813 > Blocking the <SPAN
2815 >"If-None-Match:"</SPAN
2816 > header shouldn't cause any
2817 caching problems, as long as the <SPAN
2819 >"If-Modified-Since:"</SPAN
2821 isn't blocked or missing as well.
2824 > It is recommended to use this action together with
2828 HREF="actions-file.html#HIDE-IF-MODIFIED-SINCE"
2829 >hide-if-modified-since</A
2836 HREF="actions-file.html#OVERWRITE-LAST-MODIFIED"
2837 >overwrite-last-modified</A
2843 >Example usage (section):</DT
2853 ># Let the browser revalidate cached documents but don't
2854 # allow the server to use the revalidation headers for user tracking.
2855 {+hide-if-modified-since{-60} \
2856 +overwrite-last-modified{randomize} \
2857 +crunch-if-none-match}
2871 NAME="CRUNCH-INCOMING-COOKIES"
2872 >8.5.9. crunch-incoming-cookies</A
2877 CLASS="VARIABLELIST"
2883 > Prevent the web server from setting HTTP cookies on your system
2892 >"Set-Cookie:"</SPAN
2893 > HTTP headers from server replies.
2913 > This action is only concerned with <SPAN
2930 HREF="actions-file.html#CRUNCH-OUTGOING-COOKIES"
2931 >crunch-outgoing-cookies</A
2940 > to disable HTTP cookies completely.
2949 > to use this action in conjunction
2953 HREF="actions-file.html#SESSION-COOKIES-ONLY"
2954 >session-cookies-only</A
2957 since it would prevent the session cookies from being set. See also
2961 HREF="actions-file.html#FILTER-CONTENT-COOKIES"
2962 >filter-content-cookies</A
2978 >+crunch-incoming-cookies</PRE
2991 NAME="CRUNCH-SERVER-HEADER"
2992 >8.5.10. crunch-server-header</A
2997 CLASS="VARIABLELIST"
3003 >Remove a server header <SPAN
3006 > has no dedicated action for.</P
3012 > Deletes every header sent by the server that contains the string the user supplied as parameter.
3032 > This action allows you to block server headers for which no dedicated
3036 > action exists. <SPAN
3040 will remove every server header that contains the string you supplied as parameter.
3043 > Regular expressions are <SPAN
3050 use this action to block different headers in the same request, unless
3051 they contain the same string.
3056 >crunch-server-header</TT
3057 > is only meant for quick tests.
3058 If you have to block several different headers, or only want to modify
3059 parts of them, you should use a custom
3063 HREF="actions-file.html#SERVER-HEADER-FILTER"
3064 >server-header filter</A
3087 > Don't block any header without understanding the consequences.
3095 >Example usage (section):</DT
3105 ># Crunch server headers that try to prevent caching
3106 { +crunch-server-header{no-cache} }
3120 NAME="CRUNCH-OUTGOING-COOKIES"
3121 >8.5.11. crunch-outgoing-cookies</A
3126 CLASS="VARIABLELIST"
3132 > Prevent the web server from reading any HTTP cookies from your system
3142 > HTTP headers from client requests.
3162 > This action is only concerned with <SPAN
3179 HREF="actions-file.html#CRUNCH-INCOMING-COOKIES"
3180 >crunch-incoming-cookies</A
3189 > to disable HTTP cookies completely.
3198 > to use this action in conjunction
3202 HREF="actions-file.html#SESSION-COOKIES-ONLY"
3203 >session-cookies-only</A
3206 since it would prevent the session cookies from being read.
3220 >+crunch-outgoing-cookies</PRE
3233 NAME="DEANIMATE-GIFS"
3234 >8.5.12. deanimate-gifs</A
3239 CLASS="VARIABLELIST"
3245 >Stop those annoying, distracting animated GIF images.</P
3251 > De-animate GIF animations, i.e. reduce them to their first or last image.
3277 > This will also shrink the images considerably (in bytes, not pixels!). If
3281 > is given, the first frame of the animation
3282 is used as the replacement. If <SPAN
3285 > is given, the last
3286 frame of the animation is used instead, which probably makes more sense for
3287 most banner animations, but also has the risk of not showing the entire
3288 last frame (if it is only a delta to an earlier frame).
3291 > You can safely use this action with patterns that will also match non-GIF
3292 objects, because no attempt will be made at anything that doesn't look like
3307 >+deanimate-gifs{last}</PRE
3320 NAME="DOWNGRADE-HTTP-VERSION"
3321 >8.5.13. downgrade-http-version</A
3326 CLASS="VARIABLELIST"
3332 >Work around (very rare) problems with HTTP/1.1</P
3338 > Downgrades HTTP/1.1 client requests and server replies to HTTP/1.0.
3358 > This is a left-over from the time when <SPAN
3362 didn't support important HTTP/1.1 features well. It is left here for the
3363 unlikely case that you experience HTTP/1.1-related problems with some server
3367 > Note that enabling this action is only a workaround. It should not
3368 be enabled for sites that work without it. While it shouldn't break
3369 any pages, it has an (usually negative) performance impact.
3372 > If you come across a site where enabling this action helps, please report it,
3373 so the cause of the problem can be analyzed. If the problem turns out to be
3374 caused by a bug in <SPAN
3378 fixed so the following release works without the work around.
3382 >Example usage (section):</DT
3392 >{+downgrade-http-version}
3393 problem-host.example.com</PRE
3406 NAME="EXTERNAL-FILTER"
3407 >8.5.14. external-filter</A
3412 CLASS="VARIABLELIST"
3418 >Modify content using a programming language of your choice.</P
3424 > All instances of text-based type, most notably HTML and JavaScript, to which
3425 this action applies, can be filtered on-the-fly through the specified external
3427 By default plain text documents are exempted from filtering, because web
3428 servers often use the <TT
3431 > MIME type for all files
3432 whose type they don't know.)
3445 > The name of an external content filter, as defined in the
3447 HREF="filter-file.html"
3450 External filters can be defined in one or more files as defined by the
3454 HREF="config.html#FILTERFILE"
3464 > When used in its negative form,
3465 and without parameters, <SPAN
3471 > filtering with external
3472 filters is completely disabled.
3479 > External filters are scripts or programs that can modify the content in
3483 HREF="actions-file.html#FILTER"
3487 aren't powerful enough. With the exception that this action doesn't
3488 use pcrs-based filters, the notes in the
3492 HREF="actions-file.html#FILTER"
3516 > Currently external filters are executed with <SPAN
3520 Only use external filters you understand and trust.
3527 > This feature is experimental, the <TT
3530 HREF="filter-file.html#EXTERNAL-FILTER-SYNTAX"
3534 may change in the future.
3548 >+external-filter{fancy-filter}</PRE
3561 NAME="FAST-REDIRECTS"
3562 >8.5.15. fast-redirects</A
3567 CLASS="VARIABLELIST"
3573 >Fool some click-tracking scripts and speed up indirect links.</P
3579 > Detects redirection URLs and redirects the browser without contacting
3580 the redirection server first.
3599 >"simple-check"</SPAN
3600 > to just search for the string <SPAN
3604 to detect redirection URLs.
3611 >"check-decoded-url"</SPAN
3612 > to decode URLs (if necessary) before searching
3613 for redirection URLs.
3622 > Many sites, like yahoo.com, don't just link to other sites. Instead, they
3623 will link to some script on their own servers, giving the destination as a
3624 parameter, which will then redirect you to the final target. URLs
3625 resulting from this scheme typically look like:
3628 >"http://www.example.org/click-tracker.cgi?target=http%3a//www.example.net/"</SPAN
3632 > Sometimes, there are even multiple consecutive redirects encoded in the
3633 URL. These redirections via scripts make your web browsing more traceable,
3634 since the server from which you follow such a link can see where you go
3635 to. Apart from that, valuable bandwidth and time is wasted, while your
3636 browser asks the server for one redirect after the other. Plus, it feeds
3640 > This feature is currently not very smart and is scheduled for improvement.
3641 If it is enabled by default, you will have to create some exceptions to
3642 this action. It can lead to failures in several ways:
3645 > Not every URLs with other URLs as parameters is evil.
3646 Some sites offer a real service that requires this information to work.
3647 For example a validation service needs to know, which document to validate.
3651 > assumes that every URL parameter that
3652 looks like another URL is a redirection target, and will always redirect to
3653 the last one. Most of the time the assumption is correct, but if it isn't,
3654 the user gets redirected anyway.
3657 > Another failure occurs if the URL contains other parameters after the URL parameter.
3661 >"http://www.example.org/?redirect=http%3a//www.example.net/&foo=bar"</SPAN
3663 contains the redirection URL <SPAN
3665 >"http://www.example.net/"</SPAN
3667 followed by another parameter. <TT
3671 and will cause a redirect to <SPAN
3673 >"http://www.example.net/&foo=bar"</SPAN
3675 Depending on the target server configuration, the parameter will be silently ignored
3678 >"page not found"</SPAN
3679 > error. You can prevent this problem by
3683 HREF="actions-file.html#REDIRECT"
3687 to remove the last part of the URL, but it requires a little effort.
3690 > To detect a redirection URL, <TT
3694 looks for the string <SPAN
3697 >, either in plain text
3698 (invalid but often used) or encoded as <SPAN
3702 Some sites use their own URL encoding scheme, encrypt the address
3703 of the target server or replace it with a database id. In theses cases
3707 > is fooled and the request reaches the
3708 redirection server where it probably gets logged.
3722 > { +fast-redirects{simple-check} }
3725 { +fast-redirects{check-decoded-url} }
3726 another.example.com/testing</PRE
3745 CLASS="VARIABLELIST"
3751 >Get rid of HTML and JavaScript annoyances, banner advertisements (by size),
3752 do fun text replacements, add personalized effects, etc.</P
3758 > All instances of text-based type, most notably HTML and JavaScript, to which
3759 this action applies, can be filtered on-the-fly through the specified regular
3760 expression based substitutions. (Note: as of version 3.0.3 plain text documents
3761 are exempted from filtering, because web servers often use the
3765 > MIME type for all files whose type they don't know.)
3778 > The name of a content filter, as defined in the <A
3779 HREF="filter-file.html"
3782 Filters can be defined in one or more files as defined by the
3786 HREF="config.html#FILTERFILE"
3797 > is the collection of filters
3798 supplied by the developers. Locally defined filters should go
3799 in their own file, such as <TT
3805 > When used in its negative form,
3806 and without parameters, <SPAN
3812 > filtering is completely disabled.
3819 > For your convenience, there are a number of pre-defined filters available
3820 in the distribution filter file that you can use. See the examples below for
3824 > Filtering requires buffering the page content, which may appear to
3825 slow down page rendering since nothing is displayed until all content has
3826 passed the filters. (The total time until the page is completely rendered
3827 doesn't change much, but it may be perceived as slower since the page is
3828 not incrementally displayed.)
3829 This effect will be more noticeable on slower connections.
3834 >"Rolling your own"</SPAN
3836 filters requires a knowledge of
3838 HREF="http://en.wikipedia.org/wiki/Regular_expressions"
3847 HREF="http://en.wikipedia.org/wiki/Html"
3854 This is very powerful feature, and potentially very intrusive.
3855 Filters should be used with caution, and where an equivalent
3862 > The amount of data that can be filtered is limited to the
3866 HREF="config.html#BUFFER-LIMIT"
3870 option in the main <A
3874 default is 4096 KB (4 Megs). Once this limit is exceeded, the buffered
3875 data, and all pending data, is passed through unfiltered.
3878 > Inappropriate MIME types, such as zipped files, are not filtered at all.
3879 (Again, only text-based types except plain text). Encrypted SSL data
3880 (from HTTPS servers) cannot be filtered either, since this would violate
3881 the integrity of the secure transaction. In some situations it might
3882 be necessary to protect certain text, like source code, from filtering
3883 by defining appropriate <TT
3889 > Compressed content can't be filtered either, but if <SPAN
3893 is compiled with zlib support and a supported compression algorithm
3894 is used (gzip or deflate), <SPAN
3897 > can first decompress the content
3901 > If you use a <SPAN
3904 > version without zlib support, but want filtering to work on
3905 as much documents as possible, even those that would normally be sent compressed,
3906 you must use the <TT
3909 HREF="actions-file.html#PREVENT-COMPRESSION"
3910 >prevent-compression</A
3913 action in conjunction with <TT
3919 > Content filtering can achieve some of the same effects as the
3923 HREF="actions-file.html#BLOCK"
3927 action, i.e. it can be used to block ads and banners. But the mechanism
3928 works quite differently. One effective use, is to block ad banners
3929 based on their size (see below), since many of these seem to be somewhat
3936 > with suggestions for new or
3937 improved filters is particularly welcome!
3940 > The below list has only the names and a one-line description of each
3941 predefined filter. There are <A
3942 HREF="filter-file.html#PREDEFINED-FILTERS"
3944 verbose explanations</A
3945 > of what these filters do in the <A
3946 HREF="filter-file.html"
3947 >filter file chapter</A
3952 >Example usage (with filters from the distribution <TT
3957 HREF="filter-file.html#PREDEFINED-FILTERS"
3958 >the Predefined Filters section</A
3960 more explanation on each:</DT
3964 NAME="FILTER-JS-ANNOYANCES"
3976 >+filter{js-annoyances} # Get rid of particularly annoying JavaScript abuse.</PRE
3982 NAME="FILTER-JS-EVENTS"
3994 >+filter{js-events} # Kill JavaScript event bindings and timers (Radically destructive! Only for extra nasty sites).</PRE
4000 NAME="FILTER-HTML-ANNOYANCES"
4012 >+filter{html-annoyances} # Get rid of particularly annoying HTML abuse.</PRE
4018 NAME="FILTER-CONTENT-COOKIES"
4030 >+filter{content-cookies} # Kill cookies that come in the HTML or JS content.</PRE
4036 NAME="FILTER-REFRESH-TAGS"
4048 >+filter{refresh-tags} # Kill automatic refresh tags if refresh time is larger than 9 seconds.</PRE
4054 NAME="FILTER-UNSOLICITED-POPUPS"
4066 >+filter{unsolicited-popups} # Disable only unsolicited pop-up windows.</PRE
4072 NAME="FILTER-ALL-POPUPS"
4084 >+filter{all-popups} # Kill all popups in JavaScript and HTML.</PRE
4090 NAME="FILTER-IMG-REORDER"
4102 >+filter{img-reorder} # Reorder attributes in <img> tags to make the banners-by-* filters more effective.</PRE
4108 NAME="FILTER-BANNERS-BY-SIZE"
4120 >+filter{banners-by-size} # Kill banners by size.</PRE
4126 NAME="FILTER-BANNERS-BY-LINK"
4138 >+filter{banners-by-link} # Kill banners by their links to known clicktrackers.</PRE
4144 NAME="FILTER-WEBBUGS"
4156 >+filter{webbugs} # Squish WebBugs (1x1 invisible GIFs used for user tracking).</PRE
4162 NAME="FILTER-TINY-TEXTFORMS"
4174 >+filter{tiny-textforms} # Extend those tiny textareas up to 40x80 and kill the hard wrap.</PRE
4180 NAME="FILTER-JUMPING-WINDOWS"
4192 >+filter{jumping-windows} # Prevent windows from resizing and moving themselves.</PRE
4198 NAME="FILTER-FRAMESET-BORDERS"
4210 >+filter{frameset-borders} # Give frames a border and make them resizable.</PRE
4216 NAME="FILTER-IFRAMES"
4228 >+filter{iframes} # Removes all detected iframes. Should only be enabled for individual sites.</PRE
4234 NAME="FILTER-DEMORONIZER"
4246 >+filter{demoronizer} # Fix MS's non-standard use of standard charsets.</PRE
4252 NAME="FILTER-SHOCKWAVE-FLASH"
4264 >+filter{shockwave-flash} # Kill embedded Shockwave Flash objects.</PRE
4270 NAME="FILTER-QUICKTIME-KIOSKMODE"
4282 >+filter{quicktime-kioskmode} # Make Quicktime movies saveable.</PRE
4300 >+filter{fun} # Text replacements for subversive browsing fun!</PRE
4306 NAME="FILTER-CRUDE-PARENTAL"
4318 >+filter{crude-parental} # Crude parental filtering. Note that this filter doesn't work reliably.</PRE
4324 NAME="FILTER-IE-EXPLOITS"
4336 >+filter{ie-exploits} # Disable some known Internet Explorer bug exploits.</PRE
4342 NAME="FILTER-SITE-SPECIFICS"
4354 >+filter{site-specifics} # Cure for site-specific problems. Don't apply generally!</PRE
4360 NAME="FILTER-NO-PING"
4372 >+filter{no-ping} # Removes non-standard ping attributes in <a> and <area> tags.</PRE
4378 NAME="FILTER-GOOGLE"
4390 >+filter{google} # CSS-based block for Google text ads. Also removes a width limitation and the toolbar advertisement.</PRE
4408 >+filter{yahoo} # CSS-based block for Yahoo text ads. Also removes a width limitation.</PRE
4426 >+filter{msn} # CSS-based block for MSN text ads. Also removes tracking URLs and a width limitation.</PRE
4432 NAME="FILTER-BLOGSPOT"
4444 >+filter{blogspot} # Cleans up some Blogspot blogs. Read the fine print before using this.</PRE
4457 NAME="FORCE-TEXT-MODE"
4458 >8.5.17. force-text-mode</A
4463 CLASS="VARIABLELIST"
4472 > to treat a document as if it was in some kind of <SPAN
4484 > Declares a document as text, even if the <SPAN
4486 >"Content-Type:"</SPAN
4487 > isn't detected as such.
4510 HREF="actions-file.html#FILTER"
4517 > tries to only filter files that are
4518 in some kind of text format. The same restrictions apply to
4522 HREF="actions-file.html#CONTENT-TYPE-OVERWRITE"
4523 >content-type-overwrite</A
4528 >force-text-mode</TT
4529 > declares a document as text,
4530 without looking at the <SPAN
4532 >"Content-Type:"</SPAN
4554 > Think twice before activating this action. Filtering binary data
4555 with regular expressions can cause file damage.
4573 >+force-text-mode</PRE
4586 NAME="FORWARD-OVERRIDE"
4587 >8.5.18. forward-override</A
4592 CLASS="VARIABLELIST"
4598 >Change the forwarding settings based on User-Agent or request origin</P
4604 > Overrules the forward directives in the configuration file.
4624 > to use a direct connection without any additional proxies.</P
4630 >"forward 127.0.0.1:8123"</SPAN
4631 > to use the HTTP proxy listening at 127.0.0.1 port 8123.
4638 >"forward-socks4a 127.0.0.1:9050 ."</SPAN
4639 > to use the socks4a proxy listening at
4640 127.0.0.1 port 9050. Replace <SPAN
4642 >"forward-socks4a"</SPAN
4645 >"forward-socks4"</SPAN
4647 to use a socks4 connection (with local DNS resolution) instead, use <SPAN
4649 >"forward-socks5"</SPAN
4651 for socks5 connections (with remote DNS resolution).
4658 >"forward-socks4a 127.0.0.1:9050 proxy.example.org:8000"</SPAN
4659 > to use the socks4a proxy
4660 listening at 127.0.0.1 port 9050 to reach the HTTP proxy listening at proxy.example.org port 8000.
4663 >"forward-socks4a"</SPAN
4666 >"forward-socks4"</SPAN
4667 > to use a socks4 connection
4668 (with local DNS resolution) instead, use <SPAN
4670 >"forward-socks5"</SPAN
4672 for socks5 connections (with remote DNS resolution).
4679 >"forward-webserver 127.0.0.1:80"</SPAN
4681 server listening at 127.0.0.1 port 80 without adjusting the
4685 > This makes it more convenient to use Privoxy to make
4686 existing websites available as onion services as well.
4689 > Many websites serve content with hardcoded URLs and
4690 can't be easily adjusted to change the domain based
4691 on the one used by the client.
4694 > Putting Privoxy between Tor and the webserver (or an stunnel
4695 that forwards to the webserver) allows to rewrite headers and
4696 content to make client and server happy at the same time.
4699 > Using Privoxy for webservers that are only reachable through
4700 onion addresses and whose location is supposed to be secret
4701 is not recommended and should not be necessary anyway.
4710 > This action takes parameters similar to the
4712 HREF="config.html#FORWARDING"
4714 > directives in the configuration
4715 file, but without the URL pattern. It can be used as replacement, but normally it's only
4716 used in cases where matching based on the request URL isn't sufficient.
4737 > Please read the description for the <A
4738 HREF="config.html#FORWARDING"
4741 using this action. Forwarding to the wrong people will reduce your privacy and increase the
4742 chances of man-in-the-middle attacks.
4745 > If the ports are missing or invalid, default values will be used. This might change
4746 in the future and you shouldn't rely on it. Otherwise incorrect syntax causes Privoxy
4747 to exit. Due to design limitations, invalid parameter syntax isn't detected until the
4748 action is used the first time.
4752 HREF="http://config.privoxy.org/show-url-info"
4754 >show-url-info CGI page</A
4756 to verify that your forward settings do what you thought the do.
4774 ># Use an ssh tunnel for requests previously tagged as
4777 >"User-Agent: fetch libfetch/2.0"</SPAN
4779 # resuming downloads continues to work.
4781 # This way you can continue to use Tor for your normal browsing,
4782 # without overloading the Tor network with your FreeBSD ports updates
4783 # or downloads of bigger files like ISOs.
4785 # Note that HTTP headers are easy to fake and therefore their
4786 # values are as (un)trustworthy as your clients and users.
4787 {+forward-override{forward-socks5 10.0.0.2:2222 .} \
4788 -hide-if-modified-since \
4789 -overwrite-last-modified \
4791 TAG:^User-Agent: fetch libfetch/2\.0$</PRE
4804 NAME="HANDLE-AS-EMPTY-DOCUMENT"
4805 >8.5.19. handle-as-empty-document</A
4810 CLASS="VARIABLELIST"
4816 >Mark URLs that should be replaced by empty documents <SPAN
4820 >if they get blocked</I
4828 > This action alone doesn't do anything noticeable. It just marks URLs.
4832 HREF="actions-file.html#BLOCK"
4842 the presence or absence of this mark decides whether an HTML <SPAN
4846 page, or an empty document will be sent to the client as a substitute for the blocked content.
4853 > document isn't literally empty, but actually contains a single space.
4873 > Some browsers complain about syntax errors if JavaScript documents
4874 are blocked with <SPAN
4878 default HTML page; this option can be used to silence them.
4879 And of course this action can also be used to eliminate the <SPAN
4883 BLOCKED message in frames.
4886 > The content type for the empty document can be specified with
4890 HREF="actions-file.html#CONTENT-TYPE-OVERWRITE"
4891 >content-type-overwrite{}</A
4894 but usually this isn't necessary.
4908 ># Block all documents on example.org that end with ".js",
4909 # but send an empty document instead of the usual HTML message.
4910 {+block{Blocked JavaScript} +handle-as-empty-document}
4911 example.org/.*\.js$</PRE
4924 NAME="HANDLE-AS-IMAGE"
4925 >8.5.20. handle-as-image</A
4930 CLASS="VARIABLELIST"
4936 >Mark URLs as belonging to images (so they'll be replaced by images <SPAN
4940 >if they do get blocked</I
4942 >, rather than HTML pages)</P
4948 > This action alone doesn't do anything noticeable. It just marks URLs as images.
4952 HREF="actions-file.html#BLOCK"
4962 the presence or absence of this mark decides whether an HTML <SPAN
4966 page, or a replacement image (as determined by the <TT
4969 HREF="actions-file.html#SET-IMAGE-BLOCKER"
4970 >set-image-blocker</A
4972 > action) will be sent to the
4973 client as a substitute for the blocked content.
4993 > The below generic example section is actually part of <TT
4997 It marks all URLs with well-known image file name extensions as images and should
5001 > Users will probably only want to use the handle-as-image action in conjunction with
5005 HREF="actions-file.html#BLOCK"
5008 >, to block sources of banners, whose URLs don't
5009 reflect the file type, like in the second example section.
5012 > Note that you cannot treat HTML pages as images in most cases. For instance, (in-line) ad
5013 frames require an HTML page to be sent, or they won't display properly.
5016 >handle-as-image</TT
5017 > in this situation will not replace the
5018 ad frame with an image, but lead to error messages.
5022 >Example usage (sections):</DT
5032 ># Generic image extensions:
5035 /.*\.(gif|jpg|jpeg|png|bmp|ico)$
5037 # These don't look like images, but they're banners and should be
5038 # blocked as images:
5040 {+block{Nasty banners.} +handle-as-image}
5041 nasty-banner-server.example.com/junk.cgi\?output=trash</PRE
5054 NAME="HIDE-ACCEPT-LANGUAGE"
5055 >8.5.21. hide-accept-language</A
5060 CLASS="VARIABLELIST"
5066 >Pretend to use different language settings.</P
5072 > Deletes or replaces the <SPAN
5074 >"Accept-Language:"</SPAN
5075 > HTTP header in client requests.
5091 >, or any user defined value.
5098 > Faking the browser's language settings can be useful to make a
5099 foreign User-Agent set with
5103 HREF="actions-file.html#HIDE-USER-AGENT"
5110 > However some sites with content in different languages check the
5113 >"Accept-Language:"</SPAN
5114 > to decide which one to take by default.
5115 Sometimes it isn't possible to later switch to another language without
5118 >"Accept-Language:"</SPAN
5122 > Therefore it's a good idea to either only change the
5125 >"Accept-Language:"</SPAN
5126 > header to languages you understand,
5127 or to languages that aren't wide spread.
5130 > Before setting the <SPAN
5132 >"Accept-Language:"</SPAN
5134 to a rare language, you should consider that it helps to
5135 make your requests unique and thus easier to trace.
5136 If you don't plan to change this header frequently,
5137 you should stick to a common language.
5141 >Example usage (section):</DT
5151 ># Pretend to use Canadian language settings.
5152 {+hide-accept-language{en-ca} \
5153 +hide-user-agent{Mozilla/5.0 (X11; U; OpenBSD i386; en-CA; rv:1.8.0.4) Gecko/20060628 Firefox/1.5.0.4} \
5168 NAME="HIDE-CONTENT-DISPOSITION"
5169 >8.5.22. hide-content-disposition</A
5174 CLASS="VARIABLELIST"
5180 >Prevent download menus for content you prefer to view inside the browser.</P
5186 > Deletes or replaces the <SPAN
5188 >"Content-Disposition:"</SPAN
5189 > HTTP header set by some servers.
5205 >, or any user defined value.
5212 > Some servers set the <SPAN
5214 >"Content-Disposition:"</SPAN
5216 documents they assume you want to save locally before viewing them.
5219 >"Content-Disposition:"</SPAN
5220 > header contains the file name
5221 the browser is supposed to use by default.
5224 > In most browsers that understand this header, it makes it impossible to
5231 > the document, without downloading it first,
5232 even if it's just a simple text file or an image.
5235 > Removing the <SPAN
5237 >"Content-Disposition:"</SPAN
5239 to prevent this annoyance, but some browsers additionally check the
5242 >"Content-Type:"</SPAN
5243 > header, before they decide if they can
5244 display a document without saving it first. In these cases, you have
5245 to change this header as well, before the browser stops displaying
5249 > It is also possible to change the server's file name suggestion
5250 to another one, but in most cases it isn't worth the time to set
5254 > This action will probably be removed in the future,
5255 use server-header filters instead.
5269 ># Disarm the download link in Sourceforge's patch tracker
5271 +content-type-overwrite{text/plain}\
5272 +hide-content-disposition{block} }
5273 .sourceforge.net/tracker/download\.php</PRE
5286 NAME="HIDE-IF-MODIFIED-SINCE"
5287 >8.5.23. hide-if-modified-since</A
5292 CLASS="VARIABLELIST"
5298 >Prevent yet another way to track the user's steps between sessions.</P
5306 >"If-Modified-Since:"</SPAN
5307 > HTTP client header or modifies its value.
5323 >, or a user defined value that specifies a range of hours.
5330 > Removing this header is useful for filter testing, where you want to force a real
5331 reload instead of getting status code <SPAN
5334 >, which would cause the
5335 browser to use a cached copy of the page.
5338 > Instead of removing the header, <TT
5340 >hide-if-modified-since</TT
5342 also add or subtract a random amount of time to/from the header's value.
5343 You specify a range of minutes where the random factor should be chosen from and
5347 > does the rest. A negative value means
5348 subtracting, a positive value adding.
5351 > Randomizing the value of the <SPAN
5353 >"If-Modified-Since:"</SPAN
5355 it less likely that the server can use the time as a cookie replacement,
5356 but you will run into caching problems if the random range is too high.
5359 > It is a good idea to only use a small negative value and let
5363 HREF="actions-file.html#OVERWRITE-LAST-MODIFIED"
5364 >overwrite-last-modified</A
5367 handle the greater changes.
5370 > It is also recommended to use this action together with
5374 HREF="actions-file.html#CRUNCH-IF-NONE-MATCH"
5375 >crunch-if-none-match</A
5378 otherwise it's more or less pointless.
5382 >Example usage (section):</DT
5392 ># Let the browser revalidate but make tracking based on the time less likely.
5393 {+hide-if-modified-since{-60} \
5394 +overwrite-last-modified{randomize} \
5395 +crunch-if-none-match}
5409 NAME="HIDE-FROM-HEADER"
5410 >8.5.24. hide-from-header</A
5415 CLASS="VARIABLELIST"
5421 >Keep your (old and ill) browser from telling web servers your email address</P
5427 > Deletes any existing <SPAN
5430 > HTTP header, or replaces it with the
5447 >, or any user defined value.
5457 > will completely remove the header
5458 (not to be confused with the <TT
5461 HREF="actions-file.html#BLOCK"
5468 > Alternately, you can specify any value you prefer to be sent to the web
5469 server. If you do, it is a matter of fairness not to use any address that
5470 is actually used by a real person.
5473 > This action is rarely needed, as modern web browsers don't send
5491 >+hide-from-header{block}</PRE
5505 >+hide-from-header{spam-me-senseless@sittingduck.example.com}</PRE
5518 NAME="HIDE-REFERRER"
5519 >8.5.25. hide-referrer</A
5527 CLASS="VARIABLELIST"
5533 >Conceal which link you followed to get to a particular site</P
5542 > (sic) HTTP header from the client request,
5543 or replaces it with a forged one.
5562 >"conditional-block"</SPAN
5563 > to delete the header completely if the host has changed.</P
5569 >"conditional-forge"</SPAN
5570 > to forge the header if the host has changed.</P
5577 > to delete the header unconditionally.</P
5584 > to pretend to be coming from the homepage of the server we are talking to.</P
5588 >Any other string to set a user defined referrer.</P
5598 >conditional-block</TT
5599 > is the only parameter,
5600 that isn't easily detected in the server's log file. If it blocks the
5601 referrer, the request will look like the visitor used a bookmark or
5602 typed in the address directly.
5605 > Leaving the referrer unmodified for requests on the same host
5606 allows the server owner to see the visitor's <SPAN
5610 but in most cases she could also get that information by comparing
5611 other parts of the log file: for example the User-Agent if it isn't
5612 a very common one, or the user's IP address if it doesn't change between
5616 > Always blocking the referrer, or using a custom one, can lead to
5617 failures on servers that check the referrer before they answer any
5618 requests, in an attempt to prevent their content from being
5619 embedded or linked to elsewhere.
5624 >conditional-block</TT
5629 will work with referrer checks, as long as content and valid referring page
5630 are on the same host. Most of the time that's the case.
5636 > is an alternate spelling of
5640 > and the two can be can be freely
5641 substituted with each other. (<SPAN
5645 correct English spelling, however the HTTP specification has a bug - it
5646 requires it to be spelled as <SPAN
5663 >+hide-referrer{forge}</PRE
5677 >+hide-referrer{http://www.yahoo.com/}</PRE
5690 NAME="HIDE-USER-AGENT"
5691 >8.5.26. hide-user-agent</A
5696 CLASS="VARIABLELIST"
5702 >Try to conceal your type of browser and client operating system</P
5708 > Replaces the value of the <SPAN
5710 >"User-Agent:"</SPAN
5712 in client requests with the specified value.
5725 > Any user-defined string.
5750 > This can lead to problems on web sites that depend on looking at this header in
5751 order to customize their content for different browsers (which, by the
5758 > the right thing to do: good web sites
5759 work browser-independently).
5766 > Using this action in multi-user setups or wherever different types of
5767 browsers will access the same <SPAN
5777 >. In single-user, single-browser
5778 setups, you might use it to delete your OS version information from
5779 the headers, because it is an invitation to exploit known bugs for your
5780 OS. It is also occasionally useful to forge this in order to access
5781 sites that won't let you in otherwise (though there may be a good
5782 reason in some cases).
5785 > More information on known user-agent strings can be found at
5787 HREF="http://www.user-agents.org/"
5789 >http://www.user-agents.org/</A
5793 HREF="http://en.wikipedia.org/wiki/User_agent"
5795 >http://en.wikipedia.org/wiki/User_agent</A
5810 >+hide-user-agent{Netscape 6.1 (X11; I; Linux 2.4.18 i686)}</PRE
5823 NAME="LIMIT-CONNECT"
5824 >8.5.27. limit-connect</A
5829 CLASS="VARIABLELIST"
5835 >Prevent abuse of <SPAN
5838 > as a TCP proxy relay or disable SSL for untrusted sites</P
5844 > Specifies to which ports HTTP CONNECT requests are allowable.
5857 > A comma-separated list of ports or port ranges (the latter using dashes, with the minimum
5858 defaulting to 0 and the maximum to 65K).
5865 > By default, i.e. if no <TT
5872 > allows HTTP CONNECT requests to all
5876 > if fine-grained control
5877 is desired for some or all destinations.
5880 > The CONNECT methods exists in HTTP to allow access to secure websites
5884 > URLs) through proxies. It works very simply:
5885 the proxy connects to the server on the specified port, and then
5886 short-circuits its connections to the client and to the remote server.
5887 This means CONNECT-enabled proxies can be used as TCP relays very easily.
5893 > relays HTTPS traffic without seeing
5894 the decoded content. Websites can leverage this limitation to circumvent <SPAN
5898 filters. By specifying an invalid port range you can disable HTTPS entirely.
5902 >Example usages:</DT
5912 >+limit-connect{443} # Port 443 is OK.
5913 +limit-connect{80,443} # Ports 80 and 443 are OK.
5914 +limit-connect{-3, 7, 20-100, 500-} # Ports less than 3, 7, 20 to 100 and above 500 are OK.
5915 +limit-connect{-} # All ports are OK
5916 +limit-connect{,} # No HTTPS/SSL traffic is allowed</PRE
5929 NAME="LIMIT-COOKIE-LIFETIME"
5930 >8.5.28. limit-cookie-lifetime</A
5935 CLASS="VARIABLELIST"
5941 >Limit the lifetime of HTTP cookies to a couple of minutes or hours.</P
5947 > Overwrites the expires field in Set-Cookie server headers if it's above the specified limit.
5960 > The lifetime limit in minutes, or 0.
5967 > This action reduces the lifetime of HTTP cookies coming from the
5968 server to the specified number of minutes, starting from the time
5969 the cookie passes Privoxy.
5972 > Cookies with a lifetime below the limit are not modified.
5973 The lifetime of session cookies is set to the specified limit.
5976 > The effect of this action depends on the server.
5979 > In case of servers which refresh their cookies with each response
5980 (or at least frequently), the lifetime limit set by this action
5982 Thus, a session associated with the cookie continues to work with
5983 this action enabled, as long as a new request is made before the
5984 last limit set is reached.
5987 > However, some servers send their cookies once, with a lifetime of several
5988 years (the year 2037 is a popular choice), and do not refresh them
5989 until a certain event in the future, for example the user logging out.
5990 In this case this action may limit the absolute lifetime of the session,
5991 even if requests are made frequently.
5994 > If the parameter is <SPAN
5997 >, this action behaves like
6001 HREF="actions-file.html#SESSION-COOKIES-ONLY"
6002 >session-cookies-only</A
6008 >Example usages:</DT
6018 >+limit-cookie-lifetime{60}</PRE
6031 NAME="PREVENT-COMPRESSION"
6032 >8.5.29. prevent-compression</A
6037 CLASS="VARIABLELIST"
6043 > Ensure that servers send the content uncompressed, so it can be
6047 HREF="actions-file.html#FILTER"
6057 > Removes the Accept-Encoding header which can be used to ask for compressed transfer.
6077 > More and more websites send their content compressed by default, which
6078 is generally a good idea and saves bandwidth. But the <TT
6081 HREF="actions-file.html#FILTER"
6088 HREF="actions-file.html#DEANIMATE-GIFS"
6092 actions need access to the uncompressed data.
6095 > When compiled with zlib support (available since <SPAN
6098 > 3.0.7), content that should be
6099 filtered is decompressed on-the-fly and you don't have to worry about this action.
6100 If you are using an older <SPAN
6103 > version, or one that hasn't been compiled with zlib
6104 support, this action can be used to convince the server to send the content uncompressed.
6107 > Most text-based instances compress very well, the size is seldom decreased by less than 50%,
6108 for markup-heavy instances like news feeds saving more than 90% of the original size isn't
6112 > Not using compression will therefore slow down the transfer, and you should only
6113 enable this action if you really need it. As of <SPAN
6116 > 3.0.7 it's disabled in all
6117 predefined action settings.
6120 > Note that some (rare) ill-configured sites don't handle requests for uncompressed
6121 documents correctly. Broken PHP applications tend to send an empty document body,
6122 some IIS versions only send the beginning of the content. If you enable
6125 >prevent-compression</TT
6126 > per default, you might want to add
6127 exceptions for those sites. See the example for how to do that.
6131 >Example usage (sections):</DT
6141 ># Selectively turn off compression, and enable a filter
6143 { +filter{tiny-textforms} +prevent-compression }
6144 # Match only these sites
6149 # Or instead, we could set a universal default:
6151 { +prevent-compression }
6154 # Then maybe make exceptions for broken sites:
6156 { -prevent-compression }
6170 NAME="OVERWRITE-LAST-MODIFIED"
6171 >8.5.30. overwrite-last-modified</A
6176 CLASS="VARIABLELIST"
6182 >Prevent yet another way to track the user's steps between sessions.</P
6190 >"Last-Modified:"</SPAN
6191 > HTTP server header or modifies its value.
6204 > One of the keywords: <SPAN
6209 >"reset-to-request-time"</SPAN
6221 > Removing the <SPAN
6223 >"Last-Modified:"</SPAN
6224 > header is useful for filter
6225 testing, where you want to force a real reload instead of getting status
6229 >, which would cause the browser to reuse the old
6230 version of the page.
6236 > option overwrites the value of the
6239 >"Last-Modified:"</SPAN
6240 > header with a randomly chosen time
6241 between the original value and the current time. In theory the server
6242 could send each document with a different <SPAN
6244 >"Last-Modified:"</SPAN
6246 header to track visits without using cookies. <SPAN
6250 makes it impossible and the browser can still revalidate cached documents.
6255 >"reset-to-request-time"</SPAN
6256 > overwrites the value of the
6259 >"Last-Modified:"</SPAN
6260 > header with the current time. You could use
6261 this option together with
6265 HREF="actions-file.html#HIDE-IF-MODIFIED-SINCE"
6266 >hide-if-modified-since</A
6269 to further customize your random range.
6272 > The preferred parameter here is <SPAN
6276 to use, as long as the time settings are more or less correct.
6277 If the server sets the <SPAN
6279 >"Last-Modified:"</SPAN
6280 > header to the time
6281 of the request, the random range becomes zero and the value stays the same.
6282 Therefore you should later randomize it a second time with
6286 HREF="actions-file.html#HIDE-IF-MODIFIED-SINCE"
6287 >hided-if-modified-since</A
6293 > It is also recommended to use this action together with
6297 HREF="actions-file.html#CRUNCH-IF-NONE-MATCH"
6298 >crunch-if-none-match</A
6314 ># Let the browser revalidate without being tracked across sessions
6315 { +hide-if-modified-since{-60} \
6316 +overwrite-last-modified{randomize} \
6317 +crunch-if-none-match}
6332 >8.5.31. redirect</A
6337 CLASS="VARIABLELIST"
6343 > Redirect requests to other sites.
6350 > Convinces the browser that the requested document has been moved
6351 to another location and the browser should get it from there.
6364 > An absolute URL or a single pcrs command.
6371 > Requests to which this action applies are answered with a
6372 HTTP redirect to URLs of your choosing. The new URL is
6373 either provided as parameter, or derived by applying a
6374 single pcrs command to the original URL.
6377 > The syntax for pcrs commands is documented in the
6379 HREF="filter-file.html"
6384 > Requests can't be blocked and redirected at the same time,
6385 applying this action together with
6389 HREF="actions-file.html#BLOCK"
6393 is a configuration error. Currently the request is blocked
6394 and an error message logged, the behavior may change in the
6395 future and result in Privoxy rejecting the action file.
6398 > This action can be combined with
6402 HREF="actions-file.html#FAST-REDIRECTS"
6403 >fast-redirects{check-decoded-url}</A
6406 to redirect to a decoded version of a rewritten URL.
6409 > Use this action carefully, make sure not to create redirection loops
6410 and be aware that using your own redirects might make it
6411 possible to fingerprint your requests.
6414 > In case of problems with your redirects, or simply to watch
6415 them working, enable <A
6416 HREF="config.html#DEBUG"
6422 >Example usages:</DT
6432 ># Replace example.com's style sheet with another one
6433 { +redirect{http://localhost/css-replacements/example.com.css} }
6434 example.com/stylesheet\.css
6436 # Create a short, easy to remember nickname for a favorite site
6437 # (relies on the browser to accept and forward invalid URLs to <SPAN
6441 { +redirect{https://www.privoxy.org/user-manual/actions-file.html} }
6444 # Always use the expanded view for Undeadly.org articles
6445 # (Note the $ at the end of the URL pattern to make sure
6446 # the request for the rewritten URL isn't redirected as well)
6447 {+redirect{s@$@&mode=expanded@}}
6448 undeadly.org/cgi\?action=article&sid=\d*$
6450 # Redirect Google search requests to MSN
6451 {+redirect{s@^http://[^/]*/search\?q=([^&]*).*@http://search.msn.com/results.aspx?q=$1@}}
6454 # Redirect MSN search requests to Yahoo
6455 {+redirect{s@^http://[^/]*/results\.aspx\?q=([^&]*).*@http://search.yahoo.com/search?p=$1@}}
6456 search.msn.com//results\.aspx\?q=
6458 # Redirect http://example.com/&bla=fasel&toChange=foo (and any other value but "bar")
6459 # to http://example.com/&bla=fasel&toChange=bar
6461 # The URL pattern makes sure that the following request isn't redirected again.
6462 {+redirect{s@toChange=[^&]+@toChange=bar@}}
6463 example.com/.*toChange=(?!bar)
6465 # Add a shortcut to look up illumos bugs
6466 {+redirect{s@^http://i([0-9]+)/.*@https://www.illumos.org/issues/$1@}}
6467 # Redirected URL = http://i4974/
6468 # Redirect Destination = https://www.illumos.org/issues/4974
6469 i[0-9][0-9][0-9][0-9]*/
6471 # Redirect remote requests for this manual
6472 # to the local version delivered by Privoxy
6473 {+redirect{s@^http://www@http://config@}}
6474 www.privoxy.org/user-manual/</PRE
6487 NAME="SERVER-HEADER-FILTER"
6488 >8.5.32. server-header-filter</A
6493 CLASS="VARIABLELIST"
6499 > Rewrite or remove single server headers.
6506 > All server headers to which this action applies are filtered on-the-fly
6507 through the specified regular expression based substitutions.
6520 > The name of a server-header filter, as defined in one of the
6522 HREF="filter-file.html"
6531 > Server-header filters are applied to each header on its own, not to
6532 all at once. This makes it easier to diagnose problems, but on the downside
6533 you can't write filters that only change header x if header y's value is z.
6534 You can do that by using tags though.
6537 > Server-header filters are executed after the other header actions have finished
6538 and use their output as input.
6541 > Please refer to the <A
6542 HREF="filter-file.html"
6543 >filter file chapter</A
6545 to learn which server-header filters are available by default, and how to
6550 >Example usage (section):</DT
6560 >{+server-header-filter{html-to-xml}}
6561 example.org/xml-instance-that-is-delivered-as-html
6563 {+server-header-filter{xml-to-html}}
6564 example.org/instance-that-is-delivered-as-xml-but-is-not</PRE
6577 NAME="SERVER-HEADER-TAGGER"
6578 >8.5.33. 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
6658 ># Tag every request with the content type declared by the server
6659 {+server-header-tagger{content-type}}
6662 # If the response has a tag starting with 'image/' enable an external
6663 # filter that only applies to images.
6665 # Note that the filter is not available by default, it's just a
6669 HREF="filter-file.html#EXTERNAL-FILTER-SYNTAX"
6673 {+external-filter{rotate-image} +force-text-mode}
6687 NAME="SESSION-COOKIES-ONLY"
6688 >8.5.34. session-cookies-only</A
6693 CLASS="VARIABLELIST"
6699 > Allow only temporary <SPAN
6702 > cookies (for the current
6703 browser session <SPAN
6721 >"Set-Cookie:"</SPAN
6723 server headers. Most browsers will not store such cookies permanently and
6724 forget them in between sessions.
6744 > This is less strict than <TT
6747 HREF="actions-file.html#CRUNCH-INCOMING-COOKIES"
6748 >crunch-incoming-cookies</A
6754 HREF="actions-file.html#CRUNCH-OUTGOING-COOKIES"
6755 >crunch-outgoing-cookies</A
6757 > and allows you to browse
6758 websites that insist or rely on setting cookies, without compromising your privacy too badly.
6761 > Most browsers will not permanently store cookies that have been processed by
6764 >session-cookies-only</TT
6765 > and will forget about them between sessions.
6766 This makes profiling cookies useless, but won't break sites which require cookies so
6767 that you can log in for transactions. This is generally turned on for all
6768 sites, and is the recommended setting.
6779 >session-cookies-only</TT
6784 HREF="actions-file.html#CRUNCH-INCOMING-COOKIES"
6785 >crunch-incoming-cookies</A
6791 HREF="actions-file.html#CRUNCH-OUTGOING-COOKIES"
6792 >crunch-outgoing-cookies</A
6794 >. If you do, cookies
6795 will be plainly killed.
6798 > Note that it is up to the browser how it handles such cookies without an <SPAN
6802 field. If you use an exotic browser, you might want to try it out to be sure.
6805 > This setting also has no effect on cookies that may have been stored
6806 previously by the browser before starting <SPAN
6810 These would have to be removed manually.
6818 HREF="actions-file.html#FILTER-CONTENT-COOKIES"
6819 >content-cookies filter</A
6821 to block some types of cookies. Content cookies are not effected by
6824 >session-cookies-only</TT
6839 >+session-cookies-only</PRE
6852 NAME="SET-IMAGE-BLOCKER"
6853 >8.5.35. set-image-blocker</A
6858 CLASS="VARIABLELIST"
6864 >Choose the replacement for blocked images</P
6870 > This action alone doesn't do anything noticeable. If <SPAN
6880 HREF="actions-file.html#BLOCK"
6892 HREF="actions-file.html#HANDLE-AS-IMAGE"
6902 apply, i.e. if the request is to be blocked as an image,
6909 > the parameter of this action decides what will be
6910 sent as a replacement.
6930 > to send a built-in checkerboard pattern image. The image is visually
6931 decent, scales very well, and makes it obvious where banners were busted.
6939 > to send a built-in transparent image. This makes banners disappear
6940 completely, but makes it hard to detect where <SPAN
6944 images on a given page and complicates troubleshooting if <SPAN
6948 has blocked innocent images, like navigation icons.
6962 send a redirect to <TT
6968 to any image anywhere, even in your local filesystem via <SPAN
6972 (But note that not all browsers support redirecting to a local file system).
6975 > A good application of redirects is to use special <SPAN
6979 URLs, which send the built-in images, as <TT
6985 This has the same visual effect as specifying <SPAN
6992 the first place, but enables your browser to cache the replacement image, instead of requesting
6993 it over and over again.
7002 > The URLs for the built-in images are <SPAN
7004 >"http://config.privoxy.org/send-banner?type=<TT
7025 > There is a third (advanced) type, called <SPAN
7037 >set-image-blocker</TT
7038 >, but meant for use from <A
7039 HREF="filter-file.html"
7042 Auto will select the type of image that would have applied to the referring page, had it been an image.
7059 >+set-image-blocker{pattern}</PRE
7064 > Redirect to the BSD daemon:
7074 >+set-image-blocker{http://www.freebsd.org/gifs/dae_up3.gif}</PRE
7079 > Redirect to the built-in pattern for better caching:
7089 >+set-image-blocker{http://config.privoxy.org/send-banner?type=pattern}</PRE
7106 > Note that many of these actions have the potential to cause a page to
7107 misbehave, possibly even not to display at all. There are many ways
7108 a site designer may choose to design his site, and what HTTP header
7109 content, and other criteria, he may depend on. There is no way to have hard
7110 and fast rules for all sites. See the <A
7111 HREF="appendix.html#ACTIONSANAT"
7113 > for a brief example on troubleshooting
7136 >, can be defined by combining other actions.
7137 These can in turn be invoked just like the built-in actions.
7138 Currently, an alias name can contain any character except space, tab,
7156 > that you only use <SPAN
7176 Alias names are not case sensitive, and are not required to start with a
7183 > sign, since they are merely textually
7186 > Aliases can be used throughout the actions file, but they <SPAN
7191 defined in a special section at the top of the file!</I
7194 And there can only be one such section per actions file. Each actions file may
7195 have its own alias section, and the aliases defined in it are only visible
7196 within that file.</P
7198 > There are two main reasons to use aliases: One is to save typing for frequently
7199 used combinations of actions, the other one is a gain in flexibility: If you
7200 decide once how you want to handle shops by defining an alias called
7204 >, you can later change your policy on shops in
7211 > place, and your changes will take effect everywhere
7212 in the actions file where the <SPAN
7215 > alias is used. Calling aliases
7216 by their purpose also makes your actions files more readable.</P
7218 > Currently, there is one big drawback to using aliases, though:
7222 >'s built-in web-based action file
7223 editor honors aliases when reading the actions files, but it expands
7224 them before writing. So the effects of your aliases are of course preserved,
7225 but the aliases themselves are lost when you edit sections that use aliases
7228 > Now let's define some aliases...</P
7237 > # Useful custom aliases we can use later.
7239 # Note the (required!) section header line and that this section
7240 # must be at the top of the actions file!
7244 # These aliases just save typing later:
7245 # (Note that some already use other aliases!)
7247 +crunch-all-cookies = +<A
7248 HREF="actions-file.html#CRUNCH-INCOMING-COOKIES"
7249 >crunch-incoming-cookies</A
7251 HREF="actions-file.html#CRUNCH-OUTGOING-COOKIES"
7252 >crunch-outgoing-cookies</A
7254 -crunch-all-cookies = -<A
7255 HREF="actions-file.html#CRUNCH-INCOMING-COOKIES"
7256 >crunch-incoming-cookies</A
7258 HREF="actions-file.html#CRUNCH-OUTGOING-COOKIES"
7259 >crunch-outgoing-cookies</A
7261 +block-as-image = +block{Blocked image.} +handle-as-image
7262 allow-all-cookies = -crunch-all-cookies -<A
7263 HREF="actions-file.html#SESSION-COOKIES-ONLY"
7264 >session-cookies-only</A
7266 HREF="actions-file.html#FILTER-CONTENT-COOKIES"
7267 >filter{content-cookies}</A
7270 # These aliases define combinations of actions
7271 # that are useful for certain types of sites:
7274 HREF="actions-file.html#BLOCK"
7277 HREF="actions-file.html#FILTER"
7279 > -crunch-all-cookies -<A
7280 HREF="actions-file.html#FAST-REDIRECTS"
7283 HREF="actions-file.html#HIDE-REFERER"
7286 HREF="actions-file.html#PREVENT-COMPRESSION"
7287 >prevent-compression</A
7290 shop = -crunch-all-cookies -<A
7291 HREF="actions-file.html#FILTER-ALL-POPUPS"
7292 >filter{all-popups}</A
7295 # Short names for other aliases, for really lazy people ;-)
7297 c0 = +crunch-all-cookies
7298 c1 = -crunch-all-cookies</PRE
7303 > ...and put them to use. These sections would appear in the lower part of an
7304 actions file and define exceptions to the default actions (as specified further
7317 > # These sites are either very complex or very keen on
7318 # user data and require minimal interference to work:
7321 .office.microsoft.com
7322 .windowsupdate.microsoft.com
7323 # Gmail is really mail.google.com, not gmail.com
7327 # Allow cookies (for setting and retrieving your customer data)
7331 .worldpay.com # for quietpc.com
7334 # These shops require pop-ups:
7336 {-filter{all-popups} -filter{unsolicited-popups}}
7338 .overclockers.co.uk</PRE
7343 > Aliases like <SPAN
7349 > are typically used for
7353 > sites that require more than one action to be disabled
7354 in order to function properly.</P
7362 >8.7. Actions Files Tutorial</A
7365 > The above chapters have shown <A
7366 HREF="actions-file.html"
7367 >which actions files
7368 there are and how they are organized</A
7369 >, how actions are <A
7370 HREF="actions-file.html#ACTIONS"
7373 HREF="actions-file.html#ACTIONS-APPLY"
7377 HREF="actions-file.html#AF-PATTERNS"
7381 HREF="actions-file.html#ALIASES"
7383 >. Now, let's look at an
7386 >match-all.action</TT
7394 > file and see how all these pieces come together:</P
7401 >8.7.1. match-all.action</A
7408 >all actions are disabled when matching starts</I
7411 so we have to explicitly enable the ones we want.</P
7415 >match-all.action</TT
7416 > file only contains a
7417 single section, it is probably the most important one. It has only one
7426 HREF="actions-file.html#AF-PATTERNS"
7427 >matches all URLs</A
7428 >. Therefore, the set of
7429 actions used in this <SPAN
7437 be applied to all requests as a start</I
7439 >. It can be partly or
7440 wholly overridden by other actions files like <TT
7447 >, but it will still be largely responsible
7448 for your overall browsing experience.</P
7450 > Again, at the start of matching, all actions are disabled, so there is
7451 no need to disable any actions here. (Remember: a <SPAN
7455 preceding the action name enables the action, a <SPAN
7459 Also note how this long line has been made more readable by splitting it into
7460 multiple lines with line continuation.</P
7471 HREF="actions-file.html#CHANGE-X-FORWARDED-FOR"
7472 >change-x-forwarded-for{block}</A
7475 HREF="actions-file.html#HIDE-FROM-HEADER"
7476 >hide-from-header{block}</A
7479 HREF="actions-file.html#SET-IMAGE-BLOCKER"
7480 >set-image-blocker{pattern}</A
7483 / # Match all URLs</PRE
7488 > The default behavior is now set.</P
7495 NAME="DEFAULT-ACTION"
7496 >8.7.2. default.action</A
7499 > If you aren't a developer, there's no need for you to edit the
7503 > file. It is maintained by
7507 > developers and if you disagree with some of the
7508 sections, you should overrule them in your <TT
7513 > Understanding the <TT
7517 help you with your <TT
7522 > The first section in this file is a special section for internal use
7523 that prevents older <SPAN
7526 > versions from reading the file:</P
7535 >##########################################################################
7536 # Settings -- Don't change! For internal Privoxy use ONLY.
7537 ##########################################################################
7539 for-privoxy-version=3.0.11</PRE
7544 > After that comes the (optional) alias section. We'll use the example
7545 section from the above <A
7546 HREF="actions-file.html#ALIASES"
7547 >chapter on aliases</A
7549 that also explains why and how aliases are used:</P
7558 >##########################################################################
7560 ##########################################################################
7563 # These aliases just save typing later:
7564 # (Note that some already use other aliases!)
7566 +crunch-all-cookies = +<A
7567 HREF="actions-file.html#CRUNCH-INCOMING-COOKIES"
7568 >crunch-incoming-cookies</A
7570 HREF="actions-file.html#CRUNCH-OUTGOING-COOKIES"
7571 >crunch-outgoing-cookies</A
7573 -crunch-all-cookies = -<A
7574 HREF="actions-file.html#CRUNCH-INCOMING-COOKIES"
7575 >crunch-incoming-cookies</A
7577 HREF="actions-file.html#CRUNCH-OUTGOING-COOKIES"
7578 >crunch-outgoing-cookies</A
7580 +block-as-image = +block{Blocked image.} +handle-as-image
7581 mercy-for-cookies = -crunch-all-cookies -<A
7582 HREF="actions-file.html#SESSION-COOKIES-ONLY"
7583 >session-cookies-only</A
7585 HREF="actions-file.html#FILTER-CONTENT-COOKIES"
7586 >filter{content-cookies}</A
7589 # These aliases define combinations of actions
7590 # that are useful for certain types of sites:
7593 HREF="actions-file.html#BLOCK"
7596 HREF="actions-file.html#FILTER"
7598 > -crunch-all-cookies -<A
7599 HREF="actions-file.html#FAST-REDIRECTS"
7602 HREF="actions-file.html#HIDE-REFERER"
7605 shop = -crunch-all-cookies -<A
7606 HREF="actions-file.html#FILTER-ALL-POPUPS"
7607 >filter{all-popups}</A
7613 > The first of our specialized sections is concerned with <SPAN
7617 sites, i.e. sites that require minimum interference, because they are either
7618 very complex or very keen on tracking you (and have mechanisms in place that
7619 make them unusable for people who avoid being tracked). We will use
7623 > alias instead of stating the list
7624 of actions explicitly:</P
7633 >##########################################################################
7634 # Exceptions for sites that'll break under the default action set:
7635 ##########################################################################
7637 # "Fragile" Use a minimum set of actions for these sites (see alias above):
7640 .office.microsoft.com # surprise, surprise!
7641 .windowsupdate.microsoft.com
7642 mail.google.com</PRE
7647 > Shopping sites are not as fragile, but they typically
7648 require cookies to log in, and pop-up windows for shopping
7649 carts or item details. Again, we'll use a pre-defined alias:</P
7662 .worldpay.com # for quietpc.com
7672 HREF="actions-file.html#FAST-REDIRECTS"
7676 action, which may have been enabled in <TT
7678 >match-all.action</TT
7680 breaks some sites. So disable it for popular sites where we know it misbehaves:</P
7690 HREF="actions-file.html#FAST-REDIRECTS"
7696 .altavista.com/.*(like|url|link):http
7697 .altavista.com/trans.*urltext=http
7703 > It is important that <SPAN
7707 URLs belong to images, so that <SPAN
7714 be blocked, a substitute image can be sent, rather than an HTML page.
7715 Contacting the remote site to find out is not an option, since it
7716 would destroy the loading time advantage of banner blocking, and it
7717 would feed the advertisers information about you. We can mark any
7718 URL as an image with the <TT
7721 HREF="actions-file.html#HANDLE-AS-IMAGE"
7725 and marking all URLs that end in a known image file extension is a
7735 >##########################################################################
7737 ##########################################################################
7739 # Define which file types will be treated as images, in case they get
7740 # blocked further down this file:
7743 HREF="actions-file.html#HANDLE-AS-IMAGE"
7746 /.*\.(gif|jpe?g|png|bmp|ico)$</PRE
7751 > And then there are known banner sources. They often use scripts to
7752 generate the banners, so it won't be visible from the URL that the
7753 request is for an image. Hence we block them <SPAN
7760 mark them as images in one go, with the help of our
7763 >+block-as-image</TT
7764 > alias defined above. (We could of
7765 course just as well use <TT
7768 HREF="actions-file.html#BLOCK"
7772 HREF="actions-file.html#HANDLE-AS-IMAGE"
7776 Remember that the type of the replacement image is chosen by the
7780 HREF="actions-file.html#SET-IMAGE-BLOCKER"
7781 >set-image-blocker</A
7784 action. Since all URLs have matched the default section with its
7788 HREF="actions-file.html#SET-IMAGE-BLOCKER"
7789 >set-image-blocker</A
7792 action before, it still applies and needn't be repeated:</P
7801 ># Known ad generators:
7806 .ad.*.doubleclick.net
7807 .a.yimg.com/(?:(?!/i/).)*$
7808 .a[0-9].yimg.com/(?:(?!/i/).)*$
7815 > One of the most important jobs of <SPAN
7819 is to block banners. Many of these can be <SPAN
7826 HREF="actions-file.html#FILTER"
7828 >{banners-by-size}</TT
7830 action, which we enabled above, and which deletes the references to banner
7831 images from the pages while they are loaded, so the browser doesn't request
7832 them anymore, and hence they don't need to be blocked here. But this naturally
7833 doesn't catch all banners, and some people choose not to use filters, so we
7834 need a comprehensive list of patterns for banner URLs here, and apply the
7838 HREF="actions-file.html#BLOCK"
7841 > action to them.</P
7843 > First comes many generic patterns, which do most of the work, by
7844 matching typical domain and path name components of banners. Then comes
7845 a list of individual patterns for specific sites, which is omitted here
7846 to keep the example short:</P
7855 >##########################################################################
7856 # Block these fine banners:
7857 ##########################################################################
7859 HREF="actions-file.html#BLOCK"
7860 >+block{Banner ads.}</A
7869 /.*count(er)?\.(pl|cgi|exe|dll|asp|php[34]?)
7870 /(?:.*/)?(publicite|werbung|rekla(ma|me|am)|annonse|maino(kset|nta|s)?)/
7872 # Site-specific patterns (abbreviated):
7879 > It's quite remarkable how many advertisers actually call their banner
7885 >.com, or call the directory
7886 in which the banners are stored literally <SPAN
7890 generic patterns are surprisingly effective.</P
7892 > But being very generic, they necessarily also catch URLs that we don't want
7893 to block. The pattern <TT
7905 >.nasty-corp.com"</SPAN
7915 >.sourcefroge.net"</SPAN
7925 >l.some-provider.net."</SPAN
7927 well-known exceptions to the <TT
7930 HREF="actions-file.html#BLOCK"
7936 > Note that these are exceptions to exceptions from the default! Consider the URL
7939 >"downloads.sourcefroge.net"</SPAN
7940 >: Initially, all actions are deactivated,
7941 so it wouldn't get blocked. Then comes the defaults section, which matches the
7942 URL, but just deactivates the <TT
7945 HREF="actions-file.html#BLOCK"
7949 action once again. Then it matches <TT
7952 >, an exception to the
7953 general non-blocking policy, and suddenly
7957 HREF="actions-file.html#BLOCK"
7960 > applies. And now, it'll match
7967 HREF="actions-file.html#BLOCK"
7971 applies, so (unless it matches <SPAN
7977 > further down) it ends up
7981 HREF="actions-file.html#BLOCK"
7984 > action applying.</P
7993 >##########################################################################
7994 # Save some innocent victims of the above generic block patterns:
7995 ##########################################################################
8000 HREF="actions-file.html#BLOCK"
8003 adv[io]*. # (for advogato.org and advice.*)
8004 adsl. # (has nothing to do with ads)
8005 adobe. # (has nothing to do with ads either)
8006 ad[ud]*. # (adult.* and add.*)
8007 .edu # (universities don't host banners (yet!))
8008 .*loads. # (downloads, uploads etc)
8016 www.globalintersec.com/adv # (adv = advanced)
8017 www.ugu.com/sui/ugu/adv</PRE
8022 > Filtering source code can have nasty side effects,
8023 so make an exception for our friends at sourceforge.net,
8024 and all paths with <SPAN
8027 > in them. Note that
8031 HREF="actions-file.html#FILTER"
8041 > filters in one fell swoop!</P
8050 ># Don't filter code!
8053 HREF="actions-file.html#FILTER"
8060 .sourceforge.net</PRE
8068 > is of course much more
8069 comprehensive, but we hope this example made clear how it works.</P
8077 >8.7.3. user.action</A
8080 > So far we are painting with a broad brush by setting general policies,
8081 which would be a reasonable starting point for many people. Now,
8082 you might want to be more specific and have customized rules that
8083 are more suitable to your personal habits and preferences. These would
8084 be for narrowly defined situations like your ISP or your bank, and should
8088 >, which is parsed after all other
8089 actions files and hence has the last word, over-riding any previously
8090 defined actions. <TT
8100 > place for your personal settings, since
8104 > is actively maintained by the
8108 > developers and you'll probably want
8109 to install updated versions from time to time.</P
8111 > So let's look at a few examples of things that one might typically do in
8124 ># My user.action file. <fred@example.com></PRE
8130 HREF="actions-file.html#ALIASES"
8132 > are local to the actions
8133 file that they are defined in, you can't use the ones from
8137 >, unless you repeat them here:</P
8146 ># Aliases are local to the file they are defined in.
8147 # (Re-)define aliases for this file:
8151 # These aliases just save typing later, and the alias names should
8152 # be self explanatory.
8154 +crunch-all-cookies = +crunch-incoming-cookies +crunch-outgoing-cookies
8155 -crunch-all-cookies = -crunch-incoming-cookies -crunch-outgoing-cookies
8156 allow-all-cookies = -crunch-all-cookies -session-cookies-only
8157 allow-popups = -filter{all-popups}
8158 +block-as-image = +block{Blocked as image.} +handle-as-image
8159 -block-as-image = -block
8161 # These aliases define combinations of actions that are useful for
8162 # certain types of sites:
8164 fragile = -block -crunch-all-cookies -filter -fast-redirects -hide-referrer
8165 shop = -crunch-all-cookies allow-popups
8167 # Allow ads for selected useful free sites:
8169 allow-ads = -block -filter{banners-by-size} -filter{banners-by-link}
8171 # Alias for specific file types that are text, but might have conflicting
8172 # MIME types. We want the browser to force these to be text documents.
8173 handle-as-text = -<A
8174 HREF="actions-file.html#FILTER"
8177 HREF="actions-file.html#CONTENT-TYPE-OVERWRITE"
8178 >content-type-overwrite{text/plain}</A
8180 HREF="actions-file.html#FORCE-TEXT-MODE"
8183 HREF="actions-file.html#HIDE-CONTENT-DISPOSITION"
8184 >hide-content-disposition</A
8190 > Say you have accounts on some sites that you visit regularly, and
8191 you don't want to have to log in manually each time. So you'd like
8192 to allow persistent cookies for these sites. The
8195 >allow-all-cookies</TT
8196 > alias defined above does exactly
8197 that, i.e. it disables crunching of cookies in any direction, and the
8198 processing of cookies to make them only temporary.</P
8207 >{ allow-all-cookies }
8216 > Your bank is allergic to some filter, but you don't know which, so you disable them all:</P
8226 HREF="actions-file.html#FILTER"
8229 .your-home-banking-site.com</PRE
8234 > Some file types you may not want to filter for various reasons:</P
8243 ># Technical documentation is likely to contain strings that might
8244 # erroneously get altered by the JavaScript-oriented filters:
8249 # And this stupid host sends streaming video with a wrong MIME type,
8250 # so that Privoxy thinks it is getting HTML and starts filtering:
8252 stupid-server.example.com/</PRE
8257 > Example of a simple <A
8258 HREF="actions-file.html#BLOCK"
8260 > action. Say you've
8261 seen an ad on your favourite page on example.com that you want to get rid of.
8262 You have right-clicked the image, selected <SPAN
8264 >"copy image location"</SPAN
8266 and pasted the URL below while removing the leading http://, into a
8270 > section. Note that <TT
8274 > need not be specified, since all URLs ending in
8278 > will be tagged as images by the general rules as set
8279 in default.action anyway:</P
8289 HREF="actions-file.html#BLOCK"
8292 www.example.com/nasty-ads/sponsor\.gif
8293 another.example.net/more/junk/here/</PRE
8298 > The URLs of dynamically generated banners, especially from large banner
8299 farms, often don't use the well-known image file name extensions, which
8300 makes it impossible for <SPAN
8304 the file type just by looking at the URL.
8307 >+block-as-image</TT
8308 > alias defined above for
8310 Note that objects which match this rule but then turn out NOT to be an
8311 image are typically rendered as a <SPAN
8313 >"broken image"</SPAN
8315 browser. Use cautiously.</P
8324 >{ +block-as-image }
8333 > Now you noticed that the default configuration breaks Forbes Magazine,
8334 but you were too lazy to find out which action is the culprit, and you
8335 were again too lazy to give <A
8339 you just used the <TT
8342 > alias on the site, and
8349 > -- it worked. The <TT
8353 aliases disables those actions that are most likely to break a site. Also,
8354 good for testing purposes to see if it is <SPAN
8358 that is causing the problem or not. We later find other regular sites
8359 that misbehave, and add those to our personalized list of troublemakers:</P
8376 > You like the <SPAN
8379 > text replacements in <TT
8383 but it is disabled in the distributed actions file.
8384 So you'd like to turn it on in your private,
8385 update-safe config, once and for all:</P
8395 HREF="actions-file.html#FILTER-FUN"
8398 / # For ALL sites!</PRE
8403 > Note that the above is not really a good idea: There are exceptions
8404 to the filters in <TT
8408 really shouldn't be filtered, like code on CVS->Web interfaces. Since
8412 > has the last word, these exceptions
8413 won't be valid for the <SPAN
8416 > filtering specified here.</P
8418 > You might also worry about how your favourite free websites are
8419 funded, and find that they rely on displaying banner advertisements
8420 to survive. So you might want to specifically allow banners for those
8421 sites that you feel provide value to you:</P
8441 > has been aliased to
8445 HREF="actions-file.html#BLOCK"
8452 HREF="actions-file.html#FILTER-BANNERS-BY-SIZE"
8453 >filter{banners-by-size}</A
8459 HREF="actions-file.html#FILTER-BANNERS-BY-LINK"
8460 >filter{banners-by-link}</A
8464 > Invoke another alias here to force an over-ride of the MIME type <TT
8466 > application/x-sh</TT
8467 > which typically would open a download type
8468 dialog. In my case, I want to look at the shell script, and then I can save
8469 it should I choose to.</P
8487 > is generally the best place to define
8488 exceptions and additions to the default policies of
8492 >. Some actions are safe to have their
8493 default policies set here though. So let's set a default policy to have a
8497 > image as opposed to the checkerboard pattern for
8507 > of course matches all URL
8508 paths and patterns:</P
8518 HREF="actions-file.html#SET-IMAGE-BLOCKER"
8519 >set-image-blocker{blank}</A
8533 SUMMARY="Footer navigation table"
8562 HREF="filter-file.html"
8572 >The Main Configuration File</TD
projects / privoxy.git / blob