X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=doc%2Fwebserver%2Fuser-manual%2Factions-file.html;h=d62ddefe0c6df60ac03e5d75139c8fcf120d2b23;hp=9e8e95e6335dd936484d972bcbd36474ee564679;hb=60cbbc5f5d7514135bc5afc02d24e77a231c47f4;hpb=69b45dc21f48175fb34a8e1e2f45d46870e37941 diff --git a/doc/webserver/user-manual/actions-file.html b/doc/webserver/user-manual/actions-file.html index 9e8e95e6..d62ddefe 100644 --- a/doc/webserver/user-manual/actions-file.html +++ b/doc/webserver/user-manual/actions-file.html @@ -6,7 +6,7 @@ Actions Files - + @@ -21,7 +21,7 @@ - + @@ -117,7 +117,7 @@ in default.action are:

- +

Table 1. Default Configurations

@@ -314,7 +314,7 @@ actions.

-

8.1. Finding the Right +

8.1. Finding the Right Mix

Note that some actions, like @@ -339,7 +339,7 @@

-

8.2. How to +

8.2. How to Edit

The easiest way to edit the actions files is with a browser by using @@ -529,7 +529,7 @@

-

8.4.1. The Domain +

8.4.1. The Domain Pattern

The matching of the domain part offers some flexible options: if @@ -634,7 +634,7 @@

-

8.4.2. The Path +

8.4.2. The Path Pattern

Privoxy uses 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 @@ -1301,6 +1301,28 @@ TAG:^User-Agent: fetch libfetch/ TAG:^User-Agent: Ubuntu APT-HTTP/ TAG:^User-Agent: MPlayer/ + + +

+
Privoxy 3.0.19 User ManualPrivoxy 3.0.21 User Manual
+ + + + @@ -3523,6 +3545,88 @@ nasty-banner-server.example.com/junk.cgi\?output=trash +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 + + + +
+ 
+# 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$
+
+ + + + + +
+

8.5.27. limit-cookie-lifetime

+ +
+
+
Typical use:
+ +
+

Limit the lifetime of HTTP cookies to a couple of minutes or + hours.

+
+ +
Effect:
+ +
+

Overwrites the expires field in Set-Cookie server headers if + it's above the specified limit.

+
+ +
Type:
+ +
+

Parameterized.

+
+ +
Parameter:
+ +
+

The lifetime limit in minutes, or 0.

+
+ +
Notes:
+ +
+

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.

+
+ +
Example usages:
+ +
+ + + @@ -3534,7 +3638,7 @@ nasty-banner-server.example.com/junk.cgi\?output=trash

8.5.27. prevent-compression

+ "PREVENT-COMPRESSION">8.5.28. prevent-compression
@@ -3638,7 +3742,7 @@ nasty-banner-server.example.com/junk.cgi\?output=trash

8.5.28. overwrite-last-modified

+ "OVERWRITE-LAST-MODIFIED">8.5.29. overwrite-last-modified
@@ -3734,7 +3838,7 @@ nasty-banner-server.example.com/junk.cgi\?output=trash
-

8.5.29. +

8.5.30. redirect

@@ -3773,6 +3877,9 @@ nasty-banner-server.example.com/junk.cgi\?output=trash 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.

+

This action will be ignored if you use it together with block. It can be combined @@ -3835,7 +3942,7 @@ www.privoxy.org/user-manual/

8.5.30. server-header-filter

+ "SERVER-HEADER-FILTER">8.5.31. server-header-filter

@@ -3907,7 +4014,7 @@ example.org/instance-that-is-delivered-as-xml-but-is-not

8.5.31. server-header-tagger

+ "SERVER-HEADER-TAGGER">8.5.32. server-header-tagger
@@ -3980,7 +4087,7 @@ example.org/instance-that-is-delivered-as-xml-but-is-not

8.5.32. session-cookies-only

+ "SESSION-COOKIES-ONLY">8.5.33. session-cookies-only
@@ -4078,7 +4185,7 @@ example.org/instance-that-is-delivered-as-xml-but-is-not

8.5.33. set-image-blocker

+ "SET-IMAGE-BLOCKER">8.5.34. set-image-blocker
@@ -4217,7 +4324,7 @@ example.org/instance-that-is-delivered-as-xml-but-is-not
-

8.5.34. +

8.5.35. Summary

Note that many of these actions have the potential to cause a page @@ -4376,7 +4483,7 @@ example.org/instance-that-is-delivered-as-xml-but-is-not together:

-

8.7.1. +

8.7.1. match-all.action

Remember all actions @@ -4425,7 +4532,7 @@ example.org/instance-that-is-delivered-as-xml-but-is-not

-

8.7.2. +

8.7.2. default.action

If you aren't a developer, there's no need for you to edit the @@ -4768,7 +4875,7 @@ wiki.

-

8.7.3. +

8.7.3. user.action

So far we are painting with a broad brush by setting general

+ 
++limit-cookie-lifetime{60}
+