Merge branch 'master' of ssh://git.privoxy.org:23/git/privoxy

[privoxy.git] / doc / source / faq.sgml

diff --git a/doc/source/faq.sgml b/doc/source/faq.sgml
index ae43aa0..b4ebb87 100644 (file)
--- a/doc/source/faq.sgml
+++ b/doc/source/faq.sgml
@@ -8,10 +8,10 @@
 <!entity history SYSTEM "history.sgml">
 <!entity copyright SYSTEM "copyright.sgml">
 <!entity license SYSTEM "license.sgml">
-<!entity p-version "3.0.29">
-<!entity p-status "stable">
-<!entity % p-not-stable "IGNORE">
-<!entity % p-stable "INCLUDE">
+<!entity p-version "3.0.33">
+<!entity p-status "UNRELEASED">
+<!entity % p-not-stable "INCLUDE">
+<!entity % p-stable "IGNORE">
 <!entity % p-text "IGNORE">        <!-- define we are not a text only doc -->
 <!entity % p-doc "INCLUDE">        <!-- and we are a formal doc           -->
 <!entity % p-supp-userman "INCLUDE"> <!-- Include all from supported.sgml -->
@@ -25,7 +25,7 @@
 
  Purpose     :  FAQ
 
- Copyright (C) 2001-2020 Privoxy Developers https://www.privoxy.org/
+ Copyright (C) 2001-2021 Privoxy Developers https://www.privoxy.org/
  See LICENSE.
 
  Based partially on the Internet Junkbuster FAQ originally written by and
@@ -69,7 +69,7 @@
  <subscript>
 <!-- Completely the wrong markup, but very little is allowed  -->
 <!-- in this part of an article. FIXME -->
- <link linkend="copyright">Copyright</link> &my-copy; 2001-2020 by
+ <link linkend="copyright">Copyright</link> &my-copy; 2001-2021 by
  <ulink url="https://www.privoxy.org/">Privoxy Developers</ulink>
  </subscript>
 </pubdate>
@@ -554,7 +554,10 @@ warranty? Registration?</title>
 <para>
  The logo sizes depend on the sponsor level. Logos are served from
  our server, no requests are made to the sponsor website unless
- the links are being used.
+ the links are being used. Note that Privoxy comes with a
+ <ulink url="https://www.privoxy.org/user-manual/actions-file.html#HIDE-REFERRER">hide-referrer</ulink>
+ action so Privoxy users following links to sponsor websites
+ may not necessarily send requests with a Referer header set.
 </para>
 <para>
  Link targets are without path (<quote>https://www.example.org/</quote>
@@ -568,7 +571,9 @@ warranty? Registration?</title>
  If you want to become a sponsor, please contact
  <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.
+ New sponsors are only accepted if no
+ <ulink url="../user-manual/copyright.html#AUTHORS">Privoxy team</ulink>
+ member objects.
 </para>
 
 </sect2>
@@ -1223,7 +1228,7 @@ and thus avoid individual browser configuration?</title>
  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
- <ulink url="http://tools.ietf.org/html/rfc2616">RFC 2616</ulink>.
+ <ulink url="https://tools.ietf.org/html/rfc2616">RFC 2616</ulink>.
 </para>
 <para>
  However, some people say <quote>transparent proxy</quote> when they
@@ -1915,7 +1920,7 @@ speed up web browsing?</title>
 <para>
  No, it does not have this ability at all. You want something like
  <ulink url="http://www.squid-cache.org/">Squid</ulink> or
- <ulink url="http://www.pps.jussieu.fr/~jch/software/polipo/">Polipo</ulink> for this.
+ <ulink url="https://www.irif.fr/~jch//software/polipo/">Polipo</ulink> for this.
  And, yes, before you ask, <application>Privoxy</application> can co-exist
  with other kinds of proxies like <application>Squid</application>.
  See the <ulink url="../user-manual/config.html#FORWARDING">forwarding
@@ -2986,7 +2991,7 @@ browsing has slowed to a crawl. What gives? </title>
  To prevent the crashes you can rewrite your filter to use less resources,
  increase the relevant memory limit or recompile pcre to use less stack space.
  For details please see the
- <ulink url="http://pcre.org/original/doc/html/pcrestack.html">pcrestack man page</ulink>
+ <ulink url="https://pcre.org/original/doc/html/pcrestack.html">pcrestack man page</ulink>
  and the documentation of your operating system.
 </para>
 </sect2>