X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=doc%2Fwebserver%2Ffaq%2Fconfiguration.html;h=9c30195b30da8af058d98166bbfadf79c22751fd;hp=76ce4684331687f47f665b4a42f1cb286fc6bff9;hb=1cca73f62243403dcede83e522496f1b78460b8d;hpb=dfa813a2b81538ae08985b21e6026d1183b23acc

diff --git a/doc/webserver/faq/configuration.html b/doc/webserver/faq/configuration.html
index 76ce4684..9c30195b 100644
--- a/doc/webserver/faq/configuration.html
+++ b/doc/webserver/faq/configuration.html
@@ -368,7 +368,8 @@
       trickier because the syntax can vary widely, and thus requires a certain 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 <span class="APPLICATION">Privoxy's</span>
-      reach.</p>
+      reach unless you enable <a href="../user-manual/actions-file.html#HTTPS-INSPECTION" target=
+      "_top">https-inspection</a>.</p>
       <p>All in all, <span class="APPLICATION">Privoxy</span> can help manage cookies in general, can help minimize the
       loss of privacy posed by cookies, but can't realistically stop all cookies.</p>
     </div>