<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V3.1//EN"[
-<!entity % dummy "INCLUDE">
+<!entity % dummy "IGNORE">
<!entity supported SYSTEM "supported.sgml">
<!entity newfeatures SYSTEM "newfeatures.sgml">
<!entity p-intro SYSTEM "privoxy.sgml">
<!entity seealso SYSTEM "seealso.sgml">
-<!entity p-version "2.9.13">
-<!entity p-status "BETA">
-<!entity % p-not-stable "INCLUDE"> <!-- set to IGNORE for stable release -->
-<!entity % p-stable "IGNORE"> <!-- set INCLUDE for stable release -->
+<!entity contacting SYSTEM "contacting.sgml">
+<!entity history SYSTEM "history.sgml">
+<!entity copyright SYSTEM "copyright.sgml">
+<!entity p-version "2.9.14">
+<!entity p-status "beta">
+<!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 -->
This file belongs into
ijbswa.sourceforge.net:/home/groups/i/ij/ijbswa/htdocs/
- $Id: faq.sgml,v 1.40 2002/04/03 04:22:03 hal9 Exp $
+ $Id: faq.sgml,v 1.50 2002/04/26 05:25:23 hal9 Exp $
Written by and Copyright (C) 2001 the SourceForge
Privoxy team. http://www.privoxy.org/
</QandAEntry>
</QandASet>
+ ========================================================================
+ NOTE: Please read developer-manual/documentation.html before touching
+ anything in this, or other Privoxy documentation. You have been warned!
+ Failure to abide by this rule will result in the revocation of your license
+ to live a peaceful existence!
+ ========================================================================
+
-->
<artheader>
<title>Privoxy Frequently Asked Questions</title>
-<pubdate>$Id: faq.sgml,v 1.40 2002/04/03 04:22:03 hal9 Exp $</pubdate>
+<pubdate>$Id: faq.sgml,v 1.50 2002/04/26 05:25:23 hal9 Exp $</pubdate>
<authorgroup>
<author>
]]>
<para>
This FAQ gives users and developers alike answers to frequently asked
- questions about <ulink url="http://www.privoxy.org">Privoxy</ulink>.
+ questions about <ulink url="http://www.privoxy.org">Privoxy</ulink>
+ <![%p-stable;[ v.&p-version]]>.
</para>
-<!--
- Include privoxy.sgml boilerplate:
--->
+<![%p-text;[
+
+<para>
+
+ Test of text doc only.
+
+</para>
+
+]]>
+
+<!-- Include privoxy.sgml boilerplate: -->
&p-intro;
+<!-- end boilerplate -->
<para>
You can find the latest version of the document at <ulink
url="http://www.privoxy.org/faq/">http://www.privoxy.org/faq/</ulink>.
- Please see the Contact section in the <ulink
- url="../user-manual/contact.html">user-manual</ulink> if
- you want to contact the developers.
+ Please see the Contact section if you want to contact the developers.
</para>
<!-- <para> -->
significantly at this point.
</para>
<para>
- Please see the <ulink
- url="../user-manual/copyright.html#HISTORY">user-manual</ulink> for more
+ Please see the <link linkend="copyright">History section</link> for more
information on the history of <application>Junkbuster</application> and
<application>Privoxy</application>.
</para>
</para>
<para>
There are potential legal complications from the continued use of the
- <application>Junkbuster</application> name, which is a trademark of
+ <application>Junkbuster</application> name, which is a registered trademark of
<ulink url="http://junkbusters.com">Junkbusters Corporation</ulink>.
+ And thus they <quote>own</quote> the rights to the name.
(There are, however, no objections from Junkbusters Corporation to the
<application>Privoxy</application> project itself, and they, in fact, still
share our ideals and goals.)
<para>
The developers also believed that there are so many changes from the original
code, that it was time to make a clean break from the past and make
- a name in their own right, especially now with the pending release of
- version 3.0.
+ a name in their own right<![%p-not-stable;[, especially now with the pending
+ release of version 3.0]]>.
</para>
</sect2>
</para>
<para>
The configuration has changed significantly as well. This is something that
- users will notice right off the bat. The <quote>blocklist</quote> file does
- not exist any more. This is replaced by <quote>actions</quote> files, such
- as <filename>default.actions</filename>. This is where most of the per site
- configuration is now.
+ users will notice right off the bat if you are upgrading from
+ <application>Junkbuster</application> 2.0.x. The <quote>blocklist</quote>
+ file does not exist any more. This is replaced by <quote>actions</quote>
+ files, such as <filename>default.actions</filename>. This is where most of
+ the per site configuration is now.
</para>
</sect2>
<sect2 renderas="sect3" id="features"><title>What are some of the new features?</title>
-<!--
- Include newfeatures.sgml
--->
-&newfeatures;
+<!-- Include newfeatures.sgml: -->
+ &newfeatures;
+<!-- end include -->
</sect2>
<sect2 renderas="sect3" id="license"><title>Is there is a license or fee? What about a
warranty? Registration?</title>
<para>
- <application>Privoxy</application> is licensed under the
- GNU General Public License (GPL). It is free to use, copy,
- modify or distribute as you wish under the terms of this license.
- Please see the
-<ulink url="../user-manual/copyright.html#HISTORY">user-manual</ulink> for
- more information on the license and copyright.
+ <application>Privoxy</application> is licensed under the GNU General Public
+ License (GPL). It is free to use, copy, modify or distribute as you wish
+ under the terms of this license. Please see the Copyright section for more
+ information on the license and copyright.
</para>
<para>
<para>
See the <ulink
url="../user-manual/index.html">user-manual</ulink> for
- platform specific installation instructions. [FIXME: This is meant for after
- the name change for 3.0!]
+ platform specific installation instructions.
</para>
<para>
Note: Some installers may automatically uninstall
some of these <quote>actions</quote>.</title>
<para>
These are all explained in the
- <ulink url="../user-manual/configuration.html#ACTIONSFILE">user-manual</ulink>.
+ <ulink url="../user-manual/configuration.html#ACTIONS-FILE">user-manual</ulink>.
Please refer to that.
</para>
</sect2>
<para>
Please see the
<ulink
- url="../user-manual/configuration.html#ACTIONSFILE">user-manual</ulink> for a
+ url="../user-manual/configuration.html#ACTIONS-FILE">user-manual</ulink> for a
detailed explanation of these and other configuration files, and their
various options and syntax.
</para>
</sect2>
-->
+<!--
<sect2 renderas="sect3" id="configfiles"> <title>What are the differences between
intermediate.action, basic.action, etc.?</title>
<para>
<entry>advanced.action</entry>
</row>
</thead>
-
+-->
<!-- <tfoot> -->
<!-- <row> -->
<!-- <entry>f1</entry> -->
<!-- <entry>f5</entry> -->
<!-- </row> -->
<!-- </tfoot> -->
-
+<!--
<tbody>
-<!-- new row -->
+
<row>
<entry>ad-filtering</entry>
<entry>?</entry>
<entry>x</entry>
<entry>x</entry>
</row>
-<!-- new row -->
+
<row>
<entry>blank image</entry>
<entry>?</entry>
<entry>x</entry>
<entry>x</entry>
</row>
-<!-- new row -->
+
<row>
<entry>de-animate GIFs</entry>
<entry>?</entry>
<entry>x</entry>
<entry>x</entry>
</row>
-<!-- new row -->
+
<row>
<entry>referer forging</entry>
<entry>?</entry>
<entry>x</entry>
<entry>x</entry>
</row>
-<!-- new row -->
+
<row>
<entry>jon's +no-cookies-keep (i.e. session cookies only)</entry>
<entry>?</entry>
<entry>x</entry>
<entry>x</entry>
</row>
-<!-- new row -->
+
<row>
<entry>no-popup windows</entry>
<entry>?</entry>
<entry>x</entry>
<entry>x</entry>
</row>
-<!-- new row -->
+
<row>
<entry>fast redirects</entry>
<entry>?</entry>
<entry>x</entry>
<entry>x</entry>
</row>
-<!-- new row -->
+
<row>
<entry>hide-referrer</entry>
<entry>?</entry>
<entry>x</entry>
<entry>x</entry>
</row>
-<!-- new row -->
+
<row>
<entry>hide-useragent</entry>
<entry>?</entry>
<entry>x</entry>
<entry>x</entry>
</row>
-<!-- new row -->
+
<row>
<entry>content-modification</entry>
<entry>?</entry>
<entry></entry>
<entry>x</entry>
</row>
-<!-- new row -->
+
<row>
<entry>feature-x</entry>
<entry>?</entry>
<entry></entry>
<entry></entry>
</row>
-<!-- new row -->
+
<row>
<entry>feature-y</entry>
<entry>?</entry>
<entry></entry>
<entry></entry>
</row>
-<!-- new row -->
+
<row>
<entry>feature-z</entry>
<entry>?</entry>
<entry></entry>
<entry></entry>
</row>
-<!-- finish -->
+
</tbody>
</tgroup>
</table>
</para>
</sect2>
+ -->
+
<sect2 renderas="sect3" id="browseconfig"> <title>Why can I change the configuration with a
browser? Does that not raise security issues?</title>
<para>
<para>
<screen>
listen-address 192.168.1.1:8118
- </screen>
+</screen>
</para>
<para>
</para>
</sect2>
+<sect2 renderas="sect3" id="srvany">
+<title>Can <application>Privoxy</application> run as a service
+on Win2K/NT?</title>
+<para>
+ Yes, it can run as a system service using <command>srvany.exe</command>.
+ The only catch is that this will effectively disable the
+ <application>Privoxy</application> icon in the taskbar. You can have
+ one or the other, but not both at this time :(
+</para>
+<para>
+ There is a pending feature request for this functionality. See
+ thread: <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>,
+ for details, and a sample configuration.
+
+</para>
+</sect2>
+
+
<sect2 renderas="sect3" id="otherproxy">
<title>How can I make <application>Privoxy</application> work with other
proxies like <application>Squid</application>?</title>
</para>
<para>
-With recent versions of <application>Privoxy</application> (version 2.9.x), you can get some
-information about <application>Privoxy</application> and change some settings by going to
-<ulink url="http://p.p/">http://p.p/</ulink> or, equivalently, <ulink url="http://config.privoxy.org/">http://config.privoxy.org/</ulink>
-(Note that p.p is far easier to type but may not work in some
-configurations. With the name change to <application>Privoxy</application>,
-this is changed from the previous http://i.j.b/ or earlier 2.9.x versions).
+ With recent versions of <application>Privoxy</application> (version 2.9.x and
+ greater), you can get some information about
+ <application>Privoxy</application> and change some settings by going to
+ <ulink url="http://p.p/">http://p.p/</ulink> or, equivalently, <ulink
+ url="http://config.privoxy.org/">http://config.privoxy.org/</ulink> (Note
+ that p.p is far easier to type but may not work in some configurations. With
+ the name change to <application>Privoxy</application>, this is changed from
+ the previous http://i.j.b/ and earlier 2.9.x versions).
</para>
<para>
-These pages are <emphasis>not</emphasis> forwarded to a server on the Internet
-- instead they are handled by a special web server which is built in to
-<application>Privoxy</application>.
+ These pages are <emphasis>not</emphasis> forwarded to a server on the
+ Internet - instead they are handled by a special web server which is built in to
+ <application>Privoxy</application>.
</para>
<para>
-If you are not running <application>Privoxy</application>, then <ulink
-url="http://p.p/">http://p.p/</ulink> will fail, and <ulink
-url="http://config.privoxy.org/">http://config.privoxy.org/</ulink> will
-return a web page telling you you're not running
-<application>Privoxy</application>.
+ If you are not running <application>Privoxy</application>, then <ulink
+ url="http://p.p/">http://p.p/</ulink> will fail, and <ulink
+ url="http://config.privoxy.org/">http://config.privoxy.org/</ulink> will
+ return a web page telling you you're not running
+ <application>Privoxy</application>.
</para>
<para>
-If you have version 2.0.2, then the equivalent is
-http://example.com/show-proxy-args (but you get far less information, and you
-should really consider upgrading to 2.9.x).
+ If you have version 2.0.2, then the equivalent is
+ http://example.com/show-proxy-args (but you get far less information, and
+ you should really consider upgrading to &p-version;).
</para>
</sect2>
</para>
</sect2>
-<sect2 renderas="sect3" id="proxy-chaining"><title>How do I chain <application>Privoxy</application> with other proxies
-(e.g. squid)?</title>
-<para>
- Fillme.
-</para>
-</sect2>
-->
<sect2 renderas="sect3" id="blocklist"><title>Do you still maintain the blocklists?</title>
<para>
- No. The format of the blocklists has changed significantly in the versions
- 2.9.x. Once we have released the new stable version, v3.0, there will
- again be blocklists that you can update automatically.
+ No, not by this name. The format of the blocklists has changed
+ significantly in versions 2.9.x and later. This functionality
+ is done by the <quote>actions</quote> file now. See next question ...
</para>
</sect2>
<sect2 renderas="sect3" id="newads"><title>How can I submit new ads?</title>
<para>
- As of now, please discontinue to submit new ad blocking infos. Once we
- have released the new version, there will again be a form on the website,
- which you can use to contribute new ads.
+Please see the <ulink url="contact.html">Contact section</ulink>.
</para>
+
+<para>
+ This process does not work with earlier versions of <application>Privoxy</application>
+ or <application>Junkbuster</application>.
+</para>
+
</sect2>
<sect2 renderas="sect3" id="ip"><title>How can I hide my IP address?</title>
<para>
You cannot hide your IP address with <application>Privoxy</application> or any other software, since
-the server needs to know your IP address to send the answer to you.
+the server needs to know your IP address to send the answers back to you.
</para>
<para>
Fortunately there are many publicly usable anonymous proxies out there, which
<para>
<application>Privoxy</application> can remove various information about you,
and allows <emphasis>you</emphasis> more freedom to decide which sites
- you can trust. But it's still possible that web sites can find out who you
- are. Here's one way this can happen.
+ you can trust, and what details you want to reveal. But it's still possible
+ that web sites can find out who you are. Here's one way this can happen.
</para>
<para>
A few browsers disclose the user's email address in certain situations, such
If you have problems with a site, you will have to adjust your configuration
accordingly. Cookies are probably the most likely adjustment that may
be required, but by no means the only one.
-
</para>
</sect2>
<sect2 renderas="sect3" id="seealso">
<title>Where can I find more information about <application>Privoxy</application>
and related issues?</title>
-
-<!--
- Include seealso.sgml
--->
-
+<!-- Include seealso.sgml boilerplate: -->
&seealso;
+<!-- end boilerplate -->
<!--
<para>
</sect2>
-<sect2 renderas="sect3" id="bugs">
-<title>Where can I get help? Report bugs? Feature Requests? Etc?</title>
-<para>
- Feedback is encouraged, whether good, bad or ugly. Please see the contact
- page in the <ulink url="../user-manual/contact.html">user-manual</ulink> for
- details.
-
-</para>
-
-</sect2>
-
<sect2 renderas="sect3">
<title id="time">What time is it?</title>
<para>
</sect1>
-->
-<!-- ~~~~~ New section ~~~~~ -->
-<!--
+ <!-- ~~~~~ New section ~~~~~ -->
+ <sect1 id="contact"><title>Contacting the developers, Bug Reporting and Feature Requests</title>
+<!-- Include contacting.sgml -->
+ &contacting;
+<!-- end contacting -->
+ </sect1>
+
+ <!-- ~~~~~ New section ~~~~~ -->
+ <sect1 id="copyright"><title>Copyright and History</title>
+
+<sect2><title>Copyright</title>
+<!-- Include copyright.sgml -->
+ ©right;
+<!-- end -->
+</sect2>
-This is referenced in the doc header already. HB 03/25/02
+<sect2><title>History</title>
+<!-- Include history.sgml -->
+ &history;
+<!-- end -->
+</sect2>
-<sect1 id="contact"><title>Contact the developers</title>
-<para>Please see the user manual for information on how to contact the developers.
-</para>
+ </sect1>
+
+<!-- ~~~~~ New section ~~~~~ -->
+<!--
+<sect1 id="seealso"><title>See also</title>
+-->
+<!-- Include seealso.sgml -->
+<!--
+ &see;
+-->
+<!-- end -->
+<!--
</sect1>
-->
-
<!-- hhmts end -->
<!--
Tue 09/11/01 06:38:14 PM EST: Test SGML doc by Hal Burgiss.
Temple Place - Suite 330, Boston, MA 02111-1307, USA.
$Log: faq.sgml,v $
+Revision 1.50 2002/04/26 05:25:23 hal9
+Mass commit to catch a few scattered fixes.
+
+Revision 1.49 2002/04/12 10:10:18 swa
+version update
+
+Revision 1.48 2002/04/10 18:45:15 swa
+generated
+
+Revision 1.47 2002/04/10 04:05:32 hal9
+More on BML, etc.
+
+Revision 1.45 2002/04/08 22:59:26 hal9
+Version update. Spell chkconfig correctly :)
+
+Revision 1.44 2002/04/07 21:24:29 hal9
+Touch up on name change.
+
+Revision 1.43 2002/04/04 21:59:53 hal9
+Added NT/W2K service/icon situation.
+
+Revision 1.42 2002/04/04 18:46:47 swa
+consistent look. reuse of copyright, history et. al.
+
+Revision 1.41 2002/04/04 06:48:37 hal9
+Structural changes to allow for conditional inclusion/exclusion of content
+based on entity toggles, e.g. 'entity % p-not-stable "INCLUDE"'. And
+definition of internal entities, e.g. 'entity p-version "2.9.13"' that will
+eventually be set by Makefile.
+More boilerplate text for use across multiple docs.
+
Revision 1.40 2002/04/03 04:22:03 hal9
Fixed several typos.