1 <!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V3.1//EN"[
2 <!entity % dummy "IGNORE">
3 <!entity supported SYSTEM "supported.sgml">
4 <!entity newfeatures SYSTEM "newfeatures.sgml">
5 <!entity p-intro SYSTEM "privoxy.sgml">
6 <!entity seealso SYSTEM "seealso.sgml">
7 <!entity contacting SYSTEM "contacting.sgml">
8 <!entity history SYSTEM "history.sgml">
9 <!entity copyright SYSTEM "copyright.sgml">
10 <!entity license SYSTEM "license.sgml">
11 <!entity p-version SYSTEM "doc_version.tmp">
12 <!entity p-status SYSTEM "doc_status.tmp">
13 <!entity % p-not-stable "IGNORE">
14 <!entity % p-stable "IGNORE">
15 <!entity % p-text "IGNORE"> <!-- define we are not a text only doc -->
16 <!entity % p-doc "INCLUDE"> <!-- and we are a formal doc -->
17 <!entity % p-supp-userman "INCLUDE"> <!-- Include all from supported.sgml -->
18 <!entity my-copy "©"> <!-- kludge for docbook2man -->
21 File : $Source: /cvsroot/ijbswa/current/doc/source/faq.sgml,v $
24 This file belongs into
25 ijbswa.sourceforge.net:/home/groups/i/ij/ijbswa/htdocs/
27 $Id: faq.sgml,v 2.2 2002/09/05 04:25:05 hal9 Exp $
29 Copyright (C) 2001, 2002 Privoxy Developers <developers@privoxy.org>
32 Based partially on the Internet Junkbuster FAQ originally written by and
33 Copyright (C) 1997 Anonymous Coders and Junkbusters Corporation.
34 http://www.junkbusters.com/
36 <Qandaset defaultlabel='qanda'>
51 ========================================================================
52 NOTE: Please read developer-manual/documentation.html before touching
53 anything in this, or other Privoxy documentation. You have been warned!
54 Failure to abide by this rule will result in the revocation of your license
55 to live a peaceful existence!
56 ========================================================================
62 <article id="index" class="faq">
64 <title>Privoxy Frequently Asked Questions</title>
68 <!-- Completely the wrong markup, but very little is allowed -->
69 <!-- in this part of an article. FIXME -->
70 <link linkend="copyright">Copyright</link> &my-copy; 2001, 2002 by
71 <ulink url="http://www.privoxy.org">Privoxy Developers</ulink>
75 <pubdate>$Id: faq.sgml,v 2.2 2002/09/05 04:25:05 hal9 Exp $</pubdate>
79 Note: this should generate a separate page, and a live link to it.
80 But it doesn't for some mysterious reason. Please leave commented
81 unless it can be fixed proper. For the time being, the copyright
82 statement will be in copyright.smgl.
86 <legalnotice id="legalnotice">
88 text goes here ........
98 <orgname>By: Privoxy Developers</orgname>
107 This is here to keep vim syntax file from breaking :/
108 If I knew enough to fix it, I would.
109 PLEASE DO NOT REMOVE! HB: hal@foobox.net
114 This FAQ gives quick answers to frequently asked questions about
115 <ulink url="http://www.privoxy.org/">Privoxy</ulink>.
116 It can't and doesn't replace the
117 <ulink url="../user-manual/index.html"><citetitle>User Manual</citetitle></ulink>.
119 This works, at least in some situtations:
120 Test: <ulink url="privoxy-user-manual.pdf"><citetitle>User Manual</citetitle></ulink>.
124 <!-- Include privoxy.sgml boilerplate: -->
126 <!-- end boilerplate -->
129 Please note that this document is constantly evolving. This copy represents
130 the state at the release of version &p-version;.
131 You can find the latest version of the document at <ulink
132 url="http://www.privoxy.org/faq/">http://www.privoxy.org/faq/</ulink>.
133 Please see the <link linkend="contact">Contact section</link> if you want to
134 contact the developers.
138 <!-- Feel free to send a note to the developers at <email>ijbswa-developers@lists.sourceforge.net</email>. -->
144 <!-- ~~~~~ New section ~~~~~ -->
146 <sect1 id="general"><title>General Information</title>
148 <sect2 renderas="sect3" id="newjb"><title>What is this new version of <application>Privoxy</application>?</title>
150 <!-- Include history.sgml -->
157 <sect2 renderas="sect3">
158 <title id="whyprivoxy">Why <quote>Privoxy</quote>? Why a name change at all?</title>
160 <application>Privoxy</application> is the
161 <quote><emphasis>Privacy Enhancing Proxy</emphasis></quote>. Also, its content
162 modification and junk suppression allow you to browse your
163 <quote><emphasis>private</emphasis> edition</quote> of the web.
166 <ulink url="http://junkbusters.com/">Junkbusters Corporation</ulink>
167 continues to offer their original version of the <application>Internet
168 Junkbuster</application>, so publishing our
169 <application> Junkbuster</application>-derived software under the same name
173 There are also potential legal complications from the continued use of the
174 <application>Junkbuster</application> name, which is a registered trademark of
175 <ulink url="http://junkbusters.com/">Junkbusters Corporation</ulink>.
176 There are, however, no objections from Junkbusters Corporation to the
177 <application>Privoxy</application> project itself, and they, in fact, still
178 share our ideals and goals.
181 The developers also believed that there are so many changes from the original
182 code, that it was time to make a clean break from the past and make
183 a name in their own right<![%p-not-stable;[, especially now with the pending
184 release of version 3.0]]>.
189 <sect2 renderas="sect3" id="differs"><title>How does <application>Privoxy</application> differ
190 from the old <application>Junkbuster?</application></title>
192 <application>Privoxy</application> picks up where
193 <application>Junkbuster</application> left off. All the old features remain.
194 The new <application>Privoxy</application> still blocks ads and banners,
195 still manages cookies, and still helps protect your privacy. But, these are
196 all enhanced, and many new features have been added, all in the same vein.
199 The configuration has changed significantly as well. This is something that
200 users will notice right off the bat if upgrading from
201 <application>Junkbuster</application> 2.0.x. The <quote>blocklist</quote>
202 <quote>cookielist</quote>, <quote>imagelist</quote> and much more has been
203 combined into the <quote>actions</quote> files, with a completely different
204 syntax. See the <ulink url="../user-manual/upgradersnote.html">note to
205 upgraders</ulink> for details.
208 <application>Privoxy</application>'s new features include:
211 <!-- Include newfeatures.sgml: -->
217 <sect2 renderas="sect3" id="proxymoron"><title>What is a <quote>proxy</quote>? How does
218 <application>Privoxy</application> work? </title>
220 A web proxy is a service, based on a software such as <application>Privoxy</application>,
221 that clients (i.e. browsers) can use instead of connecting directly to the web
222 servers on the Internet. The clients then ask the proxy to fetch the objects
223 they need (web pages, images, movies etc) on their behalf, and when the proxy
224 has done so, it hands the results back to the client.
227 There are many reasons to use web proxies, such as security (firewalling),
228 efficiency (caching) and others, and there are just as many different proxies
229 to accommodate those needs.
232 <application>Privoxy</application> is a proxy that is solely focused on privacy
233 protection and junk elimination. Sitting between your browser(s) and the Internet,
234 it is in a perfect position to filter outbound personal information that your
235 browser is leaking, as well as inbound junk. It uses a variety of techniques to do
236 this, all of which are under your control via the various configuration
242 <sect2 renderas="sect3" id="whatsanad">
243 <title id="knows">How does <application>Privoxy</application> know what is
244 an ad, and what is not?</title>
246 <application>Privoxy</application>'s approach to blocking ads is twofold:
249 First, there are certain patterns in the <emphasis>locations</emphasis> (URLs)
250 of banner images. This applies to both the path (you wouldn't guess how many
251 web sites serve their banners from a directory called <quote>banners</quote>!)
252 and the host (blocking the big banner hosting services like doublecklick.net
253 already helps a lot). <application>Privoxy</application> takes advantage of this
254 fact by using <ulink url="../user-manual/actions-file.html#AF-PATTERNS">URL
255 patterns</ulink> to sort out and block the requests for banners.
258 Second, banners tend to come in certain <emphasis>sizes</emphasis>. But you
259 can't tell the size of an image by its URL without downloading it, and if you
260 do, it's too late to save bandwidth. Therefore, <application>Privoxy</application>
261 also inspects the HTML sources of web pages while they are loaded, and replaces
262 references to images with standard banner sizes by dummy references, so that
263 your browser doesn't request them anymore in the first place.
266 Both of this involves a certain amount of guesswork and is, of course, freely
271 <sect2 renderas="sect3">
272 <title id="mistakes">Can <application>Privoxy</application> make mistakes?
273 This does not sound very scientific.</title>
275 Actually, it's a black art ;-) And yes, it is always possible to have a broad
276 rule accidentally block or change something by mistake. There is a good chance
277 you may run into such a situation at some point. It is tricky writing rules to
278 cover every conceivable possibility, and not occasionally get false positives.
282 But this should not be a big concern since the
283 <application>Privoxy</application> configuration is very flexible, and
284 includes tools to help identify these types of situations so they can be
285 addressed as needed, allowing you to customize your installation.
286 (<link linkend="badsite">See the Troubleshooting section below</link>.)
292 <sect2 renderas="sect3" id="browsers2"><title>My browser does the same things as
293 <application>Privoxy</application>. Why should I use
294 <application>Privoxy</application> at all?</title>
296 Modern browsers do indeed have <emphasis>some</emphasis> of the same
297 functionality as <application>Privoxy</application>. Maybe this is
298 adequate for you. But <application>Privoxy</application> is much more
299 versatile and powerful, and can do a number of things that browsers just can't.
302 In addition, a proxy is good choice if you use multiple browsers, or
303 have a LAN with multiple computers. This way all the configuration
304 is in one place, and you don't have to maintain a similar configuration
305 for possibly many browsers.
311 <sect2 renderas="sect3" id="license"><title>Is there is a license or fee? What about a
312 warranty? Registration?</title>
314 <application>Privoxy</application> is licensed under the <ulink
315 url="http://www.gnu.org/copyleft/gpl.html">GNU General Public License (GPL)</ulink>.
316 It is free to use, copy, modify or distribute as you wish under the terms of this
317 license. Please see the <link linkend="copyright">Copyright</link> section for more
318 information on the license and copyright. Or the <filename>LICENSE</filename> file
319 that should be included.
322 There is <emphasis>no warranty</emphasis> of any kind, expressed, implied or otherwise.
323 That is something that would cost real money ;-) There is no registration either.
324 <application>Privoxy</application> really is <emphasis>free</emphasis>
330 <sect2 renderas="sect3" id="jointeam"><title>I would like to help you, what do I do?</title>
332 <sect3 renderas="sect4" id="jointeam-money"><title>Money Money Money</title>
334 We, of course, welcome donations and could use money for domain registering,
335 buying software to test <application>Privoxy</application> with, and, of course,
336 for regular world-wide get-togethers (hahaha). If you enjoy the software and feel
337 like helping us with a donation, just <ulink
338 url="mailto:developers@privoxy.org">drop us a note</ulink>.
342 <sect3 renderas="sect4" id="jointeam-software"><title>Software</title>
344 If you are a vendor of a web-related software like a browser, web server
345 or proxy, and would like us to ensure that <application>Privoxy</application>
346 runs smoothly with your product, you might consider supplying us with a
347 copy or license. We can't, however, guarantee that we will fix all potential
348 compatibility issues as a result.
352 <sect3 renderas="sect4" id="jointeam-work"><title>You want to work with us?</title>
354 Well, helping the team is always a good idea. We welcome new developers,
355 packaging gurus or documentation writers. Simply <ulink
356 url="https://sourceforge.net/account/register.php">get an account on SourceForge.net</ulink>
357 and mail your id to the <ulink url="mailto:developers@privoxy.org">developers
358 mailing list</ulink>. Then read the <ulink
359 url="../developer-manual/index.html">Developer's Manual</ulink>.
362 Once we have added you to the team, you'll have write access to the <ulink
363 url="http://sourceforge.net/cvs/?group_id=11118">CVS repository</ulink>, and
364 together we'll find a suitable task for you.
373 <!-- ~~~~~ New section ~~~~~ -->
375 <sect1 id="installation"><title>Installation</title>
377 <sect2 renderas="sect3" id="whichbrowsers">
378 <title>Which browsers are supported by <application>Privoxy</application>?</title>
380 Any browser that can be configured to use a proxy, which
381 should be virtually all browsers. Direct browser support is not necessary
382 since <application>Privoxy</application> runs as a separate application and
383 talks to the browser in the standardized HTTP protocol, just like a web server
388 <sect2 renderas="sect3" id="whichos">
389 <title>Which operating systems are supported?</title>
391 Include supported.sgml here:
396 <sect2 renderas="sect3" id="newinstall"><title>Can I install
397 <application>Privoxy</application> over <application>Junkbuster</application>?</title>
399 We recommend you un-install <application>Junkbuster</application>
400 first to minimize conflicts and confusion. You may want to
401 save your old configuration files for future reference. The configuration
402 files and syntax have substantially changed, so you will need to manually
403 port your old patterns. See the <ulink url="../user-manual/upgradersnote.html">note
404 to upgraders</ulink> and <ulink url="../user-manual/installation.html">installation
405 chapter</ulink> in the <ulink url="../user-manual/index.html">user manual</ulink>
409 Note: Some installers may automatically un-install
410 <application>Junkbuster</application>, if present!
415 <sect2 renderas="sect3">
416 <title id="firststep">I just installed <application>Privoxy</application>. Is there anything
417 special I have to do now?</title>
420 All browsers must be told to use <application>Privoxy</application>
421 as a proxy by specifying the correct proxy address and port number
422 in the appropriate configuration area for the browser. See below.
423 You should also flush your browser's memory and disk cache to get rid of any
431 <sect2 renderas="sect3" id="localhost"><title>What is the proxy address of <application>Privoxy</application>?</title>
433 If you set up the <application>Privoxy</application> to run on
434 the computer you browse from (rather than your ISP's server or some
435 networked computer on a LAN), the proxy will be on <literal>127.0.0.1</literal>
436 (sometimes referred to as <quote>localhost</quote>,
437 which is the special name used by every computer on the Internet to refer
438 to itself) and the port will be 8118 (unless you have <application>Privoxy</application>
439 to run on a different port with the <ulink
440 url="../user-manual/config.html#LISTEN-ADDRESS">listen-address</ulink> config option).
443 When configuring your browser's proxy settings you typically enter
444 the word <quote>localhost</quote> or the IP address <quote>127.0.0.1</quote>
445 in the boxes next to <quote>HTTP</quote> and <quote>Secure</quote> (HTTPS) and
446 then the number <quote>8118</quote> for <quote>port</quote>.
447 This tells your browser to send all web requests to <application>Privoxy</application>
448 instead of directly to the Internet.
451 <application>Privoxy</application> can also be used to proxy for
452 a Local Area Network. In this case, your would enter either the IP
453 address of the LAN host where <application>Privoxy</application>
454 is running, or the equivalent hostname. Port assignment would be
455 same as above. Note that <application>Privoxy</application> doesn't
456 listen on any LAN interfaces by default.
459 <application>Privoxy</application> does not currently handle
460 protocols such as FTP, SMTP, IM, IRC, ICQ, or other Internet
465 <sect2 renderas="sect3" id="nothing">
466 <title>I just installed <application>Privoxy</application>, and nothing is happening.
467 All the ads are there. What's wrong?</title>
470 Did you configure your browser to use <application>Privoxy</application>
471 as a proxy? It does not sound like it. See above. You might also try flushing
472 the browser's caches to force a full re-reading of pages. You can verify
473 that <application>Privoxy</application> is running, and your browser
474 is correctly configured by entering the special URL:
475 <ulink url="http://config.privoxy.org/">http://config.privoxy.org/</ulink>.
476 This should take you to a page titled <quote>This is Privoxy..</quote> with
477 access to <application>Privoxy's</application> internal configuration.
478 If you see this, then you are good to go. If you receive a page saying
479 <quote>Privoxy is not running</quote>, then the browser is not set up to use
480 your <application>Privoxy</application> installation.
481 If you receive anything else (probably nothing at all), it could either
482 be that the browser is not set up correctly, or that
483 <application>Privoxy</application> is not running at all. Check the <ulink
484 url="../user-manual/config.html#LOGFILE">log file</ulink>.
492 <!-- ~~~~~ New section ~~~~~ -->
494 <sect1 id="configuration"><title>Configuration</title>
496 <sect2 renderas="sect3" id="getupdates"><title>Where can I get updated Actions Files?</title>
498 Based on your feedback and the continuing development, updated actions files will be
499 made available on the <ulink
500 url="http://sourceforge.net/project/showfiles.php?group_id=11118">files section</ulink> of
501 our <ulink url="http://sf.net/projects/ijbswa/">project page</ulink>.
505 If you wish to receive an email notification whenever we release updates of
506 <application>Privoxy</application> or the actions file, <ulink
507 url="http://lists.sourceforge.net/lists/listinfo/ijbswa-announce/">subscribe
508 to our announce mailing list</ulink>, ijbswa-announce@lists.sourceforge.net.
513 <sect2 renderas="sect3" id="newconfig"><title>Can I use my old config files?</title>
515 The syntax, number, and purpose of configuration files has substantially
516 changed from <application>Junkbuster</application> and earlier versions
517 of <application>Privoxy</application>. The old files, like <filename>blocklist</filename>
518 will not work at all. If you are upgrading from a 2.0.x version, you will
519 need to port your configuration data to the new format. Note that even the
520 pattern syntax has changed! Even configuration files from the 2.9.x versions
521 will need to be adapted, as configuration syntax has been very much in flow
526 <sect2 renderas="sect3">
527 <title id="actionsfile">What is an <quote>actions</quote> file?</title>
530 <ulink url="../user-manual/actions-file.html">Actions files</ulink>
531 are where various <ulink url="../user-manual/actions-file.html#ACTIONS">actions</ulink>
532 that <application>Privoxy</application> might take while processing a certain
533 request, are configured. Typically, you would define a set of default actions
534 that apply to all URLs, then add exceptions to these defaults where needed.
538 Actions can be defined on a <ulink
539 url="../user-manual/actions-file.html#AF-PATTERNS">URL pattern</ulink> basis, i.e.
540 for single URLs, whole web sites, groups or parts thereof etc. Actions can also be
541 grouped together and then applied to requests matching one or more patterns.
542 There are many possible actions that might apply to any given site. As an example,
543 if you are blocking cookies as one of your default actions, but need to accept
544 cookies from a given site, you would need to define an exception for this
545 site in one of your actions files, preferably in <filename>user.action</filename>
550 <sect2 renderas="sect3" id="actionss">
551 <title>The <quote>actions</quote> concept confuses me. Please list
552 some of these <quote>actions</quote>.</title>
554 For a comprehensive discussion of the actions concept, please refer
555 to the <ulink url="../user-manual/actions-file.html">actions file
556 chapter</ulink> in the <ulink url="../user-manual/index.html">user
557 manual</ulink>. It includes a <ulink
558 url="../user-manual/actions-file.html#ACTIONS">list of all actions</ulink>
559 and an <ulink url="../user-manual/actions-file.html#ACT-EXAMPLES">actions
560 file tutorial</ulink> to get you started.
565 <sect2 renderas="sect3">
566 <title id="actconfig">How are actions files configured? What is the easiest
567 way to do this?</title>
570 Actions files are just text files in a special syntax and can be edited
571 with a text editor. But probably the easiest way is to access
572 <application>Privoxy</application>'s user interface with your web browser
573 at <ulink url="http://config.privoxy.org/">http://config.privoxy.org/</ulink>
574 (Shortcut: <ulink url="http://p.p/">http://p.p/</ulink>) and then select
575 <quote><ulink url="http://config.privoxy.org/show-status">View &
576 change the current configuration</ulink></quote> from the menu.
581 <!-- ~~~~~ New section ~~~~~ -->
582 <sect2 renderas="sect3">
583 <title>There are several different <quote>actions</quote> files. What are
584 the differences?</title>
586 As of <application>Privoxy</application> v2.9.15, three actions files
587 are being included, to be used for
588 different purposes: These are
589 <filename>default.action</filename>, the <quote>main</quote> actions file
590 which is actively maintained by the <application>Privoxy</application>
591 developers, <filename>user.action</filename>, where users are encouraged
592 to make their private customizations, and <filename>standard.action</filename>,
593 which is for internal <application>Privoxy</application> use only.
594 Please see <ulink url="../user-manual/actions-file.html">the actions chapter</ulink>
595 in the <ulink url="../user-manual/index.html">user manual</ulink> for a more
596 detailed explanation.
600 Earlier versions included three different versions of the
601 <filename>default.action</filename> file. The new scheme allows for
602 greater flexibility of local configuration, and for browser based
603 selection of pre-defined <quote>aggressiveness</quote> levels.
608 <sect2 renderas="sect3" id="yahoo"><title>How can I make my Yahoo/Hotmail/GMX account work?</title>
610 The default configuration shouldn't impact the usability of any of these services.
611 It will, however, make all cookies temporary, so that your browser will forget your
612 login credentials in between browser sessions. If you would like not to have to log
613 in manually each time you access those websites, simply turn off all cookie handling
614 for them in the <filename>user.action</filename> file. An example for yahoo might
618 <screen># Allow all cookies for Yahoo login:
620 { -<ulink url="../user-manual/actions-file.html#CRUNCH-INCOMING-COOKIES">crunch-incoming-cookies</ulink> -<ulink url="../user-manual/actions-file.html#CRUNCH-OUTGOING-COOKIES">crunch-outgoing-cookies</ulink> -<ulink url="../user-manual/actions-file.html#SESSION-COOKIES-ONLY">session-cookies-only</ulink> }
621 .login.yahoo.com</screen>
626 <sect2 renderas="sect3" id="configfiles"> <title>What's the difference between the
627 <quote>Cautious</quote>, <quote>Medium</quote> and <quote>Advanced</quote> defaults?</title>
629 Configuring <application>Privoxy</application> is not entirely trivial. To help you get
630 started, we provide you with three different default action <quote>packages</quote> in
631 the web based actions file editor at <ulink
632 url="http://config.privoxy.org/show-status">http://config.privoxy.org/show-status</ulink>.
633 The following table shows you, which of the most important features are enabled in each
637 <table frame=all><title>Default Configurations</title>
638 <tgroup cols=4 align=left colsep=1 rowsep=1>
645 <entry>Feature</entry>
646 <entry>Cautious</entry>
647 <entry>Intermadiate</entry>
648 <entry>Advanced</entry>
653 <!-- <entry>f1</entry> -->
654 <!-- <entry>f2</entry> -->
655 <!-- <entry>f3</entry> -->
656 <!-- <entry>f4</entry> -->
662 <entry>Ad-blocking by URL</entry>
669 <entry>Ad-filtering by size</entry>
676 <entry>GIF de-animation</entry>
683 <entry>Referer forging</entry>
690 <entry>Cookie handling</entry>
692 <entry>session-only</entry>
697 <entry>Pop-up killing</entry>
704 <entry>Fast redirects</entry>
711 <entry>HTML taming</entry>
718 <entry>JavaScript taming</entry>
725 <entry>Web-bug killing</entry>
732 <entry>Fun text replacements</entry>
739 <entry>Image tag reordering</entry>
746 <entry>Ad-filtering by link</entry>
758 Where the defaults are likely to break some sites, exceptions for
759 known popular <quote>problem</quote> sites are included, but in
760 general, the more aggressive your default settings are, the more
761 exceptions you will have to make later. See the <ulink
762 url="../user-manual/index.html">user manual</ulink> for a more
768 <sect2 renderas="sect3" id="browseconfig"> <title>Why can I change the configuration
769 with a browser? Does that not raise security issues?</title>
771 It may seem strange that regular users can edit the config files with their
772 browsers, although the whole <filename>/etc/privoxy</filename> hierarchy
773 belongs to the user <quote>privoxy</quote>, with only 644 permissions.
776 When you use the browser-based editor, <application>Privoxy</application>
777 itself is writing to the config files. Because
778 <application>Privoxy</application> is running as the user <quote>privoxy</quote>,
779 it can update the config files.
782 If you run <application>Privoxy</application> for multiple untrusted users (e.g. in
783 a LAN), you will probably want to turn the web-based editor and remote toggle
784 features off by setting <quote><literal><ulink
785 url="../user-manual/config.html#ENABLE-EDIT-ACTIONS">enable-edit-actions</ulink>
786 0</literal></quote> and <quote><literal><ulink
787 url="../user-manual/config.html#ENABLE-REMOTE-TOGGLE">enable-remote-toggle</ulink>
788 0</literal></quote> in the <ulink url="../user-manual/config.html">main configuration file</ulink>.
791 Note that in the default configuration, only local users (i.e. those on
792 <quote>localhost</quote>) can connect to <application>Privoxy</application>,
793 so this is not (normally) a security problem.
798 <sect2 renderas="sect3">
799 <title id="filterfile">What is the <filename>default.filter</filename> file? What is a <quote>filter</quote>?</title>
801 The <ulink url="../user-manual/filter-file.html"><filename>default.filter</filename></ulink>
802 file is where <emphasis>filters</emphasis> are defined, which can be used to modify or
803 remove, web page content on the fly. Filters apply to <emphasis>anything</emphasis>
804 in the page source, including HTML tags, and JavaScript. Regular expressions are used
805 to accomplish this. There are a number of pre-defined filters to deal with common
806 annoyances. The filters are only defined here, to invoke them, you need to use the
808 url="../user-manual/actions-file.html#FILTER"><literal>filter</literal>
809 action</ulink> in one of the actions files. Filtering is automatically
810 disabled for inappropriate MIME types.
814 If you are familiar with regular expressions, and HTML, you can look at
815 the provided <filename>default.filter</filename> with a text editor and define
816 your own filters. This is potentially a very powerful feature, but
817 requires some expertise in both regular expressions and HTML/HTTP.
821 Presently, there is no GUI editor option for this part of the configuration,
822 but you can disable/enable the various pre-defined filters of the included
823 <filename>default.filter</filename> file with the <ulink
824 url="http://config.privoxy.org/show-status">web-based actions file editor</ulink>.
829 <sect2 renderas="sect3">
830 <title id="lanconfig">How can I set up <application>Privoxy</application> to act as a proxy for my
833 By default, <application>Privoxy</application> only responds to requests
834 from <literal>127.0.0.1</literal> (localhost). To have it act as a server for
835 a network, this needs to be changed in the <ulink
836 url="../user-manual/config.html">main configuration file</ulink>. Look for
838 url="../user-manual/config.html#LISTEN-ADDRESS">listen-address</ulink></literal>
839 option, which may be commented out with a <quote>#</quote> symbol. Make sure
840 it is uncommented, and assign it the address of the LAN gateway interface,
841 and port number to use. Assuming your LAN address is 192.168.1.1 and you
842 wish to run <application>Privoxy</application> on port 8118, this line
848 listen-address 192.168.1.1:8118</screen>
852 Save the file, and restart <application>Privoxy</application>. Configure
853 all browsers on the network then to use this address and port number.
857 If you run <application>Privoxy</application> on a LAN with untrusted users,
858 we recommend that you double-check the <ulink
859 url="../user-manual/config.html#ACCESS-CONTROL">access control and security</ulink>
866 <sect2 renderas="sect3">
867 <title id="noseeum">Instead of ads, now I get a checkerboard pattern. I don't want to see anything.</title>
869 The replacement for blocked images can be controlled with the <ulink
870 url="../user-manual/actions-file.html#SET-IMAGE-BLOCKER"><literal>set-image-blocker</literal>
871 action</ulink>. You have the choice of a checkerboard pattern, a transparent 1x1 GIF
872 image (aka <quote>blank</quote>), or a redirect to a custom image of your choice.
873 Note that this choice only has effect for images which are blocked as images, i.e.
874 whose URLs match both a <literal><ulink
875 url="../user-manual/actions-file.html#HANDLE-AS-IMAGE">handle-as-image</ulink></literal>
876 <emphasis>and</emphasis> <literal><ulink
877 url="../user-manual/actions-file.html#BLOCK">block</ulink></literal> action.
880 If you want to see nothing, then change the <ulink
881 url="../user-manual/actions-file.html#SET-IMAGE-BLOCKER"><literal>set-image-blocker</literal>
882 action</ulink> to <quote>blank</quote>. This can be done by editing the
883 <filename>default.action</filename> file, or trough the <ulink
884 url="http://config.privoxy.org/show-status">web-based actions file editor</ulink>.
889 <sect2 renderas="sect3">
890 <title id="whyseeum">Why would anybody want to see a checkerboard pattern?</title>
892 Remember that <link linkend="whatsanad">telling which image is an ad and which
893 isn't</link>, is mostly guesswork. While we hope that the standard configuration
894 is rather smart, it can and will make errors. The checkerboard image is visually
895 decent, but it shows you that and where images were blocked, which can be very
896 helpful in case some navigation aid or otherwise innocent image was
897 erraneously blocked. Some people might also enjoy seeing how many banners
898 they <emphasis>don't</emphasis> have to see..
903 <!-- This has changed with the adaptive "blocked" page
905 <sect2 renderas="sect3">
906 <title id="blockedisugly">I see large red banners on some pages that say
907 <quote>Blocked</quote>. Why and how do I get rid of this?</title>
909 These are URLs that match something in one of
910 <application>Privoxy's</application> block actions
912 url="../user-manual/actions-file.html#BLOCK"><quote>+block</quote></ulink>).
913 It is meant to be a warning so that you know something has been blocked and
914 an easy way for you to see why. These are handled differently than what has
915 been defined explicitly as <quote>images</quote> (e.g. ads that are GIF image
916 files). Depending on the URL itself, it is sometimes hard for
917 <application>Privoxy</application> to really know whether there is indeed an
918 ad image there or not. And there are limitations as to what
919 <application>Privoxy</application> can do to <quote>fool</quote> the
924 For instance, if the ad is in a frame, then it is embedded in the separate
925 HTML page used for the frame. In this case, you cannot just substitute an
926 aribitrary image (like we would for a <quote>blank</quote> image), for an HTML
927 page. The browser is expecting an HTML page, and that is what it must have
928 for frames. Such situations can be a little trickier to deal with, and
929 <application>Privoxy</application> may show the <quote>Blocked</quote> page,
930 despite your best efforts.
934 If you want these to be treated as if they were images, so that they can be
935 made invisible, you can try moving the offending URL from the
936 <quote>+block</quote> section to the <quote>+imageblock</quote> section of
937 your actions file. Just be forewarned, if any URL is made
938 <quote>invisible</quote>, you may not have any inkling that something has
939 been removed from that page, or why. If this approach does not work, then you are
940 probably dealing with a frame (or <quote>ilayer</quote>), and the only thing
941 that can go there is an HTML page of some sort.
944 To deal with this situation, you could modify the
945 <quote><filename>block</filename></quote> HTML template that is used by
946 <application>Privoxy</application> to display this, and make it something
947 more to your liking. Currently, there is no configuration option for this.
948 You will have to modify, or create your own page, and use this to replace
949 <filename>templates/blocked</filename>, which is what
950 <application>Privoxy</application> uses to display the <quote>Blocked</quote>
954 Another way to deal with this is find why and where
955 <application>Privoxy</application> is blocking the frame, and
956 diable this. Then let the <quote>+set-image-blocker</quote> action
957 handle the ad that is embedded in the frame's HTML page.
962 <sect2 renderas="sect3" id="alliseeisred">
963 <title>I cannot see all of the <quote>Blocked</quote> page banner. Help.</title>
965 There is not enough available space to fit the entire Blocked page. Try right
966 clicking on the visible portion, and select <quote>Show Frame</quote>,
967 or equivalent. This will usually allow you to see the entire Privoxy
968 <quote>Blocked</quote> page, and from there you can see just what is being
972 As of Privoxy 2.9.14, the Blocked banner page is re-sizeable, and tries
973 to adjust to the allotted space. There may be occassions where there
974 just isn't enough room to display much of anything useful though.
981 <sect2 renderas="sect3">
982 <title id="blockedbytext">I see some images being replaced by a text
983 instead of the checkerboard image. Why and how do I get rid of this?</title>
985 This happens when the banners are not embedded in the HTML code of the
986 page itself, but in separate HTML (sub)documents that are loaded into (i)frames
987 or (i)layers, and these external HTML documents are blocked. Being non-images
988 they get replaced by a substitute HTML page rather than a substitute image,
989 which wouldn't work out technically, since the browser expects and accepts
990 only HTML when it has requested an HTML document.
993 The substitute page adapts to the available space and shows itself as a
994 miniature two-liner if loaded into small frames, or full-blown with a
995 large red "BLOCKED" banner if space allows.
998 If you prefer the banners to be blocked by images, you must see to it that
999 the HTML documents in which they are embedded are not blocked. Clicking
1000 the <quote>See why</quote> link offered in the substitute page will show
1001 you which rule blocked the page. After changing the rule and un-blocking
1002 the HTML documents, the browser will try to load the actual banner images
1003 and the usual image blocking will (hopefully!) kick in.
1008 <sect2 renderas="sect3" id="srvany">
1009 <title>Can <application>Privoxy</application> run as a service
1010 on Win2K/NT?</title>
1012 Yes, it can run as a system service using <command>srvany.exe</command>.
1013 The only catch is that this will effectively disable the
1014 <application>Privoxy</application> icon (and its menu!) in the taskbar. You can have
1015 one or the other, but not both at this time :(
1018 There is a pending feature request for this functionality. See the discussion
1020 url="http://sourceforge.net/tracker/?func=detail&atid=361118&aid=485617&group_id=11118">http://sourceforge.net/tracker/?func=detail&atid=361118&aid=485617&group_id=11118</ulink>,
1021 for details, and a sample configuration.
1027 <sect2 renderas="sect3" id="otherproxy">
1028 <title>How can I make <application>Privoxy</application> work with other
1029 proxies like <application>Squid</application>?</title>
1031 This can be done and is often useful to combine the benefits of
1032 <application>Privoxy</application> with those of a caching proxy.
1034 url="../user-manual/config.html#FORWARDING">forwarding chapter</ulink>
1035 in the <ulink url="../user-manual/index.html">user manual</ulink> which
1036 describes how to do this.
1040 <sect2 renderas="sect3" id="port-80">
1041 <title>Can I just set <application>Privoxy</application> to use port 80
1042 and thus avoid individual browser configuration?</title>
1045 No, its more complicated than that. This only works with special kinds
1046 of proxies known as <quote>transparent</quote> proxies (see below).
1051 <sect2 renderas="sect3" id="transparent">
1052 <title>Can <application>Privoxy</application> run as a <quote>transparent
1053 </quote> proxy?</title>
1055 No, <application>Privoxy</application> currently does not have this ability,
1056 though it is planned for a future release. Transparent proxies require
1057 special handling of the request headers beyond what
1058 <application>Privoxy</application> is now capable of.
1062 Chaining <application>Privoxy</application> behind another proxy that has
1063 this ability should work though.
1065 url="../user-manual/config.html#FORWARDING">forwarding chapter</ulink>
1066 in the <ulink url="../user-manual/index.html">user manual</ulink>. As
1067 a transparent proxy to be used for chaining we recommend Transproxy
1068 (<ulink url="http://www.transproxy.nlc.net.au/">http://www.transproxy.nlc.net.au/</ulink>).
1075 <!-- ~ End section ~ -->
1078 <!-- ~~~~~ New section ~~~~~ -->
1080 <sect1 id="misc"><title>Miscellaneous</title>
1082 <sect2 renderas="sect3">
1083 <title id="slowsme">How much does <application>Privoxy</application> slow my browsing down? This
1084 has to add extra time to browsing.</title>
1086 It should not slow you down any in real terms, and may actually help
1087 speed things up since ads, banners and other junk are not being displayed.
1088 The actual processing time required by <application>Privoxy</application>
1089 itself for each page, is relatively small in the overall scheme of things,
1090 and happens very quickly. This is typically more than offset by time saved
1091 not downloading and rendering ad images.
1095 <quote>Filtering</quote> content via the <literal><ulink
1096 url="../user-manual/actions-file.html#FILTER">filter</ulink></literal> or
1098 url="../user-manual/actions-file.html#DEANIMATE-GIFS">deanimate-gifs</ulink></literal>
1099 actions may cause a perceived slowdown, since the entire document needs to be buffered
1100 before displaying. See below.
1106 <sect2 renderas="sect3" id="loadingtimes"><title>I noticed considerable
1107 delays in page requests compared to the old Junkbuster. What's wrong?</title>
1109 If you use any <literal><ulink
1110 url="../user-manual/actions-file.html#FILTER">filter</ulink></literal> action,
1111 such as filtering banners by size, web-bugs etc, or the <literal><ulink
1112 url="../user-manual/actions-file.html#DEANIMATE-GIFS">deanimate-gifs</ulink></literal>
1113 action, the entire document must be loaded into memory in order for the filtering
1114 mechanism to work, and nothing is sent to the browser during this time.
1117 The loading time does not really change in real numbers, but the feeling is
1118 different, because most browsers are able to start rendering incomplete
1119 content, giving the user a feeling of "it works". This effect is especially
1120 noticeable on slow dialup connections.
1123 Filtering is automatically disabled for inappropriate MIME types.
1129 <sect2 renderas="sect3" id="configurl"><title>What are "http://config.privoxy.org/" and
1130 "http://p.p/"?</title>
1132 <ulink url="http://config.privoxy.org/">http://config.privoxy.org/</ulink> is the
1133 address of <application>Privoxy</application>'s built-in user interface, and
1134 <ulink url="http://p.p/">http://p.p/</ulink> is a shortcut for it.
1137 Since <application>Privoxy</application> sits between your web browser and the Internet,
1138 it can simply intercept requests for these addresses and answer them with its built-in
1139 <quote>web server</quote>.
1142 This also makes for a good test for your browser configuration: If entering the
1143 URL <ulink url="http://config.privoxy.org/">http://config.privoxy.org/</ulink>
1144 takes you to a page saying <quote>This is Privoxy..</quote>, everything is OK.
1145 If you get a page saying <quote>Privoxy is not working</quote> instead, then
1146 your browser didn't use <application>Privoxy</application> for the request,
1147 hence it could not be intercepted, and you have accessed the <emphasis>real</emphasis>
1148 web site at config.privoxy.org.
1151 With recent versions of <application>Privoxy</application> (version 2.9.x and
1152 later), the user interface features information on the run time status, the
1153 configuration, and even a built-in editor for the <ulink
1154 url="../user-manual/actions-file.html">actions files</ulink>.
1158 Note that the built-in URLs from earlier versions of <application>Junkbuster</application>
1159 / <application>Privoxy</application>, http://example.com/show-proxy-args and http://i.j.b/,
1160 are no longer supported. If you still use such an old version, you should really consider
1161 upgrading to &p-version;.
1166 FIXME: commented out until we have data. HB 03/18/02.
1168 <sect2 renderas="sect3" id="badfiledesc"><title>I get the message 'Bad File Descriptor', why?</title>
1176 <sect2 renderas="sect3" id="blocklist"><title>Do you still maintain the blocklists?</title>
1178 No. The patterns for blocking now reside (among other things) in the <ulink
1179 url="../user-manual/actions-file.html">actions files</ulink>, which are
1180 actively maintained instead. See next question ...
1184 <sect2 renderas="sect3" id="newads"><title>How can I submit new ads?</title>
1186 Yes, absolutely! Please see the <link linkend="contact">Contact section</link> for
1187 how to do that. Please note that you (technically) need the latest
1188 <application>Privoxy</application> version for this to work.
1193 <sect2 renderas="sect3" id="ip"><title>How can I hide my IP address?</title>
1195 If you run both the browser and the proxy locally, you cannot hide your IP
1196 address with <application>Privoxy</application> or any other software. The
1197 server needs to know your IP address to send the answers back to you.
1200 Fortunately there are many publicly usable anonymous proxies out there, which
1201 solve the problem by providing a further level of indirection between you and
1202 the web server, shared by many people, and thus letting your requests "drown"
1203 in white noise of unrelated requests as far as user tracking is concerned.
1206 Most of them will, however, log your IP address and make it available to the
1207 authorities in case you abuse that anonymity for criminal purposes. In fact
1208 you can't even rule out that some of them only exist to *collect* information
1209 on (those suspicious) people with a more than average preference for privacy.
1212 You can find a list of anonymous public proxies at <ulink
1213 url="http://www.multiproxy.org/anon_list.htm">multiproxy.org</ulink> and many
1214 more through Google. A particularly interesting project is the JAP service
1215 offered by the Technical University of Dresden (<ulink
1216 url="http://anon.inf.tu-dresden.de/index_en.html">http://anon.inf.tu-dresden.de/index_en.html</ulink>.
1219 There is, however, even in the single-machine case the possibility to make the
1220 server believe that your machine is in fact a shared proxy serving a whole big
1221 LAN, and we are looking into that.
1225 <sect2 renderas="sect3">
1226 <title id="anonforsure">Can <application>Privoxy</application> guarantee I am anonymous?</title>
1228 No. Your chances of remaining anonymous are greatly improved, but unless you
1229 are an expert on Internet security it would be safest to assume that
1230 everything you do on the Web can be traced back to you.
1233 <application>Privoxy</application> can remove various information about you,
1234 and allows <emphasis>you</emphasis> more freedom to decide which sites
1235 you can trust, and what details you want to reveal. But it's still possible
1236 that web sites can find out who you are. Here's one way this can happen.
1239 A few browsers disclose the user's email address in certain situations, such
1240 as when transferring a file by FTP. <application>Privoxy</application>
1241 does not filter FTP. If you need this feature, or are concerned about the
1242 mail handler of your browser disclosing your email address, you might
1243 consider products such as <application>NSClean</application>.
1246 Browsers available only as binaries could use non-standard headers to give
1247 out any information they can have access to: see the manufacturer's license
1248 agreement. It's impossible to anticipate and prevent every breach of privacy
1249 that might occur. The professionally paranoid prefer browsers available as
1250 source code, because anticipating their behavior is easier. Trust the source,
1256 <sect2 renderas="sect3">
1257 <title id="sitebreak">Might some things break because header information or
1258 content is being altered?</title>
1261 Definitely. More and more sites use HTTP header content to decide what to
1262 display and how to display it. There is many ways that this can be handled,
1263 so having hard and fast rules, is tricky.
1267 <quote>User-Agent</quote> in particular is often used in this way to identify
1268 the browser, and adjust content accordingly. Changing this now (at least not
1269 further than removing the OS information) is not recommended, since so many
1270 sites do look for it. You may get undesirable results by changing this.
1274 For instance, different browsers use different encodings of Russian and Czech
1275 characters, certain web servers convert pages on-the-fly according to the
1276 User Agent header. Giving a <quote>User Agent</quote> with the wrong
1277 operating system or browser manufacturer causes some sites in these languages
1278 to be garbled; Surfers to Eastern European sites should change it to
1279 something closer. And then some page access counters work by looking at the
1280 <quote>Referer</quote> header; they may fail or break if unavailable. The
1281 weather maps of Intellicast have been blocked by their server when no
1282 <quote>Referer</quote> or cookie is provided, is another example. (But you
1283 can forge both headers without giving information away). There are
1284 many other ways things can go wrong when trying to fool a web server.
1288 Similar thoughts apply to modifying JavaScript, and, to a lesser degree,
1293 If you have problems with a site, you will have to adjust your configuration
1294 accordingly. Cookies are probably the most likely adjustment that may
1295 be required, but by no means the only one.
1301 <sect2 renderas="sect3">
1302 <title id="caching">Can <application>Privoxy</application> act as a <quote>caching</quote> proxy to
1303 speed up web browsing?</title>
1305 No, it does not have this ability at all. You want something like
1306 <ulink url="http://www.squid-cache.org/">Squid</ulink> for this. And, yes,
1307 before you ask, <application>Privoxy</application> can co-exist
1308 with other kinds of proxies like <application>Squid</application>.
1309 See the <ulink url="../user-manual/config.html#FORWARDING">forwarding
1310 chapter</ulink> in the <ulink url="../user-manual/index.html">user
1311 manual</ulink> for details.
1315 <sect2 renderas="sect3">
1316 <title id="firewall">What about as a firewall? Can <application>Privoxy</application> protect me?</title>
1318 Not in the way you mean, or in the way a true firewall can.
1319 <application>Privoxy</application> can help protect your privacy, but not
1320 protect you from intrusion attempts. It is, of course, perfectly possible
1321 and recommended to use <emphasis>both</emphasis>.
1325 <!-- No longer needed
1326 <sect2 renderas="sect3">
1327 <title id="logo">The <application>Privoxy</application> logo that replaces ads is very blocky
1328 and ugly looking. Can't a better font be used?</title>
1331 This is not a font problem. The logo is an image that is created by
1332 <application>Privoxy</application> on the fly. So as to not waste
1333 memory, the image is rather small. The blockiness comes when the
1334 image is scaled to fill a largish area. There is not much to be done
1335 about this, other than to use one of the other
1336 <quote>imageblock</quote> directives: <emphasis>pattern</emphasis>,
1337 <emphasis>blank</emphasis>, or a URL of your choosing.
1340 Given the above problem, we have decided to remove the logo option entirely
1346 <sect2 renderas="sect3">
1347 <title id="wasted">I have large empty spaces / a checkerboard pattern now where
1348 ads used to be. Why?</title>
1350 It would be technically possible eliminate the banners in a way that frees
1351 their screen estate in many cases, by doing all banner blocking with filters,
1352 i.e. eliminating the whole image references from the HTML pages instead
1353 of letting them stay in, and blocking the resulting requests for the
1357 But this would consume considerable CPU resources, would likely destroy
1358 the layout of many web pages which rely on the banners consuming a certain
1359 amount of screen space, and would fail in other cases, where the screen space
1360 is reserved e.g. by tables anyway. Also, making the banners disappear without
1361 a visual trace complicates troubleshooting.
1364 So we won't support this in the default configuration, but you can of course
1365 define appropriate filters yourself.
1369 <sect2 renderas="sect3">
1370 <title id="ssl">How can <application>Privoxy</application> filter Secure (HTTPS) URLs?</title>
1372 Since secure HTTP connections are encrypted SSL sessions between your browser
1373 and the secure site, and are meant to be reliably <emphasis>secure</emphasis>,
1374 there is little that <application>Privoxy</application> can do but hand the raw
1375 gibberish data though from one end to the other unprocessed.
1378 The only exception to this is blocking by host patterns, as the client needs
1379 to tell <application>Privoxy</application> the name of the remote server,
1380 so that <application>Privoxy</application> can establish the connection.
1381 If that name matches a host-only pattern, the connection will be blocked.
1384 As far as ad blocking is concerned, this is less of a restriction than it may
1385 seem, since ad sources are often identifiable by the host name, and often
1386 the banners to be placed in an encrypted page come unencrypted nonetheless
1387 for efficiency reasons, which exposes them to the full power of
1388 <application>Privoxy</application>'s ad blocking.
1393 <sect2 renderas="sect3">
1394 <title id="secure"><application>Privoxy</application> runs as a <quote>server</quote>. How
1395 secure is it? Do I need to take any special precautions?</title>
1397 There are no known exploits that might affect
1398 <application>Privoxy</application>. On Unix-like systems,
1399 <application>Privoxy</application> can run as a non-privileged
1400 user, which is how we recommend it be run. Also, by default
1401 <application>Privoxy</application> only listens to requests
1402 from <quote>localhost</quote> only. The server aspect of
1403 <application>Privoxy</application> is not itself directly exposed to the
1404 Internet in this configuration. If you want to have
1405 <application>Privoxy</application> serve as a LAN proxy, this will have to
1406 be opened up to allow for LAN requests. In this case, we'd recommend
1407 you specify only the LAN gateway address, e.g. 192.168.1.1, in the main
1408 <application>Privoxy</application> configuration file and check all <ulink
1409 url="../user-manual/config.html#ACCESS-CONTROL">access control and security
1410 options</ulink>. All LAN hosts can then use this as their proxy address
1411 in the browser proxy configuration, but <application>Privoxy</application>
1412 will not listen on any external interfaces. ACLs can be defined in addition,
1413 and using a firewall is always good too. Better safe than sorry.
1418 <sect2 renderas="sect3" id="turnoff">
1419 <title>How can I temporarily disable <application>Privoxy</application>?</title>
1421 The easiest way is to access <application>Privoxy</application> with your
1422 browser by using the remote toggle URL: <ulink
1423 url="http://config.privoxy.org/toggle">http://config.privoxy.org/toggle</ulink>.
1424 See the <ulink url="../user-manual/appendix.html#BOOKMARKLETS">Bookmarklets section</ulink>
1425 of the <citetitle>User Manual</citetitle> for an easy way to access this
1430 <sect2 renderas="sect3" id="reallyoff">
1431 <title>When <quote>disabled</quote> is <application>Privoxy</application> totally
1432 out of the picture?</title>
1434 No, this just means all filtering and actions are disabled.
1435 <application>Privoxy</application> is still acting as a proxy, but just not
1436 doing any of the things that <application>Privoxy</application> would
1437 normally be expected to do. It is still a <quote>middle-man</quote> in
1438 the interaction between your browser and web sites.
1442 <sect2 renderas="sect3" id="crunch">
1443 <title>My logs show <application>Privoxy</application> <quote>crunches</quote>
1444 ads, but also its own CGI pages. What is a <quote>crunch</quote>?</title>
1446 A <quote>crunch</quote> simply means <application>Privoxy</application> intercepted
1447 <emphasis>something</emphasis>, nothing more. Often this is indeed ads or
1448 banners, but <application>Privoxy</application> uses the same mechanism for
1449 trapping requests for its own internal pages. For instance, a request for
1450 <application>Privoxy's</application> configuration page at: <ulink
1451 url="http://config.privoxy.org">http://config.privoxy.org</ulink>, is
1452 intercepted (i.e. it does not go out to the 'net), and the familiar CGI
1453 configuration is returned to the browser, and the log consequently will show
1454 a <quote>crunch</quote>.
1458 <sect2 renderas="sect3" id="downloads">
1459 <title>Can <application>Privoxy</application> effect files that I download
1460 from a webserver? FTP server?</title>
1462 From the webserver's perspective, there is no difference between
1463 viewing a document (i.e. a page), and downloading a file. The same is true of
1464 <application>Privoxy</application>. If there is a match for a <literal><ulink
1465 url="../user-manual/actions-file.html#BLOCK">block</ulink></literal> pattern,
1466 it will still be blocked, and of course this is obvious. Filtering is
1467 potentially more of a concern since the results are not always so obvious.
1470 <application>Privoxy</application> knows the differences in files according
1471 to the <quote>Document Type</quote> as reported by the webserver. If this is
1472 reported accurately (e.g. <quote>application/zip</quote> for a zip archive),
1473 then <application>Privoxy</application> knows to ignore these where
1474 appropriate. It is possible, however, that documents that are of an unknown
1475 type (generally assumed to be <quote>text/plain</quote>) will be filtered, as
1476 will those that might be incorrectly reported by the webserver. If such a
1477 file is a downloaded file that is intended to be saved to disk, then any
1478 content that might have been altered by filtering, will be saved too, for
1479 these (probably very rare) cases.
1482 <application>Privoxy</application> does not do FTP at all, only HTTP
1488 <sect2 renderas="sect3" id="seealso">
1489 <title>Where can I find more information about <application>Privoxy</application>
1490 and related issues?</title>
1491 <!-- Include seealso.sgml boilerplate: -->
1493 <!-- end boilerplate -->
1498 <ulink url="../user-manual/seealso.html">user-manual</ulink> for
1504 <sect2 renderas="sect3" id="microsuck">
1505 <title>I've noticed that Privoxy changes <quote>Microsoft</quote> to
1506 <quote>MicroSuck</quote>! Why are you manipulating my browsing?</title>
1509 We're not. The text substitutions that you are seeing are disabled
1510 in the default configuration as shipped. You have either manually
1511 activated the <quote><literal>fun</literal></quote> filter which
1512 is clearly labeled <quote>Text replacements for subversive browsing
1513 fun!</quote> or you have implicitly activated it by choosing the
1514 <quote>Advanced</quote> profile in the web-based editor.
1521 <!-- ~~~~~ New section ~~~~~ -->
1523 <sect1 id="trouble">
1524 <title>Troubleshooting</title>
1526 <sect2 renderas="sect3">
1527 <title id="refused">I just upgraded and am getting <quote>connection refused</quote>
1528 with every web page?</title>
1530 Either <application>Privoxy</application> is not running, or your
1531 browser is configured for a different port than what
1532 <application>Privoxy</application> is using.
1536 The old <application>Privoxy</application> (and also
1537 <application>Junkbuster</application>) used port 8000 by
1538 default. This has been changed to port 8118 now, due to a conflict
1539 with NAS (Network Audio Service), which uses port 8000. If you haven't,
1540 you need to change your browser to the new port number, or alternately
1542 url="../user-manual/config.html#LISTEN-ADDRESS"><literal>listen-address</literal>
1543 option</ulink> in <application>Privoxy's</application> <ulink
1544 url="../user-manual/config.html">main configuration file</ulink>.
1549 <sect2 renderas="sect3">
1550 <title id="flushit">I just added a new rule, but the steenkin ad is
1551 still getting through. How?</title>
1553 If the ad had been displayed before you added its URL, it will probably be
1554 held in the browser's cache for some time, so it will be displayed without
1555 the need for any request to the server, and <application>Privoxy</application>
1556 will not be in the picture. The best thing to do is try flushing the browser's
1557 caches. And then try again.
1561 If this doesn't help, you probably have an error in the rule you
1562 applied. Try pasting the full URL of the offending ad into <ulink
1563 url="http://config.privoxy.org/show-url-info">http://config.privoxy.org/show-url-info</ulink>
1564 and see if it really matches your new rule.
1569 <sect2 id="badsite" renderas="sect3">
1570 <title >One of my favorite sites does not work with <application>Privoxy</application>.
1571 What can I do?</title>
1574 First verify that it is indeed a <application>Privoxy</application> problem,
1575 by toggling off <application>Privoxy</application> through <ulink
1576 url="http://config.privoxy.org/toggle">http://config.privoxy.org/toggle</ulink>,
1577 and then shift-reloading the problem page (i.e. holding down the shift key
1578 while clicking reload. Alternatively, flush your browser's disk and memory
1583 If still a problem, go to <ulink
1584 url="http://config.privoxy.org/show-url-info">http://config.privoxy.org/show-url-info</ulink>
1585 and paste the full URL of the page in question into the prompt. See which actions
1586 are being applied to the URL, and which matches in which actions files are
1587 responsible for that. Now, armed with this information, go to <ulink
1588 url="http://config.privoxy.org/show-status">http://config.privoxy.org/show-status</ulink>
1589 and select the appropriate actions files for editing.
1592 You can now either look for a section which disables the actions that
1593 you suspect to cause the problem and add a pattern for your site there,
1594 or make up a completely new section for your site. In any case, the recommended
1595 way is to disable only the prime suspect, reload the problem page, and only
1596 if the problem persists, disable more and more actions until you have
1597 identified the culprit. You may or may not want to turn the other actions
1598 on again. Remember to flush your browser's caches in between any such changes!
1601 Alternately, if you are comfortable with a text editor, you can accomplish
1602 the same thing by editing the appropriate actions file. Probably the easiest
1603 way to deal with such problems when editing by hand is to add your
1604 site to a <literal>{ fragile }</literal> section in <filename>user.action</filename>,
1605 which is an alias that turns off most <quote>dangerous</quote>
1606 actions, but is also likely to turn off more actions then needed, and thus lower
1607 your privacy and protection more than necessary,
1610 Troubleshooting actions is discussed in more detail in the <ulink
1611 url="../user-manual/appendix.html#ACTIONSANAT">user-manual appendix</ulink>.
1612 There is also an <ulink
1613 url="../user-manual/actions-file.html#ACT-EXAMPLES">actions tutorial</ulink>.
1619 <!-- ~~~~~ New section ~~~~~ -->
1620 <sect2 id="dun" renderas="sect3">
1621 <title>After installing <application>Privoxy</application>, I have to log in
1622 every time I start IE. What gives?</title>
1625 This is a quirk that effects the installation of
1626 <application>Privoxy</application>, in conjunction with Internet Explorer and
1627 Internet Connection Sharing on Windows 2000 and Windows XP. The symptoms may
1628 appear to be corrupted or invalid DUN settings, or passwords.
1632 When setting up an NT based Windows system with
1633 <application>Privoxy</application> you may find that things do not seem to be
1634 doing what you expect. When you set your system up you will probably have set
1635 up Internet Connection Sharing (ICS) with Dial up Networking (DUN) when
1636 logged in with administrator privileges. You will probably have made this DUN
1637 connection available to other accounts that you may have set-up on your
1638 system. E.g. Mum or Dad sets up the system and makes accounts suitably
1639 configured for the kids.
1643 When setting up <application>Privoxy</application> in this environment you
1644 will have to alter the proxy set-up of Internet Explorer (IE) for the
1645 specific DUN connection on which you wish to use
1646 <application>Privoxy</application>. When you do this the ICS DUN set-up
1647 becomes user specific. In this instance you will see no difference if you
1648 change the DUN connection under the account used to set-up the connection.
1649 However when you do this from another user you will notice that the DUN
1650 connection changes to make available to "Me only". You will also find that
1651 you have to store the password under each different user!
1655 The reason for this is that each user's set-up for IE is user specific. Each
1656 set-up DUN connection and each LAN connection in IE store the settings for
1657 each user individually. As such this enforces individual configurations
1658 rather than common ones. Hence the first time you use a DUN connection after
1659 re-booting your system it may not perform as you expect, and prompt you for
1660 the password. Just set and save the password again and all should be OK.
1664 [Thanks to Ray Griffith for this submission.]
1669 <!-- ~~~~~ New section ~~~~~ -->
1670 <sect2 id="ftp" renderas="sect3">
1671 <title>I cannot connect to any FTP sites. <application>Privoxy</application>
1672 seems to be blocking me.</title>
1674 <application>Privoxy</application> cannot act as a proxy for FTP traffic,
1675 so do not configure your browser to use <application>Privoxy</application>
1676 as an FTP proxy. The same is true for any protocol other than HTTP or HTTPS.
1680 <!-- ~~~~~ New section ~~~~~ -->
1681 <sect2 id="osxie" renderas="sect3">
1682 <title>In Mac OSX, I can't configure Microsoft Internet Explorer to use
1683 <application>Privoxy</application> as the HTTP proxy.</title>
1685 Microsoft Internet Explorer (in versions like 5.1) respects system-wide
1686 network settings. In order to change the HTTP proxy, open System
1687 Preferences, and click on the Network icon. In the settings pane that
1688 comes up, click on the Proxies tab. Ensure the "Web Proxy (HTTP)" checkbox
1689 is checked and enter <literal>127.0.0.1</literal> in the entry field.
1690 Enter <literal>8118</literal> in the Port field. The next time you start
1691 IE, it should reflect these values.
1695 <!-- ~~~~~ New section ~~~~~ -->
1696 <sect2 renderas="sect3" id="osxuninstall">
1697 <title>In Mac OSX, I dragged the Privoxy folder to the trash in order to
1698 uninstall it. Now the finder tells me I don't have sufficient privileges to
1699 empty the trash.</title>
1701 Just dragging the <application>Privoxy</application> folder to the trash is
1702 not enough to delete it. <application>Privoxy</application> supplies an
1703 <application>uninstall.command</application> file that takes care of
1704 these details. Open the trash, drag the <application>uninstall.command</application>
1705 file out of the trash and double-click on it. You will be prompted for
1706 confirmation and the administration password.
1709 The trash may still appear full after this command; emptying the trash
1710 from the desktop should make it appear empty again.
1715 <!-- ~~~~~ New section ~~~~~ -->
1716 <sect2 renderas="sect3" id="blankpage">
1717 <title>I get a completely blank page at one site. <quote>View Source</quote>
1718 shows only: <markup><![CDATA[<html><body></body></html>]]></markup>. Without
1719 <application>Privoxy</application> the page loads fine.</title>
1721 Chances are that the site suffers from a bug in
1722 <ulink url="http://www.php.net/"><application>PHP</application></ulink>,
1723 which results in empty pages being sent if the client explicitly requests
1724 an uncompressed page, like <application>Privoxy</application> does.
1725 This bug has been fixed in PHP 4.2.3.
1728 To find out if this is in fact the source of the problem, try adding
1729 the site to a <literal>-prevent-compression</literal> section in
1730 <filename>user.action</filename>:
1733 # Make exceptions for ill-behaved sites:
1735 {-prevent-compression}
1736 .example.com</screen>
1738 If that works, you may also want to report the problem to the
1739 site's webmasters, telling them to use zlib.output_compression
1740 instead of ob_gzhandler in their PHP applications (workaround)
1741 or upgrade to PHP 4.2.3 or later (fix).
1751 <!-- ~~~~~ New section ~~~~~ -->
1753 FIXME: Commented out until we have something to put here. HB 03/18/02.
1754 <sect1 id="knownissues"><title>Known Issues</title>
1761 <!-- ~~~~~ New section ~~~~~ -->
1762 <sect1 id="contact"><title>Contacting the developers, Bug Reporting and Feature Requests</title>
1763 <!-- Include contacting.sgml -->
1765 <!-- end contacting -->
1768 <!-- ~~~~~ New section ~~~~~ -->
1769 <sect1 id="copyright"><title>Privoxy Copyright, License and History</title>
1771 <!-- Include copyright.sgml -->
1776 Portions of this document are <quote>borrowed</quote> from the original
1777 <application>Junkbuster</application> (tm) FAQ, and modified as
1778 appropriate for <application>Privoxy</application>.
1781 <!-- ~~~~~ New section ~~~~~ -->
1782 <sect2><title>License</title>
1783 <!-- Include copyright.sgml: -->
1785 <!-- end copyright -->
1787 <!-- ~ End section ~ -->
1789 <!-- ~~~~~ New section ~~~~~ -->
1790 <sect2><title>History</title>
1791 <!-- Include history.sgml -->
1797 <!-- ~ End section ~ -->
1800 <!-- ~~~~~ New section ~~~~~ -->
1802 <sect1 id="seealso"><title>See also</title>
1804 <!-- Include seealso.sgml -->
1815 Tue 09/11/01 06:38:14 PM EST: Test SGML doc by Hal Burgiss.
1817 Last modified: Mon Sep 10 19:22:09 CEST 2001
1819 This program is free software; you can redistribute it
1820 and/or modify it under the terms of the GNU General
1821 Public License as published by the Free Software
1822 Foundation; either version 2 of the License, or (at
1823 your option) any later version.
1825 This program is distributed in the hope that it will
1826 be useful, but WITHOUT ANY WARRANTY; without even the
1827 implied warranty of MERCHANTABILITY or FITNESS FOR A
1828 PARTICULAR PURPOSE. See the GNU General Public
1829 License for more details.
1831 The GNU General Public License should be included with
1832 this file. If not, you can view it at
1833 http://www.gnu.org/copyleft/gpl.html
1834 or write to the Free Software Foundation, Inc., 59
1835 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
1838 Revision 2.2 2002/09/05 04:25:05 hal9
1839 Sync with 3.0 branch. No new content.
1841 Revision 1.61.2.19 2002/08/25 23:31:56 hal9
1842 Fix one grammatical error. Add brief FAQ relating to tranparent proxies (ie
1843 port 80 setting). Add FAQ on effects of Privoxy on downloaded files
1844 (especially filtering).
1846 Revision 1.61.2.18 2002/08/14 16:39:37 hal9
1847 Fix wrong tag on FAQ addition.
1849 Revision 1.61.2.17 2002/08/14 00:01:18 hal9
1852 Revision 1.61.2.16 2002/08/13 00:10:38 hal9
1853 Add faq to troubleshooting re: blank page syndrome, ie {-prevent-compression}.
1855 Revision 1.61.2.15 2002/08/10 11:34:22 oes
1856 Add disclaimer about probably being out-of-date
1858 Revision 1.61.2.14 2002/08/07 02:53:43 hal9
1859 Fix some minor markup errors, and move one OSX Q/A to troubleshooting section.
1861 Revision 1.61.2.13 2002/08/06 11:55:32 oes
1862 Added missing close tag
1864 Revision 1.61.2.12 2002/08/06 11:43:46 david__schmidt
1865 Updated OSX uninstall FAQ... we have an uninstall script now.
1867 Revision 1.61.2.11 2002/08/06 08:54:03 oes
1868 Style police: Fixed formatting details
1870 Revision 1.61.2.10 2002/08/02 14:00:25 david__schmidt
1871 Made the OSX removal commands far less dangerous
1873 Revision 1.61.2.9 2002/08/02 13:14:45 oes
1874 Added warning about sudo rm -r for Mac OSX deinstallation; moved this item to install section
1876 Revision 1.61.2.8 2002/08/02 02:01:42 david__schmidt
1877 Add FAQ item for MSIE on OSX HTTP proxy confusion
1879 Revision 1.61.2.7 2002/08/02 01:46:01 david__schmidt
1880 Added FAQ item for Mac OSX uninstall woes
1882 Revision 1.61.2.6 2002/07/30 20:04:56 hal9
1883 Fix typo: 'schould'.
1885 Revision 1.61.2.5 2002/07/26 15:22:58 oes
1886 - Updated to reflect changes in standard.action
1887 - Added info on where to get updated actions files
1889 Revision 1.61.2.4 2002/07/25 21:42:29 hal9
1890 Add brief notes on not proxying non-HTTP protocols.
1892 Revision 1.61.2.3 2002/06/09 16:36:33 hal9
1893 Clarifications on filtering and MIME. Hardcode 'latest release' in index.html.
1895 Revision 1.61.2.2 2002/06/06 02:51:34 hal9
1896 Fix typo in URL http:/config.privoxy.org
1898 Revision 1.61.2.1 2002/06/05 23:10:43 hal9
1899 Add new FAQ re: DUN/IE. Change release date from May to June :)
1901 Revision 1.61 2002/05/25 12:37:25 hal9
1902 Various minor changes and edits.
1904 Revision 1.60 2002/05/22 17:17:48 oes
1905 Proofread & added more links into u-m
1907 Revision 1.59 2002/05/15 04:03:30 hal9
1908 Fix ulink -> link markup.
1910 Revision 1.58 2002/05/10 01:48:20 hal9
1911 This is mostly proposed copyright/licensing additions and changes. Docs
1912 are still GPL, but licensing and copyright are more visible. Also, copyright
1913 changed in doc header comments (eliminate references to JB except FAQ).
1915 Revision 1.57 2002/05/05 20:26:02 hal9
1916 Sorting out license vs copyright in these docs.
1918 Revision 1.56 2002/05/04 08:44:44 swa
1921 Revision 1.55 2002/05/04 00:41:56 hal9
1922 -Remove TOC/first page kludge in favor of proper handling via dsl file.
1924 Revision 1.54 2002/05/03 05:06:44 hal9
1925 Add brief Q/A on transparent proxies.
1927 Revision 1.53 2002/05/03 01:34:52 hal9
1928 Fix section numbering for new sections (due to TOC kludge).
1930 Revision 1.52 2002/04/29 03:08:43 hal9
1931 -Added new Q/A on new actions file set up (pointer to u-m)
1932 -Fixed a few broken links and converted old actions as a result of
1935 Revision 1.51 2002/04/26 17:24:31 swa
1936 bookmarks cleaned, changed structure of user manual, screen and programlisting cleanups, and numerous other changes that I forgot
1938 Revision 1.50 2002/04/26 05:25:23 hal9
1939 Mass commit to catch a few scattered fixes.
1941 Revision 1.49 2002/04/12 10:10:18 swa
1944 Revision 1.48 2002/04/10 18:45:15 swa
1947 Revision 1.47 2002/04/10 04:05:32 hal9
1950 Revision 1.45 2002/04/08 22:59:26 hal9
1951 Version update. Spell chkconfig correctly :)
1953 Revision 1.44 2002/04/07 21:24:29 hal9
1954 Touch up on name change.
1956 Revision 1.43 2002/04/04 21:59:53 hal9
1957 Added NT/W2K service/icon situation.
1959 Revision 1.42 2002/04/04 18:46:47 swa
1960 consistent look. reuse of copyright, history et. al.
1962 Revision 1.41 2002/04/04 06:48:37 hal9
1963 Structural changes to allow for conditional inclusion/exclusion of content
1964 based on entity toggles, e.g. 'entity % p-not-stable "INCLUDE"'. And
1965 definition of internal entities, e.g. 'entity p-version "2.9.13"' that will
1966 eventually be set by Makefile.
1967 More boilerplate text for use across multiple docs.
1969 Revision 1.40 2002/04/03 04:22:03 hal9
1970 Fixed several typos.
1972 Revision 1.39 2002/04/03 03:53:03 hal9
1973 Revert some changes, and then make some news, to layout, and appearance.
1975 Revision 1.38 2002/04/02 03:49:10 hal9
1976 Major changes to doc structure and layout. Sections are not automatically
1977 numbered now. TOC is on page by itself.
1979 Revision 1.37 2002/04/01 16:24:07 hal9
1980 -Rework of supported Q/A.
1981 -Set up entities to include boilerplate text.
1983 Revision 1.36 2002/03/31 23:18:47 hal9
1984 More on dealing with BLOCKED.
1986 Revision 1.35 2002/03/30 04:14:19 hal9
1987 Fix privoxy.org/config links.
1989 Revision 1.34 2002/03/29 04:35:56 hal9
1992 Revision 1.33 2002/03/29 01:31:48 hal9
1993 Several new Q/A's and other touch ups.
1995 Revision 1.32 2002/03/27 00:57:03 hal9
1996 Touch ups for name change.
1998 Revision 1.31 2002/03/26 22:29:55 swa
1999 we have a new homepage!
2001 Revision 1.30 2002/03/25 16:39:22 hal9
2002 A few new sections. Made all links relative to user-manual.
2004 Revision 1.29 2002/03/25 05:23:57 hal9
2005 Moved section, and touch ups.
2007 Revision 1.28 2002/03/25 04:27:33 hal9
2008 New section related to name change.
2010 Revision 1.25 2002/03/24 16:08:08 swa
2011 we are too lazy to make a block-built
2012 privoxy logo. hence removed the option.
2014 Revision 1.24 2002/03/24 15:46:20 swa
2015 name change related issue.
2017 Revision 1.23 2002/03/24 12:33:01 swa
2020 Revision 1.22 2002/03/24 11:51:00 swa
2021 name change. changed filenames.
2023 Revision 1.21 2002/03/24 11:01:06 swa
2026 Revision 1.20 2002/03/23 15:13:11 swa
2027 renamed every reference to the old name with foobar.
2028 fixed "application foobar application" tag, fixed
2029 "the foobar" with "foobar". left junkbustser in cvs
2030 comments and remarks to history untouched.
2032 Revision 1.19 2002/03/21 17:01:54 hal9
2035 Revision 1.18 2002/03/18 16:40:31 hal9
2038 Revision 1.17 2002/03/18 03:53:53 hal9
2041 Revision 1.16 2002/03/17 21:32:56 hal9
2042 A few more additions.
2044 Revision 1.15 2002/03/17 07:25:59 hal9
2045 Correcting some of my typos, and some additions.
2047 Revision 1.14 2002/03/17 02:39:13 hal9
2048 A little more added ...
2050 Revision 1.13 2002/03/17 00:22:20 hal9
2051 Adding new stuff, and trying to incorporate stuff from old faq.
2053 Revision 1.12 2002/03/11 20:13:21 swa
2056 Revision 1.11 2002/03/11 18:42:27 swa
2059 Revision 1.10 2002/03/11 13:13:27 swa
2060 correct feedback channels
2062 Revision 1.9 2002/03/10 23:34:04 swa
2063 more info on not hiding ip address
2065 Revision 1.8 2002/03/09 15:55:48 swa
2066 added default config section
2068 Revision 1.7 2002/03/07 18:16:55 swa
2071 Revision 1.6 2002/03/07 13:16:31 oes
2072 Committing changes by Stefan
2074 Revision 1.5 2002/03/02 15:50:04 swa
2075 2.9.11 version. more input for docs.
2077 Revision 1.4 2002/02/24 14:34:24 jongfoster
2078 Formatting changes. Now changing the doctype to DocBook XML 4.1
2079 will work - no other changes are needed.
2081 Revision 1.3 2001/09/23 10:13:48 swa
2082 upload process established. run make webserver and
2083 the documentation is moved to the webserver. documents
2084 are now linked correctly.
2086 Revision 1.2 2001/09/13 15:20:17 swa
2087 merged standards into developer manual
2089 Revision 1.1 2001/09/12 15:36:41 swa
2090 source files for junkbuster documentation
2092 Revision 1.3 2001/09/10 17:43:59 swa
2093 first proposal of a structure.
2095 Revision 1.2 2001/06/13 14:28:31 swa
2096 docs should have an author.
2098 Revision 1.1 2001/06/13 14:20:37 swa
2099 first import of project's documentation for the webserver.