X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=doc%2Fwebserver%2Fuser-manual%2Factions-file.html;h=faa5e629f65191b874dfd2562425b2e6a7f58df4;hp=ce06322d8bf277142005344c36d5be20eea44057;hb=bbfe461fae901a7daf3bae1e3087c02f98a24deb;hpb=abd789ae2b66c396bf6899a82268c6849ab5ed22 diff --git a/doc/webserver/user-manual/actions-file.html b/doc/webserver/user-manual/actions-file.html index ce06322d..faa5e629 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

@@ -2280,7 +2280,7 @@ problem-host.example.com @@ -2293,7 +2293,7 @@ problem-host.example.com @@ -2305,7 +2305,7 @@ problem-host.example.com @@ -2401,6 +2401,18 @@ problem-host.example.com
Privoxy 3.0.20 User ManualPrivoxy 3.0.21 User Manual 
-+filter{js-events}           # Kill all JS 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{refresh-tags}        # Kill automatic refresh tags (for dial-on-demand setups).
++filter{refresh-tags}        # Kill automatic refresh tags if refresh time is larger than 9 seconds.
 
-+filter{unsolicited-popups}  # Disable only unsolicited pop-up windows. Useful if your browser lacks this ability.
++filter{unsolicited-popups}  # Disable only unsolicited pop-up windows.
 
-+filter{all-popups}          # Kill all popups in JavaScript and HTML. Useful if your browser lacks this ability.
++filter{all-popups}          # Kill all popups in JavaScript and HTML.
+

+ + + + + +
+ 
++filter{iframes}             # Removes all detected iframes. Should only be enabled for individual sites.
+
+
+

@@ -3545,6 +3557,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 + + + + + + + + + +
+

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:
+ +
+ + + @@ -3556,7 +3650,7 @@ nasty-banner-server.example.com/junk.cgi\?output=trash

8.5.27. prevent-compression

+ "PREVENT-COMPRESSION">8.5.28. prevent-compression
@@ -3660,7 +3754,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
@@ -3756,7 +3850,7 @@ nasty-banner-server.example.com/junk.cgi\?output=trash
-

8.5.29. +

8.5.30. redirect

@@ -3860,7 +3954,7 @@ www.privoxy.org/user-manual/

8.5.30. server-header-filter

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

@@ -3932,7 +4026,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
@@ -4005,7 +4099,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
@@ -4103,7 +4197,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
@@ -4242,7 +4336,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 @@ -4401,7 +4495,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 @@ -4450,7 +4544,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 @@ -4793,7 +4887,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}
+