X-Git-Url: http://www.privoxy.org/gitweb/?a=blobdiff_plain;f=doc%2Fwebserver%2Fuser-manual%2Factions-file.html;h=db8dae24afd32b29e00265d8f294858d14cbc553;hb=57d8b0e0ca7e2d24bd29b3a4d3f5a648a38ae393;hp=5fc01d7de1a76e9e668efa69451f61b1ac5708a8;hpb=6be4997a13c22c081656b1d3960e2e2ee4fac60f;p=privoxy.git diff --git a/doc/webserver/user-manual/actions-file.html b/doc/webserver/user-manual/actions-file.html index 5fc01d7d..db8dae24 100644 --- a/doc/webserver/user-manual/actions-file.html +++ b/doc/webserver/user-manual/actions-file.html @@ -4,7 +4,7 @@
Privoxy 3.0.27 User Manual | +Privoxy 3.0.29 User Manual | ||||
---|---|---|---|---|---|
Prev | @@ -73,7 +73,7 @@
+ {+enable-https-filtering} +www.example.com+ |
+
Filter encrypted requests and responses without verifying the certificate
+Encrypted requests are forwarded to sites without verifying the certificate.
+Boolean.
+N/A
+When the "+enable-https-filtering" 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.
+
+ {+ignore-certificate-errors} + www.example.org ++ |
+
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