strengths is that it is highly configurable giving you the ability to
completely personalize your installation. Being familiar with, or at least
having an interest in learning about <ulink
- url="http://en.wikipedia.org/wiki/Http">HTTP</ulink> and other networking
- protocols, <ulink url="http://en.wikipedia.org/wiki/Html">HTML</ulink>, and
- <ulink url="http://en.wikipedia.org/wiki/Regular_expressions"><quote>Regular
+ url="https://en.wikipedia.org/wiki/Http">HTTP</ulink> and other networking
+ protocols, <ulink url="https://en.wikipedia.org/wiki/Html">HTML</ulink>, and
+ <ulink url="https://en.wikipedia.org/wiki/Regular_expressions"><quote>Regular
Expressions</quote></ulink>
will be a big plus and will help you get the most out of &my-app;.
A new installation just includes a very basic configuration. The user
</para>
<para>
Much of <application>Privoxy's</application> configuration can be done
- with a <ulink url="http://en.wikipedia.org/wiki/Web_browser">Web browser</ulink>.
+ with a <ulink url="https://en.wikipedia.org/wiki/Web_browser">Web browser</ulink>.
But there are areas where configuration is done using a
- <ulink url="http://en.wikipedia.org/wiki/Text_editors">text editor</ulink>
+ <ulink url="https://en.wikipedia.org/wiki/Text_editors">text editor</ulink>
to edit configuration files. Also note that the web-based action editor
doesn't use authentication and should only be enabled in environments
where all clients with access to &my-app; listening port can be trusted.
<sect2 renderas="sect3" id="proxymoron"><title>What is a <quote>proxy</quote>? How does
Privoxy work? </title>
<para>
- A <ulink url="http://en.wikipedia.org/wiki/Proxy_server">web proxy</ulink>
+ A <ulink url="https://en.wikipedia.org/wiki/Proxy_server">web proxy</ulink>
is a service, based on a software such as &my-app;, that clients
(i.e. browsers) can use instead of connecting to web servers directly.
The clients then ask the proxy to request objects (web pages, images, movies etc)
on their behalf and to forward the data to the clients.
It is a <quote>go-between</quote>. For details, see
- <ulink url="http://en.wikipedia.org/wiki/Proxy_server">Wikipedia's proxy definition</ulink>.
+ <ulink url="https://en.wikipedia.org/wiki/Proxy_server">Wikipedia's proxy definition</ulink>.
</para>
<para>
There are many reasons to use web proxies, such as security (firewalling),
<application>Junkbuster</application> left off.
<application>Privoxy</application> still blocks ads and banners,
still manages <ulink
- url="http://en.wikipedia.org/wiki/Browser_cookie">cookies</ulink>, and still
+ url="https://en.wikipedia.org/wiki/Browser_cookie">cookies</ulink>, and still
helps protect your privacy. But, most of these features have been enhanced,
and many new ones have been added, all in the same vein.
</para>
<sect2 renderas="sect3" id="license"><title>Is there is a license or fee? What about a
warranty? Registration?</title>
<para>
- <application>Privoxy</application> is free software and licensed under the <ulink
- url="http://www.gnu.org/licenses/old-licenses/gpl-2.0.html">GNU General Public License (GPL) version 2</ulink>.
- It is free to use, copy, modify or distribute as you wish under the terms of this
- license. Please see the <link linkend="copyright">Copyright</link> section for more
- information on the license and copyright. Or the <filename>LICENSE</filename> file
- that should be included.
+ <application>Privoxy</application> is free software.
+ It is free to use, copy, modify or distribute as you wish under the terms of its
+ license.
+ Please see the <link linkend="copyright">Copyright</link> section for more
+ information on the license and copyright.
</para>
<para>
There is <emphasis>no warranty</emphasis> of any kind, expressed, implied or otherwise.
our server, no requests are made to the sponsor website unless
the links are being used.
</para>
+<para>
+ Link targets are without path (<quote>https://www.example.org/</quote>
+ not <quote>https://www.example.org/seo/keyword/spam/</quote>).
+</para>
<para>
The details may change over time but changes will only affect new sponsors
(or existing sponsors that explicitly agreed to the changes).
</para>
<para>
If you want to become a sponsor, please contact
- <ulink url="mailto:fk@fabiankeil.de">Fabian Keil</ulink>.
+ <ulink url="mailto:fk@fabiankeil.de">Fabian Keil</ulink>
+ and include the link target in the mail.
New sponsors are only accepted if no developer objects.
</para>
<ulink url="../user-manual/startup.html">the User Manual for more
details</ulink>. You should also flush your browser's memory and disk
cache to get rid of any cached junk items, and remove any stored
- <ulink url="http://en.wikipedia.org/wiki/Browser_cookie">cookies</ulink>.
+ <ulink url="https://en.wikipedia.org/wiki/Browser_cookie">cookies</ulink>.
</para>
</sect2>
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 <ulink url="http://en.wikipedia.org/wiki/Browser_cookie">cookies</ulink>
+ if you are blocking <ulink url="https://en.wikipedia.org/wiki/Browser_cookie">cookies</ulink>
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 <filename>user.action</filename>.
</sect2>
-<sect2 renderas="sect3">
+<sect2 renderas="sect3" id="actionfile-differences">
<title>There are several different <quote>actions</quote> files. What are
the differences?</title>
<para>
<para>
The default configuration shouldn't impact the usability of any of these services.
It may, however, make all <ulink
- url="http://en.wikipedia.org/wiki/Browser_cookie">cookies</ulink>
+ url="https://en.wikipedia.org/wiki/Browser_cookie">cookies</ulink>
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
.login.yahoo.com</screen>
<para>
These kinds of sites are often quite complex and heavy with
- <ulink url="http://en.wikipedia.org/wiki/Javascript">Javascript</ulink> and
+ <ulink url="https://en.wikipedia.org/wiki/Javascript">Javascript</ulink> and
thus <quote>fragile</quote>. So if <emphasis>still</emphasis> a problem,
we have an <ulink
url="../user-manual/actions-file.html#ALIASES">alias</ulink> just for such
<title>I sometimes notice cookies sneaking through. How?</title>
<para>
<ulink
- url="http://en.wikipedia.org/wiki/Browser_cookie">Cookies</ulink> can be
+ url="https://en.wikipedia.org/wiki/Browser_cookie">Cookies</ulink> can be
set in several ways. The classic method is via the
<literal>Set-Cookie</literal> HTTP header. This is straightforward, and an
easy one to manipulate, such as the &my-app; concept of
<ulink url="../user-manual/actions-file.html#SESSION-COOKIES-ONLY">session-cookies-only</ulink>.
There is also the possibility of using
- <ulink url="http://en.wikipedia.org/wiki/Javascript">Javascript</ulink> to
+ <ulink url="https://en.wikipedia.org/wiki/Javascript">Javascript</ulink> to
set cookies (&my-app; calls these <literal>content-cookies</literal>). 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
<para>
No, in fact there are many beneficial uses of
<ulink
- url="http://en.wikipedia.org/wiki/Browser_cookie">cookies</ulink>. Cookies are just a
+ url="https://en.wikipedia.org/wiki/Browser_cookie">cookies</ulink>. 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
</para>
<para>
See the
- <ulink url="http://en.wikipedia.org/wiki/Browser_cookie">Wikipedia cookie
+ <ulink url="https://en.wikipedia.org/wiki/Browser_cookie">Wikipedia cookie
definition</ulink> for more.
</para>
</sect2>
<para>
Upgrading <application>Privoxy</application>, or going to the most recent
<filename>default.action</filename> file available from <ulink
- url="https://sourceforge.net/project/showfiles.php?group_id=11118">SourceForge</ulink>
+ url="https://www.privoxy.org/gitweb/?p=privoxy.git;a=blob_plain;f=default.action.master;hb=HEAD">git</ulink>
might be worth a try, too.
</para>
</sect2>
</title>
<para>
<application>Privoxy</application> is attempting to disable malicious
- <ulink url="http://en.wikipedia.org/wiki/Javascript">Javascript</ulink>
+ <ulink url="https://en.wikipedia.org/wiki/Javascript">Javascript</ulink>
in this case, with the <literal>unsolicited-popups</literal>
filter. <application>Privoxy</application> cannot tell very well
<quote>good</quote> code snippets from <quote>bad</quote> code snippets.
</para>
<!-- ~~~~~ New section ~~~~~ -->
- <sect2><title>License</title>
+ <sect2 id="privoxy-license"><title>License</title>
<!-- Include copyright.sgml: -->
&license;
<!-- end copyright -->
<!-- ~ End section ~ -->
<!-- ~~~~~ New section ~~~~~ -->
- <sect2><title>History</title>
+ <sect2 id="history"><title>History</title>
<!-- Include history.sgml -->
&history;
<!-- end -->
projects / privoxy.git / blobdiff