+
+
+<sect2 renderas="sect3" id="loadingtimes"><title>I noticed 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".
+ </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.
+</para>
+</sect2>
+
+
+<sect2 renderas="sect3" id="configurl"><title>What is the "http://p.p/"?</title>
+<para>
+Since <application>Privoxy</application> sits between your web browser and the Internet, it can be
+programmed to handle certain pages specially.
+</para>
+
+<para>
+With recent versions of <application>Privoxy</application> (version 2.9.x), you can get some
+information about <application>Privoxy</application> and change some settings by going to
+<ulink url="http://p.p/">http://p.p/</ulink> or, equivalently, <ulink url="http://config.privoxy.org/">http://config.privoxy.org/</ulink>
+(Note that p.p is far easier to type but may not work in some
+configurations. With the name change to <application>Privoxy</application>,
+this is changed from the previous http://i.j.b/ or earlier 2.9.x versions).
+</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>.
+</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>.
+</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 &p-version;).
+</para>
+</sect2>
+
+<!--
+FIXME: commented out until we have data. HB 03/18/02.
+
+<sect2 renderas="sect3" id="badfiledesc"><title>I get the message 'Bad File Descriptor', why?</title>
+<para>
+ Fillme.
+</para>
+</sect2>
+
+<sect2 renderas="sect3" id="proxy-chaining"><title>How do I chain <application>Privoxy</application> with other proxies
+(e.g. squid)?</title>
+<para>
+ Fillme.
+</para>
+</sect2>
+-->
+
+<sect2 renderas="sect3" id="blocklist"><title>Do you still maintain the blocklists?</title>
+<para>
+ No. The format of the blocklists has changed significantly in versions
+ 2.9.x and later. <![%p-not-stable;[Once we have released the new stable
+ version, v3.0, there will again be blocklists that you can update
+ automatically.]]>
+</para>
+</sect2>
+
+<sect2 renderas="sect3" id="newads"><title>How can I submit new ads?</title>
+<para>
+ As of now, please discontinue to submit new ad blocking infos. Once we
+ have released the new version, there will again be a form on the website,
+ which you can use to contribute new ads.
+</para>
+</sect2>
+
+<sect2 renderas="sect3" id="ip"><title>How can I hide my IP address?</title>
+<para>
+ You cannot hide your IP address with <application>Privoxy</application> or any other software, since
+the server needs to know your IP address to send the answer to you.
+</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.
+</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.
+</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.
+</para>
+</sect2>
+
+<!-- <sect2 renderas="sect3" 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 renderas="sect3">
+<title id="anonforsure">Can <application>Privoxy</application> 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.
+</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, and what details you want to reveal. But it's still possible
+ that web sites can find out who you are. Here's one way this can happen.
+</para>
+<para>
+ A few browsers disclose the user's email address in certain situations, such
+ as when transferring a file by FTP. <application>Privoxy</application>
+ does not filter FTP. If you need this feature, or are concerned about the
+ mail handler of your browser disclosing your email address, you might
+ consider products such as <application>NSClean</application>.
+</para>
+<para>
+ Browsers available only as binaries could use non-standard headers to give
+ out any information they can have access to: see the manufacturer's license
+ agreement. It's impossible to anticipate and prevent every breach of privacy
+ that might occur. The professionally paranoid prefer browsers available as
+ source code, because anticipating their behavior is easier. Trust the source,
+ Luke!
+</para>
+
+</sect2>
+
+<sect2 renderas="sect3">
+<title id="sitebreak">Might some things break because header information is
+being altered?</title>
+
+<para>
+ Definitely. More and more sites use HTTP header content to decide what to
+ display and how to display it. There is many ways that this can be handled,
+ so having hard and fast rules, is tricky.
+</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.
+</para>
+
+<para>
+ For instance, different browsers use different encodings of Russian and Czech
+ characters, certain web servers convert pages on-the-fly according to the
+ User Agent header. Giving a <quote>User Agent</quote> with the wrong
+ 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
+ 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.
+</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 renderas="sect3">
+<title id="caching">Can <application>Privoxy</application> 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>.
+</para>
+</sect2>
+
+<sect2 renderas="sect3">
+<title id="firewall">What about as a firewall? Can <application>Privoxy</application> 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.
+</para>
+</sect2>
+
+
+<sect2 renderas="sect3">
+<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>
+
+<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.
+</para>
+<para>
+Given the above problem, we have decided to remove the logo option entirely
+[as of v2.9.13].
+</para>
+</sect2>
+
+
+<sect2 renderas="sect3">
+<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.
+</para>
+
+</sect2>
+
+<sect2 renderas="sect3">
+<title id="ssl">How can <application>Privoxy</application> filter Secure (HTTPS) URLs?</title>
+<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.
+</para>
+
+</sect2>
+
+
+<sect2 renderas="sect3">
+<title id="secure"><application>Privoxy</application> 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
+ <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
+ <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.
+</para>
+
+</sect2>
+
+<sect2 renderas="sect3" id="turnoff">
+<title>How can I temporarily disable <application>Privoxy</application>?</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.
+
+</para>
+</sect2>
+
+<sect2 renderas="sect3" id="seealso">
+<title>Where can I find more information about <application>Privoxy</application>
+and related issues?</title>
+<!-- Include seealso.sgml boilerplate: -->
+ &seealso;
+<!-- end boilerplate -->
+
+<!--
+<para>
+ Please see the
+ <ulink url="../user-manual/seealso.html">user-manual</ulink> for
+ others references.
+</para>
+-->
+</sect2>
+