X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=doc%2Fwebserver%2Fuser-manual%2Factions-file.html;h=a5a7d7a4e8b3cf531e20f45b8f8328bbd3ab100f;hp=912f33c9d67576099b5eb36b8181dfd186b40252;hb=2d1af75a04189057eb4cf4949908a3cdf9ca2b6e;hpb=cd8bce8ef339df6f04982b37aaa008a8eea0f0ac;ds=sidebyside diff --git a/doc/webserver/user-manual/actions-file.html b/doc/webserver/user-manual/actions-file.html index 912f33c9..a5a7d7a4 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

@@ -394,6 +394,9 @@

While flexible, this is not the sophistication of full regular expression based syntax.

+

When compiled with FEATURE_PCRE_HOST_PATTERNS patterns can be prefixed with "PCRE-HOST-PATTERN:" in which case full regular expression (PCRE) can be used for the host + pattern as well.

8.4.2. The Path Pattern

@@ -2523,11 +2526,13 @@ nasty-banner-server.example.com/junk.cgi\?output=trash

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.

+

Before this works the directives in the HTTPS inspection 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.

+

This is an experimental feature.

Example usage (section):
@@ -2569,8 +2574,11 @@ www.example.com

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.

+

If the certificate can't be validated by Privoxy the connection is + aborted.

+

This action disables the certificate check so requests to sites with certificates that can't be + validated are allowed.

+

Note that enabling this action allows Man-in-the-middle attacks.

Example usage: