Privoxy as HTTP and - HTTPS (SSL) proxy by setting the proxy configuration for address of + HTTPS (SSL) proxy + by setting the proxy configuration for address of 127.0.0.18118. - (Junkbuster and earlier versions of Privoxy used port 8000.) See the section Starting Privoxy below - for more details on this. +CLASS="emphasis" +>DO NOT activate proxying for FTP or + any protocols besides HTTP and HTTPS (SSL)! It won't work!
If you experience ads that slipped through, innocent images that are +> If you experience ads that slip through, innocent images that are blocked, or otherwise feel the need to fine-tune Privoxy's behaviour, take a look at the behavior, take a look at the actions files. As a quick start, you might @@ -207,10 +220,10 @@ TARGET="_top" CLASS="QUOTE" >"Anatomy of an +>Troubleshooting: Anatomy of an Action" has hints how to debug actions that +> has hints on how to understand and debug actions that "misbehave"
For easy access to Privoxy's most important controls, drag the provided +> For easy access to Privoxy's most important controls, drag the provided BookmarkletsContacting the Developers on how to report bugs or problems with websites or to get +> on how to report bugs, problems with websites or to get help.
First a bit of a warning ... blocking ads is much like blocking SPAM: the more aggressive you are about it, the more likely you are to block - things that were not intended. So there is a trade off here. If you want + things that were not intended. And the more likely that some things + may not work as intended. So there is a trade off here. If you want extreme ad free browsing, be prepared to deal with more Privoxy to perform - some task relating to HTTP transactions (i.e. web browsing). We tell + some task relating to WWW transactions (i.e. web browsing). We tell PrivoxyPrivoxy can deal with each URL individually, so, for + instance, the main page text is not touched, but images from such-and-such + server are blocked.
The actions we need to know about for ad blocking are: The most important actions for basic ad blocking are: handle-as-image, and +>, + handle-as-empty-document,and block - this action stops - any contact between your browser and any URL patterns that match this - action's configuration. It can be used for blocking ads, but also anything - that is determined to be unwanted. By itself, it simply stops any - communication with the remote server and sends - this is perhaps + the single most used action, and is particularly important for ad blocking. + This action stops any contact between your browser and any URL patterns + that match this action's configuration. It can be used for blocking ads, + but also anything that is determined to be unwanted. By itself, it simply + stops any communication with the remote server and sends + Privoxy's - own built-in BLOCKED page instead to let you now what has happened. +>'s own built-in BLOCKED page instead to + let you now what has happened (with some exceptions, see below).
There are also various + filters that can be used for ad blocking + (filters are a special subset of actions). These + fall into the "advanced" usage category, and are explained in + depth in later sections.