The actions files are used to define what actions Privoxy takes for which URLs, and thus determines @@ -51,10 +44,8 @@ veritable arsenal of tools with which to exert our control, preferences and independence. Actions can be combined so that their effects are aggregated when applied against a given set of URLs.
-There are three action files included with Privoxy with differing purposes:
-match-all.action - is used to define @@ -63,7 +54,6 @@ handling etc should be applied by default. It should be the first actions file loaded
default.action - defines many exceptions (both positive and negative) from the default set of actions that's @@ -72,19 +62,16 @@ file is only supposed to be edited by the developers. It should be the second actions file loaded.
user.action - is intended to be for local site preferences and exceptions. As an example, if your ISP or your bank has specific requirements, and need special handling, this kind of thing should go here. This file will not be upgraded.
Edit Set to Cautious Set to Medium Set to Advanced
-These have increasing levels of aggressiveness and have no influence on your browsing unless you select them explicitly in the editor. A default @@ -93,7 +80,6 @@ to more aggressive levels. The more aggressive the settings, then the more likelihood there is of problems such as sites not working as they should.
-The Edit button allows you to turn each action on/off individually for fine-tuning. The Cautious button changes the actions list to @@ -107,166 +93,105 @@ the chart below. The latter three buttons over-ride any changes via with the Edit button. More fine-tuning can be done in the lower sections of this internal page.
-While the actions file editor allows to enable these settings in all actions files, they are only supposed to be enabled in the first one to make sure you don't unintentionally overrule earlier rules.
-The default profiles, and their associated actions, as pre-defined in default.action are:
-Table 1. Default Configurations
-| Feature | -Cautious | -Medium | -Advanced |
|---|---|---|---|
| Ad-blocking Aggressiveness | -medium | -high | -high |
| Ad-filtering by size | -no | -yes | -yes |
| Ad-filtering by link | -no | -no | -yes |
| Pop-up killing | -blocks only | -blocks only | -blocks only |
| Privacy Features | -low | -medium | -medium/high |
| Cookie handling | -none | -session-only | -kill |
| Referer forging | -no | -yes | -yes |
| GIF de-animation | -no | -yes | -yes |
| Fast redirects | -no | -no | -yes |
| HTML taming | -no | -no | -yes |
| JavaScript taming | -no | -no | -yes |
| Web-bug killing | -no | -yes | -yes |
| Image tag reordering | -no | -yes | -yes |
-
- { +handle-as-image +block{Banner ads.} }
+
|
You can trace this process for URL patterns and any given URL by visiting http://config.privoxy.org/show-url-info.
-Examples and more detail on this is provided in the Appendix, Troubleshooting: Anatomy of an Action section.
As mentioned, Privoxy uses "patterns" to determine what actions might apply to which @@ -428,7 +334,6 @@ "emphasis">pattern matching to achieve a high degree of flexibility. This allows one expression to be expanded and potentially match against many similar patterns.
-Generally, an URL pattern has the form <host><port>/<path>, where the <host>, the http://) should not be included in the pattern. This is assumed already!
-The pattern matching syntax is different for the host and path parts of the URL. The host part uses a simple globbing type matching technique, while the path part uses more flexible "Regular Expressions" (POSIX 1003.2).
-The port part of a pattern is a decimal port number preceded by a colon (:). If the host part contains a numerical IPv6 address, it has to be put into angle brackets (<, >).
-is a host-only pattern and will match any request to www.example.com, regardless of which @@ -464,70 +365,52 @@ example.com is different and would NOT match.
means exactly the same. For host-only patterns, the trailing / may be omitted.
matches all the documents on www.example.com whose name starts with /index.html.
matches only the single document /index.html on www.example.com.
matches the document /index.html, regardless of the domain, i.e. on any web server anywhere.
Matches any URL because there's no requirement for either the domain or the path to match anything.
Matches any URL pointing to TCP port 8000.
Matches any URL with the host address 10.0.0.1. (Note that the real URL uses plain brackets, not angle brackets.)
Matches any URL with the host address 2001:db8::1. (Note that the real URL uses plain brackets, not angle brackets.)
matches nothing, since it would be interpreted as a domain name and there is no top-level domain called
The matching of the host part offers some flexible options: if the host pattern starts or ends with a dot, it becomes unanchored at that end. The host pattern is often referred to as domain pattern as it is usually used to match domain names and not IP addresses. For example:
-matches any domain with first-level domain com and second-level domain another-example.
matches any domain that STARTS with www. (It also matches the domain www but most of the time that doesn't matter.)
matches any domain that CONTAINS
Additionally, there are wild-cards that you can use in the domain names themselves. These work similarly to shell globbing type wild-cards: "*" represents zero or more @@ -601,33 +475,25 @@ "QUOTE">"character classes" in square brackets which is similar to the same regular expression technique. All of this can be freely mixed:
-matches "adserver.example.com", "ads.example.com", etc but not "sfads.example.com"
matches all of the above, and then some.
matches www.ipix.com, pictures.epix.com, a.b.c.d.e.upix.com etc.
matches www1.example.com, www4.example.cc,
While flexible, this is not the sophistication of full regular expression based syntax.
Privoxy uses "modern" POSIX 1003.2 "Regular Expressions" for matching the path portion (after the slash), and is thus more flexible.
-There is an Appendix with a brief quick-start into regular expressions, you also might want to have a look at your operating system's documentation on regular expressions (try man re_format).
-Note that the path pattern is automatically left-anchored at the "/", i.e. it matches as if it would start with a "^" (regular expression speak for the beginning of a line).
-Please also note that matching in the path is CASE INSENSITIVE by default, but you can switch to case sensitive at any point in the @@ -672,20 +532,16 @@ only documents whose path starts with PaTtErN in exactly this capitalization.
-Is equivalent to just ".example.com", since any documents within that domain are matched with or without the ".*" regular expression. This is redundant
Will match any page in the domain of "example.com" that is named "www.example.com/testing/index_html", because of the special meta-character ".".
This regular expression is conditional so it will match any page named "index.html" regardless @@ -710,10 +564,8 @@ ".html" (but does not have to end with that!).
This regular expression will match any path of "example.com" that contains any of the words @@ -723,10 +575,8 @@ "QUOTE">"junk". The path does not have to end in these words, just contain them.
This is very much the same as above, except now it must end in either ".jpg",
There are many, many good examples to be found in default.action, and more tutorials below in Appendix on regular expressions.
Tag patterns are used to change the applying actions based on the
- request's tags. Tags can be created with either the
+ Request tag patterns are used to change the applying actions based
+ on the request's tags. Tags can be created based on HTTP headers with
+ either the client-header-tagger or
the server-header-tagger
action. Tag patterns have to start with "TAG:",
- so Privoxy can tell them apart from
- URL patterns. Everything after the colon including white space, is
- interpreted as a regular expression with path pattern syntax, except
- that tag patterns aren't left-anchored automatically (Privoxy doesn't silently add a "^", you have to do it yourself if you need it). Request tag patterns have to start with "TAG:", so Privoxy
+ can tell them apart from other patterns. Everything after the colon
+ including white space, is interpreted as a regular expression with
+ path pattern syntax, except that tag patterns aren't left-anchored
+ automatically (Privoxy doesn't
+ silently add a "^", you have to do it
+ yourself if you need it). To match all requests that are tagged with "foo" your pattern line should be "TAG:^foo$", "TAG:foo"
@@ -768,17 +615,15 @@
contain "foo" somewhere. "TAG: foo" wouldn't work as it requires white
space. Sections can contain URL and tag patterns at the same time, but
- tag patterns are checked after the URL patterns and thus always
- overrule them, even if they are located before the URL patterns. Once a new tag is added, Privoxy checks right away if it's matched
- by one of the tag patterns and updates the action settings
- accordingly. As a result tags can be used to activate other tagger
- actions, as long as these other taggers look for headers that haven't
- already be parsed. Sections can contain URL and request tag patterns at the same
+ time, but request tag patterns are checked after the URL patterns and
+ thus always overrule them, even if they are located before the URL
+ patterns. Once a new request tag is added, Privoxy checks right away if it's
+ matched by one of the request tag patterns and updates the action
+ settings accordingly. As a result request tags can be used to
+ activate other tagger actions, as long as these other taggers look
+ for headers that haven't already be parsed. For example you could tag client requests which use the POST method, then use this tag to activate another
tagger that adds a tag if cookies are sent, and then use a block
@@ -789,34 +634,83 @@
created. The method tagger would look for the request line, but at
the time the cookie tag is created, the request line has already been
parsed. While this is a limitation you should be aware of, this kind of
indirection is seldom needed anyway and even the example doesn't make
too much sense.
To match requests that do not have a certain tag, specify a - negative tag pattern by prefixing the tag pattern line with either + "NEGATIVE-TAG-PATTERNS">8.4.4. The Negative Request Tag + Patterns +
To match requests that do not have a certain request tag, specify + a negative tag pattern by prefixing the tag pattern line with either "NO-REQUEST-TAG:" or "NO-RESPONSE-TAG:" instead of "TAG:".
- -Negative tag patterns created with Negative request tag patterns created with "NO-REQUEST-TAG:" are checked after all client headers are scanned, the ones created with "NO-RESPONSE-TAG:" are checked after all server headers are scanned. In both cases all the created tags are considered.
| Warning | +
|
+ This is an experimental feature. The syntax is likely to + change in future versions. + |
+
Client tag patterns are not set based on HTTP headers but based on + the client's IP address. Users can enable them themselves, but the + Privoxy admin controls which tags are available and what their effect + is.
+After a client-specific tag has been defined with the client-specific-tag, directive, + action sections can be activated based on the tag by using a + CLIENT-TAG pattern. The CLIENT-TAG pattern is evaluated at the same + priority as URL patterns, as a result the last matching pattern wins. + Tags that are created based on client or server headers are evaluated + later on and can overrule CLIENT-TAG and URL patterns!
+The tag is set for all requests that come from clients that + requested it to be set. Note that "clients" are differentiated by IP + address, if the IP address changes the tag has to be requested + again.
+Clients can request tags to be set by using the CGI interface + http://config.privoxy.org/client-tags.
+Example:
+
+
+ # If the admin defined the client-specific-tag circumvent-blocks,
+# and the request comes from a client that previously requested
+# the tag to be set, overrule all previous +block actions that
+# are enabled based on URL to CLIENT-TAG patterns.
+{-block}
+CLIENT-TAG:^circumvent-blocks$
+
+# This section is not overruled because it's located after
+# the previous one.
+{+block{Nobody is supposed to request this.}}
+example.org/blocked-example-page
+ |
+
All actions are disabled by default, until they are explicitly enabled somewhere in an actions file. Actions are turned on if preceded with a "+", and turned off if preceded with @@ -827,65 +721,53 @@ "LITERAL">-block means "don't block URLs that match the following patterns, even if +block previously applied."
-Again, actions are invoked by placing them on a line, enclosed in curly braces and separated by whitespace, like in {+some-action -some-other-action{some-parameter}}, followed by a list of URL patterns, one per line, to which they apply. Together, the actions line and the following pattern lines make up a section of the actions file.
-Actions fall into three categories:
-Boolean, i.e the action can only be "enabled" or "disabled". Syntax:
-
- - +name # enable action name ++name # enable action name -name # disable action name -+"REPLACEABLE">name # disable action name |
Example: +handle-as-image
Parameterized, where some value is required in order to enable this type of action. Syntax:
-
-
- +name{param} # enable action and set parameter to param,
+
|
Note that if the URL matches multiple positive forms of a parameterized action, the last match wins, i.e. the params from earlier matches are simply ignored.
-Example: +hide-user-agent{Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8.1.4) Gecko/20070602 Firefox/2.0.0.4}
Multi-value. These look exactly like parameterized actions, but they behave differently: If the action applies multiple times to @@ -895,38 +777,33 @@ are remembered. This is used for actions that can be executed for the same request repeatedly, like adding multiple headers, or filtering through multiple filters. Syntax:
-
-
- +name{param} # enable action and add param to the list of parameters
+
|
Examples: +add-header{X-Fun-Header: Some text} and +filter{html-annoyances}
If nothing is specified in any actions file, no "actions" are taken. So in this case Privoxy would just be a normal, non-blocking, non-filtering proxy. You must specifically enable the privacy and blocking features you need (although the provided default actions files will give a good starting point).
-Later defined action sections always over-ride earlier ones of the same type. So exceptions to any rules you make, should come in the latter part of the file (or in a file that is processed later when @@ -939,65 +816,58 @@ "QUOTE">"pattern" (because of wildcards and regular expressions), and thus to trigger more than one set of actions! Last match wins.
-The list of valid Privoxy actions are:
-Confuse log analysis, custom applications
Sends a user defined HTTP header to the web server.
Multi-value.
Any string value is possible. Validity of the defined HTTP headers is not checked. It is recommended that you use the "X-" prefix for custom headers.
This action may be specified multiple times, in order to define multiple headers. This is rarely needed for the typical user. If you don't know what "HTTP headers" are, you definitely don't need to worry about this one.
-Headers added by this action are not modified by other actions.
-+add-header{X-User-Tracking: sucks}
-
+ # Add a DNT ("Do not track") header to all requests,
+# event to those that already have one.
+#
+# This is just an example, not a recommendation.
+#
+# There is no reason to believe that user-tracking websites care
+# about the DNT header and depending on the User-Agent, adding the
+# header may make user-tracking easier.
+{+add-header{DNT: 1}}
+/
|
Block ads or other unwanted content
Requests for URLs to which this action applies are blocked, i.e. the requests are trapped by handle-as-empty-document actions.
Parameterized.
A block reason that should be given to the user.
Privoxy sends a special "BLOCKED" page for requests to @@ -1054,7 +913,6 @@ parameter, a link to find out why the block action applies, and a click-through to the blocked content (the latter only if the force feature is available and enabled).
-A very important exception occurs if both block and
-
It is important to understand this process, in order to
understand how Privoxy deals
with ads and other unwanted content. Blocking is a core
feature, and one upon which various other features depend. The filter action can perform a
very similar task, by "blocking"
@@ -1079,15 +935,12 @@
in the first place. Note that this is a totally different
technique, and it's easy to confuse the two.
-
-{+block{No nasty stuff for you.}}
+
|
Improve privacy by not forwarding the source of the request in the HTTP headers.
Deletes the "X-Forwarded-For:" HTTP header from the client request, or adds a new one.
Parameterized.
"block" to delete the header.
"add" to create the header (or append the client's IP address to an already existing @@ -1150,26 +992,19 @@
It is safe and recommended to use block.
-Forwarding the source address of the request may make sense in some multi-user setups but is also a privacy risk.
-
-+change-x-forwarded-for{block}
-
+ +change-x-forwarded-for{block}
|
Rewrite or remove single client headers.
All client headers to which this action applies are filtered on-the-fly through the specified regular expression based substitutions.
Parameterized.
+Multi-value.
The name of a client-header filter, as defined in one of the filter files.
Client-header filters are applied to each header on its own, not to all at once. This makes it easier to diagnose problems, but on the downside you can't write filters that only change header x if header y's value is z. You can do that by using tags though.
-Client-header filters are executed after the other header actions have finished and use their output as input.
-If the request URI gets changed, Privoxy will detect that and use the new one. This can be used to rewrite the request destination behind the client's back, for example to specify a Tor exit relay for certain requests.
-Please refer to the filter file chapter to learn which client-header filters are available by default, and how to create your own.
-# Hide Tor exit notation in Host and Referer Headers
+ # Hide Tor exit notation in Host and Referer Headers
{+client-header-filter{hide-tor-exit-notation}}
/
-
-
+
|
Block requests based on their headers.
Client headers to which this action applies are filtered on-the-fly through the specified regular expression based substitutions, the result is used as tag.
Parameterized.
+Multi-value.
The name of a client-header tagger, as defined in one of the filter files.
Client-header taggers are applied to each header on its own, and as the header isn't modified, each tagger "sees" the original.
-Client-header taggers are the first actions that are executed and their tags can be used to control every other action.
-# Tag every request with the User-Agent header
+ # Tag every request with the User-Agent header
{+client-header-tagger{user-agent}}
/
@@ -1328,17 +1132,15 @@ TAG:^User-Agent: RPM APT-HTTP/
TAG:^User-Agent: fetch libfetch/
TAG:^User-Agent: Ubuntu APT-HTTP/
TAG:^User-Agent: MPlayer/
-
-
+
|
-# Tag all requests with the Range header set
+ # Tag all requests with the Range header set
{+client-header-tagger{range-requests}}
/
@@ -1350,8 +1152,7 @@ TAG:^User-Agent: MPlayer/
# parts of multimedia files.
{-filter -deanimate-gifs}
TAG:^RANGE-REQUEST$
-
-
+
|
Stop useless download menus from popping up, or change the browser's rendering mode
Replaces the "Content-Type:" HTTP server header.
Parameterized.
Any string.
The "Content-Type:" HTTP server header is used by the browser to decide what to do with the @@ -1401,14 +1191,12 @@ TAG:^RANGE-REQUEST$ open a download menu instead of displaying the document by itself, even if the document's format is supported by the browser.
-The declared content type can also affect which rendering mode the browser chooses. If XHTML is delivered as "text/html", many browsers treat it as yet another broken HTML document. If it is send as "application/xml", browsers with XHTML support will only display it, if the syntax is correct.
-If you see a web site that proudly uses XHTML buttons, but sets "Content-Type: text/html", you can use Privoxy to overwrite @@ -1416,13 +1204,11 @@ TAG:^RANGE-REQUEST$ validate the web master's claim inside your XHTML-supporting browser. If the syntax is incorrect, the browser will complain loudly.
-You can also go the opposite direction: if your browser prints error messages instead of rendering a document falsely declared as XHTML, you can overwrite the content type with "text/html" and have it rendered as broken HTML document.
-By default content-type-overwrite only replaces "Content-Type:" headers that look like some kind of text. If you want to @@ -1431,36 +1217,31 @@ TAG:^RANGE-REQUEST$ "actions-file.html#FORCE-TEXT-MODE">force-text-mode. This limitation exists for a reason, think twice before circumventing it.
-Most of the time it's easier to replace this action with a custom server-header filter. It allows you to activate it for every document of a certain site and it will still only replace the content types you aimed at.
-Of course you can apply content-type-overwrite to a whole site and then make URL based exceptions, but it's a lot more work to get the same precision.
-# Check if www.example.net/ really uses valid XHTML
+ # Check if www.example.net/ really uses valid XHTML
{ +content-type-overwrite{application/xml} }
www.example.net/
# but leave the content type unmodified if the URL looks like a style sheet
{-content-type-overwrite}
www.example.net/.*\.css$
-www.example.net/.*style
-
+www.example.net/.*style
|
Remove a client header Privoxy has no dedicated action for.
Deletes every header sent by the client that contains the string the user supplied as parameter.
Parameterized.
Any string.
This action allows you to block client headers for which no dedicated Privoxy action exists. Privoxy will remove every client header that contains the string you supplied as parameter.
-Regular expressions are not supported and you can't use this action to block different headers in the same request, unless they contain the same string.
-crunch-client-header is only meant for quick tests. If you have to block several different headers, or only want to modify parts of them, you should use a client-header filter.
-| Warning |
|
Don't block any header without understanding the @@ -1537,19 +1303,16 @@ www.example.net/.*style |
-# Block the non-existent "Privacy-Violation:" client header
+ # Block the non-existent "Privacy-Violation:" client header
{ +crunch-client-header{Privacy-Violation:} }
/
-
-
+
|
Prevent yet another way to track the user's steps between sessions.
Deletes the "If-None-Match:" HTTP client header.
Boolean.
N/A
Removing the "If-None-Match:" HTTP client header is useful for filter testing, where you want to force a real reload instead of getting status code "304" which would cause the browser to use a cached copy of the page.
-It is also useful to make sure the header isn't used as a cookie replacement (unlikely but possible).
-Blocking the "If-None-Match:" header shouldn't cause any caching problems, as long as the "If-Modified-Since:" header isn't blocked or missing as well.
-It is recommended to use this action together with hide-if-modified-since and overwrite-last-modified.
-# Let the browser revalidate cached documents but don't
+ # Let the browser revalidate cached documents but don't
# allow the server to use the revalidation headers for user tracking.
{+hide-if-modified-since{-60} \
+overwrite-last-modified{randomize} \
+crunch-if-none-match}
-/
-
+/
|
Prevent the web server from setting HTTP cookies on your system
Deletes any "Set-Cookie:" HTTP headers from server replies.
Boolean.
N/A
This action is only concerned with incoming HTTP @@ -1679,7 +1414,6 @@ www.example.net/.*style "actions-file.html#CRUNCH-OUTGOING-COOKIES">crunch-outgoing-cookies. Use both to disable HTTP cookies completely.
-It makes no sense at all to use this action in conjunction with the filter-content-cookies.
- -+crunch-incoming-cookies -+ +crunch-incoming-cookies |
Remove a server header Privoxy has no dedicated action for.
Deletes every header sent by the server that contains the string the user supplied as parameter.
Parameterized.
Any string.
This action allows you to block server headers for which no dedicated Privoxy action exists. Privoxy will remove every server header that contains the string you supplied as parameter.
-Regular expressions are not supported and you can't use this action to block different headers in the same request, unless they contain the same string.
-crunch-server-header is only meant for quick tests. If you have to block several different headers, or only want to modify parts of them, you should use a custom server-header filter.
-| Warning |
|
Don't block any header without understanding the @@ -1774,18 +1489,15 @@ www.example.net/.*style |
-# Crunch server headers that try to prevent caching
+ # Crunch server headers that try to prevent caching
{ +crunch-server-header{no-cache} }
-/
-
+/
|
Prevent the web server from reading any HTTP cookies from your system
Deletes any "Cookie:" HTTP headers from client requests.
Boolean.
N/A
This action is only concerned with outgoing HTTP @@ -1837,7 +1538,6 @@ www.example.net/.*style "actions-file.html#CRUNCH-INCOMING-COOKIES">crunch-incoming-cookies. Use both to disable HTTP cookies completely.
-It makes no sense at all to use this action in conjunction with the
- -+crunch-outgoing-cookies -+ +crunch-outgoing-cookies |
Stop those annoying, distracting animated GIF images.
De-animate GIF animations, i.e. reduce them to their first or last image.
Parameterized.
"last" or "first"
This will also shrink the images considerably (in bytes, not pixels!). If the option "first" is @@ -1906,21 +1591,16 @@ www.example.net/.*style makes more sense for most banner animations, but also has the risk of not showing the entire last frame (if it is only a delta to an earlier frame).
-You can safely use this action with patterns that will also match non-GIF objects, because no attempt will be made at anything that doesn't look like a GIF.
-
-+deanimate-gifs{last}
-
+ +deanimate-gifs{last}
|
Work around (very rare) problems with HTTP/1.1
Downgrades HTTP/1.1 client requests and server replies to HTTP/1.0.
Boolean.
N/A
This is a left-over from the time when Privoxy didn't support important HTTP/1.1 features well. It is left here for the unlikely case that you experience HTTP/1.1-related problems with some server out there.
-Note that enabling this action is only a workaround. It should not be enabled for sites that work without it. While it shouldn't break any pages, it has an (usually negative) performance impact.
-If you come across a site where enabling this action helps, please report it, so the cause of the problem can be analyzed. If the problem turns out to be caused by a bug in Privoxy it should be fixed so the following release works without the work around.
-
-{+downgrade-http-version}
-problem-host.example.com
-
+ {+downgrade-http-version}
+problem-host.example.com
|
Modify content using a programming language of your choice.
All instances of text-based type, most notably HTML and JavaScript, to which this action applies, can be filtered @@ -2022,15 +1680,11 @@ problem-host.example.com servers often use the text/plain MIME type for all files whose type they don't know.)
Parameterized.
+Multi-value.
The name of an external content filter, as defined in the filter file. External filters @@ -2038,14 +1692,11 @@ problem-host.example.com filterfile option in the config file.
-When used in its negative form, and without parameters, all filtering with external filters is completely disabled.
External filters are scripts or programs that can modify the content in case common filter section apply.
-| Warning |
|
Currently external filters are executed with @@ -2070,22 +1719,17 @@ problem-host.example.com |
This feature is experimental, the syntax may change in the future.
-
-+external-filter{fancy-filter}
-
+ +external-filter{fancy-filter}
|
Fool some click-tracking scripts and speed up indirect links.
Detects redirection URLs and redirects the browser without contacting the redirection server first.
Parameterized.
"check-decoded-url" to decode URLs (if necessary) before searching for redirection @@ -2137,9 +1771,7 @@ problem-host.example.com
Many sites, like yahoo.com, don't just link to other sites. Instead, they will link to some script on their own servers, @@ -2147,7 +1779,6 @@ problem-host.example.com you to the final target. URLs resulting from this scheme typically look like: "http://www.example.org/click-tracker.cgi?target=http%3a//www.example.net/".
-Sometimes, there are even multiple consecutive redirects encoded in the URL. These redirections via scripts make your web browsing more traceable, since the server from which you @@ -2155,12 +1786,10 @@ problem-host.example.com valuable bandwidth and time is wasted, while your browser asks the server for one redirect after the other. Plus, it feeds the advertisers.
-This feature is currently not very smart and is scheduled for improvement. If it is enabled by default, you will have to create some exceptions to this action. It can lead to failures in several ways:
-Not every URLs with other URLs as parameters is evil. Some sites offer a real service that requires this information to work. For example a validation service needs to know, which @@ -2169,7 +1798,6 @@ problem-host.example.com a redirection target, and will always redirect to the last one. Most of the time the assumption is correct, but if it isn't, the user gets redirected anyway.
-Another failure occurs if the URL contains other parameters after the URL parameter. The URL: "http://www.example.org/?redirect=http%3a//www.example.net/&foo=bar". @@ -2184,7 +1812,6 @@ problem-host.example.com using the redirect action to remove the last part of the URL, but it requires a little effort.
-To detect a redirection URL, fast-redirects only looks for the string "http://", either in plain text @@ -2195,20 +1822,16 @@ problem-host.example.com "LITERAL">fast-redirects is fooled and the request reaches the redirection server where it probably gets logged.
-
- { +fast-redirects{simple-check} }
+
|
Get rid of HTML and JavaScript annoyances, banner advertisements (by size), do fun text replacements, add personalized effects, etc.
All instances of text-based type, most notably HTML and JavaScript, to which this action applies, can be filtered @@ -2242,15 +1860,11 @@ problem-host.example.com text/plain MIME type for all files whose type they don't know.)
Parameterized.
+Multi-value.
The name of a content filter, as defined in the filter file. Filters can be defined in @@ -2261,19 +1875,15 @@ problem-host.example.com supplied by the developers. Locally defined filters should go in their own file, such as user.filter.
-When used in its negative form, and without parameters, all filtering is completely disabled.
For your convenience, there are a number of pre-defined filters available in the distribution filter file that you can use. See the examples below for a list.
-Filtering requires buffering the page content, which may appear to slow down page rendering since nothing is displayed until all content has passed the filters. (The total time until @@ -2281,7 +1891,6 @@ problem-host.example.com be perceived as slower since the page is not incrementally displayed.) This effect will be more noticeable on slower connections.
-"Rolling your own" filters requires a knowledge of "action" is not available.
-The amount of data that can be filtered is limited to the buffer-limit option in the main config file. The default is 4096 KB (4 Megs). Once this limit is exceeded, the buffered data, and all pending data, is passed through unfiltered.
-Inappropriate MIME types, such as zipped files, are not filtered at all. (Again, only text-based types except plain text). Encrypted SSL data (from HTTPS servers) cannot be @@ -2307,20 +1914,17 @@ problem-host.example.com protect certain text, like source code, from filtering by defining appropriate -filter exceptions.
-Compressed content can't be filtered either, but if Privoxy is compiled with zlib support and a supported compression algorithm is used (gzip or deflate), Privoxy can first decompress the content and then filter it.
-If you use a Privoxy version without zlib support, but want filtering to work on as much documents as possible, even those that would normally be sent compressed, you must use the prevent-compression action in conjunction with filter.
-Content filtering can achieve some of the same effects as the block action, i.e. it can be @@ -2328,360 +1932,276 @@ problem-host.example.com differently. One effective use, is to block ad banners based on their size (see below), since many of these seem to be somewhat standardized.
-Feedback with suggestions for new or improved filters is particularly welcome!
-The below list has only the names and a one-line description of each predefined filter. There are more verbose explanations of what these filters do in the filter file chapter.
-+filter{js-annoyances} # Get rid of particularly annoying JavaScript abuse.
-
+ +filter{js-annoyances} # Get rid of particularly annoying JavaScript abuse.
|
-+filter{js-events} # Kill JavaScript event bindings and timers (Radically destructive! Only for extra nasty sites).
-
+ +filter{js-events} # Kill JavaScript event bindings and timers (Radically destructive! Only for extra nasty sites).
|
-+filter{html-annoyances} # Get rid of particularly annoying HTML abuse.
-
+ +filter{html-annoyances} # Get rid of particularly annoying HTML abuse.
|
-+filter{content-cookies} # Kill cookies that come in the HTML or JS content.
-
+ +filter{content-cookies} # Kill cookies that come in the HTML or JS content.
|
-+filter{refresh-tags} # Kill automatic refresh tags if refresh time is larger than 9 seconds.
-
+ +filter{refresh-tags} # Kill automatic refresh tags if refresh time is larger than 9 seconds.
|
-+filter{unsolicited-popups} # Disable only unsolicited pop-up windows.
-
+ +filter{unsolicited-popups} # Disable only unsolicited pop-up windows.
|
-+filter{all-popups} # Kill all popups in JavaScript and HTML.
-
+ +filter{all-popups} # Kill all popups in JavaScript and HTML.
|
-+filter{img-reorder} # Reorder attributes in <img> tags to make the banners-by-* filters more effective.
-
+ +filter{img-reorder} # Reorder attributes in <img> tags to make the banners-by-* filters more effective.
|
-+filter{banners-by-size} # Kill banners by size.
-
+ +filter{banners-by-size} # Kill banners by size.
|
-+filter{banners-by-link} # Kill banners by their links to known clicktrackers.
-
+ +filter{banners-by-link} # Kill banners by their links to known clicktrackers.
|
-+filter{webbugs} # Squish WebBugs (1x1 invisible GIFs used for user tracking).
-
+ +filter{webbugs} # Squish WebBugs (1x1 invisible GIFs used for user tracking).
|
-+filter{tiny-textforms} # Extend those tiny textareas up to 40x80 and kill the hard wrap.
-
+ +filter{tiny-textforms} # Extend those tiny textareas up to 40x80 and kill the hard wrap.
|
-+filter{jumping-windows} # Prevent windows from resizing and moving themselves.
-
+ +filter{jumping-windows} # Prevent windows from resizing and moving themselves.
|
-+filter{frameset-borders} # Give frames a border and make them resizable.
-
+ +filter{frameset-borders} # Give frames a border and make them resizable.
|
-+filter{iframes} # Removes all detected iframes. Should only be enabled for individual sites.
-
+ +filter{iframes} # Removes all detected iframes. Should only be enabled for individual sites.
|
-+filter{demoronizer} # Fix MS's non-standard use of standard charsets.
-
+ +filter{demoronizer} # Fix MS's non-standard use of standard charsets.
|
-+filter{shockwave-flash} # Kill embedded Shockwave Flash objects.
-
+ +filter{shockwave-flash} # Kill embedded Shockwave Flash objects.
|
-+filter{quicktime-kioskmode} # Make Quicktime movies saveable.
-
+ +filter{quicktime-kioskmode} # Make Quicktime movies saveable.
|
-+filter{fun} # Text replacements for subversive browsing fun!
-
+ +filter{fun} # Text replacements for subversive browsing fun!
|
-+filter{crude-parental} # Crude parental filtering. Note that this filter doesn't work reliably.
-
+ +filter{crude-parental} # Crude parental filtering. Note that this filter doesn't work reliably.
|
-+filter{ie-exploits} # Disable some known Internet Explorer bug exploits.
-
+ +filter{ie-exploits} # Disable some known Internet Explorer bug exploits.
|
-+filter{site-specifics} # Cure for site-specific problems. Don't apply generally!
-
+ +filter{site-specifics} # Cure for site-specific problems. Don't apply generally!
|
-+filter{no-ping} # Removes non-standard ping attributes in <a> and <area> tags.
-
+ +filter{no-ping} # Removes non-standard ping attributes in <a> and <area> tags.
|
-+filter{google} # CSS-based block for Google text ads. Also removes a width limitation and the toolbar advertisement.
-
+ +filter{google} # CSS-based block for Google text ads. Also removes a width limitation and the toolbar advertisement.
|
-+filter{yahoo} # CSS-based block for Yahoo text ads. Also removes a width limitation.
-
+ +filter{yahoo} # CSS-based block for Yahoo text ads. Also removes a width limitation.
|
-+filter{msn} # CSS-based block for MSN text ads. Also removes tracking URLs and a width limitation.
-
+ +filter{msn} # CSS-based block for MSN text ads. Also removes tracking URLs and a width limitation.
|
-+filter{blogspot} # Cleans up some Blogspot blogs. Read the fine print before using this.
-
+ +filter{blogspot} # Cleans up some Blogspot blogs. Read the fine print before using this.
|
Force Privoxy to treat a document as if it was in some kind of text format.
Declares a document as text, even if the "Content-Type:" isn't detected as such.
Boolean.
N/A
As explained above, force-text-mode declares a document as text, without looking at the "Content-Type:" first.
-| Warning |
|
Think twice before activating this action. Filtering @@ -2752,17 +2259,13 @@ problem-host.example.com |
- -+force-text-mode - -+ +force-text-mode + |
Change the forwarding settings based on User-Agent or request origin
Overrules the forward directives in the configuration file.
Multi-value.
+Parameterized.
"forward ." to use a direct connection without any additional proxies.
"forward 127.0.0.1:8123" to use the HTTP proxy listening at 127.0.0.1 port 8123.
"forward-socks4a 127.0.0.1:9050 ." to use the socks4a proxy listening at 127.0.0.1 @@ -2821,7 +2313,6 @@ problem-host.example.com "QUOTE">"forward-socks5" for socks5 connections (with remote DNS resolution).
"forward-socks4a 127.0.0.1:9050 proxy.example.org:8000" to use the socks4a proxy @@ -2833,24 +2324,39 @@ problem-host.example.com "forward-socks5" for socks5 connections (with remote DNS resolution).
"forward-webserver + 127.0.0.1:80" to use the HTTP server listening at + 127.0.0.1 port 80 without adjusting the request + headers.
+This makes it more convenient to use Privoxy to make + existing websites available as onion services as well.
+Many websites serve content with hardcoded URLs and + can't be easily adjusted to change the domain based on the + one used by the client.
+Putting Privoxy between Tor and the webserver (or an + stunnel that forwards to the webserver) allows to rewrite + headers and content to make client and server happy at the + same time.
+Using Privoxy for webservers that are only reachable + through onion addresses and whose location is supposed to + be secret is not recommended and should not be necessary + anyway.
+This action takes parameters similar to the forward directives in the configuration file, but without the URL pattern. It can be used as replacement, but normally it's only used in cases where matching based on the request URL isn't sufficient.
-
-# Use an ssh tunnel for requests previously tagged as
+ # Use an ssh tunnel for requests previously tagged as
# "User-Agent: fetch libfetch/2.0" and make sure
# resuming downloads continues to work.
#
@@ -2898,8 +2400,7 @@ problem-host.example.com
-overwrite-last-modified \
}
TAG:^User-Agent: fetch libfetch/2\.0$
-
-
+
|
Mark URLs that should be replaced by empty documents if they get blocked
This action alone doesn't do anything noticeable. It just marks URLs. If the empty document isn't literally empty, but actually contains a single space.
Boolean.
N/A
Some browsers complain about syntax errors if JavaScript documents are blocked with Privoxy BLOCKED message in frames.
-The content type for the empty document can be specified with content-type-overwrite{}, but usually this isn't necessary.
-# Block all documents on example.org that end with ".js",
+ # Block all documents on example.org that end with ".js",
# but send an empty document instead of the usual HTML message.
{+block{Blocked JavaScript} +handle-as-empty-document}
example.org/.*\.js$
-
-
+
|
Mark URLs as belonging to images (so they'll be replaced by images if they do get blocked, rather than HTML pages)
This action alone doesn't do anything noticeable. It just marks URLs as images. If the
Boolean.
N/A
The below generic example section is actually part of default.action. It marks all URLs with well-known image file name extensions as images and should be left intact.
-Users will probably only want to use the handle-as-image action in conjunction with block, to block sources of banners, whose URLs don't reflect the file type, like in the second example section.
-Note that you cannot treat HTML pages as images in most cases. For instance, (in-line) ad frames require an HTML page to be sent, or they won't display properly. Forcing
-
-# Generic image extensions:
+
|
Pretend to use different language settings.
Deletes or replaces the "Accept-Language:" HTTP header in client requests.
Parameterized.
Keyword: "block", or any user defined value.
Faking the browser's language settings can be useful to make a foreign User-Agent set with hide-user-agent more believable.
-However some sites with content in different languages check the "Accept-Language:" to decide which one to take by default. Sometimes it isn't possible to later switch to another language without changing the "Accept-Language:" header first.
-Therefore it's a good idea to either only change the "Accept-Language:" header to languages you understand, or to languages that aren't wide spread.
-Before setting the "Accept-Language:" header to a rare language, you should consider that it helps to make your requests unique and thus easier to trace. If you don't plan to change this header frequently, you should stick to a common language.
-# Pretend to use Canadian language settings.
+ # Pretend to use Canadian language settings.
{+hide-accept-language{en-ca} \
+hide-user-agent{Mozilla/5.0 (X11; U; OpenBSD i386; en-CA; rv:1.8.0.4) Gecko/20060628 Firefox/1.5.0.4} \
}
-/
-
+/
|
Prevent download menus for content you prefer to view inside the browser.
Deletes or replaces the "Content-Disposition:" HTTP header set by some servers.
Parameterized.
Keyword: "block", or any user defined value.
Some servers set the "Content-Disposition:" HTTP header for documents @@ -3198,12 +2639,10 @@ nasty-banner-server.example.com/junk.cgi\?output=trash "Content-Disposition:" header contains the file name the browser is supposed to use by default.
-In most browsers that understand this header, it makes it impossible to just view the document, without downloading it first, even if it's just a simple text file or an image.
-Removing the "Content-Disposition:" header helps to prevent this annoyance, but some browsers additionally check the @@ -3211,28 +2650,23 @@ nasty-banner-server.example.com/junk.cgi\?output=trash decide if they can display a document without saving it first. In these cases, you have to change this header as well, before the browser stops displaying download menus.
-It is also possible to change the server's file name suggestion to another one, but in most cases it isn't worth the time to set it up.
-This action will probably be removed in the future, use server-header filters instead.
-# Disarm the download link in Sourceforge's patch tracker
+ # Disarm the download link in Sourceforge's patch tracker
{ -filter \
+content-type-overwrite{text/plain}\
+hide-content-disposition{block} }
- .sourceforge.net/tracker/download\.php
-
+ .sourceforge.net/tracker/download\.php
|
Prevent yet another way to track the user's steps between sessions.
Deletes the "If-Modified-Since:" HTTP client header or modifies its value.
Parameterized.
Keyword: "block", or a user defined value that specifies a range of hours.
Removing this header is useful for filter testing, where you want to force a real reload instead of getting status code "304", which would cause the browser to use a cached copy of the page.
-Instead of removing the header, hide-if-modified-since can also add or subtract a random amount of time to/from the header's value. You specify @@ -3289,37 +2711,31 @@ nasty-banner-server.example.com/junk.cgi\?output=trash from and Privoxy does the rest. A negative value means subtracting, a positive value adding.
-Randomizing the value of the "If-Modified-Since:" makes it less likely that the server can use the time as a cookie replacement, but you will run into caching problems if the random range is too high.
-It is a good idea to only use a small negative value and let overwrite-last-modified handle the greater changes.
-It is also recommended to use this action together with crunch-if-none-match, otherwise it's more or less pointless.
-# Let the browser revalidate but make tracking based on the time less likely.
+ # Let the browser revalidate but make tracking based on the time less likely.
{+hide-if-modified-since{-60} \
+overwrite-last-modified{randomize} \
+crunch-if-none-match}
-/
-
+/
|
Keep your (old and ill) browser from telling web servers your email address
Deletes any existing "From:" HTTP header, or replaces it with the specified string.
Parameterized.
Keyword: "block", or any user defined value.
The keyword "block" will completely remove the header (not to be confused with the block action).
-Alternately, you can specify any value you prefer to be sent to the web server. If you do, it is a matter of fairness not to use any address that is actually used by a real person.
-This action is rarely needed, as modern web browsers don't send "From:" headers anymore.
-
-+hide-from-header{block}
-
+ +hide-from-header{block}
|
-+hide-from-header{spam-me-senseless@sittingduck.example.com}
-
+ +hide-from-header{spam-me-senseless@sittingduck.example.com}
|
Conceal which link you followed to get to a particular site
Deletes the "Referer:" (sic) HTTP header from the client request, or replaces it with a forged one.
Parameterized.
"conditional-block" to delete the header completely if the host has changed.
"conditional-forge" to forge the header if the host has changed.
"block" to delete the header unconditionally.
"forge" to pretend to be coming from the homepage of the server we are talking to.
Any other string to set a user defined referrer.
conditional-block is the only parameter, that isn't easily detected in the server's log file. If it blocks the referrer, the request will look like the visitor used a bookmark or typed in the address directly.
-Leaving the referrer unmodified for requests on the same host allows the server owner to see the visitor's "click path", but in most cases she could also @@ -3477,17 +2858,14 @@ nasty-banner-server.example.com/junk.cgi\?output=trash for example the User-Agent if it isn't a very common one, or the user's IP address if it doesn't change between different requests.
-Always blocking the referrer, or using a custom one, can lead to failures on servers that check the referrer before they answer any requests, in an attempt to prevent their content from being embedded or linked to elsewhere.
-Both conditional-block and forge will work with referrer checks, as long as content and valid referring page are on the same host. Most of the time that's the case.
-hide-referer is an alternate spelling of hide-referrer and the two can be can be freely substituted with each other. ("referer".)
-
-+hide-referrer{forge}
-
+ +hide-referrer{forge}
|
-+hide-referrer{http://www.yahoo.com/}
-
+ +hide-referrer{http://www.yahoo.com/}
|
Try to conceal your type of browser and client operating system
Replaces the value of the "User-Agent:" HTTP header in client requests with the specified value.
Parameterized.
Any user-defined string.
| Warning |
|
This can lead to problems on web sites that depend @@ -3577,7 +2937,6 @@ nasty-banner-server.example.com/junk.cgi\?output=trash |
Using this action in multi-user setups or wherever different
types of browsers will access the same Privoxy is
-
More information on known user-agent strings can be found at
http://www.user-agents.org/ and http://en.wikipedia.org/wiki/User_agent.
-+hide-user-agent{Netscape 6.1 (X11; I; Linux 2.4.18 i686)}
-
+ +hide-user-agent{Netscape 6.1 (X11; I; Linux 2.4.18 i686)}
|
Prevent abuse of Privoxy as a TCP proxy relay or disable SSL for untrusted sites
Specifies to which ports HTTP CONNECT requests are allowable.
Parameterized.
A comma-separated list of ports or port ranges (the latter using dashes, with the minimum defaulting to 0 and the maximum to 65K).
By default, i.e. if no limit-connect action applies, limit-connect if fine-grained control is desired for some or all destinations.
-The CONNECT methods exists in HTTP to allow access to secure websites ("https://" URLs) through proxies. It works very simply: the proxy connects to the server @@ -3664,27 +3007,23 @@ nasty-banner-server.example.com/junk.cgi\?output=trash to the client and to the remote server. This means CONNECT-enabled proxies can be used as TCP relays very easily.
-Privoxy relays HTTPS traffic without seeing the decoded content. Websites can leverage this limitation to circumvent Privoxy's filters. By specifying an invalid port range you can disable HTTPS entirely.
-+limit-connect{443} # Port 443 is OK.
+ +limit-connect{443} # Port 443 is OK.
+limit-connect{80,443} # Ports 80 and 443 are OK.
+limit-connect{-3, 7, 20-100, 500-} # Ports less than 3, 7, 20 to 100 and above 500 are OK.
+limit-connect{-} # All ports are OK
-+limit-connect{,} # No HTTPS/SSL traffic is allowed
-
++limit-connect{,} # No HTTPS/SSL traffic is allowed
|
Limit the lifetime of HTTP cookies to a couple of minutes or hours.
Overwrites the expires field in Set-Cookie server headers if it's above the specified limit.
Parameterized.
The lifetime limit in minutes, or 0.
This action reduces the lifetime of HTTP cookies coming from the server to the specified number of minutes, starting from the time the cookie passes Privoxy.
-Cookies with a lifetime below the limit are not modified. The lifetime of session cookies is set to the specified limit.
-The effect of this action depends on the server.
-In case of servers which refresh their cookies with each response (or at least frequently), the lifetime limit set by this action is updated as well. Thus, a session associated with the cookie continues to work with this action enabled, as long as a new request is made before the last limit set is reached.
-However, some servers send their cookies once, with a lifetime of several years (the year 2037 is a popular choice), and do not refresh them until a certain event in the future, for example the user logging out. In this case this action may limit the absolute lifetime of the session, even if requests are made frequently.
-If the parameter is "0", this action behaves like session-cookies-only.
-
-+limit-cookie-lifetime{60}
-
-
+ +limit-cookie-lifetime{60}
+
|
Ensure that servers send the content uncompressed, so it can be passed through filters.
Removes the Accept-Encoding header which can be used to ask for compressed transfer.
Boolean.
N/A
More and more websites send their content compressed by default, which is generally a good idea and saves bandwidth. @@ -3818,7 +3126,6 @@ nasty-banner-server.example.com/junk.cgi\?output=trash "LITERAL">deanimate-gifs actions need access to the uncompressed data.
-When compiled with zlib support (available since Privoxy 3.0.7), content that should be filtered is decompressed on-the-fly and you don't @@ -3826,17 +3133,14 @@ nasty-banner-server.example.com/junk.cgi\?output=trash Privoxy version, or one that hasn't been compiled with zlib support, this action can be used to convince the server to send the content uncompressed.
-Most text-based instances compress very well, the size is seldom decreased by less than 50%, for markup-heavy instances like news feeds saving more than 90% of the original size isn't unusual.
-Not using compression will therefore slow down the transfer, and you should only enable this action if you really need it. As of Privoxy 3.0.7 it's disabled in all predefined action settings.
-Note that some (rare) ill-configured sites don't handle requests for uncompressed documents correctly. Broken PHP applications tend to send an empty document body, some IIS @@ -3845,15 +3149,13 @@ nasty-banner-server.example.com/junk.cgi\?output=trash might want to add exceptions for those sites. See the example for how to do that.
-# Selectively turn off compression, and enable a filter
+ # Selectively turn off compression, and enable a filter
#
{ +filter{tiny-textforms} +prevent-compression }
# Match only these sites
@@ -3869,8 +3171,7 @@ nasty-banner-server.example.com/junk.cgi\?output=trash
# Then maybe make exceptions for broken sites:
#
{ -prevent-compression }
-.compusa.com/
-
+.compusa.com/
|
Prevent yet another way to track the user's steps between sessions.
Deletes the "Last-Modified:" HTTP server header or modifies its value.
Parameterized.
One of the keywords: "block", "reset-to-request-time" and "randomize"
Removing the "Last-Modified:" header is useful for filter testing, where you want to force a real reload instead of getting status code "304", which would cause the browser to reuse the old version of the page.
-The "randomize" option overwrites the value of the "Last-Modified:" header with a randomly chosen time between the original value @@ -3931,7 +3220,6 @@ nasty-banner-server.example.com/junk.cgi\?output=trash using cookies. "Randomize" makes it impossible and the browser can still revalidate cached documents.
-"reset-to-request-time" overwrites the value of the "Last-Modified:" header with the current time. @@ -3939,7 +3227,6 @@ nasty-banner-server.example.com/junk.cgi\?output=trash "LITERAL">hide-if-modified-since to further customize your random range.
-The preferred parameter here is "randomize". It is safe to use, as long as the time settings are more or less correct. If the server sets the @@ -3949,25 +3236,21 @@ nasty-banner-server.example.com/junk.cgi\?output=trash second time with hided-if-modified-since, just to be sure.
-It is also recommended to use this action together with crunch-if-none-match.
-# Let the browser revalidate without being tracked across sessions
+ # Let the browser revalidate without being tracked across sessions
{ +hide-if-modified-since{-60} \
+overwrite-last-modified{randomize} \
+crunch-if-none-match}
-/
-
+/
|
Redirect requests to other sites.
Convinces the browser that the requested document has been moved to another location and the browser should get it from there.
Parameterized
An absolute URL or a single pcrs command.
Requests to which this action applies are answered with a HTTP redirect to URLs of your choosing. The new URL is either provided as parameter, or derived by applying a single pcrs command to the original URL.
-The syntax for pcrs commands is documented in the filter file section.
-Requests can't be blocked and redirected at the same time, applying this action together with block is a configuration error. Currently the request is blocked and an error message logged, the behavior may change in the future and result in Privoxy rejecting the action file.
-This action can be combined with fast-redirects{check-decoded-url} to redirect to a decoded version of a rewritten URL.
-Use this action carefully, make sure not to create redirection loops and be aware that using your own redirects might make it possible to fingerprint your requests.
-In case of problems with your redirects, or simply to watch them working, enable debug 128.
-# Replace example.com's style sheet with another one
+ # Replace example.com's style sheet with another one
{ +redirect{http://localhost/css-replacements/example.com.css} }
example.com/stylesheet\.css
# Create a short, easy to remember nickname for a favorite site
# (relies on the browser to accept and forward invalid URLs to Privoxy)
-{ +redirect{http://www.privoxy.org/user-manual/actions-file.html} }
+{ +redirect{https://www.privoxy.org/user-manual/actions-file.html} }
a
# Always use the expanded view for Undeadly.org articles
@@ -4086,8 +3351,7 @@ i[0-9][0-9][0-9][0-9]*/
# Redirect remote requests for this manual
# to the local version delivered by Privoxy
{+redirect{s@^http://www@http://config@}}
-www.privoxy.org/user-manual/
-
+www.privoxy.org/user-manual/
|
Rewrite or remove single server headers.
All server headers to which this action applies are filtered on-the-fly through the specified regular expression based substitutions.
Parameterized.
+Multi-value.
The name of a server-header filter, as defined in one of the filter files.
Server-header filters are applied to each header on its own, not to all at once. This makes it easier to diagnose problems, but on the downside you can't write filters that only change header x if header y's value is z. You can do that by using tags though.
-Server-header filters are executed after the other header actions have finished and use their output as input.
-Please refer to the filter file chapter to learn which server-header filters are available by default, and how to create your own.
-
-{+server-header-filter{html-to-xml}}
+
|
Enable or disable filters based on the Content-Type header.
Server headers to which this action applies are filtered on-the-fly through the specified regular expression based substitutions, the result is used as tag.
Parameterized.
+Multi-value.
The name of a server-header tagger, as defined in one of the filter files.
Server-header taggers are applied to each header on its own, and as the header isn't modified, each tagger "sees" the original.
-Server-header taggers are executed before all other header actions that modify server headers. Their tags can be used to control all of the other server-header actions, the content filters and the crunch actions (redirect and block).
-Obviously crunching based on tags created by server-header taggers doesn't prevent the request from showing up in the server's log file.
-# Tag every request with the content type declared by the server
+ # Tag every request with the content type declared by the server
{+server-header-tagger{content-type}}
/
@@ -4240,8 +3472,7 @@ example.org/instance-that-is-delivered-as-xml-but-is-not
"filter-file.html#EXTERNAL-FILTER-SYNTAX">silly example.
{+external-filter{rotate-image} +force-text-mode}
TAG:^image/
-
-
+
|
Allow only temporary "session" cookies (for the current browser session only).
Deletes the "expires" field from "Set-Cookie:" server headers. Most browsers will not store such cookies permanently and forget them in between sessions.
Boolean.
N/A
This is less strict than crunch-incoming-cookies @@ -4295,7 +3515,6 @@ TAG:^image/ and allows you to browse websites that insist or rely on setting cookies, without compromising your privacy too badly.
-Most browsers will not permanently store cookies that have been processed by session-cookies-only and will forget about them between sessions. This makes @@ -4303,7 +3522,6 @@ TAG:^image/ cookies so that you can log in for transactions. This is generally turned on for all sites, and is the recommended setting.
-It makes no sense at all to use session-cookies-only together with crunch-outgoing-cookies. If you do, cookies will be plainly killed.
-Note that it is up to the browser how it handles such cookies without an "expires" field. If you use an exotic browser, you might want to try it out to be sure.
-This setting also has no effect on cookies that may have been stored previously by the browser before starting Privoxy. These would have to be removed manually.
-Privoxy also uses the content-cookies @@ -4330,16 +3545,12 @@ TAG:^image/ not effected by session-cookies-only.
- -+session-cookies-only -+ +session-cookies-only |
Choose the replacement for blocked images
This action alone doesn't do anything noticeable. If both @@ -4376,15 +3582,11 @@ TAG:^image/ parameter of this action decides what will be sent as a replacement.
Parameterized.
"blank" to send a built-in transparent image. This makes banners disappear completely, @@ -4403,7 +3604,6 @@ TAG:^image/ "APPLICATION">Privoxy has blocked innocent images, like navigation icons.
"target-url" to send a @@ -4412,7 +3612,6 @@ TAG:^image/ filesystem via "file:///" URL. (But note that not all browsers support redirecting to a local file system).
-A good application of redirects is to use special Privoxy-built-in URLs, which send the built-in images, as
The URLs for the built-in images are "http://config.privoxy.org/send-banner?type=type is either "blank" or "pattern".
-There is a third (advanced) type, called "auto". It is NOT to be used in
Built-in pattern:
-
-
-+set-image-blocker{pattern}
-
+ +set-image-blocker{pattern}
|
Redirect to the BSD daemon:
-
-+set-image-blocker{http://www.freebsd.org/gifs/dae_up3.gif}
-
+ +set-image-blocker{http://www.freebsd.org/gifs/dae_up3.gif}
|
Redirect to the built-in pattern for better caching:
-
-+set-image-blocker{http://config.privoxy.org/send-banner?type=pattern}
-
+ +set-image-blocker{http://config.privoxy.org/send-banner?type=pattern}
|
Custom "actions", known to Privoxy as "aliases", can be defined by combining other actions. These can in turn be invoked @@ -4519,14 +3700,12 @@ TAG:^image/ are not required to start with a "+" or "-" sign, since they are merely textually expanded.
-Aliases can be used throughout the actions file, but they must be defined in a special section at the top of the file! And there can only be one such section per actions file. Each actions file may have its own alias section, and the aliases defined in it are only visible within that file.
-There are two main reasons to use aliases: One is to save typing for frequently used combinations of actions, the other one is a gain in flexibility: If you decide once how you want to handle shops by @@ -4536,21 +3715,17 @@ TAG:^image/ everywhere in the actions file where the "shop" alias is used. Calling aliases by their purpose also makes your actions files more readable.
-Currently, there is one big drawback to using aliases, though: Privoxy's built-in web-based action file editor honors aliases when reading the actions files, but it expands them before writing. So the effects of your aliases are of course preserved, but the aliases themselves are lost when you edit sections that use aliases with it.
-Now let's define some aliases...
-
- - # Useful custom aliases we can use later. +# Useful custom aliases we can use later. # # Note the (required!) section header line and that this section # must be at the top of the actions file! @@ -4584,22 +3759,19 @@ TAG:^image/ # Short names for other aliases, for really lazy people ;-) # c0 = +crunch-all-cookies - c1 = -crunch-all-cookies -+ c1 = -crunch-all-cookies |
...and put them to use. These sections would appear in the lower part of an actions file and define exceptions to the default actions (as specified further up for the "/" pattern):
-
- # These sites are either very complex or very keen on
+ # These sites are either very complex or very keen on
# user data and require minimal interference to work:
#
{fragile}
@@ -4620,22 +3792,18 @@ TAG:^image/
#
{-filter{all-popups} -filter{unsolicited-popups}}
.dabs.com
- .overclockers.co.uk
-
+ .overclockers.co.uk
|
Aliases like "shop" and "fragile" are typically used for "problem" sites that require more than one action to be disabled in order to function properly.
The above chapters have shown which actions files there are and how they are organized, how actions are specified and default.action and user.action file and see how all these pieces come together:
-Remember all actions are disabled when matching starts, so we have to explicitly enable the ones we want.
-While the match-all.action file only contains a single section, it is probably the most important one. It has only one pattern, "default.action and user.action, but it will still be largely responsible for your overall browsing experience.
-Again, at the start of matching, all actions are disabled, so there is no need to disable any actions here. (Remember: a "+" preceding the action name enables the action, a "-" disables!). Also note how this long line has been made more readable by splitting it into multiple lines with line continuation.
-
-
-{ \
+
|
The default behavior is now set.
If you aren't a developer, there's no need for you to edit the default.action file. It is maintained by the Privoxy developers and if you disagree with some of the sections, you should overrule them in your user.action.
-Understanding the default.action file can help you with your user.action, though.
-The first section in this file is a special section for internal use that prevents older Privoxy versions from reading the file:
-
-##########################################################################
+ ##########################################################################
# Settings -- Don't change! For internal Privoxy use ONLY.
##########################################################################
{{settings}}
-for-privoxy-version=3.0.11
-
+for-privoxy-version=3.0.11
|
After that comes the (optional) alias section. We'll use the example section from the above chapter on aliases, that also explains why and how aliases are used:
-
-##########################################################################
+ ##########################################################################
# Aliases
##########################################################################
{{alias}}
@@ -4762,25 +3914,22 @@ for-privoxy-version=3.0.11
"actions-file.html#FAST-REDIRECTS">fast-redirects -hide-referrer
shop = -crunch-all-cookies -filter{all-popups}
-
+"actions-file.html#FILTER-ALL-POPUPS">filter{all-popups}
|
The first of our specialized sections is concerned with "fragile" sites, i.e. sites that require minimum interference, because they are either very complex or very keen on tracking you (and have mechanisms in place that make them - unusable for people who avoid being tracked). We will simply use our + unusable for people who avoid being tracked). We will use our pre-defined fragile alias instead of stating the list of actions explicitly:
-
-##########################################################################
+ ##########################################################################
# Exceptions for sites that'll break under the default action set:
##########################################################################
@@ -4789,54 +3938,45 @@ for-privoxy-version=3.0.11
{ fragile }
.office.microsoft.com # surprise, surprise!
.windowsupdate.microsoft.com
-mail.google.com
-
+mail.google.com
|
Shopping sites are not as fragile, but they typically require cookies to log in, and pop-up windows for shopping carts or item details. Again, we'll use a pre-defined alias:
-
-
-# Shopping sites:
+
|
The fast-redirects action, which may have been enabled in match-all.action, breaks some sites. So disable it for popular sites where we know it misbehaves:
-
-
-{ -fast-redirects }
+
|
It is important that Privoxy knows which URLs belong to images, so that if they are to be blocked, @@ -4848,12 +3988,11 @@ edit.*.yahoo.com "actions-file.html#HANDLE-AS-IMAGE">handle-as-image action, and marking all URLs that end in a known image file extension is a good start:
-
-##########################################################################
+ ##########################################################################
# Images:
##########################################################################
@@ -4861,12 +4000,10 @@ edit.*.yahoo.com
# blocked further down this file:
#
{ +handle-as-image }
-/.*\.(gif|jpe?g|png|bmp|ico)$
-
+/.*\.(gif|jpe?g|png|bmp|ico)$
|
And then there are known banner sources. They often use scripts to generate the banners, so it won't be visible from the URL that the request is for an image. Hence we block them +set-image-blocker{pattern} action before, it still applies and needn't be repeated:
-
-
-# Known ad generators:
+
|
One of the most important jobs of Privoxy is to block banners. Many of these can be "blocked" by the block action to them.
-First comes many generic patterns, which do most of the work, by matching typical domain and path name components of banners. Then comes a list of individual patterns for specific sites, which is omitted here to keep the example short:
-
-##########################################################################
+ ##########################################################################
# Block these fine banners:
##########################################################################
{ +block{Banner ads.} }
@@ -4940,18 +4071,15 @@ count*.
# Site-specific patterns (abbreviated):
#
-.hitbox.com
-
+.hitbox.com
|
It's quite remarkable how many advertisers actually call their banner servers ads.company.com, - or call the directory in which the banners are stored simply + or call the directory in which the banners are stored literally "banners". So the above generic patterns are surprisingly effective.
-But being very generic, they necessarily also catch URLs that we don't want to block. The pattern .*ads. e.g. catches "nasty-adsl.some-provider.net." So here come some well-known exceptions to the +block section above.
-Note that these are exceptions to exceptions from the default! Consider the URL "downloads.sourcefroge.net": Initially, all actions @@ -4978,12 +4105,11 @@ count*. "EMPHASIS">again further down) it ends up with no block action applying.
-
-########################################################################## + ########################################################################## # Save some innocent victims of the above generic block patterns: ########################################################################## @@ -5004,45 +4130,37 @@ ad[ud]*. # (adult.* and add.*) # Site-specific: # www.globalintersec.com/adv # (adv = advanced) -www.ugu.com/sui/ugu/adv -+www.ugu.com/sui/ugu/adv |
Filtering source code can have nasty side effects, so make an exception for our friends at sourceforge.net, and all paths with "cvs" in them. Note that -filter disables all filters in one fell swoop!
-
-
-# Don't filter code!
+
|
The actual default.action is of course much more comprehensive, but we hope this example made clear how it works.
So far we are painting with a broad brush by setting general policies, which would be a reasonable starting point for many people. Now, you might want to be more specific and have customized rules @@ -5057,30 +4175,25 @@ wiki. actively maintained by the Privoxy developers and you'll probably want to install updated versions from time to time.
-So let's look at a few examples of things that one might typically do in user.action:
-
-# My user.action file. <fred@example.com> -+ # My user.action file. <fred@example.com> |
As aliases are local to the actions file that they are defined in, you can't use the ones from default.action, unless you repeat them here:
-
-# Aliases are local to the file they are defined in.
+ # Aliases are local to the file they are defined in.
# (Re-)define aliases for this file:
#
{{alias}}
@@ -5108,55 +4221,45 @@ allow-ads = -block -filter{banners-by-size} -filter{banners-by-link}
# Alias for specific file types that are text, but might have conflicting
# MIME types. We want the browser to force these to be text documents.
handle-as-text = -filter +-content-type-overwrite{text/plain} +-force-text-mode -hide-content-disposition
-
+"actions-file.html#CONTENT-TYPE-OVERWRITE">content-type-overwrite{text/plain} +-force-text-mode -hide-content-disposition
|
Say you have accounts on some sites that you visit regularly, and you don't want to have to log in manually each time. So you'd like to allow persistent cookies for these sites. The allow-all-cookies alias defined above does exactly that, i.e. it disables crunching of cookies in any direction, and the processing of cookies to make them only temporary.
-
-
-{ allow-all-cookies }
+
|
Your bank is allergic to some filter, but you don't know which, so you disable them all:
-
-
-{ -filter }
- .your-home-banking-site.com
-
+ { -filter }
+ .your-home-banking-site.com
|
Some file types you may not want to filter for various reasons:
-
-# Technical documentation is likely to contain strings that might + # Technical documentation is likely to contain strings that might # erroneously get altered by the JavaScript-oriented filters: # .tldp.org @@ -5165,12 +4268,10 @@ handle-as-text = -filter +- +stupid-server.example.com/ |
Example of a simple block action. Say you've seen an ad on your favourite page on example.com that you want to get rid of. You have right-clicked the image, @@ -5180,19 +4281,16 @@ stupid-server.example.com/ +handle-as-image } need not be specified, since all URLs ending in .gif will be tagged as images by the general rules as set in default.action anyway:
-
-
-{ +block{Nasty ads.} }
+
|
The URLs of dynamically generated banners, especially from large banner farms, often don't use the well-known image file name extensions, which makes it impossible for "broken image" icon by the browser. Use cautiously.
-
-
-{ +block-as-image }
+
|
Now you noticed that the default configuration breaks Forbes Magazine, but you were too lazy to find out which action is the culprit, and you were again too lazy to give Privoxy that is causing the problem or not. We later find other regular sites that misbehave, and add those to our personalized list of troublemakers:
-
-
-{ fragile }
+
|
You like the "fun" text replacements in default.filter, but it is disabled in the distributed actions file. So you'd like to turn it on in your private, update-safe config, once and for all:
-
-
-{ +filter{fun} }
- / # For ALL sites!
-
+ { +filter{fun} }
+ / # For ALL sites!
|
Note that the above is not really a good idea: There are exceptions to the filters in default.action for things that really shouldn't be filtered, like code on CVS->Web interfaces. Since user.action has the last word, these exceptions won't be valid for the "fun" filtering specified here.
-You might also worry about how your favourite free websites are funded, and find that they rely on displaying banner advertisements to survive. So you might want to specifically allow banners for those sites that you feel provide value to you:
-
-
-{ allow-ads }
+
|
Note that allow-ads has been aliased to -block, -filter{banners-by-link} above.
-Invoke another alias here to force an over-ride of the MIME type application/x-sh which typically would open a download type dialog. In my case, I want to look at the shell script, and then I can save it should I choose to.
-
-
-{ handle-as-text }
- /.*\.sh$
-
+ { handle-as-text }
+ /.*\.sh$
|
user.action is generally the best place to define exceptions and additions to the default policies of default.action. Some actions are safe to @@ -5316,44 +4393,34 @@ stupid-server.example.com/ to the checkerboard pattern for ALL sites. "/" of course matches all URL paths and patterns:
-
-
-{ +set-image-blocker{blank} }
-/ # ALL sites
-
+ { +set-image-blocker{blank} }
+/ # ALL sites
|