+5.9. I get a completely blank page at one site. "View Source" shows only:
+<html><body></body></html>. Without Privoxy the page loads fine.
+
+Chances are that the site suffers from a bug in PHP, which results in empty
+pages being sent if the client explicitly requests an uncompressed page, like
+Privoxy does. This bug has been fixed in PHP 4.2.3.
+
+To find out if this is in fact the source of the problem, try adding the site
+to a -prevent-compression section in user.action:
+
+ # Make exceptions for ill-behaved sites:
+ #
+ {-prevent-compression}
+ .example.com
+
+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).
+
+-------------------------------------------------------------------------------
+
+5.10. Why am I getting a 503 Error (WSAECONNREFUSED) on every page?
+
+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.
+
+-------------------------------------------------------------------------------
+
+5.11. My logs show many "Unable to get my own hostname" lines. Why?
+
+Privoxy 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 config file
+listen-address setting). If the system cannot supply this information, Privoxy
+logs this condition.
+
+Typically, this would be considered a minor system configuration error. It is
+not a fatal error to Privoxy however, but may result in a much slower response
+from Privoxy on some platforms due to DNS timeouts.
+
+This can be caused by a problem with the local HOSTS file. If this file has
+been changed from the original, try reverting it to see if that helps.
+
+-------------------------------------------------------------------------------
+
+5.12. When I try to launch Privoxy, I get an error message "port 8118 is
+already in use" (or similar wording). Why?
+
+Port 8118 is Privoxy's default TCP "listening" port. Typically this message
+would mean that there is already one instance of Privoxy running, and you are
+actually trying to start a second Privoxy 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.
+
+-------------------------------------------------------------------------------
+
+5.13. Pages with UTF-8 fonts are garbled.
+
+This is caused by the "demoronizer" filter. You should either upgrade Privoxy,
+or at least upgrade to the most recent default.action file available from
+SourceForge. Or you can simply disable the demoronizer filter.
+
+-------------------------------------------------------------------------------
+
+5.14. Why are binary files (such as images) corrupted when Privoxy is used?
+
+This may also be caused by the "demoronizer" filter, in conjunction with a web
+server that is misreporting a file type. Binary files are exempted from
+Privoxy's filtering (unless the web server by mistake says the file is
+something else). Either upgrade Privoxy, or go to the most recent
+default.action file available from SourceForge.
+
+-------------------------------------------------------------------------------
+
+5.15. What is the "demoronizer" and why is it there?
+
+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. Privoxy borrowed from this script,
+introducing a filter based on the original demoronizer, which in turn could
+correct these errors on the fly.
+
+But this is only needed in some situations, and will cause serious problems in
+some other situations.
+
+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 should not be on.
+
+On the other hand, if you use non-Microsoft products, and you occasionally
+notice wierd characters on pages, you might want to try it.
+
+-------------------------------------------------------------------------------
+
+5.16. Why do I keep seeing "PrivoxyWindowOpen()" in raw source code?
+
+Privoxy is attempting to disable malicious Javascript in this case, with the
+unsolicited-popups filter. Privoxy cannot tell very well "good" code snippets
+from "bad" code snippets.
+
+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.
+
+-------------------------------------------------------------------------------
+
+5.17. I am getting too many DNS errors like "404 No Such Domain". Why can't
+Privoxy do this better?
+
+There are potentially several factors here. First of all, the DNS resolution is
+done by the underlying operating system -- not Privoxy itself. Privoxy 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 "www."
+to the URL). In other cases, if Privoxy is being chained with another proxy,
+this could complicate the issue, and cause undue delays and timeouts. In the
+case of a "socks4a" proxy, the socks server handles all the DNS. Privoxy would
+just be the "messenger" which is reporting whatever problem occurred
+downstream, and not the root cause of the error.
+
+In any case, v. 3.0.5 includes various improvements to help Privoxy better
+handle these cases.
+
+-------------------------------------------------------------------------------
+
+5.18. At one site Privoxy just hangs, and starts taking all CPU. Why is this?
+
+This is probably a manifestation of the "100% cpu" 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 Privoxy's 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 js-annoyances and unsolicited-popups
+filters.
+
+-------------------------------------------------------------------------------
+
+5.19. I just installed Privoxy, and all my browsing has slowed to a crawl. What
+gives?
+
+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.
+
+-------------------------------------------------------------------------------
+
+6. Contacting the developers, Bug Reporting and Feature Requests
+
+We value your feedback. In fact, we rely on it to improve Privoxy and its
+configuration. However, please note the following hints, so we can provide you
+with the best support:
+
+-------------------------------------------------------------------------------
+
+6.1. Get Support
+
+For casual users, our support forum at SourceForge is probably best suited:
+http://sourceforge.net/tracker/?group_id=11118&atid=211118
+
+All users are of course welcome to discuss their issues on the users mailing
+list, where the developers also hang around.
+
+-------------------------------------------------------------------------------
+
+6.2. Reporting Problems
+
+"Problems" for our purposes, come in two forms:
+
+ * Configuration issues, such as ads that slip through, or sites that don't
+ function properly due to one Privoxy "action" or another being turned "on".
+
+ * "Bugs" in the programming code that makes up Privoxy, such as that might
+ cause a crash.
+
+-------------------------------------------------------------------------------
+
+6.2.1. Reporting Ads or Other Configuration Problems
+
+Please send feedback on ads that slipped through, innocent images that were
+blocked, sites that don't work properly, and other configuration related
+problem of default.action file, to http://sourceforge.net/tracker/?group_id=
+11118&atid=460288, the Actions File Tracker.
+
+New, improved default.action files may occasionally be made available based on
+your feedback. These will be announced on the ijbswa-announce list and
+available from our the files section of our project page.
+
+-------------------------------------------------------------------------------
+
+6.2.2. Reporting Bugs
+
+Please report all bugs only through our bug tracker: http://sourceforge.net/
+tracker/?group_id=11118&atid=111118.
+
+Before doing so, please make sure that the bug has not already been submitted
+and observe the additional hints at the top of the submit form. If already
+submitted, please feel free to add any info to the original report that might
+help to solve the issue.
+
+Please try to verify that it is a Privoxy bug, and not a browser or site bug
+first. If unsure, try toggling off Privoxy, and see if the problem persists. If
+you are using your own custom configuration, please try the stock configs to
+see if the problem is configuration related.
+
+If not using the latest version, the bug may have been found and fixed in the
+meantime. We would appreciate if you could take the time to upgrade to the
+latest version (or even the latest CVS snapshot) and verify your bug.
+
+Please be sure to provide the following information:
+
+ * The exact Privoxy version of the proxy software (if you got the source from
+ CVS, please also provide the source code revisions as shown in http://
+ config.privoxy.org/show-version).
+
+ * The operating system and versions you run Privoxy on, (e.g. Windows XP
+ SP2), if you are using some kind of Unix flavour, sending the output of
+ "uname -a" should do.
+
+ * The name, platform, and version of the browser you were using (e.g.
+ Internet Explorer v5.5 for Mac).
+
+ * The URL where the problem occurred, or some way for us to duplicate the
+ problem (e.g. http://somesite.example.com/?somethingelse=123).
+
+ * Whether your version of Privoxy is one supplied by the developers of
+ Privoxy via SourceForge, or somewhere else.
+
+ * Whether you are using Privoxy in tandem with another proxy such as Tor. If
+ so, please try disabling the other proxy.
+
+ * Whether you are using a personal firewall product. If so, does Privoxy work
+ without it?
+
+ * Any other pertinent information to help identify the problem such as config
+ or log file excerpts (yes, you should have log file entries for each action
+ taken).
+
+ * Please provide your SF login, or email address, in case we need to contact
+ you.
+
+The appendix of the Privoxy User Manual also has helpful information on
+understanding actions, and action debugging.
+
+-------------------------------------------------------------------------------
+
+6.3. Request New Features
+
+You are welcome to submit ideas on new features or other proposals for
+improvement through our feature request tracker at http://sourceforge.net/
+tracker/?atid=361118&group_id=11118.
+
+-------------------------------------------------------------------------------
+
+6.4. Other
+
+For any other issues, feel free to use the mailing lists. Technically
+interested users and people who wish to contribute to the project are also
+welcome on the developers list! You can find an overview of all Privoxy-related
+mailing lists, including list archives, at: http://sourceforge.net/mail/?
+group_id=11118.
+
+-------------------------------------------------------------------------------
+
+7. Privoxy Copyright, License and History
+
+Copyright © 2001 - 2006 by Privoxy Developers <
+ijbswa-developers@lists.sourceforge.net>
+
+Some source code is based on code Copyright © 1997 by Anonymous Coders and
+Junkbusters, Inc. and licensed under the GNU General Public License.
+
+Portions of this document are "borrowed" from the original Junkbuster (tm) FAQ,
+and modified as appropriate for Privoxy.
+
+-------------------------------------------------------------------------------
+
+7.1. License
+
+Privoxy is free software; you can redistribute it and/or modify it under the
+terms of the GNU General Public License, version 2, as published by the Free
+Software Foundation.
+
+This program is distributed in the hope that it will be useful, but WITHOUT ANY
+WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A
+PARTICULAR PURPOSE. See the GNU General Public License for more details, which
+is available from the Free Software Foundation, Inc, 51 Franklin Street, Fifth
+Floor, Boston, MA 02110-1301, USA
+
+You should have received a copy of the GNU General Public License along with
+this program; if not, write to the
+
+ Free Software
+ Foundation, Inc. 51 Franklin Street, Fifth Floor
+ Boston, MA 02110-1301
+ USA
+
+-------------------------------------------------------------------------------