<!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 contacting SYSTEM "contacting.sgml">
+<!entity history SYSTEM "history.sgml">
+<!entity copyright SYSTEM "copyright.sgml">
+<!entity license SYSTEM "license.sgml">
+<!entity p-version "3.0.4">
+<!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 -->
+<!entity my-copy "©"> <!-- kludge for docbook2man -->
]>
<!--
File : $Source: /cvsroot/ijbswa/current/doc/source/faq.sgml,v $
This file belongs into
ijbswa.sourceforge.net:/home/groups/i/ij/ijbswa/htdocs/
- $Id: faq.sgml,v 1.37 2002/04/01 16:24:07 hal9 Exp $
+ $Id: faq.sgml,v 2.15 2006/09/08 23:05:07 hal9 Exp $
+
+ Copyright (C) 2001-2006 Privoxy Developers <developers@privoxy.org>
+ See LICENSE.
+
+ Based partially on the Internet Junkbuster FAQ originally written by and
+ Copyright (C) 1997 Anonymous Coders and Junkbusters Corporation.
+ http://www.junkbusters.com/
+
+ <Qandaset defaultlabel='qanda'>
+ <QandAEntry>
+ <question>
+ <para>
+ How are you?
+ </para>
+ </question>
+ <answer>
+ <para>
+ Fine.
+ </para>
+ </answer>
+ </QandAEntry>
+ </QandASet>
+
+ ========================================================================
+ NOTE: Please read developer-manual/documentation.html before touching
+ this file!
+
+ Please we keep the info in this file as version independent as possible
+ so we only have to maintain one FAQ. Where significant changes are
+ made to Privoxy configuration, please note the change in such a way that
+ it makes sense to both users of older and newer versions.
+ ========================================================================
- Written by and Copyright (C) 2001 the SourceForge
- Privoxy team. http://www.privoxy.org/
-
- Based on the Internet Junkbuster originally written
- by and Copyright (C) 1997 Anonymous Coders and
- Junkbusters Corporation. http://www.junkbusters.com
-
- =============================================================
- IMPORTANT: READ: This document does not use automatic section
- numbering. It is turned off by GNUmakefile to keep the Table
- of contents from being so messy. Sections will need to be
- manually numbered as a consequence.
- =============================================================
-->
-<article id="index">
+<article id="index" class="faq">
<artheader>
<title>Privoxy Frequently Asked Questions</title>
-<pubdate>$Id: faq.sgml,v 1.37 2002/04/01 16:24:07 hal9 Exp $</pubdate>
+<pubdate>
+ <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-2006 by
+ <ulink url="http://www.privoxy.org">Privoxy Developers</ulink>
+ </subscript>
+</pubdate>
+
+<pubdate>$Id: faq.sgml,v 2.15 2006/09/08 23:05:07 hal9 Exp $</pubdate>
+
+<!--
+
+Note: this should generate a separate page, and a live link to it.
+But it doesn't for some mysterious reason. Please leave commented
+unless it can be fixed proper. For the time being, the copyright
+statement will be in copyright.smgl.
+
+Hal.
+
+<legalnotice id="legalnotice">
+ <para>
+ text goes here ........
+ </para>
+</legalnotice>
+
+-->
+<!--
<authorgroup>
<author>
<affiliation>
</affiliation>
</author>
</authorgroup>
-
+-->
<abstract>
<![%dummy;[
<para>
</para>
]]>
<para>
- This FAQ gives users and developers alike answers to frequently asked
- questions about <ulink url="http://www.privoxy.org">Privoxy</ulink>.
+ This FAQ gives quick answers to frequently asked questions about
+ <ulink url="http://www.privoxy.org/">Privoxy</ulink>.
+ It can't and doesn't replace the
+ <ulink url="../user-manual/index.html"><citetitle>User Manual</citetitle></ulink>.
+<!--
+ This works, at least in some situtations:
+ Test: <ulink url="privoxy-user-manual.pdf"><citetitle>User Manual</citetitle></ulink>.
+-->
</para>
-<!--
- Include privoxy.sgml boilerplate:
--->
+<!-- Include privoxy.sgml boilerplate: -->
&p-intro;
+<!-- end boilerplate -->
<para>
+ 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>.
- Please see the Contact section in the <ulink
- url="http://www.privoxy.org/user-manual/contact.html">user-manual</ulink> if
- you want to contact the developers.
+ Please see the <link linkend="contact">Contact section</link> if you want to
+ contact the developers.
</para>
<!-- <para> -->
<!-- ~~~~~ New section ~~~~~ -->
-<sect1 id="intro">
-<title></title>
-<!-- dummy section to force TOC on page by itself -->
-<!-- DO NOT REMOVE! please ;) -->
-<para> </para>
-</sect1>
-<!-- ~~~~~ New section ~~~~~ -->
+<sect1 id="general"><title>General Information</title>
-<sect1 id="general"><title>1. General Information</title>
+<sect2 renderas="sect3" id="newjb"><title>What is this new version of
+<emphasis>Junkbuster</emphasis>?</title>
-<sect2 id="newjb"><title>What is this new version of <application>Privoxy</application>?</title>
- <para>
- The original <application>Internet Junkbuster</application> (tm) is a
- copyrighted product of <ulink url="http://www.junkbusters.com">Junkbusters
- Corporation</ulink>. Development of this effort stopped some time ago as of
- version 2.0.2. Stefan Waldherr started the ijbswa project on <ulink
- url="http://sourceforge.net/projects/ijbswa/">Sourceforge</ulink> to rekindle
- development. Other developers subsequently joined with Stefan, and have
- since added many new features, refinements and enhancements. The result
- of this effort is <application>Privoxy</application>.
- </para>
- <para>
- <application>Privoxy</application> started with the
- <application>Junkbuster 2.0.2</application> code base, but has advanced
- significantly at this point.
- </para>
- <para>
- Please see the <ulink
- url="../user-manual/copyright.html#HISTORY">user-manual</ulink> for more
- information on the history of <application>Junkbuster</application> and
- <application>Privoxy</application>.
- </para>
+<!-- Include history.sgml -->
+ &history;
+<!-- end -->
</sect2>
-<sect2>
-<title id="whyprivoxy">Why <quote>Privoxy</quote>? Why a name change at all?</title>
+<sect2 renderas="sect3">
+<title id="whyprivoxy">Why <quote>Privoxy</quote>? Why change the name from
+Junkbuster at all?</title>
<para>
- <application>Privoxy</application> is the
- <quote><emphasis>Privacy Enhancing Proxy</emphasis></quote>.
+ <ulink url="http://junkbusters.com/">Junkbusters Corporation</ulink>
+ continues to offer their original version of the <application>Internet
+ Junkbuster</application>, so publishing our
+ <application> Junkbuster</application>-derived software under the same name
+ led to confusion.
</para>
<para>
- There are possible legal complications from the continued use of the
- <application>Junkbuster</application> name, which is a trademark of
- <ulink url="http://junkbusters.com">Junkbusters Corporation</ulink>.
- (There are, however, no objections from Junkbusters Corporation to the
+ There are also potential legal complications from the continued use of the
+ <application>Junkbuster</application> name, which is a registered trademark of
+ <ulink url="http://junkbusters.com/">Junkbusters Corporation</ulink>.
+ 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.)
+ share our ideals and goals.
</para>
-
<para>
- The developers also believed that there so many changes from the original
+ The developers also believed that there are so many improvements over 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.
+</para>
+<para>
+ <application>Privoxy</application> is the
+ <quote><emphasis>Privacy Enhancing Proxy</emphasis></quote>. Also, its content
+ modification and junk suppression gives <emphasis>you</emphasis>, the user, more
+ control, more freedom, and allows you to browse your personal and
+ <quote><emphasis>private</emphasis> edition</quote> of the web.
</para>
</sect2>
-<sect2 id="differs"><title>How does <application>Privoxy</application> differ
-from the old <application>Junkbuster?</application></title>
+<sect2 renderas="sect3" id="differs"><title>How does Privoxy differ
+from the old Junkbuster?</title>
<para>
-
<application>Privoxy</application> picks up where
-
<application>Junkbuster</application> left off. All the old features remain.
-
The new <application>Privoxy</application> still blocks ads and banners,
- still manages cookies, and still helps protect your privacy. But, these are
- all enhanced, and many new features have been added, all in the same vein.
+ <application>Privoxy</application> picks up where
+ <application>Junkbuster</application> left off. All the old features remain.
+ The new <application>Privoxy</application> still blocks ads and banners,
+ still manages cookies, and still helps protect your privacy. But, these are
+ all greatly enhanced, and many, many new features have been added, all in the same vein.
</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.
-
- </para>
-</sect2>
+ The configuration has changed significantly as well. This is something that
+ users will notice right off the bat if upgrading from
+ <application>Junkbuster</application> 2.0.x. The <quote>blocklist</quote>
+ <quote>cookielist</quote>, <quote>imagelist</quote> and much more has been
+ combined into the <quote>actions</quote> files, with a completely different
+ syntax. See the <ulink url="../user-manual/whatsnew.html">What's New</ulink>
+ page for the latest updates.
+</para>
+<para>
+ <application>Privoxy</application>'s new features include:
+</para>
-<sect2 id="features"><title>What are some of the new features?</title>
-<!--
-Include newfeatures.sgml
--->
-&newfeatures;
+<!-- Include newfeatures.sgml: -->
+ &newfeatures;
+<!-- end include -->
</sect2>
-<sect2 id="proxymoron"><title>What is a <quote>proxy</quote>? How does
-<application>Privoxy</application> work? </title>
+<sect2 renderas="sect3" id="proxymoron"><title>What is a <quote>proxy</quote>? How does
+Privoxy work? </title>
<para>
- When you connect to a web site with <application>Privoxy</application>,
- you are really connecting to your locally running version of
- <application>Privoxy</application>. <application>Privoxy</application>
- intercepts your requests for the web page, and relays that to the
- <quote>real</quote> web site. The web site sends the HTTP data stream
- back to <application>Privoxy</application>, where
- <application>Privoxy</application> can work its magic before it
- relays this data back to your web browser.
+ A web proxy is a service, based on a software such as <application>Privoxy</application>,
+ that clients (i.e. browsers) can use instead of connecting directly to the web
+ servers on the Internet. The clients then ask the proxy to fetch the objects
+ they need (web pages, images, movies etc) on their behalf, and when the proxy
+ has done so, it hands the results back to the client.
</para>
-
<para>
- Since <application>Privoxy</application> sits between you and the
- WWW, it is in a position to intercept and completely manage all web traffic and
- HTTP content before it gets to your browser.
- <application>Privoxy</application> uses various programming methods to do
- this, all of which is under your control via the various configuration
- files and options.
+ There are many reasons to use web proxies, such as security (firewalling),
+ efficiency (caching) and others, and there are just as many different proxies
+ to accommodate those needs.
</para>
-
<para>
- There are many kinds of proxies. <application>Privoxy</application> best
- fits the <quote>filtering proxy</quote> category.
+ <application>Privoxy</application> is a proxy that is primarily focused on privacy
+ protection, junk elimination and freeing the user from restrictions placed on his
+ activities. Sitting between your browser(s) and the Internet,
+ it is in a perfect position to filter outbound personal information that your
+ browser is leaking, as well as inbound junk. It uses a variety of techniques to do
+ this, all of which are under your control via the various configuration
+ files and options.
</para>
-
</sect2>
-<sect2>
-<title id="knows">How does <application>Privoxy</application> know what is
+<sect2 renderas="sect3" id="whatsanad">
+<title id="knows">How does Privoxy know what is
an ad, and what is not?</title>
<para>
- <application>Privoxy</application> processes all the raw content of every
- web page. So it reads everything on each page. It then compares this to the
- rules as set up in the configuration files, and looks for any matches to
- these rules. <application>Privoxy</application> makes heavy use of
- <quote>regular expressions</quote>. (If you are not familiar with regular
- expressions, it is explained briefly in <ulink
- url="../user-manual/appendix.html">the user manual</ulink>.) Regular
- expressions facilitate matching of one text string against another, using
- wildcards to build complex patterns. So <application>Privoxy</application>
- will typically look for URLs and other content that match certain key words
- and expressions as defined in the configuration files. For instance a URL
- that contains <quote>/banners</quote>, has a high probability of containing
- ad banners, and thus would be a prime candidate to have a matching rule.
+ <application>Privoxy</application>'s approach to blocking ads is twofold:
+</para>
+<para>
+ First, there are certain patterns in the <emphasis>locations</emphasis> (URLs)
+ of banner images. This applies to both the path (you wouldn't guess how many
+ web sites serve their banners from a directory called <quote>banners</quote>!)
+ and the host (blocking the big banner hosting services like doublecklick.net
+ already helps a lot). <application>Privoxy</application> takes advantage of this
+ fact by using <ulink url="../user-manual/actions-file.html#AF-PATTERNS">URL
+ patterns</ulink> to sort out and block the requests for banners.
+</para>
+<para>
+ Second, banners tend to come in certain <emphasis>sizes</emphasis>. But you
+ can't tell the size of an image by its URL without downloading it, and if you
+ do, it's too late to save bandwidth. Therefore, <application>Privoxy</application>
+ also inspects the HTML sources of web pages while they are loaded, and replaces
+ references to images with standard banner sizes by dummy references, so that
+ your browser doesn't request them anymore in the first place.
</para>
<para>
- So <application>Privoxy</application> will look for these kinds of obvious
- looking culprits. And also, will use lists of known organizations that
- specialize in ads. Again, using complex patterns to match as many potential
- combinations as possible since there tend to be many, many variations used by
- advertisers, and new ones are being introduced all the time.
+ Both of this involves a certain amount of guesswork and is, of course, freely
+ configurable.
</para>
</sect2>
-<sect2>
-<title id="mistakes">Can <application>Privoxy</application> make mistakes?
+<sect2 renderas="sect3">
+<title id="mistakes">Can Privoxy make mistakes?
This does not sound very scientific.</title>
<para>
- Actually, it's a black art ;-) And yes, it is always possible to have a broad rule
- accidentally block something by mistake. There is a good chance you may run
- into such a situation at some point. It is tricky writing rules to cover
- every conceivable possibility, and not occasionally get false positives.
+ Actually, it's a black art ;-) And yes, it is always possible to have a broad
+ rule accidentally block or change something by mistake. You will almost surely
+ run into such situations at some point. It is tricky writing rules to
+ cover every conceivable possibility, and not occasionally get false positives.
</para>
<para>
<application>Privoxy</application> configuration is very flexible, and
includes tools to help identify these types of situations so they can be
addressed as needed, allowing you to customize your installation.
- (<link linkend="badsite">See the appendix below</link>.)
+ (<link linkend="badsite">See the Troubleshooting section below</link>.)
</para>
</sect2>
-<sect2 id="browsers2"><title>My browser does the same things as
-<application>Privoxy</application>. Why should I use
-<application>Privoxy</application> at all?</title>
+<sect2 renderas="sect3">
+<title id="configornot">Will I have to configure Privoxy
+ before I can use it?</title>
+<para>
+ No, not really. The default installation should give you a good starting
+ point, and block <emphasis>most</emphasis> unwanted content.
+</para>
+<para>
+ But you will certainly run into situations where there are false positives,
+ or ads not being blocked that you may not want to see. In these cases, you
+ would certainly benefit by customizing <application>Privoxy's</application>
+ configuration to more closely match your individual situation. And we would
+ encourage you to do this. This is where the real power of
+ <application>Privoxy</application> lies!
+</para>
+
+</sect2>
+
+<sect2 renderas="sect3" id="browsers2"><title>My browser does the same things as
+Privoxy. Why should I use
+Privoxy at all?</title>
<para>
Modern browsers do indeed have <emphasis>some</emphasis> of the same
functionality as <application>Privoxy</application>. Maybe this is
have a LAN with multiple computers. This way all the configuration
is in one place, and you don't have to maintain a similar configuration
for possibly many browsers.
-
</para>
</sect2>
-<sect2 id="license"><title>Is there is a license or fee? What about a
+<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.
-
- </para>
+ <application>Privoxy</application> is licensed under the <ulink
+ url="http://www.gnu.org/copyleft/gpl.html">GNU General Public License (GPL)</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.
+ </para>
<para>
- There is no warranty of any kind, expressed, implied or otherwise. That is
- something that would cost real money ;-) There is no registration either.
+ There is <emphasis>no warranty</emphasis> of any kind, expressed, implied or otherwise.
+ That is something that would cost real money ;-) There is no registration either.
<application>Privoxy</application> really is <emphasis>free</emphasis>
in every respect!
-
</para>
</sect2>
-<sect2 id="jointeam"><title>I would like to help you, what do I do?</title>
+<sect2 renderas="sect3" id="jointeam"><title>I would like to help you, what can I do?</title>
-<sect3 id="jointeam-money"><title>Money Money Money</title>
+<sect3 renderas="sect4" id="jointeam-work"><title>Would you like to participate?</title>
<para>
- We, of course, welcome donations and use the money for domain registering,
- regular world-wide get-togethers (hahaha). Anyway, we'll soon describe the
- process how to donate money to the team.
+ Well, we <emphasis>always</emphasis> need help. There is something for
+ everybody who wants to help us. We welcome new developers, packagers,
+ testers, documentation writers or really anyone with a desire to help in
+ any way. You <emphasis>DO NOT</emphasis> need to be a
+ <quote>programmer</quote>. There are many other tasks available. In fact,
+ the programmers often can't spend as much time programming because of some
+ of the other, more mundane things that need to be done, like checking the
+ Tracker feedback sections.
+ </para>
+ <para>
+ So first thing, <ulink
+ url="https://sourceforge.net/account/register.php">get an account on SourceForge.net</ulink>
+ and mail your id to the <ulink url="mailto:ijbswa-developers@lists.sourceforge.net">developers
+ mailing list</ulink>. Then, please read the <ulink
+ url="../developer-manual/index.html">Developer's Manual</ulink>, at least
+ the pertinent sections.
+</para>
+<para>
+ Once we have added you to the team, you'll have access to the <ulink
+ url="http://sourceforge.net/cvs/?group_id=11118">CVS repository</ulink>, and
+ together we'll find a suitable task for you.
</para>
</sect3>
-<sect3 id="jointeam-work"><title>You want to work with us?</title>
+<sect3 renderas="sect4" id="jointeam-money"><title>Contribute!</title>
<para>
- Well, helping the team is always a good idea. We welcome new developers,
- RPM gurus or documentation makers. Simply get an account on sourceforge.net
- and mail your id to the developer mailing list. Then read the
- section Quickstart in the <ulink url="http://privoxy.org/developer-manual/quickstart.html">
- Developer's Manual</ulink>.
+ We, of course, welcome donations and could use money for domain registering,
+ buying software to test <application>Privoxy</application> with, and, of course,
+ for regular world-wide get-togethers (hahaha). If you enjoy the software and feel
+ like helping us with a donation, just <ulink
+ url="mailto: ijbswa-developers@lists.sourceforge.net">drop us a note</ulink>.
</para>
+</sect3>
+
+<sect3 renderas="sect4" id="jointeam-software"><title>Software</title>
<para>
- Once we have added you to the team, you'll have write access to the CVS
- repository, and together we'll find a suitable task for you.
+ If you are a vendor of a web-related software like a browser, web server
+ or proxy, and would like us to ensure that <application>Privoxy</application>
+ runs smoothly with your product, you might consider supplying us with a
+ copy or license. We can't, however, guarantee that we will fix all potential
+ compatibility issues as a result.
</para>
</sect3>
+
</sect2>
</sect1>
<!-- ~~~~~ New section ~~~~~ -->
-<sect1 id="installation"><title>2. Installation</title>
+<sect1 id="installation"><title>Installation</title>
-<sect2 id="whichbrowsers">
-<title>Which browsers are supported by <application>Privoxy</application>?</title>
+<sect2 renderas="sect3" id="whichbrowsers">
+<title>Which browsers are supported by Privoxy?</title>
<para>
- Any browser that can be configured to use a <quote>proxy</quote>, which
- should be virtually all browsers. Direct browser support is not necessary
- since <application>Privoxy</application> runs as a separate application and
- just exchanges standard HTML data with your browser, just like a web server
+ Any browser that can be configured to use a proxy, which
+ should be virtually all browsers, including
+ <application>Firefox</application>, <application>Internet
+ Explorer</application>, and <application>Opera</application> among others.
+ Direct browser support is not an absolute requirement since
+ <application>Privoxy</application> runs as a separate application and talks
+ to the browser in the standardized HTTP protocol, just like a web server
does.
</para>
</sect2>
-<sect2 id="whichos">
+<sect2 renderas="sect3" id="whichos">
<title>Which operating systems are supported?</title>
<!--
Include supported.sgml here:
&supported;
</sect2>
-<sect2 id="newinstall"><title>Can I install
- <application>Privoxy</application> over <application>Junkbuster</application>?</title>
+<sect2 renderas="sect3" id="email-client">
+<title>Can I use Privoxy with my email client?</title>
+<para>
+ As long as there is some way to set a HTTP proxy for the client, then yes,
+ any application can be used, whether it is strictly speaking a
+ <quote>browser</quote> or not. Though this may not be the best approach for
+ dealing with some of the common abuses of HTML in email. See <link
+ linkend="outlook">How can I configure <application>Privoxy</application>
+ with <application>Outlook Express</application>?</link> below for more on
+ this.
+</para>
+<para>
+ Be aware that HTML email presents a number of unique security and privacy
+ related issues, that can require advanced skills to overcome. The developers
+ recommend using email clients that can be configured to convert HTML to plain
+ text for these reasons.
+</para>
+</sect2>
+
+<sect2 renderas="sect3" id="newinstall"><title>Can I install
+ Privoxy over Junkbuster?</title>
<para>
- We recommend you uninstall <application>Junkbuster</application>
+ We recommend you un
-install <application>Junkbuster</application>
first to minimize conflicts and confusion. You may want to
save your old configuration files for future reference. The configuration
- is substantially changed.
- </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!]
+ files and syntax have substantially changed, so you will need to manually
+ port your old patterns. See the <ulink url="../user-manual/upgradersnote.html">note
+ to upgraders</ulink> and <ulink url="../user-manual/installation.html">installation
+ chapter</ulink> in the <ulink url="../user-manual/index.html">user manual</ulink>
+ for details.
</para>
<para>
- Note: Some installers may automatically uninstall
+ Note: Some installers may automatically un-install
<application>Junkbuster</application>, if present!
</para>
</sect2>
-<sect2>
-<title id="firststep">I just installed <application>Privoxy</application>. Is there anything
+<sect2 renderas="sect3">
+<title id="firststep">I just installed Privoxy. Is there anything
special I have to do now?</title>
<para>
All browsers must be told to use <application>Privoxy</application>
as a proxy by specifying the correct proxy address and port number
in the appropriate configuration area for the browser. See below.
- Also, you should flush your browser's memory and disk cache to get rid of any
- cached items.
+ You should also flush your browser's memory and disk cache to get rid of any
+ cached junk items, and remove any stored cookies.
</para>
</sect2>
-<sect2 id="localhost"><title>What is the proxy address of <application>Privoxy</application>?</title>
+<sect2 renderas="sect3" id="localhost"><title>What is the proxy address of Privoxy?</title>
<para>
If you set up the <application>Privoxy</application> to run on
the computer you browse from (rather than your ISP's server or some
- networked computer on a LAN), the proxy will be on <quote>localhost</quote>
- (which is the special name used by every computer on the Internet to refer
- to itself) and the port will be 8118 (unless you have <application>Privoxy</application> to run on a different port with the
- <emphasis>listen-address</emphasis> config option).
+ networked computer on a LAN), the proxy will be on <literal>127.0.0.1</literal>
+ (sometimes referred to as <quote>localhost</quote>,
+ which is the special name used by every computer on the Internet to refer
+ to itself) and the port will be 8118 (unless you have <application>Privoxy</application>
+ to run on a different port with the <ulink
+ url="../user-manual/config.html#LISTEN-ADDRESS">listen-address</ulink> config option).
</para>
<para>
When configuring your browser's proxy settings you typically enter
- the word <quote>localhost</quote> in the boxes next to <quote>HTTP</quote>
- and <quote>Secure</quote> (HTTPS) and then the number <quote>8118</quote>
- for <quote>port</quote>. This tells your browser to send all web
- requests to <application>Privoxy</application> instead of directly to the
- Internet.
+ the word <quote>localhost</quote> or the IP address <quote>127.0.0.1</quote>
+ in the boxes next to <quote>HTTP</quote> and <quote>Secure</quote> (HTTPS) and
+ then the number <quote>8118</quote> for <quote>port</quote>.
+ This tells your browser to send all web requests to <application>Privoxy</application>
+ instead of directly to the Internet.
</para>
<para>
<application>Privoxy</application> can also be used to proxy for
a Local Area Network. In this case, your would enter either the IP
address of the LAN host where <application>Privoxy</application>
is running, or the equivalent hostname. Port assignment would be
- same as above.
+ same as above. Note that <application>Privoxy</application> doesn't
+ listen on any LAN interfaces by default.
</para>
<para>
<application>Privoxy</application> does not currently handle
- protocols such as FTP, SMTP, IM, IRC, ICQ, or other Internet
- protocols.
+ any other protocols such as FTP, SMTP, IM, IRC, ICQ, etc. Be sure that
+ proxying any of these other protocols is not activated.
</para>
</sect2>
-<sect2>
-<title id="nothing">I just installed <application>Privoxy</application>, and nothing is happening.
+<sect2 renderas="sect3" id="nothing">
+<title>I just installed Privoxy, and nothing is happening.
All the ads are there. What's wrong?</title>
<para>
the browser's caches to force a full re-reading of pages. You can verify
that <application>Privoxy</application> is running, and your browser
is correctly configured by entering the special URL:
- <ulink url="http://p.p/">http://p.p/</ulink>. This should give you
- a banner that says <quote>This is Privoxy</quote> and
- access to <application>Privoxy's</application> internal configuration.
- If you see this, then you are good to go. If not, the browser or
- <application>Privoxy</application> are not set up correctly.
+ <ulink url="http://p.p/">http://p.p/</ulink>.
+ <!-- Use http://p.p/ instead of http://config.privoxy.org/ here because
+ of potential redirect caching problem (see next Q). -->
+ This should take you to a page titled <quote>This is Privoxy..</quote> with
+ access to <application>Privoxy's</application> internal configuration.
+ If you see this, then you are good to go. If you receive a page saying
+ <quote>Privoxy is not running</quote>, then the browser is not set up to use
+ your <application>Privoxy</application> installation.
+ If you receive anything else (probably nothing at all), it could either
+ be that the browser is not set up correctly, or that
+ <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
+ on starting <application>Privoxy</application></ulink> in the
+ <ulink url="http://www.privoxy.org/user-manual/">user manual</ulink>.
+</para>
+
+</sect2>
+
+<sect2 renderas="sect3" id="notused">
+<title>I get a <quote>Privoxy is not being used</quote> dummy page although
+Privoxy is running and being used.</title>
+<para>
+ 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
+ on starting <application>Privoxy</application></ulink> in the
+ <ulink url="http://www.privoxy.org/user-manual/">user manual</ulink>.
+</para>
+
+<para>
+ Now if <ulink url="http://p.p/">http://p.p/</ulink> works for you, but
+ other parts of <application>Privoxy</application>'s web interface show
+ the dummy page, your browser has cached a redirection it encountered before
+ <application>Privoxy</application> was being used. You need to clear your
+ browser's cache. Note that shift-reloading the dummy page won't help, since
+ that'll only refresh the dummy page, not the redirection that lead you there.
</para>
+<para>
+ The procedure for clearing the cache varies from browser to browser. For
+ example, <application>Mozilla/Netscape</application> users would click
+ <guibutton>Edit</guibutton> --> <guibutton>Preferences</guibutton> -->
+ <guibutton>Advanced</guibutton> --> <guibutton>Cache</guibutton> and
+ then click both <quote><guibutton>Clear Memory Cache</guibutton></quote>
+ and <quote><guibutton>Clear Disk Cache</guibutton></quote>.
+ And, <application>Firefox</application> users would click
+ <guibutton>Tools</guibutton> --> <guibutton>Options</guibutton> -->
+ <guibutton>Privacy</guibutton> --> <guibutton>Cache</guibutton> and
+ then click <quote><guibutton>Clear Cache Now</guibutton></quote>.
+
+</para>
</sect2>
</sect1>
<!-- ~~~~~ New section ~~~~~ -->
-<sect1 id="configuration"><title>3. Configuration</title>
+<sect1 id="configuration"><title>Configuration</title>
+
+<sect2 renderas="sect3" id="getupdates"><title>Where can I get updated Actions Files?</title>
+ <para>
+ Based on your feedback and the continuing development, updated actions files will be
+ made available 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>.
+ </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
+ to our announce mailing list</ulink>, ijbswa-announce@lists.sourceforge.net.
+ </para>
+
+</sect2>
-<sect2 id="newconfig"><title>Can I use my old config files?</title>
+<sect2 renderas="sect3" id="newconfig"><title>Can I use my old config files?</title>
<para>
- There are major changes to <application>Junkbuster</application>,
- <application>Privoxy</application>, configuration from version 2.0.x to
- 2.9.x and later. Most of the older files will not work at all. This is
- especially true of <filename>blocklist</filename>. If this is the case, you
- will need to re-enter your old data into the new configuration structure.
- This is probably also a good recommendation even if upgrading from 2.9.x to
- 3.x since there were many minor changes along the way.
+ The syntax and purpose of configuration files has remained the same
+ throughout the 3.x series. Although each release contains updated,
+ <quote>improved</quote> versions and it is recommended to use the newer
+ configuration files.
+ </para>
+ <para>
+ But all configuration files have substantially
+ changed from the <application>Junkbuster</application> days, and early
+ versions of <application>Privoxy 2.x</application>. The old files, like
+ <filename>blocklist</filename> will not work at all.
+ </para>
+ <para>
+ Refer to the <ulink url="../user-manual/whatsnew.html">What's New</ulink>
+ page for information on configuration changes that may occur from one release to another.
</para>
</sect2>
-<sect2>
+<sect2 renderas="sect3">
<title id="actionsfile">What is an <quote>actions</quote> file?</title>
<para>
- <quote>actions</quote> files are where various actions that
- <application>Privoxy</application> might take, are configured.
- Typically, you would define a set of default actions that apply
- to all URLs, then add exceptions to these defaults.
+ <ulink url="../user-manual/actions-file.html">Actions files</ulink>
+ are where various <ulink url="../user-manual/actions-file.html#ACTIONS">actions</ulink>
+ that <application>Privoxy</application> could take while processing a certain
+ request, are configured. Typically, you would define a set of default actions
+ that apply to all URLs, then add exceptions to these defaults where needed.
+ There is a wide array of actions available that give the user a high degree
+ of control and flexibility on how to process each and every web page.
</para>
<para>
- Actions can be defined on a per site basis, or for groups of sites. Actions
- can also be grouped together and then applied to one or more sites. There
- are many possible actions that might apply to any given site. As an example,
- if we are blocking cookies as one of our default
- <application>actions</application>, but need to accept cookies from a given
- site, we would define this in our <quote>actions</quote> file.
-
-</para>
-
-<para>
- <application>Privoxy</application> comes with several default
- <application>actions</application> files, with varying degrees
- of filtering and blocking, as starting points for your own
- configuration (see below).
+ Actions can be defined on a <ulink
+ url="../user-manual/actions-file.html#AF-PATTERNS">URL pattern</ulink> 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 cookies 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>.
</para>
</sect2>
-<sect2 id="actionss">
-<title>The <quote>actions</quote>concept confuses me. Please list
+<sect2 renderas="sect3" id="actionss">
+<title>The <quote>actions</quote> concept confuses me. Please list
some of these <quote>actions</quote>.</title>
<para>
- These are all explained in the
- <ulink url="../user-manual/configuration.html#ACTIONSFILE">user-manual</ulink>.
- Please refer to that.
+ For a comprehensive discussion of the actions concept, please refer
+ to the <ulink url="../user-manual/actions-file.html">actions file
+ chapter</ulink> in the <ulink url="../user-manual/index.html">user
+ manual</ulink>. It includes a <ulink
+ url="../user-manual/actions-file.html#ACTIONS">list of all actions</ulink>
+ and an <ulink url="../user-manual/actions-file.html#ACT-EXAMPLES">actions
+ file tutorial</ulink> to get you started.
</para>
</sect2>
-<sect2>
+<sect2 renderas="sect3">
<title id="actconfig">How are actions files configured? What is the easiest
way to do this?</title>
<para>
- The easiest way to do this, is to access <application>Privoxy</application>
- with your web browser at <ulink url="http://p.p/">http://p.p/</ulink>,
- and then select
- "<ulink url="http://config.privoxy.org">Edit the actions list</ulink>"
- from the selection list. You can also do this by editing the appropriate
- file with a text editor.
+ Actions files are just text files in a special syntax and can be edited
+ with a text editor. But probably the easiest way is to access
+ <application>Privoxy</application>'s user interface with your web browser
+ at <ulink url="http://config.privoxy.org/">http://config.privoxy.org/</ulink>
+ (Shortcut: <ulink url="http://p.p/">http://p.p/</ulink>) and then select
+ <quote><ulink url="http://config.privoxy.org/show-status">View &
+ change the current configuration</ulink></quote> from the menu.
</para>
+</sect2>
+
+<sect2 renderas="sect3">
+<title>There are several different <quote>actions</quote> files. What are
+the differences?</title>
<para>
- Please see the
- <ulink
- url="../user-manual/configuration.html#ACTIONSFILE">user-manual</ulink> for a
- detailed explanation of these and other configuration files, and their
- various options and syntax.
+ As of <application>Privoxy</application> v2.9.15, three actions files
+ are being included, to be used for
+ different purposes: These are
+ <filename>default.action</filename>, the <quote>main</quote> actions file
+ which is actively maintained by the <application>Privoxy</application>
+ developers, <filename>user.action</filename>, where users are encouraged
+ to make their private customizations, and <filename>standard.action</filename>,
+ which is for internal <application>Privoxy</application> use only.
+ Please see <ulink url="../user-manual/actions-file.html">the actions chapter</ulink>
+ in the <ulink url="../user-manual/index.html">user manual</ulink> for a more
+ detailed explanation.
</para>
-</sect2>
+<para>
+ Earlier versions included three different versions of the
+ <filename>default.action</filename> file. The new scheme allows for
+ greater flexibility of local configuration, and for browser based
+ selection of pre-defined <quote>aggressiveness</quote> levels.
+</para>
-<!--
-FIXME: Commenting these out until we have some data there. HB 03/17/02.
+</sect2>
-<sect2 id="yahoo"><title>How can I make my Yahoo account work?</title>
+<sect2 renderas="sect3" id="yahoo"><title>How can I make my Yahoo/Hotmail/Gmail account work?</title>
<para>
- Fillme.
+ The default configuration shouldn't impact the usability of any of these services.
+ It will, however, make all cookies 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 <filename>user.action</filename> file. An example for yahoo might
+ look like:
+ </para>
+ <para>
+ <screen># Allow all cookies for Yahoo login:
+#
+{ -<ulink url="../user-manual/actions-file.html#CRUNCH-INCOMING-COOKIES">crunch-incoming-cookies</ulink> -<ulink url="../user-manual/actions-file.html#CRUNCH-OUTGOING-COOKIES">crunch-outgoing-cookies</ulink> -<ulink url="../user-manual/actions-file.html#SESSION-COOKIES-ONLY">session-cookies-only</ulink> }
+.login.yahoo.com</screen>
</para>
-</sect2>
-<sect2 id="hotmail"> <title>How can I make my Hotmail account work?</title>
- <para>
- Fillme.
- </para>
</sect2>
-<sect2 id="gmx"> <title>How can I make my GMX account work?</title>
+<sect2 renderas="sect3" id="configfiles"> <title>What's the difference between the
+<quote>Cautious</quote>, <quote>Medium</quote> and <quote>Adventuresome</quote> defaults?</title>
<para>
- Fillme.
+ Configuring <application>Privoxy</application> is not entirely trivial. To
+ help you get started, we provide you with three different default action
+ <quote>profiles</quote> in the web based actions file editor at <ulink
+ url="http://config.privoxy.org/show-status">http://config.privoxy.org/show-status</ulink>.
+ See the <ulink url="../user-manual/actions-file.html"><citetitle>User
+ Manual</citetitle></ulink> for a list of actions, and how the default
+ profiles are set.
</para>
+
+<para>
+ Where the defaults are likely to break some sites, exceptions for
+ known popular <quote>problem</quote> sites are included, but in
+ general, the more aggressive your default settings are, the more exceptions
+ you will have to make later. See the <ulink
+ url="../user-manual/index.html"><citetitle>User Manual</citetitle></ulink>
+ for a more detailed discussion.
+</para>
+
+<para>
+ It should be noted that the <quote>Adventuresome</quote> profile (formerly known
+ as the <quote>Advanced</quote> profile) is not only more
+ aggressive, but also includes fun and, extreme usage of most of
+ <application>Privoxy's</application> features. Use at your own risk!
+</para>
+
</sect2>
--->
-<sect2 id="configfiles"> <title>What are the differences between
-intermediate.action, basic.action, etc.?</title>
- <para>
-Configuring <application>Privoxy</application> is not easy. To help you get
-started, we provide you with three different default configurations. The
-following table shows you, which features are enabled in each configuration.
- </para>
- <para>
-<table frame=all><title>Default Configurations</title>
-<tgroup cols=5 align=left colsep=1 rowsep=1>
-<colspec colname=c1>
-<colspec colname=c2>
-<colspec colname=c3>
-<colspec colname=c4>
-<colspec colname=c5>
-<thead>
-<row>
- <entry>Feature</entry>
- <entry>default.action</entry>
- <entry>basic.action</entry>
- <entry>intermediate.action</entry>
- <entry>advanced.action</entry>
-</row>
-</thead>
-
-<!-- <tfoot> -->
-<!-- <row> -->
-<!-- <entry>f1</entry> -->
-<!-- <entry>f2</entry> -->
-<!-- <entry>f3</entry> -->
-<!-- <entry>f4</entry> -->
-<!-- <entry>f5</entry> -->
-<!-- </row> -->
-<!-- </tfoot> -->
-
-<tbody>
-<!-- new row -->
-<row>
- <entry>ad-filtering</entry>
- <entry>?</entry>
- <entry>x</entry>
- <entry>x</entry>
- <entry>x</entry>
-</row>
-<!-- new row -->
-<row>
- <entry>blank image</entry>
- <entry>?</entry>
- <entry>x</entry>
- <entry>x</entry>
- <entry>x</entry>
-</row>
-<!-- new row -->
-<row>
- <entry>de-animate GIFs</entry>
- <entry>?</entry>
- <entry>x</entry>
- <entry>x</entry>
- <entry>x</entry>
-</row>
-<!-- new row -->
-<row>
- <entry>referer forging</entry>
- <entry>?</entry>
- <entry>x</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>
- <entry>x</entry>
-</row>
-<!-- new row -->
-<row>
- <entry>no-popup windows</entry>
- <entry>?</entry>
- <entry></entry>
- <entry>x</entry>
- <entry>x</entry>
-</row>
-<!-- new row -->
-<row>
- <entry>fast redirects</entry>
- <entry>?</entry>
- <entry></entry>
- <entry>x</entry>
- <entry>x</entry>
-</row>
-<!-- new row -->
-<row>
- <entry>hide-referrer</entry>
- <entry>?</entry>
- <entry></entry>
- <entry>x</entry>
- <entry>x</entry>
-</row>
-<!-- new row -->
-<row>
- <entry>hide-useragent</entry>
- <entry>?</entry>
- <entry></entry>
- <entry>x</entry>
- <entry>x</entry>
-</row>
-<!-- new row -->
-<row>
- <entry>content-modification</entry>
- <entry>?</entry>
- <entry></entry>
- <entry></entry>
- <entry>x</entry>
-</row>
-<!-- new row -->
-<row>
- <entry>feature-x</entry>
- <entry>?</entry>
- <entry></entry>
- <entry></entry>
- <entry></entry>
-</row>
-<!-- new row -->
-<row>
- <entry>feature-y</entry>
- <entry>?</entry>
- <entry></entry>
- <entry></entry>
- <entry></entry>
-</row>
-<!-- new row -->
-<row>
- <entry>feature-z</entry>
- <entry>?</entry>
- <entry></entry>
- <entry></entry>
- <entry></entry>
-</row>
-<!-- finish -->
-</tbody>
-</tgroup>
-</table>
-</para>
-</sect2>
-
-<sect2 id="browseconfig"> <title>Why can I change the configuration with a
-browser? Does that not raise security issues?</title>
+<sect2 renderas="sect3" id="browseconfig"> <title>Why can I change the configuration
+with a browser? Does that not raise security issues?</title>
<para>
-What I don't understand, is how I can browser edit the config file as a
-regular user, while the whole /etc/privoxy hierarchy belongs to the user
-"privoxy", with only 644 perms.
+ It may seem strange that regular users can edit the config files with their
+ browsers, although the whole <filename>/etc/privoxy</filename> hierarchy
+ belongs to the user <quote>privoxy</quote>, with only 644 permissions.
</para>
<para>
-When you use the browser-based editor, <application>Privoxy</application>
-itself is writing to the config files. Because
-<application>Privoxy</application> is running as the user "privoxy", it can
-update the config files.
+
When you use the browser-based editor, <application>Privoxy</application>
+ itself is writing to the config files. Because
+ <application>Privoxy</application> is running as the user <quote>privoxy</quote>,
+ it can update the config files.
</para>
<para>
-If you don't like this, setting "enable-edit-actions 0" in the config file
-will disable the browser-based editor. If you're that paranoid, you should
-also consider setting "enable-remote-toggle 0" to prevent browser-based
-enabling/disabling of <application>Privoxy</application>.
+ If you run <application>Privoxy</application> for multiple untrusted users (e.g. in
+ a LAN), you will probably want to turn the web-based editor and remote toggle
+ features off by setting <quote><literal><ulink
+ url="../user-manual/config.html#ENABLE-EDIT-ACTIONS">enable-edit-actions</ulink>
+ 0</literal></quote> and <quote><literal><ulink
+ url="../user-manual/config.html#ENABLE-REMOTE-TOGGLE">enable-remote-toggle</ulink>
+ 0</literal></quote> in the <ulink url="../user-manual/config.html">main configuration file</ulink>.
</para>
<para>
-Note that normally only local users can connect to <application>Privoxy</application>, so this is not
-(normally) a security problem.
+ Note that in the default configuration, only local users (i.e. those on
+ <quote>localhost</quote>) can connect to <application>Privoxy</application>,
+ so this is not (normally) a security problem.
</para>
</sect2>
-<sect2>
-<title id="filterfile">What is <quote>default.filter</quote>?</title>
+<sect2 renderas="sect3">
+<title id="filterfile">What is the <filename>default.filter</filename> file? What is a <quote>filter</quote>?</title>
<para>
- The <quote>default.filter</quote> file is used to <quote>filter</quote> any
- web page content. By <quote>filtering</quote> we mean it can modify, remove,
- or change <emphasis>anything</emphasis> on the page, including HTML tags, and
- JavaScript. Regular expressions are used to accomplish this, and operate
- on a line by line basis. This is potentially a very powerful feature, but
- requires some expertise.
+ The <ulink url="../user-manual/filter-file.html"><filename>default.filter</filename></ulink>
+ file is where <emphasis>filters</emphasis> as supplied by the developers are defined.
+ Filters are a special subset of actions that can be used to modify or
+ remove, web page content on the fly. Filters apply to <emphasis>anything</emphasis>
+ in the page source (and optionally both client and server headers), including
+ HTML tags, and JavaScript. Regular expressions are used to accomplish this.
+ There are a number of pre-defined filters to deal with common annoyances. The
+ filters are only defined here, to invoke them, you need to use the
+ <ulink
+ url="../user-manual/actions-file.html#FILTER"><literal>filter</literal>
+ action</ulink> in one of the actions files. Filtering is automatically
+ disabled for inappropriate MIME types.
</para>
<para>
If you are familiar with regular expressions, and HTML, you can look at
- the provided <filename>default.filter</filename> with a text editor and see
- some of things it can be used for.
+ the provided <filename>default.filter</filename> with a text editor and define
+ your own filters. This is potentially a very powerful feature, but
+ requires some expertise in both regular expressions and HTML/HTTP. You should
+ place any modifications to the default filters, or any new ones you create
+ in a separate file, such as <filename>user.filter</filename>, so they won't
+ be overwritten during upgrades. The ability to define multiple filter files
+ in <filename>config</filename> is a new feature as of v. 3.0.4.
</para>
<para>
- Presently, there is no GUI editor option for this part of the configuration,
- but you can disable/enable various sections of the included default
- file with the <quote>Actions List Editor</quote> from your browser.
+ There is no GUI editor option for this part of the configuration,
+ but you can disable/enable the various pre-defined filters of the included
+ <filename>default.filter</filename> file with the <ulink
+ url="http://config.privoxy.org/show-status">web-based actions file editor</ulink>.
</para>
</sect2>
-<sect2>
-<title id="lanconfig">How can I set up <application>Privoxy</application> to act as a proxy for my
+<sect2 renderas="sect3">
+<title id="lanconfig">How can I set up Privoxy to act as a proxy for my
LAN?</title>
<para>
By default, <application>Privoxy</application> only responds to requests
- from localhost. To have it act as a server for a network, this needs to be
- changed in the main config file where the <application>Privoxy</application>
- configuration is located. In that file is a <quote>listen-address</quote>
- option. It may be commented out with a <quote>#</quote> symbol. Make sure
- it is uncommented, and assign it the address of the LAN gateway interface,
- and port number to use:
+ from <literal>127.0.0.1</literal> (localhost). To have it act as a server for
+ a network, this needs to be changed in the <ulink
+ url="../user-manual/config.html">main configuration file</ulink>. Look for
+ the <literal><ulink
+ url="../user-manual/config.html#LISTEN-ADDRESS">listen-address</ulink></literal>
+ option, which may be commented out with a <quote>#</quote> symbol. Make sure
+ it is uncommented, and assign it the address of the LAN gateway interface,
+ and port number to use. Assuming your LAN address is 192.168.1.1 and you
+ wish to run <application>Privoxy</application> on port 8118, this line
+ should look like:
</para>
<para>
<screen>
- listen-address 192.168.1.1:8118
- </screen>
+ listen-address 192.168.1.1:8118</screen>
</para>
<para>
all browsers on the network then to use this address and port number.
</para>
-</sect2>
+<para>
+ Alternately, you can have <application>Privoxy</application> listen on
+ all available interfaces:
+</para>
+
+<para>
+ <screen>
+ listen-address :8118</screen>
+</para>
+<para>
+ And then use <application>Privoxy's</application>
+ <ulink
+ url="../user-manual/config.html#PERMIT-ACCESS">permit-access</ulink>
+ feature to limit connections. A firewall in this situation is recommended
+ as well.
+</para>
-<sect2>
-<title id="noseeum">Instead of ads, now I get a checkerboard pattern. I don't want to see anything.</title>
<para>
- This is a configuration option for images that
- <application>Privoxy</application> is stopping. You have the choice <!-- of
- the --> <!-- <application>Privoxy</application> logo, --> of a checkerboard
- pattern, a transparent 1x1 GIF image (aka <quote>blank</quote>), or a custom
- URL of your choice. Note that to fit this category, the URL must match both
- the <quote>+image</quote> and <quote>+block</quote> actions.
+ The above steps should be the same for any TCP network, regardless of
+ operating system.
</para>
<para>
- If you want to see nothing, then change the <quote>+image-blocker</quote>
- action to <quote>+image-blocker{blank}</quote>. This can be done from the
- <quote>Edit Actions List</quote> selection at <ulink
- url="http://p.p/">http://p.p/</ulink>. Or by hand editing the appropriate
- actions file. This will only effect what is defined as <quote>images</quote>
- though. Also, some URLs that generate the bright red <quote>Blocked</quote>
- banner, can be moved to the <quote>+image-blocker</quote> section for the
- same reason, but there are some limits and risks to this (see below).
+ If you run <application>Privoxy</application> on a LAN with untrusted users,
+ we recommend that you double-check the <ulink
+ url="../user-manual/config.html#ACCESS-CONTROL">access control and security</ulink>
+ options!
</para>
</sect2>
-<sect2>
+<sect2 renderas="sect3">
+<title id="noseeum">Instead of ads, now I get a checkerboard pattern. I don't want to see anything.</title>
+<para>
+ The replacement for blocked images can be controlled with the <ulink
+ url="../user-manual/actions-file.html#SET-IMAGE-BLOCKER"><literal>set-image-blocker</literal>
+ action</ulink>. You have the choice of a checkerboard pattern, a transparent 1x1 GIF
+ image (aka <quote>blank</quote>), or a redirect to a custom image of your choice.
+ Note that this choice only has effect for images which are blocked as images, i.e.
+ whose URLs match both a <literal><ulink
+ url="../user-manual/actions-file.html#HANDLE-AS-IMAGE">handle-as-image</ulink></literal>
+ <emphasis>and</emphasis> <literal><ulink
+ url="../user-manual/actions-file.html#BLOCK">block</ulink></literal> action.
+</para>
+<para>
+ If you want to see nothing, then change the <ulink
+ url="../user-manual/actions-file.html#SET-IMAGE-BLOCKER"><literal>set-image-blocker</literal>
+ action</ulink> to <quote>blank</quote>. This can be done by editing the
+ <filename>default.action</filename> file, or trough the <ulink
+ url="http://config.privoxy.org/show-status">web-based actions file editor</ulink>.
+</para>
+
+</sect2>
+
+<sect2 renderas="sect3">
<title id="whyseeum">Why would anybody want to see a checkerboard pattern?</title>
<para>
- This can be helpful for troubleshooting problems. It might also be good
- for anyone new to <application>Privoxy</application> so that they can
- see if their favorite pages are displaying correctly, and
- <application>Privoxy</application> is not inadvertently removing something
- important.
+ Remember that <link linkend="whatsanad">telling which image is an ad and which
+ isn't</link>, is mostly guesswork. While we hope that the standard configuration
+ is rather smart, it can and will make errors. The checkerboard image is visually
+ decent, but it shows you that and where images were blocked, which can be very
+ helpful in case some navigation aid or otherwise innocent image was
+ erroneously blocked. Some people might also enjoy seeing how many banners
+ they <emphasis>don't</emphasis> have to see..
</para>
</sect2>
-<sect2>
-<title id="blockedisugly">I see large red banners on some pages that say
-<quote>Blocked</quote>. Why and how do I get rid of this?</title>
+<sect2 renderas="sect3">
+<title id="blockedbytext">I see some images being replaced by a text
+instead of the checkerboard image. Why and how do I get rid of this?</title>
+<para>
+ This happens when the banners are not embedded in the HTML code of the
+ page itself, but in separate HTML (sub)documents that are loaded into (i)frames
+ or (i)layers, and these external HTML documents are blocked. Being non-images
+ they get replaced by a substitute HTML page rather than a substitute image,
+ which wouldn't work out technically, since the browser expects and accepts
+ only HTML when it has requested an HTML document.
+</para>
+<para>
+ The substitute page adapts to the available space and shows itself as a
+ miniature two-liner if loaded into small frames, or full-blown with a
+ large red "BLOCKED" banner if space allows.
+</para>
<para>
- These are URLs that match something in one of
- <application>Privoxy's</application> block actions (+block). It is meant
- to be a warning so that you know something has been blocked and an easy way
- for you to see why. These are handled differently than what has been defined
- explicitly as <quote>images</quote> (e.g. ad banners). Depending on the
- URL itself, it is sometimes hard for <application>Privoxy</application> to
- really know whether there is indeed an ad image there or not. And there are
- limitations as to what <application>Privoxy</application> can do to
- <quote>fool</quote> the browser.
+ If you prefer the banners to be blocked by images, you must see to it that
+ the HTML documents in which they are embedded are not blocked. Clicking
+ the <quote>See why</quote> link offered in the substitute page will show
+ you which rule blocked the page. After changing the rule and un-blocking
+ the HTML documents, the browser will try to load the actual banner images
+ and the usual image blocking will (hopefully!) kick in.
</para>
+</sect2>
+
+<sect2 renderas="sect3" id="srvany">
+<title>Can Privoxy run as a service
+on Win2K/NT/XP?</title>
+<para>
+ Yes. Version 3.0.4 introduces full <application>Windows</application> service
+ functionality. See <ulink url="../user-manual/installation.html#installation-pack-win">
+ the User Manual</ulink> for details on how to install and configure
+ <application>Privoxy</application> as a service.
+</para>
<para>
- For instance, if the ad is in a frame, then it is embedded in the separate
- HTML page used for the frame. In this case, you cannot just substitute an
- aribitray image (like we would for a <quote>blank</quote> image), for an HTML
- page. The browser is expecting an HTML page, and that is what it must have
- for frames. So this situation can be a little trickier to deal with, and
- <application>Privoxy</application> will use the <quote>Blocked</quote> page.
+ Earlier 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>,
+ for details, and a sample configuration.
</para>
+</sect2>
+
+
+<sect2 renderas="sect3" id="otherproxy">
+<title>How can I make Privoxy work with other
+proxies like Squid or Tor?</title>
+<para>
+ This can be done and is often useful to combine the benefits of
+ <application>Privoxy</application> with those of a another proxy.
+ See the <ulink
+ url="../user-manual/config.html#FORWARDING">forwarding chapter</ulink>
+ in the <ulink url="../user-manual/index.html">user manual</ulink> which
+ describes how to do this.
+</para>
+</sect2>
+
+<sect2 renderas="sect3" id="port-80">
+<title>Can I just set Privoxy to use port 80
+and thus avoid individual browser configuration?</title>
<para>
- If you want these to be treated as if they were images, so that they can be
- made invisible, you can try moving the offending URL from the
- <quote>+block</quote> section to the <quote>+imageblock</quote> section of
- your actions file. Just be forewarned, if any URL is made
- <quote>invisible</quote>, you may not have any inkling that something has
- been removed from that page, or why. If this approach does not work, then you are
- probably dealing with a frame (or <quote>ilayer</quote>), and the only thing
- that can go there is an HTML page of some sort.
+ No, its more complicated than that. This only works with special kinds
+ of proxies known as <quote>transparent</quote> proxies (see below).
</para>
+
+</sect2>
+
+<sect2 renderas="sect3" id="transparent">
+<title>Can Privoxy run as a <quote>transparent
+</quote> proxy?</title>
<para>
- To deal with this situation, you could modify the
- <quote><filename>block</filename></quote> HTML template that is used by
- <application>Privoxy</application> to display this, and make it something
- more to your liking. Currently, there is no configuration option for this.
- You will have to modify, or create your own page, and use this to replace
- <filename>templates/blocked</filename>, which is what
- <application>Privoxy</application> uses to display the <quote>Blocked</quote>
- page.
+ No, <application>Privoxy</application> currently does not have this ability,
+ though it may be added in a future release. Transparent proxies require
+ special handling of the request headers beyond what
+ <application>Privoxy</application> is now capable of.
</para>
+
<para>
- Another way to deal with this is find why and where
- <application>Privoxy</application> is blocking the frame, and
- diable this. Then let the <quote>+image-blocker</quote> action
- handle the ad that is embedded in the frame's HTML page.
+ Chaining <application>Privoxy</application> behind another proxy that has
+ this ability should work though.
+ See the <ulink
+ url="../user-manual/config.html#FORWARDING">forwarding chapter</ulink>
+ in the <ulink url="../user-manual/index.html">user manual</ulink>. As
+ a transparent proxy to be used for chaining we recommend Transproxy
+ (<ulink url="http://transproxy.sourceforge.net/">http://transproxy.sourceforge.net/</ulink>).
</para>
</sect2>
-<sect2 id="alliseeisred">
-<title>I cannot see all of the <quote>Blocked</quote> page banner. All I
-see is a bright red square.</title>
+<sect2 renderas="sect3" id="outlook">
+<title>How can I configure Privoxy for use with Outlook
+ Express?</title>
<para>
- There is not enough space to fit the entire page. Try right clicking on the
- visible, red portion, and select <quote>Show Frame</quote>, or equivalent.
- This will usually allow you to see the entire Privoxy <quote>Blocked</quote>
- page, and from there you can see just what is being blocked, and why.
+ <application>Outlook Express</application> uses <application>Internet Explorer</application>
+ components to both render HTML, and fetch any HTTP requests that may be embedded in an HTML email.
+ So however you have <application>Privoxy</application> configured to work
+ with IE, this configuration should automatically be shared.
</para>
</sect2>
-<sect2 id="otherproxy">
-<title>How can I make <application>Privoxy</application> work with other
-proxies like <application>Squid</application>?</title>
+<sect2 renderas="sect3" id="outlook-more">
+<title>How can I have separate rules just for HTML mail?</title>
+<para>
+ The short answer is, you can't. <application>Privoxy</application> has no way
+ of knowing which particular application makes a request, so there is no way to
+ distinguish between web pages and HTML mail.
+ <application>Privoxy</application> just blindly proxies all requests. In the
+ case of <application>Outlook Express</application> (see above), OE uses
+ IE anyway, and there is no way for <application>Privoxy</application> to ever
+ be able to distinguish between them (nor could any other proxy type application for
+ that matter).
+</para>
<para>
- This can be done. See the <ulink
- url="../user-manual/configuration.html#FORWARDING">user manual</ulink>,
- which describes how to do this.
+ 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>.
+</para>
+</sect2>
+<sect2 renderas="sect3" id="allow-cookies">
+<title>How can I allow permanent cookies for my trusted sites?</title>
+
+<para>
+ There are several actions that relate to cookies. The default behavior is to
+ allow only <quote>session cookies</quote>, which means the cookies only last
+ for the current browser session. This eliminates most kinds of abuse related
+ to cookies. But there may be cases where we want cookies to last.
</para>
+<para>
+ To disable all cookie actions, so that cookies are allowed unrestricted,
+ both in and out, for <literal>example.com</literal>:
+</para>
+<para>
+ <screen>
+ { -crunch-incoming-cookies -crunch-outgoing-cookies -session-cookies-only -filter{content-cookies} }
+ .example.com</screen>
+</para>
+<para>
+ Place the above in <filename>user.action</filename>. Note some of these may
+ be off by default anyway, so this might be redundant, but there is no harm
+ being explicit in what you want to happen. <filename>user.action</filename>
+ includes an alias for this situation, called
+ <literal>allow-all-cookies</literal>.
+</para>
+</sect2>
+<sect2 renderas="sect3" id="multiples">
+<title>Can I have separate configurations for different users?</title>
+<para>
+ Each instance of <application>Privoxy</application> has its own
+ configuration, including such attributes as the TCP port that it listens on.
+ What you can do is run multiple instances of <application>Privoxy</application>, each with
+ a unique <literal>listen-address</literal> and configuration path, and then
+ each of these can have their own configurations. Think of it as per-port
+ configuration.
+</para>
+<para>
+ Simple enough for a few users, but for large installations, consider having
+ groups of users that might share like configurations.
+</para>
+</sect2>
+
+<sect2 renderas="sect3" id="whitelists">
+<title>Can I set-up Privoxy as a whitelist of
+<quote>good</quote> sites?</title>
+<para>
+ Sure. There are a couple of things you can do for simple whitelisting.
+ Here's one real easy one:
+</para>
+ <screen>
+ ############################################################
+ # Blacklist
+ ############################################################
+ { <ulink url="../user-manual/actions-file.html#BLOCK">+block</ulink> }
+ / # Block *all* URLs
+
+ ############################################################
+ # Whitelist
+ ############################################################
+ { <ulink url="../user-manual/actions-file.html#BLOCK">-block</ulink> }
+ kids.example.com
+ toys.example.com
+ games.example.com</screen>
+<para>
+ This allows access to only those three sites.
+</para>
+<para>
+ A more interesting approach is <application>Privoxy's</application>
+ <literal>trustfile</literal> concept, which incorporates the notion of
+ <quote>trusted referrers</quote>. See the <ulink
+ url="../user-manual/config.html#TRUSTFILE">User Manual Trust</ulink>
+ documentation.
+</para>
+<para>
+ These are fairly simple approaches and are not completely foolproof. There
+ are various other configuration options that should be disabled (described
+ elsewhere here and in <ulink url="../user-manual/">the User Manual</ulink>)
+ so that users can't modify their own configuration and easily circumvent the
+ whitelist.
+</para>
</sect2>
</sect1>
+<!-- ~ End section ~ -->
+
+
<!-- ~~~~~ New section ~~~~~ -->
-<sect1 id="misc"><title>4. Miscellaneous</title>
+<sect1 id="misc"><title>Miscellaneous</title>
-<sect2>
-<title id="slowsme">How much does <application>Privoxy</application> slow my browsing down? This
+<sect2 renderas="sect3">
+<title id="slowsme">How much does Privoxy slow my browsing down? This
has to add extra time to browsing.</title>
<para>
- It should not slow you down any in real terms, and may actually help
- speed things up since ads, banners and other junk are not being displayed.
+ How much of an impact depends on many things, including the CPU of the host
+ system, how aggressive the configuration is, which specific actions are being triggered,
+ the size of the page, etc.
+</para>
+<para>
+ Overall, it should not slow you down any in real terms, and may actually help
+ speed things up since ads, banners and other junk are not typically being displayed.
The actual processing time required by <application>Privoxy</application>
itself for each page, is relatively small in the overall scheme of things,
and happens very quickly. This is typically more than offset by time saved
- not downloading and rendering ad images.
+ not downloading and rendering ad images (if ad blocking is being used).
</para>
<para>
- <quote>Filtering</quote> via the <filename>filterfile</filename>
- mechanism may cause a perceived slowdown, since the entire page is buffered
- before displaying. See below.
+ <quote>Filtering</quote> content via the <literal><ulink
+ url="../user-manual/actions-file.html#FILTER">filter</ulink></literal> or
+ <literal><ulink
+ url="../user-manual/actions-file.html#DEANIMATE-GIFS">deanimate-gifs</ulink></literal>
+ actions will certainly cause a perceived slowdown, since the entire document
+ needs to be buffered before displaying. And on very large documents, there may be
+ some impact. How much depends on the page size, the actual definition of the
+ filter(s), etc. See below. Most other actions have little to no impact on
+ speed.
</para>
</sect2>
-
-<sect2 id="loadingtimes"><title>I noticed considerable
+<sect2 renderas="sect3" id="loadingtimes"><title>I notice considerable
delays in page requests compared to the old Junkbuster. What's wrong?</title>
<para>
-Using the default filtering configuration, I noticed considerable delays in
-page requests compared to the old Junkbuster. Loading pages with large contents
-seemed to take forever, then suddenly delivering all the content at once.
- </para>
-<para>
-The whole content must be loaded in order to filter, and nothing is is
-sent to the browser during this time. The loading time does not really
-change in real numbers, but the feeling is different, because most
-browsers are able to start rendering incomplete content, giving the
-user a feeling of "it works".
+ If you use any <literal><ulink
+ url="../user-manual/actions-file.html#FILTER">filter</ulink></literal> action,
+ such as filtering banners by size, web-bugs etc, or the <literal><ulink
+ url="../user-manual/actions-file.html#DEANIMATE-GIFS">deanimate-gifs</ulink></literal>
+ action, the entire document must be loaded into memory in order for the filtering
+ mechanism to work, and nothing is sent to the browser during this time.
+</para>
+<para>
+ The loading time typically does not really change much in real numbers, but
+ the feeling is different, because most browsers are able to start rendering
+ incomplete content, giving the user a feeling of "it works". This effect is
+ more noticeable on slower dialup connections. Extremely large documents
+ may have some impact on the time to load the page where there is filtering
+ being done. But overall, the difference should be very minimal. If there is a
+ big impact, then probably some other problem is contributing.
</para>
<para>
-To modify the content of a page (i.e. make frames resizeable again, etc.) and
-not just replace ads, <application>Privoxy</application> needs to download the
-entire page first, do its content magic and then send the page to the browser.
+ Filtering is automatically disabled for inappropriate MIME types. But note
+ that if the web server mis-reports the MIME type, then content that should
+ not be filtered, could be. <application>Privoxy</application> only knows how
+ to differentiate filterable content because of the MIME type as reported by
+ the server, or because of some configuration setting that enables/disables
+ filtering.
+
</para>
</sect2>
-
-<sect2 id="configurl"><title>What is the "http://p.p/"?</title>
+<sect2 renderas="sect3" id="slowcrawl">
+<title>I just installed Privoxy, and all my
+browsing has slowed to a crawl. What gives? </title>
<para>
-Since <application>Privoxy</application> sits between your web browser and the Internet, it can be
-programmed to handle certain pages specially.
+ This should not happen, and for the overwhelming number of users world-wide,
+ it does not happen. I would suspect some inadvertent interaction of software
+ components such as anti-virus software, spyware protectors, personal
+ firewalls or similar components. Try disabling (or uninstalling) these one
+ at a time and see if that helps.
</para>
+</sect2>
+<sect2 renderas="sect3" id="configurl"><title>What are "http://config.privoxy.org/" and
+"http://p.p/"?</title>
<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).
+ <ulink url="http://config.privoxy.org/">http://config.privoxy.org/</ulink> is the
+ address of <application>Privoxy</application>'s built-in user interface, and
+ <ulink url="http://p.p/">http://p.p/</ulink> is a shortcut for it.
</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>.
+ Since <application>Privoxy</application> sits between your web browser and the Internet,
+ it can simply intercept requests for these addresses and answer them with its built-in
+ <quote>web server</quote>.
</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>.
+ This also makes for a good test for your browser configuration: If entering the
+ URL <ulink url="http://config.privoxy.org/">http://config.privoxy.org/</ulink>
+ takes you to a page saying <quote>This is Privoxy ...</quote>, everything is OK.
+ If you get a page saying <quote>Privoxy is not working</quote> instead, then
+ your browser didn't use <application>Privoxy</application> for the request,
+ hence it could not be intercepted, and you have accessed the <emphasis>real</emphasis>
+ web site at config.privoxy.org.
</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).
+ With recent versions of <application>Privoxy</application> (version 2.9.x and
+ later), the user interface features information on the run time status, the
+ configuration, and even a built-in editor for the <ulink
+ url="../user-manual/actions-file.html">actions files</ulink>.
</para>
-</sect2>
-
-<!--
-FIXME: commented out until we have data. HB 03/18/02.
-<sect2 id="badfiledesc"><title>I get the message 'Bad File Descriptor', why?</title>
<para>
- Fillme.
+ Note that the built-in URLs from earlier versions of <application>Junkbuster</application>
+ / <application>Privoxy</application>, http://example.com/show-proxy-args and http://i.j.b/,
+ are no longer supported. If you still use such an old version, you should really consider
+ upgrading to &p-version;.
</para>
</sect2>
-<sect2 id="proxy-chaining"><title>How do I chain <application>Privoxy</application> with other proxies
-(e.g. squid)?</title>
-<para>
- Fillme.
+<!--
+ out of date 09/02/06 HB
+<sect2 renderas="sect3" id="blocklist"><title>Do you still maintain the blocklists?</title>
+ <para>
+ No. The patterns for blocking now reside (among other things) in the <ulink
+ url="../user-manual/actions-file.html">actions files</ulink>, which are
+ actively maintained instead. See next question ...
</para>
</sect2>
-->
-
-<sect2 id="blocklist"><title>Do you still maintain the blocklists?</title>
+<sect2 renderas="sect3" id="newads"><title>How can I submit new ads, or report
+problems?</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.
+Please see the <link linkend="contact">Contact section</link> for
+various ways to interact with the developers.
</para>
+
</sect2>
-<sect2 id="newads"><title>How can I submit new ads?</title>
+<sect2 renderas="sect3" id="noonecares"><title>Why doesn't anyone answer my support
+request?</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.
+Rest assured that it has been read and considered. Why it is not answered,
+could be for various reasons, including no one has a good answer for it, no
+one has had time to yet investigate it thoroughly, it has been reported
+numerous times already, or because not enough information was provided to help
+us help you. Your efforts are not wasted, and we do appreciate them.
</para>
+
</sect2>
-<sect2 id="ip"><title>How can I hide my IP address?</title>
+
+<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.
+ If you run both the browser and the proxy locally, you cannot hide your IP
+ address with <application>Privoxy</application> or ultimately any other
+ software. The server needs to know your IP address so that it knows where to
+ send the responses back.
</para>
<para>
-Fortunately there are many publicly usable anonymous proxies out there, which
-solve the problem by providing a further level of indirection between you and
-the web server, shared by many people and thus letting your requests "drown"
-in white noise of unrelated requests as far as user tracking is concerned.
+ There are many publicly usable "anonymous" proxies out there, which
+ provide a further level of indirection between you and the web server.
</para>
<para>
-Most of them will, however, log your IP address and make it available to the
-authorities in case you abuse that anonymity for criminal purposes. In fact
-you can't even rule out that some of them only exist to *collect* information
-on (those suspicious) people with a more than average preference for privacy.
+ However, these proxies are called "anonymous" because you don't need
+ a password, not because they would offer any real anonymity.
+ Most of them will log your IP address and make it available to the
+ authorities in case you violate the law of the country they run in. In fact
+ you can't even rule out that some of them only exist to *collect* information
+ on (those suspicious) people with a more than average preference for privacy.
</para>
<para>
-You can find a list of anonymous public proxies at <ulink
-url="http://www.multiproxy.org/anon_list.htm">multiproxy.org</ulink> and many
-more through Google.
+ Your best bet is to chain <application>Privoxy</application>
+ with <ulink url="http://tor.eff.org/">Tor</ulink>,
+ an <ulink url="http://www.eff.org/">EFF</ulink> supported onion routing system.
+ The configuration details can be found in
+ <ulink url="#TOR">How do I use <application>Privoxy</application> together with <application>Tor</application>?</ulink>.
</para>
+<!--
+<para>
+ There is, however, even in the single-machine case the possibility to make the
+ server believe that your machine is in fact a shared proxy serving a large
+ LAN, and we are looking into that.
+</para>
+ I assume this is about sending fake forward IP addresses?
+ David and I looked into it and considered it a waste of time to implement.
+ Fabian 2006-09-04
+-->
</sect2>
-<!-- <sect2 id="image"><title>What is the imagefile (simage.ini, etc.) for?</title> -->
-<!-- <para> -->
-<!-- Anytime <application>Privoxy</application> determines (with the help of the blocklist) that a URL -->
-<!-- contains an advertisement, it has to decide whether this advertisement is an -->
-<!-- image or not. <application>Privoxy</application> uses the imagefile for that purpose. -->
-<!-- </para> -->
-<!-- </sect2> -->
-
-<sect2>
-<title id="anonforsure">Can <application>Privoxy</application> guarantee I am anonymous?</title>
+<sect2 renderas="sect3">
+<title id="anonforsure">Can Privoxy guarantee I am anonymous?</title>
<para>
No. Your chances of remaining anonymous are greatly improved, but unless you
- are an expert on Internet security it would be safest to assume that
- everything you do on the Web can be traced back to you.
+ <ulink url="#TOR">chain <application>Privoxy</application> with <application>Tor</application></ulink>
+ or a similar system and know what you're doing when it comes to configuring
+ the rest of your system, it would be safest to assume that everything you do
+ on the Web can be traced back to you.
</para>
<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 neither
+ hides your ip address, nor can it guarantee that the rest of the system
+ behaves correctly. There are several possibilities how a web sites can find
+ out who you are, even if you are using a strict <application>Privoxy</application>
+ configuration and chained it with <application>Tor</application>.
+</para>
+<para>
+ Most of <application>Privoxy's</application> protection can be easily subverted
+ by an insecure browser configuration, therefore you should use a browser that can
+ be configured to only execute code from trusted sites, and be careful which sites you trust.
+ For example there is no point in having <application>Privoxy</application>
+ modify the User-Agent header, if websites can get all the information they want
+ through JavaScript, ActiveX, Flash, Java etc.
</para>
<para>
A few browsers disclose the user's email address in certain situations, such
</sect2>
-<sect2>
-<title id="sitebreak">Might some things break because header information is
-being altered?</title>
+<sect2 renderas="sect3" id="tor"><title>How do I use Privoxy
+ together with Tor?</title>
+<para>
+ Before you configure <application>Privoxy</application> to use <application>Tor</application>
+ (<ulink url="http://tor.eff.org/">http://tor.eff.org/</ulink>),
+ please follow the User Manual chapters
+ <ulink url="../user-manual/installation.html">2. Installation</ulink> and
+ <ulink url="../user-manual/startup.html">5. Startup</ulink> to make sure
+ <application>Privoxy</application> itself is setup correctly.
+</para>
+<para>
+ If it is, refer to <ulink url="http://tor.eff.org/documentation.html.en">Tor's
+ extensive documentation</ulink> to learn how to install <application>Tor</application>,
+ and make sure <application>Tor</application>'s logfile says that
+ <quote>Tor has successfully opened a circuit</quote> and it
+ <quote>[l]ooks like client functionality is working</quote>.
+</para>
+<para>
+ If either <application>Tor</application> or <application>Privoxy</application>
+ isn't working, their combination most likely will neither. Testing them on their
+ own will also help you to direct problem reports to the right audience.
+ If <application>Privoxy</application> isn't working, don't bother the
+ <application>Tor</application> developers. If <application>Tor</application>
+ isn't working, don't send bug reports to the <application>Privoxy</application> Team.
+</para>
+<para>
+ If you verified that <application>Privoxy</application> and <application>Tor</application>
+ are working, it is time to connect them. As far as <application>Privoxy</application>
+ is concerned, <application>Tor</application> is just another proxy that can be reached
+ by socks4 or socks4a. Most likely you are interested in <application>Tor</application>
+ to increase your anonymity level, therefore you should use socks4a,
+ to make sure <application>Privoxy's</application> DNS requests are
+ done through <application>Tor</application> and thus invisible to your local network.
+</para>
+<para>
+ Since <application>Privoxy</application> 3.0.4, its configuration (section 5.2)
+ is already prepared for <application>Tor</application>, if you are using a
+ default <application>Tor</application> configuration and run it on the same
+ system as Privoxy, you just have to uncomment the line:
+</para>
+<para>
+ <screen>
+# forward-socks4a / 127.0.0.1:9050 .
+ </screen>
+</para>
+<para>
+ This is enough to reach the Internet, but additionally you should
+ uncomment the following forward rules, to make sure your local network is still
+ reachable through Privoxy:
+</para>
+<para>
+ <screen>
+# forward 192.168.*.*/ .
+# forward 10.*.*.*/ .
+# forward 127.*.*.*/ .
+ </screen>
+</para>
+<para>
+ Unencrypted connections to systems in these address ranges will
+ be as (un)secure as the local network is, but the alternative is
+ that you can't reach the network at all.
+ If you also want to be able to reach servers in your local
+ network by using their names, you will need additional
+ exceptions that look like this:
+</para>
+<para>
+ <screen>
+# forward localhost/ .
+ </screen>
+</para>
+<para>
+ Save the modified configuration file and open
+ <ulink url="http://config.privoxy.org/show-status">http://config.privoxy.org/show-status/</ulink>
+ in your browser, confirm that <application>Privoxy</application> has reloaded its configuration
+ and that there are no other forward lines, unless you know that you need them. I everything looks good,
+ refer to
+ <ulink url="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#head-0e1cc2ac330ede8c6ad1ac0d0db0ac163b0e6143">Tor
+ Faq 4.2</ulink> to learn how to verify that you are really using <application>Tor</application>.
+</para>
+<para>
+ Afterward, please take the time to at least skim through the rest
+ of <application>Tor's</application> documentation. Make sure you understand
+ what <application>Tor</application> does, why it is no replacement for
+ application level security, and why you shouldn't use it for unencrypted logins.
+</para>
+</sect2>
+
+<sect2 renderas="sect3">
+<title id="sitebreak">Might some things break because header information or
+content is being altered?</title>
<para>
Definitely. More and more sites use HTTP header content to decide what to
</para>
<para>
- <quote>USER AGENT</quote> in particular is often used in this way to identify
- the browser, and adjust content accordingly. Changing this now is not
- recommended, since so many sites do look for this. You may get undesirable
- results by changing this.
+ <quote>User-Agent</quote> in particular is often used in this way to identify
+ the browser, and adjust content accordingly. Changing this now (at least not
+ further than removing the OS information) is not recommended, since so many
+ sites do look for it. You may get undesirable results by changing this.
</para>
<para>
operating system or browser manufacturer causes some sites in these languages
to be garbled; Surfers to Eastern European sites should change it to
something closer. And then some page access counters work by looking at the
- <quote>REFERER</quote> header; they may fail or break if unavailable. The
+ <quote>Referer</quote> header; they may fail or break if unavailable. The
weather maps of Intellicast have been blocked by their server when no
- <quote>REFERER</quote> or cookie is provided, is another example. There are
- many, many other ways things can go wrong when trying to fool a web server.
+ <quote>Referer</quote> or cookie is provided, is another example. (But you
+ can forge both headers without giving information away). There are
+ many other ways things can go wrong when trying to fool a web server.
+</para>
+
+<para>
+ Similar thoughts apply to modifying JavaScript, and, to a lesser degree,
+ HTML elements.
</para>
<para>
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>
-<title id="caching">Can <application>Privoxy</application> act as a <quote>caching</quote> proxy to
+<sect2 renderas="sect3">
+<title id="caching">Can Privoxy act as a <quote>caching</quote> proxy to
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> 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
+ chapter</ulink> in the <ulink url="../user-manual/index.html">user
+ manual</ulink> for details.
</para>
</sect2>
-<sect2>
-<title id="firewall">What about as a firewall? Can <application>Privoxy</application> protect me?</title>
+<sect2 renderas="sect3">
+<title id="firewall">What about as a firewall? Can Privoxy protect me?</title>
<para>
- Not in the way you mean, or in the way a true firewall can, or a proxy that
- has this specific capability. <application>Privoxy</application> can help
- protect your privacy, but not really protect you from intrusion attempts.
+ Not in the way you mean, or in the way a true firewall can.
+ <application>Privoxy</application> can help protect your privacy, but not
+ protect you from intrusion attempts. It is, of course, perfectly possible
+ and recommended to use <emphasis>both</emphasis>.
</para>
</sect2>
-
-<sect2>
-<title id="logo">The <application>Privoxy</application> logo that replaces ads is very blocky
-and ugly looking. Can't a better font be used?</title>
-
+<sect2 renderas="sect3">
+<title id="wasted">I have large empty spaces / a checkerboard pattern now where
+ads used to be. Why?</title>
<para>
- This is not a font problem. The logo is an image that is created by
- <application>Privoxy</application> on the fly. So as to not waste
- memory, the image is rather small. The blockiness comes when the
- image is scaled to fill a largish area. There is not much to be done
- about this, other than to use one of the other
- <quote>imageblock</quote> directives: <emphasis>pattern</emphasis>,
- <emphasis>blank</emphasis>, or a URL of your choosing.
+ It would be technically possible eliminate the banners in a way that frees
+ their screen estate in many cases, by doing all banner blocking with filters,
+ i.e. eliminating the whole image references from the HTML pages instead
+ of letting them stay in, and blocking the resulting requests for the
+ banners themselves.
</para>
<para>
-Given the above problem, we have decided to remove the logo option entirely
-[as of v2.9.13].
+ But this would consume considerable CPU resources, would likely destroy
+ the layout of many web pages which rely on the banners consuming a certain
+ amount of screen space, and would fail in other cases, where the screen space
+ is reserved e.g. by tables anyway. Also, making the banners disappear without
+ a visual trace complicates troubleshooting.
</para>
-</sect2>
-
-
-<sect2>
-<title id="wasted">I have large empty spaces now where ads used to be.
-Why?</title>
<para>
- It would be easy enough to just eliminate this space altogether, rather than
- fill it with blank space. But, this would create problems with many pages
- that use the overall size of the ad to help organize the page layout and
- position the various components of the page where they were intended to be.
- It is best left this way.
+ So we won't support this in the default configuration, but you can of course
+ define appropriate filters yourself.
</para>
-
</sect2>
-<sect2>
-<title id="ssl">How can <application>Privoxy</application> filter Secure (HTTPS) URLs?</title>
+<sect2 renderas="sect3">
+<title id="ssl">How can Privoxy filter Secure (HTTPS) URLs?</title>
+<para>
+ Since secure HTTP connections are encrypted SSL sessions between your browser
+ and the secure site, and are meant to be reliably <emphasis>secure</emphasis>,
+ there is little that <application>Privoxy</application> can do but hand the raw
+ gibberish data though from one end to the other unprocessed.
+</para>
+<para>
+ The only exception to this is blocking by host patterns, as the client needs
+ to tell <application>Privoxy</application> the name of the remote server,
+ so that <application>Privoxy</application> can establish the connection.
+ If that name matches a host-only pattern, the connection will be blocked.
+</para>
+<para>
+ As far as ad blocking is concerned, this is less of a restriction than it may
+ seem, since ad sources are often identifiable by the host name, and often
+ the banners to be placed in an encrypted page come unencrypted nonetheless
+ for efficiency reasons, which exposes them to the full power of
+ <application>Privoxy</application>'s ad blocking.
+</para>
<para>
- This is a limitation since HTTPS transactions are encrypted SSL sessions
- between your browser and the secure site, and are meant to be reliably
- <emphasis>secure</emphasis> and private. This means that all cookies and HTTP
- header information are also encrypted from the time they leave your browser,
- to the site, and vice versa. <application>Privoxy</application> does not
- try to unencrypt this information, so it just passes through as is.
- <application>Privoxy</application> can still catch images and ads that
- are embedded in the SSL stream though.
+ <quote>Content cookies</quote> (those that are embedded in the actual HTML or
+ JS page content, see <literal><ulink
+ url="../user-manual/actions-file.html#FILTER-CONTENT-COOKIES">filter{content-cookies}</ulink></literal>),
+ in an SSL transaction will be impossible to block under these conditions.
+ Fortunately, this does not seem to be a very common scenario since most
+ cookies come by traditional means.
</para>
</sect2>
-
-<sect2>
-<title id="secure"><application>Privoxy</application> runs as a <quote>server</quote>. How
+<sect2 renderas="sect3">
+<title id="secure">Privoxy runs as a <quote>server</quote>. How
secure is it? Do I need to take any special precautions?</title>
<para>
- There are no known exploits that might effect
+ There are no known exploits that might affect
<application>Privoxy</application>. On Unix-like systems,
<application>Privoxy</application> can run as a non-privileged
user, which is how we recommend it be run. Also, by default
<application>Privoxy</application> only listens to requests
- from <quote>localhost</quote>. The server aspect of
+ from <quote>localhost</quote> only. The server aspect of
<application>Privoxy</application> is not itself directly exposed to the
Internet in this configuration. If you want to have
<application>Privoxy</application> serve as a LAN proxy, this will have to
be opened up to allow for LAN requests. In this case, we'd recommend
you specify only the LAN gateway address, e.g. 192.168.1.1, in the main
- <application>Privoxy</application> config file. All LAN hosts can then use
- this as their proxy address in the browser proxy configuration. In this way,
- <application>Privoxy</application> will not listen on any external ports.
- Of course, a firewall is always good too. Better safe than sorry.
+ <application>Privoxy</application> configuration file and check all <ulink
+ url="../user-manual/config.html#ACCESS-CONTROL">access control and security
+ options</ulink>. All LAN hosts can then use this as their proxy address
+ in the browser proxy configuration, but <application>Privoxy</application>
+ will not listen on any external interfaces. ACLs can be defined in addition,
+ and using a firewall is always good too. Better safe than sorry.
</para>
</sect2>
-<sect2 id="turnoff">
-<title>How can I temporarily disable <application>Privoxy</application>?</title>
+<sect2 renderas="sect3" id="turnoff">
+<title>How can I temporarily disable Privoxy?</title>
<para>
The easiest way is to access <application>Privoxy</application> with your
- browser by using the special URL: <ulink url="http://p.p/">http://p.p/</ulink>
- and select "Toggle Privoxy on or off" from that page.
+ browser by using the remote toggle URL: <ulink
+ url="http://config.privoxy.org/toggle">http://config.privoxy.org/toggle</ulink>.
+ See the <ulink url="../user-manual/appendix.html#BOOKMARKLETS">Bookmarklets section</ulink>
+ of the <citetitle>User Manual</citetitle> for an easy way to access this
+ feature.
+</para>
+</sect2>
+<sect2 renderas="sect3" id="reallyoff">
+<title>When <quote>disabled</quote> is Privoxy totally
+out of the picture?</title>
+<para>
+ No, this just means all filtering and actions are disabled.
+ <application>Privoxy</application> is still acting as a proxy, but just not
+ doing any of the things that <application>Privoxy</application> would
+ normally be expected to do. It is still a <quote>middle-man</quote> in
+ the interaction between your browser and web sites.
</para>
</sect2>
-<sect2 id="seealso">
-<title>Where can I find more information about <application>Privoxy</application>
-and related issues?</title>
+<sect2 renderas="sect3" id="crunch">
+<title>My logs show Privoxy <quote>crunches</quote>
+ads, but also its own internal CGI pages. What is a <quote>crunch</quote>?</title>
+<para>
+ A <quote>crunch</quote> simply means <application>Privoxy</application> intercepted
+ <emphasis>something</emphasis>, nothing more. Often this is indeed ads or
+ banners, but <application>Privoxy</application> uses the same mechanism for
+ trapping requests for its own internal pages. For instance, a request for
+ <application>Privoxy's</application> configuration page at: <ulink
+ url="http://config.privoxy.org">http://config.privoxy.org</ulink>, is
+ intercepted (i.e. it does not go out to the 'net), and the familiar CGI
+ configuration is returned to the browser, and the log consequently will show
+ a <quote>crunch</quote>.
+</para>
+</sect2>
-<!--
- Include seealso.sgml
--->
-
+<sect2 renderas="sect3" id="downloads">
+<title>Can Privoxy effect files that I download
+from a webserver? FTP server?</title>
+<para>
+ From the webserver's perspective, there is no difference between
+ viewing a document (i.e. a page), and downloading a file. The same is true of
+ <application>Privoxy</application>. If there is a match for a <literal><ulink
+ url="../user-manual/actions-file.html#BLOCK">block</ulink></literal> pattern,
+ it will still be blocked, and of course this is obvious.
+ </para>
+ <para>
+ Filtering is potentially more of a concern since the results are not always
+ so obvious, and the effects of filtering are there whether the file is simply
+ viewed, or downloaded. And potentially whether the content is some obnoxious
+ advertizement, or Mr. Jimmy's latest/greatest source code jewel. Of course,
+ one of these presumably is <quote>bad</quote> content that we don't want, and
+ the other is <quote>good</quote> content that we do want.
+ <application>Privoxy</application> is blind to the differences, and can only
+ distinguish <quote>good from bad</quote> by the configuration parameters
+ <emphasis>we</emphasis> give it.
+</para>
+<para>
+ <application>Privoxy</application> knows the differences in files according
+ to the <quote>Document Type</quote> as reported by the webserver. If this is
+ reported accurately (e.g. <quote>application/zip</quote> for a zip archive),
+ then <application>Privoxy</application> knows to ignore these where
+ appropriate. <application>Privoxy</application> potentially can filter HTML
+ as well as plain text documents, subject to configuration parameters of
+ course. Also, documents that are of an unknown type (generally assumed to be
+ <quote>text/plain</quote>) can be filtered, as will those that might be
+ incorrectly reported by the webserver. If such a file is a downloaded file
+ that is intended to be saved to disk, then any content that might have been
+ altered by filtering, will be saved too, for these (probably rare) cases.
+</para>
+<para>
+ Note that versions later than 3.0.2 do NOT filter document types reported as
+ <quote>text/plain</quote>. Prior to this, <application>Privoxy</application>
+ did filter this document type.
+</para>
+<para>
+ In short, filtering is <quote>ON</quote> if a) the Document Type as reported
+ by the webserver is appropriate <emphasis>and</emphasis> b) the configuration
+ allows it (or at least does not disallow it). That's it. There is no magic
+ cookie anywhere to say this is <quote>good</quote> and this is
+ <quote>bad</quote>. It's the configuration that let's it all happen or not.
+</para>
+<para>
+ If you download text files, you probably do not want these to be filtered,
+ particularly if the content is source code, or other critical content. Source
+ code sometimes might be mistaken for Javascript (i.e. the kind that might
+ open a pop-up window). It is recommended to turn off filtering for download
+ sites (particularly if the content may be plain text files and you are using
+ version 3.0.2 or earlier) in your <filename>user.action</filename> file. And
+ also, for any site or page where making <emphasis>any</emphasis> changes at
+ all to the content is to be avoided.
+</para>
+<para>
+ <application>Privoxy</application> does not do FTP at all, only HTTP
+ protocols, so please don't try.
+</para>
+</sect2>
+
+<sect2 renderas="sect3" id="downloads2">
+<title>I just downloaded a Perl script, and Privoxy
+altered it! Yikes, what is wrong!</title>
+<para>
+ Please read above.
+</para>
+</sect2>
+
+<sect2 renderas="sect3" id="hostsfile">
+<title>Should I continue to use a <quote>HOSTS</quote> file for ad-blocking?</title>
+<para>
+ One time-tested technique to defeat common ads is to trick the local DNS
+ system by giving a phony IP address for the ad generator in the local
+ <filename>HOSTS</filename> file, typically using <literal>127.0.0.1</literal>, aka
+ <literal>localhost</literal>. This effectively blocks the ad.
+</para>
+<para>
+ There is no reason to use this technique in conjunction with
+ <application>Privoxy</application>. <application>Privoxy</application>
+ does essentially the same thing, much more elegantly and with much more
+ flexibility. A large <filename>HOSTS</filename> file, in fact, not only
+ duplicates effort, but may get in the way. It is recommended to remove
+ such entries from your <filename>HOSTS</filename> file. If you think
+ your hosts list is neglected by <application>Privoxy's </application>
+ configuration, consider adding your list to your <filename>user.action</filename> file:
+</para>
+<para>
+ <screen>
+ { +block }
+ www.ad.example1.com
+ ad.example2.com
+ ads.galore.example.com
+ etc.example.com</screen>
+</para>
+</sect2>
+
+<sect2 renderas="sect3" id="seealso">
+<title>Where can I find more information about Privoxy
+and related issues?</title>
+<!-- Include seealso.sgml boilerplate: -->
&seealso;
+<!-- end boilerplate -->
<!--
<para>
-->
</sect2>
+<sect2 renderas="sect3" id="microsuck">
+<title>I've noticed that Privoxy changes <quote>Microsoft</quote> to
+<quote>MicroSuck</quote>! Why are you manipulating my browsing?</title>
+
+<para>
+ We're not. The text substitutions that you are seeing are disabled
+ in the default configuration as shipped. You have either manually
+ activated the <quote><literal>fun</literal></quote> filter which
+ is clearly labeled <quote>Text replacements for subversive browsing
+ fun!</quote> or you are using an older Privoxy version and have implicitly
+ activated it by choosing the <quote>Adventuresome</quote> profile in the
+ web-based editor.
+</para>
+</sect2>
+
</sect1>
<!-- ~~~~~ New section ~~~~~ -->
<sect1 id="trouble">
-<title>5. Troubleshooting</title>
+<title>Troubleshooting</title>
-<sect2>
-<title id="refused">I just upgraded and am getting <quote>connection refused</quote>
+<sect2 renderas="sect3">
+<title id="refused">I am getting <quote>connection refused</quote>
with every web page?</title>
<para>
Either <application>Privoxy</application> is not running, or your
</para>
<para>
- The old <application>Privoxy</application> (and also
+ Early <application>Privoxy</application> 2.x versions (and also
<application>Junkbuster</application>) used port 8000 by
default. This has been changed to port 8118 now, due to a conflict
with NAS (Network Audio Service), which uses port 8000. If you haven't,
you need to change your browser to the new port number, or alternately
- change <application>Privoxy's</application> <quote>listen-address</quote>
- setting in the <filename>config</filename> file used to start
- <application>Privoxy</application>.
+ change the <ulink
+ url="../user-manual/config.html#LISTEN-ADDRESS"><literal>listen-address</literal>
+ option</ulink> in <application>Privoxy's</application> <ulink
+ url="../user-manual/config.html">main configuration file</ulink>.
</para>
</sect2>
-<sect2>
+<sect2 renderas="sect3">
<title id="flushit">I just added a new rule, but the steenkin ad is
still getting through. How?</title>
<para>
If this doesn't help, you probably have an error in the rule you
applied. Try pasting the full URL of the offending ad into <ulink
url="http://config.privoxy.org/show-url-info">http://config.privoxy.org/show-url-info</ulink>
- and see if any actions match your new rule.
+ and see if it really matches your new rule. Blocking ads is like blocking
+ spam: a lot of tinkering is required to stay ahead of the game.
</para>
</sect2>
-<sect2>
-<title id="badsite">One of my favorite sites does not work with <application>Privoxy</application>.
+<sect2 id="badsite" renderas="sect3">
+<title >One of my favorite sites does not work with Privoxy.
What can I do?</title>
<para>
First verify that it is indeed a <application>Privoxy</application> problem,
- by disabling <application>Privoxy</application> filtering and blocking.
- Go to <ulink url="http://p.p/">http://p.p/</ulink> and click on
- <quote>Toggle Privoxy On or Off</quote>, then disable it. Now try that
- page again. It's probably a good idea to flush the browser cache as well.
+ by toggling off <application>Privoxy</application> through <ulink
+ url="http://config.privoxy.org/toggle">http://config.privoxy.org/toggle</ulink>,
+ and then shift-reloading the problem page (i.e. holding down the shift key
+ while clicking reload. Alternatively, flush your browser's disk and memory
+ caches).
</para>
<para>
- If still a problem, go to <quote>Show which actions apply to a URL and
- why</quote> from <ulink url="http://p.p/">http://p.p/</ulink> and paste
- the full URL of the page in question into the prompt. See which actions are
- being applied to the URL. Now, armed with this information, go to <quote>Edit
- the actions list</quote>. Here you should see various sections that have
- various <application>Privoxy</application> features disabled for specific
- sites. Disabled <quote>actions</quote> will have a <quote>-</quote> (minus
- sign) in front of them. Add your problem page URL to one of these sections
- that looks like it is disabling the feature that is causing the
- problem. Re-try the page. There might be some trial and error involved. This
- is discussed in a little more detail in the
- <ulink url="../user-manual/appendix.html#ACTIONSANAT">user-manual
- appendix</ulink>.
+ If still a problem, go to <ulink
+ url="http://config.privoxy.org/show-url-info">http://config.privoxy.org/show-url-info</ulink>
+ and paste the full URL of the page in question into the prompt. See which actions
+ are being applied to the URL, and which matches in which actions files are
+ responsible for that. Now, armed with this information, go to <ulink
+ url="http://config.privoxy.org/show-status">http://config.privoxy.org/show-status</ulink>
+ and select the appropriate actions files for editing.
+</para>
+<para>
+ You can now either look for a section which disables the actions that
+ you suspect to cause the problem and add a pattern for your site there,
+ or make up a completely new section for your site. In any case, the recommended
+ way is to disable only the prime suspect, reload the problem page, and only
+ if the problem persists, disable more and more actions until you have
+ identified the culprit. You may or may not want to turn the other actions
+ on again. Remember to flush your browser's caches in between any such changes!
+</para>
+<para>
+ Alternately, if you are comfortable with a text editor, you can accomplish
+ the same thing by editing the appropriate actions file. Probably the easiest
+ way to deal with such problems when editing by hand is to add your
+ site to a <literal>{ fragile }</literal> section in <filename>user.action</filename>,
+ which is an alias that turns off most <quote>dangerous</quote>
+ actions, but is also likely to turn off more actions then needed, and thus lower
+ your privacy and protection more than necessary,
+</para>
+<para>
+ Troubleshooting actions is discussed in more detail in the <ulink
+ url="../user-manual/appendix.html#ACTIONSANAT">user-manual appendix</ulink>.
+ There is also an <ulink
+ url="../user-manual/actions-file.html#ACT-EXAMPLES">actions tutorial</ulink>.
+</para>
+
+</sect2>
+
+<!-- ~~~~~ New section ~~~~~ -->
+<sect2 id="dun" renderas="sect3">
+<title>After installing Privoxy, I have to log in
+every time I start IE. What gives?</title>
+
+<para>
+ This is a quirk that effects the installation of
+ <application>Privoxy</application>, in conjunction with Internet Explorer and
+ Internet Connection Sharing on Windows 2000 and Windows XP. The symptoms may
+ appear to be corrupted or invalid DUN settings, or passwords.
</para>
<para>
- Alternately, if you are comfortable with a text editor, you can accomplish
- the same thing by editing the appropriate <quote>actions</quote> file.
+ When setting up an NT based Windows system with
+ <application>Privoxy</application> you may find that things do not seem to be
+ doing what you expect. When you set your system up you will probably have set
+ up Internet Connection Sharing (ICS) with Dial up Networking (DUN) when
+ logged in with administrator privileges. You will probably have made this DUN
+ connection available to other accounts that you may have set-up on your
+ system. E.g. Mum or Dad sets up the system and makes accounts suitably
+ configured for the kids.
</para>
+<para>
+ When setting up <application>Privoxy</application> in this environment you
+ will have to alter the proxy set-up of Internet Explorer (IE) for the
+ specific DUN connection on which you wish to use
+ <application>Privoxy</application>. When you do this the ICS DUN set-up
+ becomes user specific. In this instance you will see no difference if you
+ change the DUN connection under the account used to set-up the connection.
+ However when you do this from another user you will notice that the DUN
+ connection changes to make available to "Me only". You will also find that
+ you have to store the password under each different user!
+</para>
+
+<para>
+ The reason for this is that each user's set-up for IE is user specific. Each
+ set-up DUN connection and each LAN connection in IE store the settings for
+ each user individually. As such this enforces individual configurations
+ rather than common ones. Hence the first time you use a DUN connection after
+ re-booting your system it may not perform as you expect, and prompt you for
+ the password. Just set and save the password again and all should be OK.
+</para>
+
+<para>
+[Thanks to Ray Griffith for this submission.]
+</para>
+</sect2>
+
+
+<!-- ~~~~~ New section ~~~~~ -->
+<sect2 id="ftp" renderas="sect3">
+<title>I cannot connect to any FTP sites. Privoxy
+ is blocking me.</title>
+ <para>
+ <application>Privoxy</application> cannot act as a proxy for FTP traffic,
+ so do not configure your browser to use <application>Privoxy</application>
+ as an FTP proxy. The same is true for <emphasis>any protocol other than HTTP
+ or HTTPS (SSL)</emphasis>.
+ </para>
+ <para>
+ Most browsers understand FTP as well as HTTP. If you connect to a site, with
+ a URL like <literal>ftp://ftp.example.com</literal>, your browser is making
+ an FTP connection, and not a HTTP connection. So while your browser may
+ speak FTP, <application>Privoxy</application> does not, and cannot proxy
+ such traffic.
+ </para>
+ <para>
+ To complicate matters, some systems may have a generic <quote>proxy</quote>
+ setting, which will silently various protocols, including
+ <emphasis>both</emphasis> HTTP and FTP proxying! So it is possible to
+ accidentally enable FTP proxying in these cases. And of course, if this
+ happens, <application>Privoxy</application> will indeed cause problems since
+ it does not know FTP. Newer version will give a sane error message if a FTP
+ connection is attempted.
+ </para>
+ <para>
+ Will <application>Privoxy</application> ever proxy FTP traffic? Unlikely.
+ There just is not much reason, and the work to make this happen is more than
+ it may seem.
+ </para>
+</sect2>
+
+<!-- ~~~~~ New section ~~~~~ -->
+<sect2 id="osxie" renderas="sect3">
+<title>In Mac OSX, I can't configure Microsoft Internet Explorer to use
+ Privoxy as the HTTP proxy.</title>
+ <para>
+ Microsoft Internet Explorer (in versions like 5.1) respects system-wide
+ network settings. In order to change the HTTP proxy, open System
+ Preferences, and click on the Network icon. In the settings pane that
+ comes up, click on the Proxies tab. Ensure the "Web Proxy (HTTP)" checkbox
+ is checked and enter <literal>127.0.0.1</literal> in the entry field.
+ Enter <literal>8118</literal> in the Port field. The next time you start
+ IE, it should reflect these values.
+ </para>
+</sect2>
+
+<!-- ~~~~~ New section ~~~~~ -->
+<sect2 renderas="sect3" id="osxuninstall">
+<title>In Mac OSX, I dragged the Privoxy folder to the trash in order to
+ uninstall it. Now the finder tells me I don't have sufficient privileges to
+ empty the trash.</title>
+ <para>
+ Just dragging the <application>Privoxy</application> folder to the trash is
+ not enough to delete it. <application>Privoxy</application> supplies an
+ <application>uninstall.command</application> file that takes care of
+ these details. Open the trash, drag the <application>uninstall.command</application>
+ file out of the trash and double-click on it. You will be prompted for
+ confirmation and the administration password.
+ </para>
+ <para>
+ The trash may still appear full after this command; emptying the trash
+ from the desktop should make it appear empty again.
+ </para>
</sect2>
-<sect2 id="bugs">
-<title>Where can I get help? Report bugs? Feature Requests? Etc?</title>
+
+<!-- ~~~~~ New section ~~~~~ -->
+<sect2 renderas="sect3" id="osximages">
+<title>In Mac OSX Panther (10.3), images often fail to load and/or I
+ experience random delays in page loading. I'm using
+ <literal>localhost</literal> as my browser's proxy setting.</title>
+ <para>
+ We believe this is due to an IPv6-related bug in OSX, but don't fully
+ understand the issue yet. In any case, changing the proxy setting to
+ <literal>127.0.0.1</literal> instead of <literal>localhost</literal>
+ works around the problem.
+ </para>
+</sect2>
+
+<!-- ~~~~~ New section ~~~~~ -->
+<sect2 renderas="sect3" id="blankpage">
+<title>I get a completely blank page at one site. <quote>View Source</quote>
+ shows only: <markup><![CDATA[<html><body></body></html>]]></markup>. Without
+ Privoxy the page loads fine.</title>
+ <para>
+ Chances are that the site suffers from a bug in
+ <ulink url="http://www.php.net/"><application>PHP</application></ulink>,
+ which results in empty pages being sent if the client explicitly requests
+ an uncompressed page, like <application>Privoxy</application> does.
+ This bug has been fixed in PHP 4.2.3.
+ </para>
+ <para>
+ To find out if this is in fact the source of the problem, try adding
+ the site to a <literal>-prevent-compression</literal> section in
+ <filename>user.action</filename>:
+ </para>
+ <screen>
+ # Make exceptions for ill-behaved sites:
+ #
+ {-prevent-compression}
+ .example.com</screen>
+ <para>
+ If that works, you may also want to report the problem to the
+ site's webmasters, telling them to use zlib.output_compression
+ instead of ob_gzhandler in their PHP applications (workaround)
+ or upgrade to PHP 4.2.3 or later (fix).
+ </para>
+</sect2>
+
+<!-- ~~~~~ New section ~~~~~ -->
+<sect2 renderas="sect3" id="error503">
+<title>Why am I getting a 503 Error (WSAECONNREFUSED) on every page?</title>
+ <para>
+ More than likely this is a problem with your TCP/IP networking. ZoneAlarm has
+ been reported to cause this symptom -- even if not running. The solution is
+ to either fight the ZA configuration, or uninstall ZoneAlarm, and then find
+ something better behaved in its place. Other personal firewall type products
+ may cause similar type problems if not configured correctly.
+ </para>
+</sect2>
+
+<sect2 renderas="sect3" id="nohostname">
+<title>My logs show many <quote>Unable to get my own hostname</quote> lines.
+Why?</title>
+<para>
+ <application>Privoxy</application> tries to get the hostname of the system
+ its running on from the IP address of the system interface it is bound to
+ (from the <filename>config</filename> file
+ <emphasis>listen-address</emphasis> setting). If the system cannot supply
+ this information, <application>Privoxy</application> logs this condition.
+</para>
<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.
+ Typically, this would be considered a minor system configuration error. It is
+ not a fatal error to <application>Privoxy</application> however, but may
+ result in a much slower response from <application>Privoxy</application> on
+ some platforms due to DNS timeouts.
+</para>
+</sect2>
+<sect2 renderas="sect3" id="inuse">
+<title>When I try to launch Privoxy, I get an
+error message <quote>port 8118 is already in use</quote> (or similar wording).
+Why?</title>
+<para>
+ Port 8118 is <application>Privoxy's</application> default TCP
+ <quote>listening</quote> port. Typically this message would mean that there
+ is already one instance of <application>Privoxy</application> running, and
+ you are actually trying to start a second <application>Privoxy</application>
+ on the same port, which will not work. (You can have multiple instances but
+ they must be assigned different ports.) How and why this might happen varies
+ from platform to platform, but you need to check your installation and
+ start-up procedures.
</para>
+</sect2>
+<sect2 renderas="sect3" id="demoronizer">
+<title>
+ Pages with UTF-8 fonts are garbled.
+</title>
+<para>
+ This is caused by the <quote>demoronizer</quote> filter. You should either
+ upgrade <application>Privoxy</application>, or at least upgrade to the most
+ recent <filename>default.action</filename> file available from <ulink
+ url="http://sourceforge.net/project/showfiles.php?group_id=11118">SourceForge</ulink>.
+ Or you can simply disable the demoronizer filter.
+</para>
</sect2>
-<sect2>
-<title id="time">What time is it?</title>
+<sect2 renderas="sect3" id="demoronizer2">
+<title>
+ Why are binary files (such as images) corrupted when Privoxy
+ is used?
+</title>
<para>
- Time for you to go!
+ This may also be caused by the <quote>demoronizer</quote> filter,
+ in conjunction with a web server that is misreporting a file type. Binary
+ files are exempted from <application>Privoxy's</application> filtering
+ (unless the web server by mistake says the file is something else). Either
+ upgrade <application>Privoxy</application>, or go to the most recent
+ <filename>default.action</filename> file available from <ulink
+ url="http://sourceforge.net/project/showfiles.php?group_id=11118">SourceForge</ulink>.
</para>
</sect2>
-</sect1>
-<!--
-</sect1>
--->
+<sect2 renderas="sect3" id="demoronizer3">
+<title>
+ What is the <quote>demoronizer</quote> and why is it there?
+</title>
+<para>
+ The original demoronizer was a Perl script that cleaned up HTML pages which
+ were created with certain Microsoft products. MS has used proprietary extensions
+ to standardized font encodings (ISO 8859-1), which has caused problems for pages
+ that are viewed with non-Microsoft products (and are expecting to see a
+ standard set of fonts). The demoronizer corrected these errors so the pages
+ displayed correctly. <application>Privoxy</application> borrowed from this
+ script, introducing a filter based on the original demoronizer, which in turn could
+ correct these errors on the fly.
+</para>
+<para>
+ But this is only needed in some situations, and will cause serious problems in some
+ other situations.
+</para>
+<para>
+ If you are using Microsoft products, you do not need it. If you need to view
+ pages with UTF-8 characters (such as Cyrillic or Chinese), then it will
+ cause corruption of the fonts, and thus <emphasis>should not be on</emphasis>.
+</para>
+<para>
+ On the other hand, if you use non-Microsoft products, and you occasionally
+ notice wierd characters on pages, you might want to try it.
+</para>
+</sect2>
-<!-- ~~~~~ New section ~~~~~ -->
-<!--
-FIXME: Commented out until we have something to put here. HB 03/18/02.
-<sect1 id="knownissues"><title>Known Issues</title>
+<sect2 renderas="sect3" id="windowopen">
+<title>
+ Why do I keep seeing <quote>PrivoxyWindowOpen()</quote> in raw source code?
+</title>
<para>
- Fillme.
+ <application>Privoxy</application> is attempting to disable malicious
+ Javascript 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>
+<para>
+ If you see this in HTML source, and the page displays without problems, then
+ this is good, and likely some pop-up window was disabled. If you see this
+ where it is causing a problem, such as a downloaded program source code file,
+ then you should set an exception for this site or page such that the
+ integrity of the page stays in tact by disabling all filtering.
+</para>
+</sect2>
+
+<sect2 renderas="sect3" id="dnserrors">
+<title>
+ I am getting too many DNS errors like <quote>404 No Such Domain</quote>. Why
+ can't Privoxy do this better?
+</title>
+<para>
+ There are potentially several factors here. First of all, the DNS resolution
+ is done by the underlying operating system -- not
+ <application>Privoxy</application> itself. <application>Privoxy</application>
+ merely initiates the process and hands it off, and then later reports
+ whatever the outcome was. And tries to give a coherent message if there seems
+ to be a problem. In some cases, this might otherwise be mitigated by the
+ browser itself which might try some work-arounds and alternate approaches (e.g
+ adding <quote>www.</quote> to the URL). In other cases, if
+ <application>Privoxy</application> is being chained with another proxy, this
+ could complicate the issue, and cause undue
+ delays and timeouts. In the case of a <quote>socks4a</quote> proxy, the socks
+ server handles all the DNS. <application>Privoxy</application> would just be
+ the <quote>messenger</quote> which is reporting whatever problem occurred
+ downstream, and not the root cause of the error.
+</para>
+<para>
+ In any case, v. 3.0.4 includes various improvements to help
+ <application>Privoxy</application> better handle these cases.
+</para>
+</sect2>
+
+<sect2 renderas="sect3" id="allcpu">
+<title>
+ At one site Privoxy just hangs, and starts taking
+ all CPU. Why is this?
+</title>
+<para>
+ This is probably a manifestation of the <quote>100% cpu</quote> problem that
+ occurs on pages containing many (thousands upon thousands) of blank lines. The blank lines
+ are in the raw HTML source of the page, and the browser just ignores them. But the
+ pattern matching in <application>Privoxy's</application> page filtering
+ mechanism is trying to match against absurdly long strings and this becomes
+ very CPU-intensive, taking a long, long time to complete. Until a better
+ solution comes along, disable filtering on these pages, particularly the
+ <literal>js-annoyances</literal> and <literal>unsolicited-popups</literal>
+ filters.
</para>
+</sect2>
+
+
+
</sect1>
--->
+ <!-- ~~~~~ 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>Privoxy Copyright, License and History</title>
-This is referenced in the doc header already. HB 03/25/02
+ <!-- Include copyright.sgml -->
+ ©right;
+ <!-- end -->
+
-<sect1 id="contact"><title>Contact the developers</title>
-<para>Please see the user manual for information on how to contact the developers.
-</para>
+ <para>
+ Portions of this document are <quote>borrowed</quote> from the original
+ <application>Junkbuster</application> (tm) FAQ, and modified as
+ appropriate for <application>Privoxy</application>.
+ </para>
+
+ <!-- ~~~~~ New section ~~~~~ -->
+ <sect2><title>License</title>
+ <!-- Include copyright.sgml: -->
+ &license;
+ <!-- end copyright -->
+ </sect2>
+ <!-- ~ End section ~ -->
+
+ <!-- ~~~~~ New section ~~~~~ -->
+ <sect2><title>History</title>
+ <!-- Include history.sgml -->
+ &history;
+ <!-- end -->
+ </sect2>
+
+ </sect1>
+ <!-- ~ End section ~ -->
+
+
+<!-- ~~~~~ 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.
- Last modified: Mon Sep 10 19:22:09 CEST 2001
-
This program is free software; you can redistribute it
and/or modify it under the terms of the GNU General
Public License as published by the Free Software
The GNU General Public License should be included with
this file. If not, you can view it at
http://www.gnu.org/copyleft/gpl.html
- or write to the Free Software Foundation, Inc., 59
- Temple Place - Suite 330, Boston, MA 02111-1307, USA.
+ or write to the Free Software Foundation, Inc.,
+ 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA
$Log: faq.sgml,v $
+Revision 2.15 2006/09/08 23:05:07 hal9
+Fix broken links. Add faq on hosts files. Move most of new windows service
+feature to user manual and reference in faq. Various other small changes.
+
+Revision 2.14 2006/09/05 13:25:12 david__schmidt
+Add Windows service invocation stuff (duplicated) in FAQ and in user manual under Windows startup. One probably ought to reference the other.
+
+Revision 2.13 2006/09/04 19:20:33 fabiankeil
+Adjusted anonymity related sections to match reality.
+Added a section about using Privoxy with Tor.
+
+Revision 2.12 2006/09/03 14:15:30 hal9
+Various updates, including 7 or 8 new FAQs, and updates/changes to various
+other ones to better reflect improvements, additions and changes for the
+upcoming release. This is close to final form for 3.0.4 IMHO.
+
+Revision 2.11 2006/07/18 14:48:50 david__schmidt
+Reorganizing the repository: swapping out what was HEAD (the old 3.1 branch)
+with what was really the latest development (the v_3_0_branch branch)
+
+Revision 1.61.2.41 2004/04/05 13:44:05 oes
+Fixed allow-all-cookies alias name; closes SR #929746
+
+Revision 1.61.2.40 2004/01/30 17:00:33 oes
+Added OSX Panther problem
+
+Revision 1.61.2.39 2004/01/29 22:53:08 hal9
+Minor changes for exempting docs of text/plain. Change copyright date.
+
+Revision 1.61.2.38 2003/12/10 03:39:45 hal9
+Added FAQs for: demoronizer, related problems and why its included. Also,
+port 8118 already in use questions, and PrivoxyWindowOpen() questions. All in
+troubleshooting section.
+
+Revision 1.61.2.37 2003/10/17 11:01:50 oes
+Added Q&A for "not being used" page problem
+
+Revision 1.61.2.36 2003/06/26 23:49:20 hal9
+More on the filter/source code problem.
+
+Revision 1.61.2.35 2003/06/26 13:38:08 hal9
+Add FAQ on whether configuring Privoxy is necessary or not.
+
+Revision 1.61.2.34 2003/06/26 03:00:03 hal9
+Sorry, found another copyright date.
+
+Revision 1.61.2.33 2003/06/26 02:57:05 hal9
+Fix typo (finally!) and very minor modifications.
+
+Revision 1.61.2.32 2003/06/26 02:52:04 hal9
+Test, no changes.
+
+Revision 1.61.2.31 2003/06/25 01:27:51 hal9
+Fix copyright, and a few nits.
+
+Revision 1.61.2.30 2003/06/25 01:13:52 hal9
+Add:
+
+ - FAQ on "Unable to get my own hostname"
+ - Another one on filtering effects on text files.
+
+Revision 1.61.2.29 2003/06/15 21:32:58 hal9
+Add to the 4.17 (filtering effects on downloaded files).
+
+Revision 1.61.2.28 2003/03/18 19:37:21 oes
+s/Advanced|Radical/Adventuresome/g to avoid complaints re fun filter
+
+Revision 1.61.2.27 2002/12/01 06:31:58 hal9
+Add faq on win32 error 503 due to ZoneAlarm.
+
+Revision 1.61.2.26 2002/11/17 06:41:06 hal9
+Move default profiles table from FAQ to U-M, and other minor related changes.
+Add faq on cookies.
+
+Revision 1.61.2.25 2002/10/29 03:21:50 hal9
+Add 3 Q/A's relating to HTML in email. Other minor touchups.
+
+Revision 1.61.2.24 2002/10/15 12:50:22 oes
+s/Advanced/Radical/ (stupid me)
+
+Revision 1.61.2.23 2002/10/15 12:38:56 oes
+Added Microsuck faq; more detail for PHP problem
+
+Revision 1.61.2.22 2002/10/12 01:13:13 hal9
+Updates for demoronizer, more commentary on Radical profile, and update on
+the srvany.exe/icon fix.
+
+Revision 1.61.2.21 2002/10/10 04:09:35 hal9
+s/Advanced/Radical/ and added very brief note.
+
+Revision 1.61.2.20 2002/09/26 01:22:45 hal9
+Small additions for LAN setup, content-cookies/SSL, and FTP non-support.
+
+Revision 1.61.2.19 2002/08/25 23:31:56 hal9
+Fix one grammatical error. Add brief FAQ relating to tranparent proxies (ie
+port 80 setting). Add FAQ on effects of Privoxy on downloaded files
+(especially filtering).
+
+Revision 1.61.2.18 2002/08/14 16:39:37 hal9
+Fix wrong tag on FAQ addition.
+
+Revision 1.61.2.17 2002/08/14 00:01:18 hal9
+Add a crunch FAQ.
+
+Revision 1.61.2.16 2002/08/13 00:10:38 hal9
+Add faq to troubleshooting re: blank page syndrome, ie {-prevent-compression}.
+
+Revision 1.61.2.15 2002/08/10 11:34:22 oes
+Add disclaimer about probably being out-of-date
+
+Revision 1.61.2.14 2002/08/07 02:53:43 hal9
+Fix some minor markup errors, and move one OSX Q/A to troubleshooting section.
+
+Revision 1.61.2.13 2002/08/06 11:55:32 oes
+Added missing close tag
+
+Revision 1.61.2.12 2002/08/06 11:43:46 david__schmidt
+Updated OSX uninstall FAQ... we have an uninstall script now.
+
+Revision 1.61.2.11 2002/08/06 08:54:03 oes
+Style police: Fixed formatting details
+
+Revision 1.61.2.10 2002/08/02 14:00:25 david__schmidt
+Made the OSX removal commands far less dangerous
+
+Revision 1.61.2.9 2002/08/02 13:14:45 oes
+Added warning about sudo rm -r for Mac OSX deinstallation; moved this item to install section
+
+Revision 1.61.2.8 2002/08/02 02:01:42 david__schmidt
+Add FAQ item for MSIE on OSX HTTP proxy confusion
+
+Revision 1.61.2.7 2002/08/02 01:46:01 david__schmidt
+Added FAQ item for Mac OSX uninstall woes
+
+Revision 1.61.2.6 2002/07/30 20:04:56 hal9
+Fix typo: 'schould'.
+
+Revision 1.61.2.5 2002/07/26 15:22:58 oes
+- Updated to reflect changes in standard.action
+- Added info on where to get updated actions files
+
+Revision 1.61.2.4 2002/07/25 21:42:29 hal9
+Add brief notes on not proxying non-HTTP protocols.
+
+Revision 1.61.2.3 2002/06/09 16:36:33 hal9
+Clarifications on filtering and MIME. Hardcode 'latest release' in index.html.
+
+Revision 1.61.2.2 2002/06/06 02:51:34 hal9
+Fix typo in URL http:/config.privoxy.org
+
+Revision 1.61.2.1 2002/06/05 23:10:43 hal9
+Add new FAQ re: DUN/IE. Change release date from May to June :)
+
+Revision 1.61 2002/05/25 12:37:25 hal9
+Various minor changes and edits.
+
+Revision 1.60 2002/05/22 17:17:48 oes
+Proofread & added more links into u-m
+
+Revision 1.59 2002/05/15 04:03:30 hal9
+Fix ulink -> link markup.
+
+Revision 1.58 2002/05/10 01:48:20 hal9
+This is mostly proposed copyright/licensing additions and changes. Docs
+are still GPL, but licensing and copyright are more visible. Also, copyright
+changed in doc header comments (eliminate references to JB except FAQ).
+
+Revision 1.57 2002/05/05 20:26:02 hal9
+Sorting out license vs copyright in these docs.
+
+Revision 1.56 2002/05/04 08:44:44 swa
+bumped version
+
+Revision 1.55 2002/05/04 00:41:56 hal9
+-Remove TOC/first page kludge in favor of proper handling via dsl file.
+
+Revision 1.54 2002/05/03 05:06:44 hal9
+Add brief Q/A on transparent proxies.
+
+Revision 1.53 2002/05/03 01:34:52 hal9
+Fix section numbering for new sections (due to TOC kludge).
+
+Revision 1.52 2002/04/29 03:08:43 hal9
+-Added new Q/A on new actions file set up (pointer to u-m)
+-Fixed a few broken links and converted old actions as a result of
+ recent changes.
+
+Revision 1.51 2002/04/26 17:24:31 swa
+bookmarks cleaned, changed structure of user manual, screen and programlisting cleanups, and numerous other changes that I forgot
+
+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.
+
+Revision 1.39 2002/04/03 03:53:03 hal9
+Revert some changes, and then make some news, to layout, and appearance.
+
+Revision 1.38 2002/04/02 03:49:10 hal9
+Major changes to doc structure and layout. Sections are not automatically
+numbered now. TOC is on page by itself.
+
Revision 1.37 2002/04/01 16:24:07 hal9
-Rework of supported Q/A.
-Set up entities to include boilerplate text.
projects / privoxy.git / blobdiff