From 5473a49999459de303a5d534a7654eaa48587e5f Mon Sep 17 00:00:00 2001 From: Fabian Keil Date: Sat, 6 Jun 2020 09:42:56 +0200 Subject: [PATCH 1/1] FAQ: Mention http-inspection in two answers Sponsored by: Robert Klemme --- doc/source/faq.sgml | 17 +++++++++++++---- 1 file changed, 13 insertions(+), 4 deletions(-) diff --git a/doc/source/faq.sgml b/doc/source/faq.sgml index 773d9fe0..e281a629 100644 --- a/doc/source/faq.sgml +++ b/doc/source/faq.sgml @@ -1341,7 +1341,8 @@ and thus avoid individual browser configuration? amount of guesswork. It is not realistic to catch all of these short of disabling Javascript, which would break many sites. And lastly, if the cookies are embedded in a HTTPS/SSL secure session via Javascript, they are beyond - Privoxy's reach. + Privoxy's reach unless you enable + https-inspection. All in all, &my-app; can help manage cookies in general, can help minimize @@ -1996,9 +1997,17 @@ ads used to be. Why? How can Privoxy filter Secure (HTTPS) URLs? - Since secure HTTP connections are encrypted SSL sessions between your browser - and the secure site, and are meant to be reliably secure, - there is little that Privoxy can do but hand the raw + If you enable + https-inspection + Privoxy will impersonate the destination + server and can thus filter encrypted requests and responses as well. + + + Without + https-inspection + secure HTTP connections are encrypted SSL sessions between your + browser and the secure site, and there is little + that Privoxy can do but hand the raw gibberish data though from one end to the other unprocessed. -- 2.39.2