This file belongs into
ijbswa.sourceforge.net:/home/groups/i/ij/ijbswa/htdocs/
- $Id: faq.sgml,v 2.116 2016/02/26 12:33:18 fabiankeil Exp $
+ $Id: faq.sgml,v 2.120 2016/04/09 10:23:54 fabiankeil Exp $
- Copyright (C) 2001-2014 Privoxy Developers http://www.privoxy.org/
+ Copyright (C) 2001-2014 Privoxy Developers https://www.privoxy.org/
See LICENSE.
Based partially on the Internet Junkbuster FAQ originally written by and
<!-- Completely the wrong markup, but very little is allowed -->
<!-- in this part of an article. FIXME -->
<link linkend="copyright">Copyright</link> &my-copy; 2001-2014 by
- <ulink url="http://www.privoxy.org/">Privoxy Developers</ulink>
+ <ulink url="https://www.privoxy.org/">Privoxy Developers</ulink>
</subscript>
</pubdate>
-<pubdate>$Id: faq.sgml,v 2.116 2016/02/26 12:33:18 fabiankeil Exp $</pubdate>
+<pubdate>$Id: faq.sgml,v 2.120 2016/04/09 10:23:54 fabiankeil Exp $</pubdate>
<!--
]]>
<para>
This FAQ gives quick answers to frequently asked questions about
- <ulink url="http://www.privoxy.org/">Privoxy</ulink>.
+ <ulink url="https://www.privoxy.org/">Privoxy</ulink>.
It is not a substitute for the
<ulink url="../user-manual/index.html"><citetitle>Privoxy User Manual</citetitle></ulink>.
<!--
Please note that this document is a work in progress. This copy represents
the state at the release of version &p-version;.
You can find the latest version of the document at <ulink
- url="http://www.privoxy.org/faq/">http://www.privoxy.org/faq/</ulink>.
+ url="https://www.privoxy.org/faq/">https://www.privoxy.org/faq/</ulink>.
Please see the <link linkend="contact">Contact section</link> if you want to
contact the developers.
</para>
<sect3 renderas="sect4" id="donate"><title>Would you like to donate?</title>
<para>
Donations are welcome. Our
- <ulink url="http://ijbswa.cvs.sourceforge.net/viewvc/ijbswa/current/TODO">TODO list</ulink>
+ <ulink url="http://ijbswa.cvs.sourceforge.net/viewvc/ijbswa/current/TODO?view=markup">TODO list</ulink>
is rather long and being able to pay one (or more) developers to work on Privoxy
would make a huge difference, even if it was only for a couple of weeks. Donations may
also be used for Privoxy-related travel expenses (for example to attend conferences),
<para>
If you have any questions regarding donations please mail to either the
public user mailing list or, if it's a private matter, to
- <ulink url="mailto:fk@fabiankeil.de">Fabian Keil</ulink> (Privoxy's SPI liason)
+ <ulink url="mailto:fk@fabiankeil.de">Fabian Keil</ulink> (Privoxy's SPI liaison)
directly.
</sect3>
<application>Privoxy</application> is not running at all. Check the <ulink
url="../user-manual/config.html#LOGFILE">log file</ulink>. For instructions
on starting <application>Privoxy</application> and browser configuration,
- see the <ulink url="http://www.privoxy.org/user-manual/startup.html">chapter
+ see the <ulink url="https://www.privoxy.org/user-manual/startup.html">chapter
on starting <application>Privoxy</application></ulink> in the
- <ulink url="http://www.privoxy.org/user-manual/">User Manual</ulink>.
+ <ulink url="https://www.privoxy.org/user-manual/">User Manual</ulink>.
</para>
</sect2>
First, make sure that Privoxy is <emphasis>really</emphasis> running and
being used by visiting <ulink url="http://p.p/">http://p.p/</ulink>. You
should see the <application>Privoxy</application> main page. If not, see
- the <ulink url="http://www.privoxy.org/user-manual/startup.html">chapter
+ the <ulink url="https://www.privoxy.org/user-manual/startup.html">chapter
on starting <application>Privoxy</application></ulink> in the
- <ulink url="http://www.privoxy.org/user-manual/">User Manual</ulink>.
+ <ulink url="https://www.privoxy.org/user-manual/">User Manual</ulink>.
</para>
<para>
Based on your feedback and the continuing development, updates of
<filename>default.action</filename> will be
made available from time to time on the <ulink
- url="http://sourceforge.net/project/showfiles.php?group_id=11118">files section</ulink> of
- our <ulink url="http://sf.net/projects/ijbswa/">project page</ulink>.
+ url="https://sourceforge.net/project/showfiles.php?group_id=11118">files section</ulink> of
+ our <ulink url="https://sourceforge.net/projects/ijbswa/">project page</ulink>.
</para>
<para>
If you wish to receive an email notification whenever we release updates of
<application>Privoxy</application> or the actions file, <ulink
- url="http://lists.sourceforge.net/lists/listinfo/ijbswa-announce/">subscribe
+ url="https://lists.sourceforge.net/lists/listinfo/ijbswa-announce/">subscribe
to our announce mailing list</ulink>, ijbswa-announce@lists.sourceforge.net.
</para>
<para>
If you intend to develop your own filters, you might want to have a look at
<ulink
- url="http://www.fabiankeil.de/sourcecode/pft/">Privoxy-Filter-Test</ulink>.
+ url="https://www.fabiankeil.de/sourcecode/pft/">Privoxy-Filter-Test</ulink>.
</para>
</sect2>
<para>
Earlier ]]>3.x versions could run as a system service using <command>srvany.exe</command>.
See the discussion at <ulink
- url="http://sourceforge.net/tracker/?func=detail&atid=361118&aid=485617&group_id=11118">http://sourceforge.net/tracker/?func=detail&atid=361118&aid=485617&group_id=11118</ulink>,
+ url="https://sourceforge.net/tracker/?func=detail&atid=361118&aid=485617&group_id=11118">https://sourceforge.net/tracker/?func=detail&atid=361118&aid=485617&group_id=11118</ulink>,
for details, and a sample configuration.
</para>
</sect2>
<para>
For a good discussion of some of the issues involved (including privacy and
security issues), see
- <ulink url="http://sourceforge.net/tracker/?func=detail&atid=211118&aid=629518&group_id=11118">http://sourceforge.net/tracker/?func=detail&atid=211118&aid=629518&group_id=11118</ulink>.
+ <ulink url="https://sourceforge.net/tracker/?func=detail&atid=211118&aid=629518&group_id=11118">https://sourceforge.net/tracker/?func=detail&atid=211118&aid=629518&group_id=11118</ulink>.
</para>
</sect2>
<para>
Lately there have been reports of problems with some kind of
"parental control" software based on Privoxy that came preinstalled on
- certain <ulink url="http://sourceforge.net/p/ijbswa/bugs/813/">ASUS Netbooks</ulink>.
+ certain <ulink url="https://sourceforge.net/p/ijbswa/bugs/813/">ASUS Netbooks</ulink>.
The problems described are inconsistent with the behaviour of official
Privoxy versions, which suggests that the preinstalled software may
contain vendor modifications that we don't know about and thus can't debug.
<para>
Upgrading <application>Privoxy</application>, or going to the most recent
<filename>default.action</filename> file available from <ulink
- url="http://sourceforge.net/project/showfiles.php?group_id=11118">SourceForge</ulink>
+ url="https://sourceforge.net/project/showfiles.php?group_id=11118">SourceForge</ulink>
might be worth a try, too.
</para>
</sect2>
</para>
</sect2>
+<sect2 renderas="sect3" id="tainted-sockets">
+<title>What are tainted sockets and how do I prevent them?</title>
+<para>
+ &my-app; marks sockets as tainted when it can't use them to
+ serve additional requests.
+ This does not necessarily mean that something went wrong and
+ information about tainted sockets is only logged if connection
+ debugging is enabled (debug 2).
+</para>
+<para>
+ For example server sockets that were used for CONNECT requests
+ (which are used to tunnel https:// requests) are considered tainted
+ once the client closed its connection to &my-app;.
+ Technically &my-app; could keep the connection to the server open,
+ but the server would not accept requests that do not belong to the
+ previous TLS/SSL session (and the client may even have terminated
+ the session).
+</para>
+<para>
+ Server sockets are also marked tainted when a client requests a
+ resource, but closes the connection before &my-app; has completely
+ received (and forwarded) the resource to the client.
+ In this case the server would (probably) accept additional requests,
+ but &my-app; could not get the response without completely reading
+ the leftovers from the previous response.
+</para>
+<para>
+ These are just two examples, there are currently a bit more than
+ 25 scenarios in which a socket is considered tainted.
+</para>
+<para>
+ While sockets can also be marked tainted as a result of a technical
+ problem that may be worth fixing, the problem will be explicitly
+ logged as error.
+</para>
+</sect2>
</sect1>
projects / privoxy.git / blobdiff