X-Git-Url: http://www.privoxy.org/gitweb/?a=blobdiff_plain;f=doc%2Fwebserver%2Fuser-manual%2Factions-file.html;h=f5a98de2db7cf46c68cb935f1385b2153e27a6dc;hb=0f3edd93a652011049e2bfc9b67947f92e236ef8;hp=f641896c3bc85ea80fe046e944b32f9bb7898dcf;hpb=098f3f996e9465705bc3e02b9454b99568c8e372;p=privoxy.git diff --git a/doc/webserver/user-manual/actions-file.html b/doc/webserver/user-manual/actions-file.html index f641896c..f5a98de2 100644 --- a/doc/webserver/user-manual/actions-file.html +++ b/doc/webserver/user-manual/actions-file.html @@ -1403,50 +1403,7 @@ problem-host.example.com
-

8.5.15. - enable-https-filtering

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

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

8.5.16. external-filter

+

8.5.15. external-filter

Typical use:
@@ -1508,7 +1465,7 @@ www.example.com
-

8.5.17. fast-redirects

+

8.5.16. fast-redirects

Typical use:
@@ -1589,7 +1546,7 @@ www.example.com
-

8.5.18. filter

+

8.5.17. filter

Typical use:
@@ -1904,7 +1861,7 @@ www.example.com
-

8.5.19. force-text-mode

+

8.5.18. force-text-mode

Typical use:
@@ -1961,7 +1918,7 @@ www.example.com
-

8.5.20. forward-override

+

8.5.19. forward-override

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

8.5.21. +

8.5.20. handle-as-empty-document

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

-

8.5.22. handle-as-image

+

8.5.21. handle-as-image

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

8.5.23. +

8.5.22. hide-accept-language

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

-

8.5.24. +

8.5.23. hide-content-disposition

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

-

8.5.25. +

8.5.24. hide-if-modified-since

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

-

8.5.26. hide-from-header

+

8.5.25. hide-from-header

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

8.5.27. hide-referrer

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

8.5.28. hide-user-agent

+

8.5.27. hide-user-agent

Typical use:
@@ -2541,6 +2498,51 @@ nasty-banner-server.example.com/junk.cgi\?output=trash
+
+

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

@@ -2564,9 +2566,9 @@ nasty-banner-server.example.com/junk.cgi\?output=trash
Notes:
-

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

+

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.