-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
<HTML
><HEAD
><TITLE
>Troubleshooting</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
REL="HOME"
TITLE="Privoxy Frequently Asked Questions"
HREF="index.html"><LINK
HREF="contact.html"><LINK
REL="STYLESHEET"
TYPE="text/css"
-HREF="../p_doc.css"></HEAD
+HREF="../p_doc.css"><META
+HTTP-EQUIV="Content-Type"
+CONTENT="text/html;
+charset=ISO-8859-1"></HEAD
><BODY
CLASS="SECT1"
BGCOLOR="#EEEEEE"
><H3
CLASS="SECT2"
><A
-NAME="AEN801"
->5.1. I just upgraded and am getting <SPAN
+NAME="AEN1081"
+>5.1. I cannot connect to any websites. Or, I am getting
+<SPAN
CLASS="QUOTE"
>"connection refused"</SPAN
->
-with every web page?</A
+> message with every web page. Why?</A
></H3
><P
-> Either <SPAN
+> There are several possibilities:</P
+><P
+><P
+></P
+><UL
+><LI
+><P
+><SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
-> is not running, or your
- browser is configured for a different port than what
- <SPAN
+> is not running. Solution: verify
+ that <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
-> is using.</P
+> is installed correctly, has not crashed, and is indeed running.
+ Turn on <SPAN
+CLASS="APPLICATION"
+>Privoxy's</SPAN
+> logging, and look at the logs to see what they say.</P
+></LI
+><LI
><P
-> The old <SPAN
+>Or your browser is configured for a different port than what
+ <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
-> (and also
- <SPAN
+> is using. Solution: verify that <SPAN
CLASS="APPLICATION"
->Junkbuster</SPAN
->) 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 the <A
-HREF="../user-manual/config.html#LISTEN-ADDRESS"
-TARGET="_top"
-><VAR
-CLASS="LITERAL"
->listen-address</VAR
+>Privoxy</SPAN
>
- option</A
-> in <SPAN
-CLASS="APPLICATION"
->Privoxy's</SPAN
-> <A
-HREF="../user-manual/config.html"
-TARGET="_top"
->main configuration file</A
->.</P
+ and your browser are set to the same port (<TT
+CLASS="LITERAL"
+>listen-address</TT
+>).</P
+></LI
+><LI
+><P
+>Or if using a forwarding rule, you have a configuration problem or a
+ problem with a host in the forwarding chain. Solution: temporarily alter your
+ configuration and take the forwarders out of the equation.</P
+></LI
+><LI
+><P
+> Or you have a firewall that is interfering and blocking you. Solution:
+ try disabling or removing the firewall as a simple test.
+ </P
+></LI
+></UL
+></P
></DIV
><DIV
CLASS="SECT2"
><H3
CLASS="SECT2"
><A
-NAME="AEN814"
->5.2. I just added a new rule, but the steenkin ad is
+NAME="ERROR503"
+>5.2. Why am I getting a 503 Error (WSAECONNREFUSED) on every page?</A
+></H3
+><P
+> 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.
+ </P
+></DIV
+><DIV
+CLASS="SECT2"
+><H3
+CLASS="SECT2"
+><A
+NAME="AEN1104"
+>5.3. I just added a new rule, but the steenkin ad is
still getting through. How?</A
></H3
><P
CLASS="APPLICATION"
>Privoxy</SPAN
>
- will not be in the picture. The best thing to do is try flushing the browser's
- caches. And then try again.</P
+ will not be involved. Flush the browser's caches, and then try again.</P
><P
> 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 <A
TARGET="_top"
>http://config.privoxy.org/show-url-info</A
>
- and see if it really matches your new rule.</P
+ 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. And
+ remember you need to block the URL of the ad in question, which may be
+ entirely different from the site URL itself. Most ads are hosted on different
+ servers than the main site itself. If you right-click on the ad, you should
+ be able to get all the relevant information you need. Alternately, you can
+ find the correct URL by looking at <SPAN
+CLASS="APPLICATION"
+>Privoxy's</SPAN
+> logs
+ (you may need to enable logging in the main config file if its disabled).</P
+><P
+> Below is a slightly modified real-life log snippet that originates with one
+ requested URL: <TT
+CLASS="LITERAL"
+>www.example.com</TT
+> (name of site was changed
+ for this example, the number of requests is real). You can see in this the
+ complexity of what goes into making up this one <SPAN
+CLASS="QUOTE"
+>"page"</SPAN
+>. There
+ are eight different domains involved here, with thirty two separate URLs
+ requested in all, making up all manner of images, Shockwave Flash,
+ JavaScript, CSS stylesheets, scripts, and other related content. Some of this
+ content is obviously <SPAN
+CLASS="QUOTE"
+>"good"</SPAN
+> or <SPAN
+CLASS="QUOTE"
+>"bad"</SPAN
+>, but not all.
+ Many of the more questionable looking requests, are going to outside domains
+ that seem to be identifying themselves with suspicious looking names, making
+ our job a little easier. <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+> has <SPAN
+CLASS="QUOTE"
+>"crunched"</SPAN
+> (meaning caught
+ and BLOCKED) quite a few items in this example, but perhaps missed a few as well. </P
+><P
+><TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><PRE
+CLASS="SCREEN"
+>Request: www.example.com/
+Request: www.example.com/favicon.ico
+Request: img.example.com/main.css
+Request: img.example.com/sr.js
+Request: example.betamarker.com/example.html
+Request: www.lik-sang.com/Banners/bestsellers/skyscraper.php?likref=BSellers
+Request: img.example.com/pb.png
+Request: www.google-analytics.com/urchin.js crunch! (Blocked)
+Request: www.advertising-department.com/ats/switch.ps.php?26856 crunch! (Blocked)
+Request: img.example.com/p.gif
+Request: www.popuptraffic.com/assign.php?l=example&mode=behind crunch! (Blocked)
+Request: www.popuptraffic.com/scripts/popup.php?hid=5c3cf&tmpl=PBa.tmpl crunch! (Blocked)
+Request: www.popuptraffic.com/assign.php?l=example crunch! (Blocked)
+Request: www.lik-sang.com/Banners/best_sellers/best_sellers.css
+Request: www.adtrak.net/adx.js crunch! (Blocked)
+Request: img.example.com/hbg.gif
+Request: img.example.com/example.jpg
+Request: img.example.com/mt.png
+Request: img.example.com/mm.png
+Request: img.example.com/mb.png
+Request: www.popuptraffic.com/scripts/popup.php?hid=a71b91fa5&tmpl=Ua.tmp crunch! (Blocked)
+Request: www.example.com/tracker.js
+Request: www.lik-sang.com/Banners/best_sellers/lsi_head.gif
+Request: www.adtrak.net/adjs.php?n=020548130&what=zone:61 crunch! (Blocked)
+Request: www.adtrak.net/adjs.php?n=463594413&what=zone:58&source=Ua crunch! (Blocked)
+Request: www.lik-sang.com/Banners/best_sellers/bottomani.swf
+Request: mmm.elitemediagroup.net/install.php?allowpop=no&popupmincook=0&allowsp2=1 crunch! (Blocked)
+Request: www.example.com/tracker.js?screen=1400x1050&win=962x693
+Request: www.adtrak.net/adlog.php?bannerid=1309&clientid=439&zoneid=61 crunch! (Blocked)
+Request: 66.70.21.80/scripts/click.php?hid=5c3cf599a9efd0320d26&si
+Request: 66.70.21.80/img/pixel.gif
+Request: www.adtrak.net/adlog.php?bannerid=1309&clientid=439&zoneid=58&source=Ua&block=86400 crunch! (Blocked)
+Request: 66.70.21.80/scripts/click.php?hid=a71b9f6504b0c5681fa5&si=Ua</PRE
+></TD
+></TR
+></TABLE
+></P
+><P
+> Despite 12 out of 32 requests being blocked, the page looked, and seemed to
+ behave perfectly <SPAN
+CLASS="QUOTE"
+>"normal"</SPAN
+> (minus some ads, of course).</P
></DIV
><DIV
CLASS="SECT2"
CLASS="SECT2"
><A
NAME="BADSITE"
->5.3. One of my favorite sites does not work with <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
->.
+>5.4. One of my favorite sites does not work with Privoxy.
What can I do?</A
></H3
><P
HREF="http://config.privoxy.org/toggle"
TARGET="_top"
>http://config.privoxy.org/toggle</A
->,
+>
+ (the toggle feature may need to be enabled in the main
+ <TT
+CLASS="FILENAME"
+>config</TT
+>),
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).</P
><P
-> If still a problem, go to <A
+> If the problem went away, we know we have a configuration related problem.
+ Now go to <A
HREF="http://config.privoxy.org/show-url-info"
TARGET="_top"
>http://config.privoxy.org/show-url-info</A
>
- 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 <A
+ 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. It might be helpful also to look at your logs
+ for this site too, to see what else might be happening (note: logging may need
+ to be enabled in the main config file). Many sites are
+ complex and require a number of related pages to help present their content.
+ Look at what else might be used by the page in question, and what of that
+ might be <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>required</I
+></SPAN
+>.
+ Now, armed with this information, go to
+ <A
HREF="http://config.privoxy.org/show-status"
TARGET="_top"
>http://config.privoxy.org/show-status</A
>
- and select the appropriate actions files for editing.</P
+ and select the appropriate actions files for editing. </P
><P
> 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,
> 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 <VAR
+ site to a <TT
CLASS="LITERAL"
->{ fragile }</VAR
+>{ fragile }</TT
> section in <TT
CLASS="FILENAME"
>user.action</TT
> Troubleshooting actions is discussed in more detail in the <A
HREF="../user-manual/appendix.html#ACTIONSANAT"
TARGET="_top"
->user-manual appendix</A
+>User Manual appendix,
+ Troubleshooting: the Anatomy of an Action</A
>.
There is also an <A
HREF="../user-manual/actions-file.html#ACT-EXAMPLES"
TARGET="_top"
>actions tutorial</A
->.</P
+>
+ with general configuration information and examples.</P
+><P
+> As a last resort, you can always see if your browser has a setting that will
+ bypass the proxy setting for selective sites. Modern browsers can do this.</P
></DIV
><DIV
CLASS="SECT2"
CLASS="SECT2"
><A
NAME="DUN"
->5.4. After installing <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
->, I have to log in
+>5.5. After installing Privoxy, I have to log in
every time I start IE. What gives?</A
></H3
><P
CLASS="SECT2"
><A
NAME="FTP"
->5.5. I cannot connect to any FTP sites. <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
->
- seems to be blocking me.</A
+>5.6. I cannot connect to any FTP sites. Privoxy
+ is blocking me.</A
></H3
><P
> <SPAN
><I
CLASS="EMPHASIS"
>any protocol other than HTTP
- or HTTPS</I
+ or HTTPS (SSL)</I
></SPAN
>.
</P
><P
> Most browsers understand FTP as well as HTTP. If you connect to a site, with
- a URL like <VAR
+ a URL like <TT
CLASS="LITERAL"
->ftp://ftp.example.com</VAR
+>ftp://ftp.example.com</TT
>, your browser is making
an FTP connection, and not a HTTP connection. So while your browser may
speak FTP, <SPAN
CLASS="QUOTE"
>"proxy"</SPAN
>
- setting, which will silently enable <SPAN
+ setting, which will enable various protocols, including
+ <SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>both</I
></SPAN
-> HTTP and FTP
- proxying! So it is possible to accidentally enable FTP proxying in these
- cases. And of course, if this happens, <SPAN
+> HTTP and FTP proxying! So it is possible to
+ accidentally enable FTP proxying in these cases. And of course, if this
+ happens, <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
->
- will indeed cause problems since it does not know FTP.
+> will indeed cause problems since
+ it does not know FTP. Newer version will give a sane error
+ message if a FTP connection is attempted. Just disable the FTP setting
+ and all will be well again.
</P
><P
> Will <SPAN
><H3
CLASS="SECT2"
><A
-NAME="OSXIE"
->5.6. In Mac OSX, I can't configure Microsoft Internet Explorer to use
- <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
-> as the HTTP proxy.</A
+NAME="MACOSXIE"
+>5.7. In Mac OS X, I can't configure Microsoft Internet Explorer to use
+ Privoxy as the HTTP proxy.</A
></H3
><P
> 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 <VAR
+ is checked and enter <TT
CLASS="LITERAL"
->127.0.0.1</VAR
+>127.0.0.1</TT
> in the entry field.
- Enter <VAR
+ Enter <TT
CLASS="LITERAL"
->8118</VAR
+>8118</TT
> in the Port field. The next time you start
IE, it should reflect these values.
</P
><H3
CLASS="SECT2"
><A
-NAME="OSXUNINSTALL"
->5.7. In Mac OSX, I dragged the Privoxy folder to the trash in order to
+NAME="MACOSXUNINSTALL"
+>5.8. In Mac OS X, 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.</A
></H3
><P
-> Just dragging the <SPAN
+> Note: This ONLY applies to privoxy 3.0.6 and earlier.
+ </P
+><P
+> Just dragging the <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
> folder to the trash is
><H3
CLASS="SECT2"
><A
-NAME="OSXIMAGES"
->5.8. In Mac OSX Panther (10.3), images often fail to load and/or I
+NAME="MACOSXIMAGES"
+>5.9. In Mac OS X Panther (10.3), images often fail to load and/or I
experience random delays in page loading. I'm using
- <VAR
+ <TT
CLASS="LITERAL"
->localhost</VAR
+>localhost</TT
> as my browser's proxy setting.</A
></H3
><P
-> We believe this is due to an IPv6-related bug in OSX, but don't fully
+> We believe this is due to an IPv6-related bug in Mac OS X, but don't fully
understand the issue yet. In any case, changing the proxy setting to
- <VAR
+ <TT
CLASS="LITERAL"
->127.0.0.1</VAR
-> instead of <VAR
+>127.0.0.1</TT
+> instead of <TT
CLASS="LITERAL"
->localhost</VAR
+>localhost</TT
>
works around the problem.
</P
CLASS="SECT2"
><A
NAME="BLANKPAGE"
->5.9. I get a completely blank page at one site. <SPAN
+>5.10. I get a completely blank page at one site. <SPAN
CLASS="QUOTE"
>"View Source"</SPAN
>
CLASS="MARKUP"
><html><body></body></html></SPAN
>. Without
- <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
-> the page loads fine.</A
+ Privoxy the page loads fine.</A
></H3
><P
> Chances are that the site suffers from a bug in
</P
><P
> To find out if this is in fact the source of the problem, try adding
- the site to a <VAR
+ the site to a <TT
CLASS="LITERAL"
->-prevent-compression</VAR
+>-prevent-compression</TT
> section in
<TT
CLASS="FILENAME"
><H3
CLASS="SECT2"
><A
-NAME="ERROR503"
->5.10. Why am I getting a 503 Error (WSAECONNREFUSED) on every page?</A
-></H3
-><P
-> 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.
- </P
-></DIV
-><DIV
-CLASS="SECT2"
-><H3
-CLASS="SECT2"
-><A
NAME="NOHOSTNAME"
>5.11. My logs show many <SPAN
CLASS="QUOTE"
>Privoxy</SPAN
> logs this condition. </P
><P
-> Typically, this would be considered a system configuration error. It is not a
- fatal error to <SPAN
+> Typically, this would be considered a minor system configuration error. It is
+ not a fatal error to <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
-> however, but may result in
- a much slower response from <SPAN
+> however, but may
+ result in a much slower response from <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
-> due to DNS
- timeouts.</P
+> on
+ some platforms due to DNS timeouts.</P
+><P
+> This can be caused by a problem with the local <TT
+CLASS="FILENAME"
+>HOSTS</TT
+>
+ file. If this file has been changed from the original, try reverting it to
+ see if that helps. Make sure whatever name(s) are used for the local system,
+ that they resolve both ways.</P
></DIV
><DIV
CLASS="SECT2"
CLASS="SECT2"
><A
NAME="INUSE"
->5.12. When I try to launch <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
->, I get an
+>5.12. When I try to launch Privoxy, I get an
error message <SPAN
CLASS="QUOTE"
>"port 8118 is already in use"</SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
> running, and
- you are actually trying to start a second <SPAN
+ your system is actually trying to start a second
+ <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
->
- 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.</P
+> 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.</P
></DIV
><DIV
CLASS="SECT2"
> This is caused by the <SPAN
CLASS="QUOTE"
>"demoronizer"</SPAN
-> filter, which was introduced
- in version 3.0.2, and was inappropriately turned on by default. You should
- either upgrade <SPAN
+> filter. You should either
+ upgrade <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
->, or at least upgrade to the most
+>, or at least upgrade to the most
recent <TT
CLASS="FILENAME"
>default.action</TT
-> file available from
- <A
+> file available from <A
HREF="http://sourceforge.net/project/showfiles.php?group_id=11118"
TARGET="_top"
>SourceForge</A
CLASS="SECT2"
><A
NAME="DEMORONIZER2"
->5.14. Why are binary files (such as images) corrupted when <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
->
+>5.14. Why are binary files (such as images) corrupted when Privoxy
is used?</A
></H3
><P
CLASS="QUOTE"
>"demoronizer"</SPAN
> filter,
- in conjunction with a web server that is misreporting a file type. Binary
+ in conjunction with a web server that is misreporting the content type. Binary
files are exempted from <SPAN
CLASS="APPLICATION"
>Privoxy's</SPAN
> filtering
- (unless the web server by mistake says the file is a plain text file). Either
+ (unless the web server by mistake says the file is something else). Either
upgrade <SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
>.</P
><P
> On the other hand, if you use non-Microsoft products, and you occasionally
- notice wierd characters on pages, you might want to try it.</P
-><P
-> This filter was introduced with version 3.0.2 of <SPAN
-CLASS="APPLICATION"
->Privoxy</SPAN
->,
- and was on by default in that version. It is off in all subsequent versions
- (unless turned on by the user).</P
+ notice weird characters on pages, you might want to try it.</P
></DIV
><DIV
CLASS="SECT2"
CLASS="APPLICATION"
>Privoxy</SPAN
> is attempting to disable malicious
- Javascript in this case, with the <VAR
+ <A
+HREF="http://en.wikipedia.org/wiki/Javascript"
+TARGET="_top"
+>Javascript</A
+>
+ in this case, with the <TT
CLASS="LITERAL"
->unsolicited-popups</VAR
+>unsolicited-popups</TT
>
filter. <SPAN
CLASS="APPLICATION"
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.</P
></DIV
+><DIV
+CLASS="SECT2"
+><H3
+CLASS="SECT2"
+><A
+NAME="DNSERRORS"
+>5.17. I am getting too many DNS errors like <SPAN
+CLASS="QUOTE"
+>"404 No Such Domain"</SPAN
+>. Why
+ can't Privoxy do this better?</A
+></H3
+><P
+> There are potentially several factors here. First of all, the DNS resolution
+ is done by the underlying operating system -- not
+ <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+> itself. <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+>
+ 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 <SPAN
+CLASS="QUOTE"
+>"www."</SPAN
+> to the URL).</P
+><P
+> In other cases, if <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+> is being chained
+ with another proxy, this could complicate the issue, and cause undue
+ delays and timeouts. In the case of a <SPAN
+CLASS="QUOTE"
+>"socks4a"</SPAN
+> proxy, the socks
+ server handles all the DNS. <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+> would just be
+ the <SPAN
+CLASS="QUOTE"
+>"messenger"</SPAN
+> which is reporting whatever problem occurred
+ downstream, and not the root cause of the error.</P
+><P
+> In any case, versions newer than 3.0.3 include various improvements to help
+ <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+> better handle these cases.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><H3
+CLASS="SECT2"
+><A
+NAME="ALLCPU"
+>5.18. At one site Privoxy just hangs, and starts taking
+ all CPU. Why is this?</A
+></H3
+><P
+> This is probably a manifestation of the <SPAN
+CLASS="QUOTE"
+>"100% cpu"</SPAN
+> 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 <SPAN
+CLASS="APPLICATION"
+>Privoxy's</SPAN
+> 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
+ <TT
+CLASS="LITERAL"
+>js-annoyances</TT
+> and <TT
+CLASS="LITERAL"
+>unsolicited-popups</TT
+>
+ filters.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><H3
+CLASS="SECT2"
+><A
+NAME="SLOWCRAWL"
+>5.19. I just installed Privoxy, and all my
+browsing has slowed to a crawl. What gives?</A
+></H3
+><P
+> 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.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><H3
+CLASS="SECT2"
+><A
+NAME="PREVENTCOMP"
+>5.20. Why do my filters work on some sites but not on others?</A
+></H3
+><P
+> It's probably due to compression. It is a common practice for web servers to
+ send their content <SPAN
+CLASS="QUOTE"
+>"compressed"</SPAN
+> in order to speed things up, and
+ then let the browser <SPAN
+CLASS="QUOTE"
+>"uncompress"</SPAN
+> them. When compiled with zlib support
+ <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+> can decompress content before filtering, otherwise you may want to enable
+<A
+HREF="../user-manual/actions-file.html#PREVENT-COMPRESSION"
+TARGET="_top"
+>prevent-compression</A
+>.</P
+></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
projects / privoxy.git / blobdiff