pattern</a> basis, i.e. for single URLs, whole web sites, groups or parts thereof etc. Actions can also be
grouped together and then applied to requests matching one or more patterns. There are many possible actions that
might apply to any given site. As an example, if you are blocking <a href=
- "http://en.wikipedia.org/wiki/Browser_cookie" target="_top">cookies</a> as one of your default actions, but need
+ "https://en.wikipedia.org/wiki/Browser_cookie" target="_top">cookies</a> as one of your default actions, but need
to accept cookies from a given site, you would need to define an exception for this site in one of your actions
files, preferably in <tt class="FILENAME">user.action</tt>.</p>
</div>
"../user-manual/config.html#ENABLE-EDIT-ACTIONS" target="_top">enable-edit-actions</a>).</p>
</div>
<div class="SECT2">
- <h3 class="SECT2"><a name="AEN416" id="AEN416">3.4. There are several different <span class=
- "QUOTE">"actions"</span> files. What are the differences?</a></h3>
+ <h3 class="SECT2"><a name="ACTIONFILE-DIFFERENCES" id="ACTIONFILE-DIFFERENCES">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>
</div>
<div class="SECT2">
<h3 class="SECT2"><a name="YAHOO" id="YAHOO">3.8. How can I make my Yahoo/Hotmail/Gmail account work?</a></h3>
<p>The default configuration shouldn't impact the usability of any of these services. It may, however, make all
- <a href="http://en.wikipedia.org/wiki/Browser_cookie" target="_top">cookies</a> temporary, so that your browser
+ <a href="https://en.wikipedia.org/wiki/Browser_cookie" target="_top">cookies</a> temporary, so that your browser
will forget your login credentials in between browser sessions. If you would like not to have to log in manually
each time you access those websites, simply turn off all cookie handling for them in the <tt class=
"FILENAME">user.action</tt> file. An example for yahoo might look like:</p>
<table border="0" bgcolor="#E0E0E0" width="100%">
<tr>
<td>
- <pre class="SCREEN"># Allow all cookies for Yahoo login:
-#
-{ -<a href="../user-manual/actions-file.html#CRUNCH-INCOMING-COOKIES" target=
+ <pre class="SCREEN"> # Allow all cookies for Yahoo login:
+ #
+ { -<a href="../user-manual/actions-file.html#CRUNCH-INCOMING-COOKIES" target=
"_top">crunch-incoming-cookies</a> -<a href="../user-manual/actions-file.html#CRUNCH-OUTGOING-COOKIES" target=
"_top">crunch-outgoing-cookies</a> -<a href="../user-manual/actions-file.html#SESSION-COOKIES-ONLY" target=
"_top">session-cookies-only</a> }
-.login.yahoo.com</pre>
+ .login.yahoo.com</pre>
</td>
</tr>
</table>
- <p>These kinds of sites are often quite complex and heavy with <a href="http://en.wikipedia.org/wiki/Javascript"
+ <p>These kinds of sites are often quite complex and heavy with <a href="https://en.wikipedia.org/wiki/Javascript"
target="_top">Javascript</a> and thus <span class="QUOTE">"fragile"</span>. So if <span class=
"emphasis"><i class="EMPHASIS">still</i></span> a problem, we have an <a href=
"../user-manual/actions-file.html#ALIASES" target="_top">alias</a> just for such sticky situations:</p>
<table border="0" bgcolor="#E0E0E0" width="100%">
<tr>
<td>
- <pre class="SCREEN"># Gmail is a _fragile_ site:
-#
-{ <tt class="LITERAL">fragile</tt> }
- # Gmail is ...
- mail.google.com</pre>
+ <pre class="SCREEN"> # Gmail is a _fragile_ site:
+ #
+ { <tt class="LITERAL">fragile</tt> }
+ # Gmail is ...
+ mail.google.com</pre>
</td>
</tr>
</table>
<h3 class="SECT2"><a name="TRANSPARENT" id="TRANSPARENT">3.19. Can Privoxy run as a <span class=
"QUOTE">"transparent"</span> proxy?</a></h3>
<p>The whole idea of Privoxy is to modify client requests and server responses in all sorts of ways and therefore
- it's not a transparent proxy as described in <a href="http://tools.ietf.org/html/rfc2616" target="_top">RFC
+ it's not a transparent proxy as described in <a href="https://tools.ietf.org/html/rfc2616" target="_top">RFC
2616</a>.</p>
<p>However, some people say <span class="QUOTE">"transparent proxy"</span> when they mean <span class=
"QUOTE">"intercepting proxy"</span>. If you are one of them, please read the <a href=
<div class="SECT2">
<h3 class="SECT2"><a name="SNEAKY-COOKIES" id="SNEAKY-COOKIES">3.23. I sometimes notice cookies sneaking through.
How?</a></h3>
- <p><a href="http://en.wikipedia.org/wiki/Browser_cookie" target="_top">Cookies</a> can be set in several ways.
+ <p><a href="https://en.wikipedia.org/wiki/Browser_cookie" target="_top">Cookies</a> can be set in several ways.
The classic method is via the <tt class="LITERAL">Set-Cookie</tt> HTTP header. This is straightforward, and an
easy one to manipulate, such as the <span class="APPLICATION">Privoxy</span> concept of <a href=
"../user-manual/actions-file.html#SESSION-COOKIES-ONLY" target="_top">session-cookies-only</a>. There is also the
- possibility of using <a href="http://en.wikipedia.org/wiki/Javascript" target="_top">Javascript</a> to set
+ possibility of using <a href="https://en.wikipedia.org/wiki/Javascript" target="_top">Javascript</a> to set
cookies (<span class="APPLICATION">Privoxy</span> calls these <tt class="LITERAL">content-cookies</tt>). This is
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
</div>
<div class="SECT2">
<h3 class="SECT2"><a name="EVIL-COOKIES" id="EVIL-COOKIES">3.24. Are all cookies bad? Why?</a></h3>
- <p>No, in fact there are many beneficial uses of <a href="http://en.wikipedia.org/wiki/Browser_cookie" target=
+ <p>No, in fact there are many beneficial uses of <a href="https://en.wikipedia.org/wiki/Browser_cookie" target=
"_top">cookies</a>. Cookies are just a method that browsers can use to store data between pages, or between
browser sessions. Sometimes there is a good reason for this, and the user's life is a bit easier as a result. But
there is a long history of some websites taking advantage of this layer of trust, and using the data they glean
from you and your browsing habits for their own purposes, and maybe to your potential detriment. Such sites are
using you and storing their data on your system. That is why the privacy conscious watch from whom those cookies
come, and why they really <span class="emphasis"><i class="EMPHASIS">need</i></span> to be there.</p>
- <p>See the <a href="http://en.wikipedia.org/wiki/Browser_cookie" target="_top">Wikipedia cookie definition</a>
+ <p>See the <a href="https://en.wikipedia.org/wiki/Browser_cookie" target="_top">Wikipedia cookie definition</a>
for more.</p>
</div>
<div class="SECT2">
<tr>
<td>
<pre class=
- "SCREEN"> { -crunch-incoming-cookies -crunch-outgoing-cookies -session-cookies-only -filter{content-cookies} }
+ "SCREEN"> { -crunch-incoming-cookies -crunch-outgoing-cookies -session-cookies-only -filter{content-cookies} }
.example.com</pre>
</td>
</tr>
<table border="0" bgcolor="#E0E0E0" width="100%">
<tr>
<td>
- <pre class="SCREEN"> ############################################################
- # Blacklist
- ############################################################
- { <a href="../user-manual/actions-file.html#BLOCK" target="_top">+block</a> }
- / # Block *all* URLs
+ <pre class="SCREEN"> ############################################################
+ # Blacklist
+ ############################################################
+ { <a href="../user-manual/actions-file.html#BLOCK" target="_top">+block</a> }
+ / # Block *all* URLs
- ############################################################
- # Whitelist
- ############################################################
- { <a href="../user-manual/actions-file.html#BLOCK" target="_top">-block</a> }
+ ############################################################
+ # Whitelist
+ ############################################################
+ { <a href="../user-manual/actions-file.html#BLOCK" target="_top">-block</a> }
kids.example.com
toys.example.com
games.example.com</pre>
<table border="0" bgcolor="#E0E0E0" width="100%">
<tr>
<td>
- <pre class="SCREEN"> # Unblock everybody, everywhere
- { <a href="../user-manual/actions-file.html#BLOCK" target="_top">-block</a> }
- / # UN-Block *all* URLs</pre>
+ <pre class="SCREEN"> # Unblock everybody, everywhere
+ { <a href="../user-manual/actions-file.html#BLOCK" target="_top">-block</a> }
+ / # UN-Block *all* URLs</pre>
</td>
</tr>
</table>
<table border="0" bgcolor="#E0E0E0" width="100%">
<tr>
<td>
- <pre class="SCREEN"> # Unblock everybody, everywhere, and turn off appropriate filtering, etc
- { <a href="../user-manual/actions-file.html#BLOCK" target="_top">-block</a> \
- <a href="../user-manual/actions-file.html#FILTER-BANNERS-BY-SIZE" target="_top">-filter{banners-by-size}</a> \
- <a href="../user-manual/actions-file.html#FILTER-BANNERS-BY-LINK" target="_top">-filter{banners-by-link}</a> \
- <tt class="LITERAL">allow-popups</tt> \
- }
- / # UN-Block *all* URLs and allow ads</pre>
+ <pre class="SCREEN"> # Unblock everybody, everywhere, and turn off appropriate filtering, etc
+ { <a href="../user-manual/actions-file.html#BLOCK" target="_top">-block</a> \
+ <a href="../user-manual/actions-file.html#FILTER-BANNERS-BY-SIZE" target="_top">-filter{banners-by-size}</a> \
+ <a href="../user-manual/actions-file.html#FILTER-BANNERS-BY-LINK" target="_top">-filter{banners-by-link}</a> \
+ <tt class="LITERAL">allow-popups</tt> \
+ }
+ / # UN-Block *all* URLs and allow ads</pre>
</td>
</tr>
</table>
<table border="0" bgcolor="#E0E0E0" width="100%">
<tr>
<td>
- <pre class="SCREEN"> ./configure --disable-toggle --disable-editor --disable-force</pre>
+ <pre class="SCREEN"> ./configure --disable-toggle --disable-editor --disable-force</pre>
</td>
</tr>
</table>