X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=doc%2Fwebserver%2Fuser-manual%2Factions-file.html;h=d1c0e092a102e8ae4658154c5b4df715b4100f8d;hp=e58a0febcfbbed0cbf22e7d6c47b1accb579bb45;hb=75397537c3986cafa8dc1b4b37af40f93ab9372f;hpb=086d4aacf2fe1d729b4f4a67a7167cb6f19db043 diff --git a/doc/webserver/user-manual/actions-file.html b/doc/webserver/user-manual/actions-file.html index e58a0feb..d1c0e092 100644 --- a/doc/webserver/user-manual/actions-file.html +++ b/doc/webserver/user-manual/actions-file.html @@ -73,7 +73,7 @@

The default profiles, and their associated actions, as pre-defined in default.action are:

- +

Table 1. Default Configurations

@@ -1313,7 +1313,50 @@ www.example.net/.*style
-

8.5.13. +

8.5.13. delay-response

+
+
+
Typical use:
+
+

Delay responses to the client to reduce the load

+
+
Effect:
+
+

Delays responses to the client by sending the response in ca. 10 byte chunks.

+
+
Type:
+
+

Parameterized.

+
+
Parameter:
+
+

"Number of milliseconds"

+
+
Notes:
+
+

Sometimes when JavaScript code is used to fetch advertisements it doesn't respect Privoxy's blocks and + retries to fetch the same resource again causing unnecessary load on the client.

+

This action delays responses to the client and can be combined with blocks to slow down the JavaScript code, thus reducing the load on the + client.

+

When used without blocks the action can + also be used to simulate a slow internet connection.

+
+
Example usage:
+
+

+ + + +
+
+delay-response{100}
+
+ + +
+ +
+

8.5.14. downgrade-http-version

@@ -1360,7 +1403,7 @@ problem-host.example.com
-

8.5.14. external-filter

+

8.5.15. external-filter

Typical use:
@@ -1422,7 +1465,7 @@ problem-host.example.com
-

8.5.15. fast-redirects

+

8.5.16. fast-redirects

Typical use:
@@ -1503,7 +1546,7 @@ problem-host.example.com
-

8.5.16. filter

+

8.5.17. filter

Typical use:
@@ -1579,8 +1622,8 @@ problem-host.example.com
-
+filter{js-annoyances}       # Get rid of particularly annoying JavaScript abuse.
+
+                    +filter{js-annoyances}       # Get rid of particularly annoying JavaScript abuse.
@@ -1588,8 +1631,8 @@ problem-host.example.com
-
+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).
@@ -1597,8 +1640,8 @@ problem-host.example.com
-
+filter{html-annoyances}     # Get rid of particularly annoying HTML abuse.
+
+                    +filter{html-annoyances}     # Get rid of particularly annoying HTML abuse.
@@ -1606,8 +1649,8 @@ problem-host.example.com
-
+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.
@@ -1615,8 +1658,8 @@ problem-host.example.com
-
+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.
@@ -1640,8 +1683,8 @@ problem-host.example.com
-
+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.
@@ -1657,8 +1700,8 @@ problem-host.example.com
-
+filter{banners-by-link}     # Kill banners by their links to known clicktrackers.
+
+                    +filter{banners-by-link}     # Kill banners by their links to known clicktrackers.
@@ -1666,8 +1709,8 @@ problem-host.example.com
-
+filter{webbugs}             # Squish WebBugs (1x1 invisible GIFs used for user tracking).
+
+                    +filter{webbugs}             # Squish WebBugs (1x1 invisible GIFs used for user tracking).
@@ -1675,8 +1718,8 @@ problem-host.example.com
-
+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.
@@ -1684,8 +1727,8 @@ problem-host.example.com
-
+filter{jumping-windows}     # Prevent windows from resizing and moving themselves.
+
+                    +filter{jumping-windows}     # Prevent windows from resizing and moving themselves.
@@ -1693,8 +1736,8 @@ problem-host.example.com
-
+filter{frameset-borders}    # Give frames a border and make them resizable.
+
+                    +filter{frameset-borders}    # Give frames a border and make them resizable.
@@ -1702,8 +1745,8 @@ problem-host.example.com
-
+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.
@@ -1711,8 +1754,8 @@ problem-host.example.com
-
+filter{demoronizer}         # Fix MS's non-standard use of standard charsets.
+
+                    +filter{demoronizer}         # Fix MS's non-standard use of standard charsets.
@@ -1736,8 +1779,8 @@ problem-host.example.com
-
+filter{fun}                 # Text replacements for subversive browsing fun!
+
+                    +filter{fun}                 # Text replacements for subversive browsing fun!
@@ -1745,8 +1788,8 @@ problem-host.example.com
-
+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.
@@ -1754,8 +1797,8 @@ problem-host.example.com
-
+filter{ie-exploits}         # Disable some known Internet Explorer bug exploits.
+
+                    +filter{ie-exploits}         # Disable some known Internet Explorer bug exploits.
@@ -1763,8 +1806,8 @@ problem-host.example.com
-
+filter{site-specifics}      # Cure for site-specific problems. Don't apply generally!
+
+                    +filter{site-specifics}      # Cure for site-specific problems. Don't apply generally!
@@ -1772,8 +1815,8 @@ problem-host.example.com
-
+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.
@@ -1781,8 +1824,8 @@ problem-host.example.com
-
+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.
@@ -1790,8 +1833,8 @@ problem-host.example.com
-
+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.
@@ -1799,8 +1842,8 @@ problem-host.example.com
-
+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.
@@ -1808,8 +1851,8 @@ problem-host.example.com
-
+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.
@@ -1818,7 +1861,7 @@ problem-host.example.com
-

8.5.17. force-text-mode

+

8.5.18. force-text-mode

Typical use:
@@ -1875,7 +1918,7 @@ problem-host.example.com
-

8.5.18. forward-override

+

8.5.19. forward-override

Typical use:
@@ -1982,7 +2025,7 @@ TAG:^User-Agent: fetch libfetch/2\.0$
-

8.5.19. +

8.5.20. handle-as-empty-document

@@ -2035,7 +2078,7 @@ example.org/.*\.js$

-

8.5.20. handle-as-image

+

8.5.21. handle-as-image

Typical use:
@@ -2095,7 +2138,7 @@ nasty-banner-server.example.com/junk.cgi\?output=trash
-

8.5.21. +

8.5.22. hide-accept-language

@@ -2148,7 +2191,7 @@ nasty-banner-server.example.com/junk.cgi\?output=trash

-

8.5.22. +

8.5.23. hide-content-disposition

@@ -2204,7 +2247,7 @@ nasty-banner-server.example.com/junk.cgi\?output=trash

-

8.5.23. +

8.5.24. hide-if-modified-since

@@ -2263,7 +2306,7 @@ nasty-banner-server.example.com/junk.cgi\?output=trash

-

8.5.24. hide-from-header

+

8.5.25. hide-from-header

Typical use:
@@ -2314,7 +2357,7 @@ nasty-banner-server.example.com/junk.cgi\?output=trash
-

8.5.25. hide-referrer

8.5.26. hide-referrer
@@ -2395,7 +2438,7 @@ nasty-banner-server.example.com/junk.cgi\?output=trash
-

8.5.26. hide-user-agent

+

8.5.27. hide-user-agent

Typical use:
@@ -2456,7 +2499,7 @@ nasty-banner-server.example.com/junk.cgi\?output=trash
-

8.5.27. limit-connect

+

8.5.28. limit-connect

Typical use:
@@ -2508,7 +2551,7 @@ nasty-banner-server.example.com/junk.cgi\?output=trash
-

8.5.28. +

8.5.29. limit-cookie-lifetime

@@ -2560,7 +2603,7 @@ nasty-banner-server.example.com/junk.cgi\?output=trash

-

8.5.29. prevent-compression

+

8.5.30. prevent-compression

Typical use:
@@ -2631,7 +2674,7 @@ nasty-banner-server.example.com/junk.cgi\?output=trash
-

8.5.30. +

8.5.31. overwrite-last-modified

@@ -2693,7 +2736,7 @@ nasty-banner-server.example.com/junk.cgi\?output=trash

-

8.5.31. redirect

+

8.5.32. redirect

Typical use:
@@ -2785,7 +2828,7 @@ www.privoxy.org/user-manual/
-

8.5.32. +

8.5.33. server-header-filter

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

-

8.5.33. +

8.5.34. server-header-tagger

@@ -2892,7 +2935,7 @@ TAG:^image/

-

8.5.34. +

8.5.35. session-cookies-only

@@ -2954,7 +2997,7 @@ TAG:^image/

-

8.5.35. set-image-blocker

+

8.5.36. set-image-blocker

Typical use:
@@ -3043,7 +3086,7 @@ TAG:^image/
-

8.5.36. Summary

+

8.5.37. Summary

Note that many of these actions have the potential to cause a page to misbehave, possibly even not to display at all. There are many ways a site designer may choose to design his site, and what HTTP header content, and other criteria, he may depend on. There is no way to have hard and fast rules for all sites. See