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=68c0b5e8b37ee7daea66b3687ae27baea8f524ff;hb=2d1af75a04189057eb4cf4949908a3cdf9ca2b6e;hpb=979620bb4c7aaaeb96f07b73b823c686d83cf14c
diff --git a/doc/webserver/user-manual/actions-file.html b/doc/webserver/user-manual/actions-file.html
index 68c0b5e8..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
@@ -2526,8 +2526,9 @@ 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.