X-Git-Url: http://www.privoxy.org/gitweb/?a=blobdiff_plain;f=doc%2Fwebserver%2Fuser-manual%2Factions-file.html;h=912f33c9d67576099b5eb36b8181dfd186b40252;hb=55fc826b8acc4cc6f300c7ec1fa93952eb253824;hp=590d0e9523f5146e5f476f0303b5aa00441b09cf;hpb=6231ae15da15f2db745a7dd1bccc672b2394f7cb;p=privoxy.git diff --git a/doc/webserver/user-manual/actions-file.html b/doc/webserver/user-manual/actions-file.html index 590d0e95..912f33c9 100644 --- a/doc/webserver/user-manual/actions-file.html +++ b/doc/webserver/user-manual/actions-file.html @@ -4,7 +4,7 @@ Actions Files - + @@ -15,7 +15,7 @@
- + @@ -73,7 +73,7 @@

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

- +

Table 1. Default Configurations

Privoxy 3.0.27 User ManualPrivoxy 3.0.29 User Manual
Prev
@@ -1524,7 +1524,7 @@ problem-host.example.com

To detect a redirection URL, fast-redirects only looks for the string "http://", either in plain text (invalid but often used) or encoded as "http%3a//". Some sites use their own URL encoding scheme, encrypt the address - of the target server or replace it with a database id. In theses cases fast-redirects is fooled and the request reaches the redirection server where it probably gets logged.

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

8.5.28. limit-connect

+

8.5.28. https-inspection

+
+
+
Typical use:
+
+

Filter encrypted requests and responses

+
+
Effect:
+
+

Encrypted requests are decrypted, filtered and forwarded encrypted.

+
+
Type:
+
+

Boolean.

+
+
Parameter:
+
+

N/A

+
+
Notes:
+
+

This action allows Privoxy to filter encrypted requests and + responses. For this to work Privoxy has to generate a certificate and + send it to the client which has to accept it.

+

Before this works the directives in the TLS section of the config file have to be configured.

+

Note that the action has to be enabled based on the CONNECT request which doesn't contain a path. + Enabling it based on a pattern with path doesn't work as the path is only seen by Privoxy if the action is already enabled.

+
+
Example usage (section):
+
+
+ + + +
+ 
{+https-inspection}
+www.example.com
+
+ + +
+ +
+

8.5.29. + ignore-certificate-errors

+
+
+
Typical use:
+
+

Filter encrypted requests and responses without verifying the certificate

+
+
Effect:
+
+

Encrypted requests are forwarded to sites without verifying the certificate.

+
+
Type:
+
+

Boolean.

+
+
Parameter:
+
+

N/A

+
+
Notes:
+
+

When the "+https-inspection" action is used Privoxy by default + verifies that the remote site uses a valid certificate.

+

If the certificate is invalid the connection is aborted.

+

This action disabled the certificate check allowing requests to sites with invalid certificates.

+
+
Example usage:
+
+ + + + +
+ 
    {+ignore-certificate-errors}
+    www.example.org
+
+
+
+
+
+
+
+

8.5.30. limit-connect

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

8.5.29. +

8.5.31. limit-cookie-lifetime

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

-

8.5.30. prevent-compression

+

8.5.32. prevent-compression

Typical use:
@@ -2641,8 +2730,9 @@ nasty-banner-server.example.com/junk.cgi\?output=trash 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 versions only send the beginning of - the content. If you enable prevent-compression per default, you might want to - add exceptions for those sites. See the example for how to do that.

+ the content and some content delivery networks let the connection time out. If you enable prevent-compression per default, you might want to add exceptions for those sites. See the + example for how to do that.

Example usage (sections):
@@ -2674,7 +2764,7 @@ nasty-banner-server.example.com/junk.cgi\?output=trash
-

8.5.31. +

8.5.33. overwrite-last-modified

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

-

8.5.32. redirect

+

8.5.34. redirect

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

8.5.33. +

8.5.35. server-header-filter

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

-

8.5.34. +

8.5.36. server-header-tagger

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

-

8.5.35. +

8.5.37. session-cookies-only

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

-

8.5.36. set-image-blocker

+

8.5.38. set-image-blocker

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

8.5.37. Summary

+

8.5.39. 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