X-Git-Url: http://www.privoxy.org/gitweb/?p=privoxy.git;a=blobdiff_plain;f=doc%2Fwebserver%2Ffaq%2Fconfiguration.html;h=f9c4c4dba51f58e580ed11541e84ead0c0dd30f9;hp=7802ae2e207c017b5d91093672126421043c5da3;hb=4fd7d8795b9f049065db3d4f236b27560d273738;hpb=d5bba1fd0bce2185b191b7a8280cae9a62c829d6

diff --git a/doc/webserver/faq/configuration.html b/doc/webserver/faq/configuration.html
index 7802ae2e..f9c4c4db 100644
--- a/doc/webserver/faq/configuration.html
+++ b/doc/webserver/faq/configuration.html
@@ -66,7 +66,7 @@
       "../user-manual/config.html#ENABLE-EDIT-ACTIONS" target="_top">enable-edit-actions</a>).</p>
     </div>
     <div class="SECT2">
-      <h3 class="SECT2"><a name="AEN417" id="AEN417">3.4. There are several different <span class=
+      <h3 class="SECT2"><a name="AEN411" id="AEN411">3.4. There are several different <span class=
       "QUOTE">"actions"</span> files. What are the differences?</a></h3>
       <p>Please have a look at the <a href="../user-manual/actions-file.html" target="_top">the actions chapter</a> in
       the <a href="../user-manual/index.html" target="_top">User Manual</a> for a detailed explanation.</p>
@@ -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>
@@ -395,8 +396,8 @@
       <table border="0" bgcolor="#E0E0E0" width="100%">
         <tr>
           <td>
-            <pre class="SCREEN">
-            { -crunch-incoming-cookies -crunch-outgoing-cookies -session-cookies-only -filter{content-cookies} }
+            <pre class=
+            "SCREEN"> { -crunch-incoming-cookies -crunch-outgoing-cookies -session-cookies-only -filter{content-cookies} }
   .example.com</pre>
           </td>
         </tr>