"Filtering" content via the filter or deanimate-gifs actions may cause a perceived slowdown, since the entire document needs to be buffered before displaying. See below.
If you use any filter action, such as filtering banners by size, web-bugs etc, or the deanimate-gifs action, the entire document must be loaded into memory in order for the filtering mechanism to work, and nothing 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". This effect is especially noticeable on slow dialup connections.
Filtering is automatically disabled for inappropriate MIME types.
http://config.privoxy.org/ is the address of Privoxy's built-in user interface, and http://p.p/ is a shortcut for it.
Since Privoxy sits between your web browser and the Internet, it can simply intercept requests for these addresses and answer them with its built-in "web server".
This also makes for a good test for your browser configuration: If entering the URL http://config.privoxy.org/ takes you to a page saying "This is Privoxy..", everything is OK. If you get a page saying "Privoxy is not working" instead, then your browser didn't use Privoxy for the request, hence it could not be intercepted, and you have accessed the real web site at config.privoxy.org.
With recent versions of Privoxy (version 2.9.x and later), the user interface features information on the run time status, the configuration, and even a built-in editor for the actions files.
Note that the built-in URLs from earlier versions of Junkbuster / Privoxy, http://example.com/show-proxy-args and http://i.j.b/, are no longer supported. If you still use such an old version, you should really consider upgrading to 3.0.0.
No. The patterns for blocking now reside (among other things) in the actions files, which are actively maintained instead. See next question ...
Yes, absolutely! Please see the Contact section for how to do that. Please note that you (technically) need the latest Privoxy version for this to work.
You can find a list of anonymous public proxies at multiproxy.org and many more through Google. A particularly interesting project is the JAP service offered by the Technical University of Dresden (http://anon.inf.tu-dresden.de/index_en.html.
There is, however, even in the single-machine case the possibility to make the server believe that your machine is in fact a shared proxy serving a whole big LAN, and we are looking into that.
Similar thoughts apply to modifying JavaScript, and, to a lesser degree, HTML elements.
No, it does not have this ability at all. You want something like Squid for this. And, yes, before you ask, Privoxy can co-exist with other kinds of proxies like Squid. See the forwarding chapter in the user manual for details.
There are no known exploits that might affect Privoxy. On Unix-like systems, Privoxy can run as a non-privileged user, which is how we recommend it be run. Also, by default Privoxy only listens to requests from "localhost" only. The server aspect of Privoxy is not itself directly exposed to the Internet in this configuration. If you want to have Privoxy 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 Privoxy configuration file and check all access control and security options. All LAN hosts can then use this as their proxy address in the browser proxy configuration, but Privoxy will not listen on any external interfaces. ACLs can be defined in addition, and using a firewall is always good too. Better safe than sorry.
The easiest way is to access Privoxy with your browser by using the remote toggle URL: http://config.privoxy.org/toggle. See the Bookmarklets section of the User Manual for an easy way to access this feature.
A "crunch" simply means Privoxy intercepted something, nothing more. Often this is indeed ads or banners, but Privoxy uses the same mechanism for trapping requests for its own internal pages. For instance, a request for Privoxy's configuration page at: http://config.privoxy.org, is intercepted (i.e. it does not go out to the 'net), and the familiar CGI configuration is returned to the browser, and the log consequently will show a "crunch".
From the webserver's perspective, there is no difference between viewing a document (i.e. a page), and downloading a file. The same is true of Privoxy. If there is a match for a block pattern, it will still be blocked, and of course this is obvious. Filtering is potentially more of a concern since the results are not always so obvious.
Privoxy knows the differences in files according to the "Document Type" as reported by the webserver. If this is reported accurately (e.g. "application/zip" for a zip archive), then Privoxy knows to ignore these where appropriate. It is possible, however, that documents that are of an unknown type (generally assumed to be "text/plain") will be filtered, as will those that might be incorrectly reported by the webserver. If such a file is a downloaded file that is intended to be saved to disk, then any content that might have been altered by filtering, will be saved too, for these (probably very rare) cases.
Privoxy does not do FTP at all, only HTTP protocols.
Other references and sites of interest to Privoxy users:
http://www.privoxy.org/, the Privoxy Home page. |
http://www.privoxy.org/faq/, the Privoxy FAQ. |
http://sourceforge.net/projects/ijbswa/, the Project Page for Privoxy on SourceForge. |
http://config.privoxy.org/, the web-based user interface. Privoxy must be running for this to work. Shortcut: http://p.p/ |
http://www.privoxy.org/actions/, to submit "misses" to the developers. |
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/ijbswa/contrib/, cool and fun ideas from Privoxy users. |
http://www.junkbusters.com/ht/en/cookies.html, an explanation how cookies are used to track web users. |
http://www.junkbusters.com/ijb.html, the original Internet Junkbuster. |
http://www.waldherr.org/junkbuster/, Stefan Waldherr's version of Junkbuster, from which Privoxy was derived. |
http://privacy.net/analyze/, a useful site to check what information about you is leaked while you browse the web. |
http://www.squid-cache.org/, a very popular caching proxy, which is often used together with Privoxy. |
http://www.privoxy.org/developer-manual/, the Privoxy developer manual. |