X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=doc%2Fsource%2Fuser-manual.sgml;h=d9ee3ea0eccbd1238759b5a1ad91f95e9cda6095;hp=a7e88842876036c123a99f4636719da4265da8db;hb=8875cc0bd68dd60dfc150adf6d147eec216789ec;hpb=805251d14df3900b8e818b7ec963b50c08035456;ds=sidebyside
diff --git a/doc/source/user-manual.sgml b/doc/source/user-manual.sgml
index a7e88842..d9ee3ea0 100644
--- a/doc/source/user-manual.sgml
+++ b/doc/source/user-manual.sgml
@@ -34,7 +34,7 @@
Purpose : user manual
- Copyright (C) 2001-2019 Privoxy Developers https://www.privoxy.org/
+ Copyright (C) 2001-2020 Privoxy Developers https://www.privoxy.org/
See LICENSE.
========================================================================
@@ -53,7 +53,7 @@
- Copyright &my-copy; 2001-2019 by
+ Copyright &my-copy; 2001-2020 by
Privoxy Developers
@@ -3802,71 +3802,6 @@ problem-host.example.com
-
-
-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 &my-app; to filter encrypted requests and responses.
- For this to work &my-app; 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
-
-
-
-
-
-
external-filter
@@ -4052,7 +3987,7 @@ www.example.com
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
+ of the target server or replace it with a database id. In these cases
fast-redirects is fooled and the request reaches the
redirection server where it probably gets logged.
@@ -5212,6 +5147,78 @@ new action
+
+
+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 &my-app; to filter encrypted requests and responses.
+ For this to work &my-app; 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 &my-app; if the action is already enabled.
+
+
+
+
+
+ Example usage (section):
+
+ {+https-inspection}
+www.example.com
+
+
+
+
+
+
+
ignore-certificate-errors
@@ -5255,7 +5262,7 @@ new action
When the
- +enable-https-filtering
+ +https-inspection
action is used &my-app; by default verifies that the remote site uses a valid
certificate.
@@ -5516,9 +5523,10 @@ new action
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.
+ some IIS versions only send the beginning of 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.
@@ -7466,7 +7474,7 @@ pre-defined filters for your convenience:
sometimes appear on some pages, or user agents that don't correct for this on
the fly.