"../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>
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>
<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>