</para>
<variablelist>
<varlistentry>
- <term>Gold (10000 EUR/year)</term>
+ <term>Gold (12000 USD/year)</term>
<listitem>
<para>
Logo shown at the bottom of the
</listitem>
</varlistentry>
<varlistentry>
- <term>Silver (1000 EUR/year)</term>
+ <term>Silver (1200 USD/year)</term>
<listitem>
<para>
Logo shown randomly at the bottom of the
</listitem>
</varlistentry>
<varlistentry>
- <term>Bronze (500 EUR/year)</term>
+ <term>Bronze (600 USD/year)</term>
<listitem>
<para>
Logo and link on the <ulink url="https://www.privoxy.org/sponsors/">sponsor page</ulink>.
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
- <application>Privoxy's</application> reach.
+ <application>Privoxy's</application> reach unless you enable
+ <ulink url="../user-manual/actions-file.html#HTTPS-INSPECTION">https-inspection</ulink>.
</para>
<para>
All in all, &my-app; can help manage cookies in general, can help minimize
<sect2 renderas="sect3" id="ssl">
<title>How can Privoxy filter Secure (HTTPS) URLs?</title>
<para>
- Since secure HTTP connections are encrypted SSL sessions between your browser
- and the secure site, and are meant to be reliably <emphasis>secure</emphasis>,
- there is little that <application>Privoxy</application> can do but hand the raw
+ If you enable
+ <ulink url="../user-manual/actions-file.html#HTTPS-INSPECTION">https-inspection</ulink>
+ <application>Privoxy</application> will impersonate the destination
+ server and can thus filter encrypted requests and responses as well.
+</para>
+<para>
+ Without
+ <ulink url="../user-manual/actions-file.html#HTTPS-INSPECTION">https-inspection</ulink>
+ secure HTTP connections are encrypted SSL sessions between your
+ browser and the secure site, and there is little
+ that <application>Privoxy</application> can do but hand the raw
gibberish data though from one end to the other unprocessed.
</para>
<para>
for HTTPS.
</para>
<para>
- Adding HTTP/2 support is on the TODO list but currently
- nobody is known to work on it.
+ Adding HTTP/2 support is on the
+ <ulink url="https://www.privoxy.org/gitweb/?p=privoxy.git;a=blob_plain;f=TODO;hb=HEAD">TODO</ulink>
+ list but currently nobody is known to work on it.
</para>
</sect2>