+5.8. In Mac OSX Panther (10.3), images often fail to load and/or I experience
+random delays in page loading. I'm using localhost as my browser's proxy
+setting.
+
+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 127.0.0.1
+instead of localhost works around the problem.
+
+-------------------------------------------------------------------------------
+
+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 the network stack. 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 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 system configuration error. It is not a
+fatal error to Privoxy however, but may result in a much slower response from
+Privoxy due to DNS timeouts.
+
+-------------------------------------------------------------------------------
+
+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. 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, which was introduced in version
+3.0.2, and was inappropriately turned on by default. 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 a plain
+text file). 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.
+
+This filter was introduced with version 3.0.2 of Privoxy, and was on by default
+in that version. It is off in all subsequent versions (unless turned on by the
+user).
+
+-------------------------------------------------------------------------------
projects / privoxy.git / blobdiff