@@ -438,33 +422,33 @@ body {
As mentioned, Privoxy uses
"patterns" to determine what actions might apply to which sites and
- pages your browser attempts to access. These actions might apply to which
+ sites and pages your browser attempts to access. These "patterns" use wild card type pattern matching to achieve a high degree
- of flexibility. This allows one expression to be expanded and
- potentially match against many similar patterns.
+ "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 <domain><port>/<path>, where the
- <domain>, the <host><port>/<path>, where the
+ <host>, the <port> and the <path> are optional. (This is why the special
/ pattern matches all URLs). Note that the
protocol portion of the URL pattern (e.g. http://) should not be included in the pattern. This is
- assumed already!
+ "LITERAL">http://) should not be included in the pattern. This is assumed
+ already!
- The pattern matching syntax is different for the domain and path
- parts of the URL. The domain part uses a simple globbing type matching
+ 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 domain part contains a
+ colon (:). If the host part contains a
numerical IPv6 address, it has to be put into angle brackets
(<, >).
@@ -473,7 +457,7 @@ body {
www.example.com/
- is a domain-only pattern and will match any request to
+ is a host-only pattern and will match any request to
www.example.com, regardless of which
document on that server is requested. So ALL pages in this domain
would be covered by the scope of this action. Note that a simple
@@ -484,7 +468,7 @@ body {
www.example.com
- means exactly the same. For domain-only patterns, the trailing
+ means exactly the same. For host-only patterns, the trailing
/ may be omitted.
@@ -509,7 +493,8 @@ body {
matches the document /index.html,
regardless of the domain, i.e. on any web server anywhere.
+ "emphasis">any web server
+ anywhere.
/
@@ -525,6 +510,14 @@ body {
Matches any URL pointing to TCP port 8000.
+ 10.0.0.1/
+
+
+ Matches any URL with the host address 10.0.0.1. (Note that the real URL uses plain
+ brackets, not angle brackets.)
+
+
<2001:db8::1>/
@@ -544,12 +537,14 @@ body {
-
+
- The matching of the domain part offers some flexible options: if
- the domain starts or ends with a dot, it becomes unanchored at that
- end. For example:
+ 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:
@@ -569,18 +564,17 @@ body {
- www.
-
-
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 STARTS with www.
+ (It also matches the domain www but
+ most of the time that doesn't matter.)
- .example.
-
-
matches any domain that CONTAINS matches any domain that CONTAINS .example.. And, by the way, also included would
be any files or documents that exist within that domain since
no path limitations are specified. (Correctly speaking: It
@@ -639,7 +633,7 @@ body {
www4.example.cc, wwwd.example.cy, wwwz.example.com etc., but not not wwww.example.com.
@@ -650,7 +644,7 @@ body {
@@ -831,14 +843,14 @@ body {
"QUOTE">"enabled" or "disabled".
Syntax:
-
+
- +name # enable action name
- -name # disable action name
+ +name # enable action name
+ -name # disable action name
|
@@ -851,16 +863,15 @@ body {
Parameterized, where some value is required in order to enable
this type of action. Syntax:
-
+
- +name{param} # enable action and set parameter to param,
+ +name{param} # enable action and set parameter to param,
# overwriting parameter from previous match if necessary
-name # disable action. The parameter can be omitted
+"REPLACEABLE">name # disable action. The parameter can be omitted
|
@@ -879,25 +890,25 @@ body {
Multi-value. These look exactly like parameterized actions, but
they behave differently: If the action applies multiple times to
the same URL, but with different parameters, all the parameters from all matches 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:
+ "emphasis">all the parameters from
+ all matches
+ 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
- -name{param} # remove the parameter param from the list of parameters
+ +name{param} # enable action and add param to the list of parameters
+ -name{param} # remove the parameter param from the list of parameters
# If it was the last one left, disable the action.
-name # disable this action completely and remove all parameters from the list
+"REPLACEABLE">-name # disable this action completely and remove all parameters from the list
|
@@ -981,7 +992,7 @@ body {
Example usage:
-
+
@@ -1045,7 +1056,7 @@ body {
force feature is available and enabled).
A very important exception occurs if both both block and handle-as-image,
apply to the same request: it will then be replaced by an
@@ -1072,7 +1083,7 @@ body {
Example usage (section):
-
+
@@ -1153,7 +1164,7 @@ body {
Example usage:
-
+
@@ -1190,7 +1201,7 @@ body {
Type:
- Parameterized.
+ Multi-value.
Parameter:
@@ -1212,7 +1223,7 @@ body {
Client-header filters are executed after the other header
actions have finished and use their output as input.
- If the request URL gets changed, 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
@@ -1226,7 +1237,7 @@ body {
Example usage (section):
-
+
@@ -1266,7 +1277,7 @@ body {
Type:
- Parameterized.
+ Multi-value.
Parameter:
@@ -1291,7 +1302,7 @@ body {
Example usage (section):
-
+
@@ -1318,6 +1329,28 @@ TAG:^User-Agent: fetch libfetch/
TAG:^User-Agent: Ubuntu APT-HTTP/
TAG:^User-Agent: MPlayer/
+
+ |
+
+
+
+
+
+
+
+# Tag all requests with the Range header set
+{+client-header-tagger{range-requests}}
+/
+
+# Disable filtering for the tagged requests.
+#
+# With filtering enabled Privoxy would remove the Range headers
+# to be able to filter the whole response. The downside is that
+# it prevents clients from resuming downloads or skipping over
+# parts of multimedia files.
+{-filter -deanimate-gifs}
+TAG:^RANGE-REQUEST$
+
|
@@ -1415,7 +1448,7 @@ TAG:^User-Agent: MPlayer/
Example usage (sections):
-
+
@@ -1477,10 +1510,10 @@ www.example.net/.*style
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.
+ 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
@@ -1492,7 +1525,7 @@ www.example.net/.*style
- Warning |
+ Warning |
@@ -1508,7 +1541,7 @@ www.example.net/.*style
Example usage (section):
-
+
@@ -1584,7 +1617,7 @@ www.example.net/.*style
Example usage (section):
-
+
@@ -1639,15 +1672,16 @@ www.example.net/.*style
This action is only concerned with incoming HTTP cookies. For
- outgoing HTTP
- cookies, use incoming HTTP
+ cookies. For outgoing HTTP cookies, use crunch-outgoing-cookies.
- Use both to disable
- HTTP cookies completely.
+ Use both
+ to disable HTTP cookies completely.
- It makes no sense at
- all to use this action in conjunction with the
+ It makes no sense
+ at all to use this action in conjunction with the
session-cookies-only
action, since it would prevent the session cookies from being
@@ -1658,7 +1692,7 @@ www.example.net/.*style
Example usage:
-
+
@@ -1713,10 +1747,10 @@ www.example.net/.*style
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.
+ 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
@@ -1728,7 +1762,7 @@ www.example.net/.*style
- Warning |
+ Warning |
@@ -1744,7 +1778,7 @@ www.example.net/.*style
Example usage (section):
- | | | | | | | | |