+ Copyright (C) 2001, 2002 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
+ anything in this, or other Privoxy documentation. You have been warned!
+ Failure to abide by this rule will result in the revocation of your license
+ to live a peaceful existence!
+ ========================================================================
+
+
+-->
+
+
+<article id="index" class="faq">
+<artheader>
+<title>Privoxy Frequently Asked Questions</title>
+
+<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, 2002 by
+ <ulink url="http://www.privoxy.org">Privoxy Developers</ulink>
+ </subscript>
+</pubdate>
+
+<pubdate>$Id: faq.sgml,v 1.60 2002/05/22 17:17:48 oes 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>
+ <orgname>By: Privoxy Developers</orgname>
+ </affiliation>
+ </author>
+</authorgroup>
+-->
+<abstract>
+<![%dummy;[
+<para>
+ <comment>
+ This is here to keep vim syntax file from breaking :/
+ If I knew enough to fix it, I would.
+ PLEASE DO NOT REMOVE! HB: hal@foobox.net
+ </comment>
+</para>
+]]>
+ <para>
+ This FAQ gives quick answers to frequently asked questions about
+ <ulink url="http://www.privoxy.org/">Privoxy</ulink>
+ <![%p-stable;[ v.&p-version]]>. It can't and doesn't replace the
+ <ulink url="../user-manual/index.html">user manual</ulink>.
+ </para>
+
+<!-- Include privoxy.sgml boilerplate: -->
+ &p-intro;
+<!-- end boilerplate -->
+
+ <para>
+ You can find the latest version of the document at <ulink
+ url="http://www.privoxy.org/faq/">http://www.privoxy.org/faq/</ulink>.
+ Please see the Contact section if you want to contact the developers.
+ </para>
+
+<!-- <para> -->
+<!-- Feel free to send a note to the developers at <email>ijbswa-developers@lists.sourceforge.net</email>. -->
+<!-- </para> -->
+</abstract>
+</artheader>
+
+
+<!-- ~~~~~ New section ~~~~~ -->
+
+<sect1 id="general"><title>General Information</title>
+
+<sect2 renderas="sect3" id="newjb"><title>What is this new version of <application>Privoxy</application>?</title>
+
+<!-- Include history.sgml -->
+ &history;
+<!-- end -->
+
+</sect2>
+
+
+<sect2 renderas="sect3">
+<title id="whyprivoxy">Why <quote>Privoxy</quote>? Why a name change at all?</title>
+<para>
+ <application>Privoxy</application> is the
+ <quote><emphasis>Privacy Enhancing Proxy</emphasis></quote>. Also, its content
+ modification and junk suppression allow you to browse your
+ <quote><emphasis>private</emphasis> edition</quote> of the web.
+</para>
+<para>
+ <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 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.
+</para>
+<para>
+ The developers also believed that there are so many changes from the original
+ code, that it was time to make a clean break from the past and make
+ a name in their own right<![%p-not-stable;[, especially now with the pending
+ release of version 3.0]]>.
+</para>
+</sect2>
+
+
+<sect2 renderas="sect3" id="differs"><title>How does <application>Privoxy</application> differ
+from the old <application>Junkbuster?</application></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.
+ </para>
+ <para>
+ 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/upgradersnote.html">note to
+ upgraders</ulink> for details.
+</para>
+<para>
+ <application>Privoxy</application>'s new features include:
+</para>
+
+<!-- Include newfeatures.sgml: -->
+ &newfeatures;
+<!-- end include -->
+
+</sect2>
+
+<sect2 renderas="sect3" id="proxymoron"><title>What is a <quote>proxy</quote>? How does
+<application>Privoxy</application> work? </title>
+ <para>
+ 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>
+ 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>
+ <application>Privoxy</application> is a proxy that is solely focused on privacy
+ protection and junk elimination. 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 renderas="sect3" id="whatsanad">
+<title id="knows">How does <application>Privoxy</application> know what is
+an ad, and what is not?</title>
+<para>
+ <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>
+ Both of this involves a certain amount of guesswork and is, of course, freely
+ configurable.
+</para>
+</sect2>
+
+<sect2 renderas="sect3">
+<title id="mistakes">Can <application>Privoxy</application> 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 or change 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.
+</para>
+
+<para>
+ But this should not be a big concern since the
+ <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 Troubleshooting section below</link>.)
+</para>
+
+</sect2>
+
+
+<sect2 renderas="sect3" id="browsers2"><title>My browser does the same things as
+<application>Privoxy</application>. Why should I use
+<application>Privoxy</application> at all?</title>
+ <para>
+ Modern browsers do indeed have <emphasis>some</emphasis> of the same
+ functionality as <application>Privoxy</application>. Maybe this is
+ adequate for you. But <application>Privoxy</application> is much more
+ versatile and powerful, and can do a number of things that browsers just can't.
+ </para>
+ <para>
+ In addition, a proxy is good choice if you use multiple browsers, or
+ 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 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 <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 <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 renderas="sect3" id="jointeam"><title>I would like to help you, what do I do?</title>
+
+<sect3 renderas="sect4" id="jointeam-money"><title>Money Money Money</title>
+<para>
+ 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:developers@privoxy.org">drop us a note</ulink>.
+</para>
+</sect3>
+
+<sect3 renderas="sect4" id="jointeam-software"><title>Software</title>
+<para>
+ 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>
+
+<sect3 renderas="sect4" id="jointeam-work"><title>You want to work with us?</title>
+<para>
+ Well, helping the team is always a good idea. We welcome new developers,
+ packaging gurus or documentation writers. Simply <ulink
+ url="https://sourceforge.net/account/register.php">get an account on SourceForge.net</ulink>
+ and mail your id to the <ulink url="mailto:developers@privoxy.org">developers
+ mailing list</ulink>. Then read the <ulink
+ url="../developer-manual/index.html">Developer's Manual</ulink>.
+</para>
+<para>
+ Once we have added you to the team, you'll have write 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>
+
+</sect2>
+
+</sect1>
+
+
+<!-- ~~~~~ New section ~~~~~ -->
+
+<sect1 id="installation"><title>Installation</title>
+
+<sect2 renderas="sect3" id="whichbrowsers">
+<title>Which browsers are supported by <application>Privoxy</application>?</title>
+<para>
+ Any browser that can be configured to use a proxy, which
+ should be virtually all browsers. Direct browser support is not necessary
+ 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 renderas="sect3" id="whichos">
+<title>Which operating systems are supported?</title>
+<!--
+Include supported.sgml here:
+-->
+&supported;
+</sect2>
+
+<sect2 renderas="sect3" id="newinstall"><title>Can I install
+ <application>Privoxy</application> over <application>Junkbuster</application>?</title>
+ <para>
+ 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
+ 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 un-install
+ <application>Junkbuster</application>, if present!
+ </para>
+
+</sect2>
+
+<sect2 renderas="sect3">
+<title id="firststep">I just installed <application>Privoxy</application>. 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.
+ You should also flush your browser's memory and disk cache to get rid of any
+ cached junk items.
+
+</para>
+
+</sect2>
+
+
+<sect2 renderas="sect3" id="localhost"><title>What is the proxy address of <application>Privoxy</application>?</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 <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> 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. 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.
+ </para>
+</sect2>
+
+<sect2 renderas="sect3">
+<title id="nothing">I just installed <application>Privoxy</application>, and nothing is happening.
+All the ads are there. What's wrong?</title>
+
+<para>
+ Did you configure your browser to use <application>Privoxy</application>
+ as a proxy? It does not sound like it. See above. You might also try flushing
+ 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:/config.privoxy.org/">http://config.privoxy.org/</ulink>.
+ 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>.
+
+
+</para>
+
+</sect2>
+
+</sect1>
+
+
+<!-- ~~~~~ New section ~~~~~ -->
+
+<sect1 id="configuration"><title>Configuration</title>
+
+<sect2 renderas="sect3" id="newconfig"><title>Can I use my old config files?</title>
+ <para>
+ The syntax, number, and purpose of configuration files has substantially
+ changed from <application>Junkbuster</application> and earlier versions
+ of <application>Privoxy</application>. The old files, like <filename>blocklist</filename>
+ will not work at all. If you are upgrading from a 2.0.x version, you will
+ need to port your configuration data to the new format. Note that even the
+ pattern syntax has changed! Even configuration files from the 2.9.x versions
+ will need to be adapted, as configuration syntax has been very much in flow
+ in the 2.9.x series.
+ </para>
+</sect2>
+
+<sect2 renderas="sect3">
+<title id="actionsfile">What is an <quote>actions</quote> file?</title>
+
+<para>
+ <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> might 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.
+</para>
+
+<para>
+ 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 renderas="sect3" id="actionss">
+<title>The <quote>actions</quote> concept confuses me. Please list
+some of these <quote>actions</quote>.</title>
+<para>
+ 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 renderas="sect3">
+<title id="actconfig">How are actions files configured? What is the easiest
+way to do this?</title>
+
+<para>
+ Actions files are just text files in a special syntax and can be edited
+ with a text editor. The probably 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>
+
+
+<!-- ~~~~~ New section ~~~~~ -->
+<sect2 renderas="sect3">
+<title>There are several different <quote>actions</quote> files. What are
+the differences?</title>
+<para>
+ 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>
+
+<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>
+
+</sect2>
+
+<sect2 renderas="sect3" id="yahoo"><title>How can I make my Yahoo/Hotmail/GMX account work?</title>
+ <para>
+ 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 renderas="sect3" id="configfiles"> <title>What's the difference between the
+<quote>Cautious</quote>, <quote>Medium</quote> and <quote>Advenced</quote> defaults?</title>
+ <para>
+ Configuring <application>Privoxy</application> is not entirely trivial. To help you get
+ started, we provide you with three different default action <quote>packages</quote> in
+ the web based actions file editor at <ulink
+ url="http://config.privoxy.org/show-status">http://config.privoxy.org/show-status</ulink>.
+ The following table shows you, which of the most important features are enabled in each
+ configuration:
+ </para>
+ <para>
+<table frame=all><title>Default Configurations</title>
+<tgroup cols=4 align=left colsep=1 rowsep=1>
+<colspec colname=c1>
+<colspec colname=c2>
+<colspec colname=c3>
+<colspec colname=c4>
+<thead>
+<row>
+ <entry>Feature</entry>
+ <entry>Cautious</entry>
+ <entry>Intermadiate</entry>
+ <entry>Advanced</entry>
+</row>
+</thead>
+<!-- <tfoot> -->
+<!-- <row> -->
+<!-- <entry>f1</entry> -->
+<!-- <entry>f2</entry> -->
+<!-- <entry>f3</entry> -->
+<!-- <entry>f4</entry> -->
+<!-- </row> -->
+<!-- </tfoot> -->
+<tbody>
+
+<row>
+ <entry>Ad-blocking by URL</entry>
+ <entry>yes</entry>
+ <entry>yes</entry>
+ <entry>yes</entry>
+</row>
+
+<row>
+ <entry>Ad-filtering by size</entry>
+ <entry>yes</entry>
+ <entry>yes</entry>
+ <entry>yes</entry>
+</row>
+
+<row>
+ <entry>GIF de-animation</entry>
+ <entry>no</entry>
+ <entry>yes</entry>
+ <entry>yes</entry>
+</row>
+
+<row>
+ <entry>Referer forging</entry>
+ <entry>no</entry>
+ <entry>yes</entry>
+ <entry>yes</entry>
+</row>
+
+<row>
+ <entry>Cookie handling</entry>
+ <entry>none</entry>
+ <entry>session-only</entry>
+ <entry>kill</entry>
+</row>
+
+<row>
+ <entry>Pop-up killing</entry>
+ <entry>no</entry>
+ <entry>no</entry>
+ <entry>yes</entry>
+</row>
+
+<row>
+ <entry>Fast redirects</entry>
+ <entry>no</entry>
+ <entry>no</entry>
+ <entry>yes</entry>
+</row>
+
+<row>
+ <entry>HTML taming</entry>
+ <entry>yes</entry>
+ <entry>yes</entry>
+ <entry>yes</entry>
+</row>
+
+<row>
+ <entry>JavaScript taming</entry>
+ <entry>yes</entry>
+ <entry>yes</entry>
+ <entry>yes</entry>
+</row>
+
+<row>
+ <entry>Web-bug killing</entry>
+ <entry>yes</entry>
+ <entry>yes</entry>
+ <entry>yes</entry>
+</row>
+
+<row>
+ <entry>Fun text replacements</entry>
+ <entry>no</entry>
+ <entry>no</entry>
+ <entry>yes</entry>
+</row>
+
+</tbody>
+</tgroup>
+</table>
+</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">user manual</ulink> for a more
+ deatiled discussion.
+</para>
+
+</sect2>
+
+<sect2 renderas="sect3" id="browseconfig"> <title>Why can I change the configuration
+with a browser? Does that not raise security issues?</title>
+ <para>
+ 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 <quote>privoxy</quote>,
+ it can update the config files.
+ </para>
+ <para>
+ 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 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 renderas="sect3">
+<title id="filterfile">What is the <filename>default.filter</filename> file?</title>
+<para>
+ The <ulink url="../user-manual/filter-file.html"><filename>default.filter</filename></ulink>
+ file is where <emphasis>filters</emphasis> are defined, which can be used to modify or
+ remove, web page content on the fly. This applies to <emphasis>anything</emphasis>
+ in the page source, 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>.
+</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 define
+ your own filters. This is potentially a very powerful feature, but
+ requires some expertise.
+</para>
+
+<para>
+ Presently, 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 renderas="sect3">
+<title id="lanconfig">How can I set up <application>Privoxy</application> to act as a proxy for my
+ LAN?</title>
+<para>
+ By default, <application>Privoxy</application> only responds to requests
+ 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
+ schould look like:
+</para>
+
+<para>
+ <screen>
+ listen-address 192.168.1.1:8118</screen>
+</para>
+
+<para>
+ Save the file, and restart <application>Privoxy</application>. Configure
+ all browsers on the network then to use this address and port number.
+</para>
+
+<para>
+ 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 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>
+ 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
+ erraneously blocked. Some people might also enjoy seeing how many banners
+ they <emphasis>don't</emphasis> have to see..
+</para>
+
+</sect2>
+
+<!-- This has changed with the adaptive "blocked" page
+
+<sect2 renderas="sect3">
+<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>
+<para>
+ These are URLs that match something in one of
+ <application>Privoxy's</application> block actions
+ (<ulink
+ url="../user-manual/actions-file.html#BLOCK"><quote>+block</quote></ulink>).
+ 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. ads that are GIF image
+ files). 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.
+</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
+ aribitrary 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. Such situations can be a little trickier to deal with, and
+ <application>Privoxy</application> may show the <quote>Blocked</quote> page,
+ despite your best efforts.
+</para>
+
+<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.
+</para>
+<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.
+</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>+set-image-blocker</quote> action
+ handle the ad that is embedded in the frame's HTML page.
+</para>
+
+</sect2>
+
+<sect2 renderas="sect3" id="alliseeisred">
+<title>I cannot see all of the <quote>Blocked</quote> page banner. Help.</title>
+<para>
+ There is not enough available space to fit the entire Blocked page. Try right
+ clicking on the visible 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.
+</para>
+<para>
+ As of Privoxy 2.9.14, the Blocked banner page is re-sizeable, and tries
+ to adjust to the allotted space. There may be occassions where there
+ just isn't enough room to display much of anything useful though.
+
+</para>
+</sect2>