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 "3.0.0">
12 <!entity p-status "stable">
13 <!entity % p-not-stable "IGNORE">
14 <!entity % p-stable "INCLUDE">
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 1.61.2.25 2002/10/29 03:21:50 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 to live a peaceful existence!
55 Please we keep the info in this file as version independent as possible
56 so we only have to maintain one FAQ. Where significant changes are
57 made to Privoxy configuration, please note the change in such a way that
58 it makes sense to both users of older and newer versions.
59 ========================================================================
65 <article id="index" class="faq">
67 <title>Privoxy Frequently Asked Questions</title>
71 <!-- Completely the wrong markup, but very little is allowed -->
72 <!-- in this part of an article. FIXME -->
73 <link linkend="copyright">Copyright</link> &my-copy; 2001, 2002 by
74 <ulink url="http://www.privoxy.org">Privoxy Developers</ulink>
78 <pubdate>$Id: faq.sgml,v 1.61.2.25 2002/10/29 03:21:50 hal9 Exp $</pubdate>
82 Note: this should generate a separate page, and a live link to it.
83 But it doesn't for some mysterious reason. Please leave commented
84 unless it can be fixed proper. For the time being, the copyright
85 statement will be in copyright.smgl.
89 <legalnotice id="legalnotice">
91 text goes here ........
101 <orgname>By: Privoxy Developers</orgname>
110 This is here to keep vim syntax file from breaking :/
111 If I knew enough to fix it, I would.
112 PLEASE DO NOT REMOVE! HB: hal@foobox.net
117 This FAQ gives quick answers to frequently asked questions about
118 <ulink url="http://www.privoxy.org/">Privoxy</ulink>.
119 It can't and doesn't replace the
120 <ulink url="../user-manual/index.html"><citetitle>User Manual</citetitle></ulink>.
122 This works, at least in some situtations:
123 Test: <ulink url="privoxy-user-manual.pdf"><citetitle>User Manual</citetitle></ulink>.
127 <!-- Include privoxy.sgml boilerplate: -->
129 <!-- end boilerplate -->
132 Please note that this document is constantly evolving. This copy represents
133 the state at the release of version &p-version;.
134 You can find the latest version of the document at <ulink
135 url="http://www.privoxy.org/faq/">http://www.privoxy.org/faq/</ulink>.
136 Please see the <link linkend="contact">Contact section</link> if you want to
137 contact the developers.
141 <!-- Feel free to send a note to the developers at <email>ijbswa-developers@lists.sourceforge.net</email>. -->
147 <!-- ~~~~~ New section ~~~~~ -->
149 <sect1 id="general"><title>General Information</title>
151 <sect2 renderas="sect3" id="newjb"><title>What is this new version of <application>Privoxy</application>?</title>
153 <!-- Include history.sgml -->
160 <sect2 renderas="sect3">
161 <title id="whyprivoxy">Why <quote>Privoxy</quote>? Why a name change at all?</title>
163 <application>Privoxy</application> is the
164 <quote><emphasis>Privacy Enhancing Proxy</emphasis></quote>. Also, its content
165 modification and junk suppression allow you to browse your
166 <quote><emphasis>private</emphasis> edition</quote> of the web.
169 <ulink url="http://junkbusters.com/">Junkbusters Corporation</ulink>
170 continues to offer their original version of the <application>Internet
171 Junkbuster</application>, so publishing our
172 <application> Junkbuster</application>-derived software under the same name
176 There are also potential legal complications from the continued use of the
177 <application>Junkbuster</application> name, which is a registered trademark of
178 <ulink url="http://junkbusters.com/">Junkbusters Corporation</ulink>.
179 There are, however, no objections from Junkbusters Corporation to the
180 <application>Privoxy</application> project itself, and they, in fact, still
181 share our ideals and goals.
184 The developers also believed that there are so many changes from the original
185 code, that it was time to make a clean break from the past and make
186 a name in their own right<![%p-not-stable;[, especially now with the pending
187 release of version 3.0]]>.
192 <sect2 renderas="sect3" id="differs"><title>How does <application>Privoxy</application> differ
193 from the old <application>Junkbuster?</application></title>
195 <application>Privoxy</application> picks up where
196 <application>Junkbuster</application> left off. All the old features remain.
197 The new <application>Privoxy</application> still blocks ads and banners,
198 still manages cookies, and still helps protect your privacy. But, these are
199 all enhanced, and many new features have been added, all in the same vein.
202 The configuration has changed significantly as well. This is something that
203 users will notice right off the bat if upgrading from
204 <application>Junkbuster</application> 2.0.x. The <quote>blocklist</quote>
205 <quote>cookielist</quote>, <quote>imagelist</quote> and much more has been
206 combined into the <quote>actions</quote> files, with a completely different
207 syntax. See the <ulink url="../user-manual/upgradersnote.html">note to
208 upgraders</ulink> for details.
211 <application>Privoxy</application>'s new features include:
214 <!-- Include newfeatures.sgml: -->
220 <sect2 renderas="sect3" id="proxymoron"><title>What is a <quote>proxy</quote>? How does
221 <application>Privoxy</application> work? </title>
223 A web proxy is a service, based on a software such as <application>Privoxy</application>,
224 that clients (i.e. browsers) can use instead of connecting directly to the web
225 servers on the Internet. The clients then ask the proxy to fetch the objects
226 they need (web pages, images, movies etc) on their behalf, and when the proxy
227 has done so, it hands the results back to the client.
230 There are many reasons to use web proxies, such as security (firewalling),
231 efficiency (caching) and others, and there are just as many different proxies
232 to accommodate those needs.
235 <application>Privoxy</application> is a proxy that is solely focused on privacy
236 protection and junk elimination. Sitting between your browser(s) and the Internet,
237 it is in a perfect position to filter outbound personal information that your
238 browser is leaking, as well as inbound junk. It uses a variety of techniques to do
239 this, all of which are under your control via the various configuration
245 <sect2 renderas="sect3" id="whatsanad">
246 <title id="knows">How does <application>Privoxy</application> know what is
247 an ad, and what is not?</title>
249 <application>Privoxy</application>'s approach to blocking ads is twofold:
252 First, there are certain patterns in the <emphasis>locations</emphasis> (URLs)
253 of banner images. This applies to both the path (you wouldn't guess how many
254 web sites serve their banners from a directory called <quote>banners</quote>!)
255 and the host (blocking the big banner hosting services like doublecklick.net
256 already helps a lot). <application>Privoxy</application> takes advantage of this
257 fact by using <ulink url="../user-manual/actions-file.html#AF-PATTERNS">URL
258 patterns</ulink> to sort out and block the requests for banners.
261 Second, banners tend to come in certain <emphasis>sizes</emphasis>. But you
262 can't tell the size of an image by its URL without downloading it, and if you
263 do, it's too late to save bandwidth. Therefore, <application>Privoxy</application>
264 also inspects the HTML sources of web pages while they are loaded, and replaces
265 references to images with standard banner sizes by dummy references, so that
266 your browser doesn't request them anymore in the first place.
269 Both of this involves a certain amount of guesswork and is, of course, freely
274 <sect2 renderas="sect3">
275 <title id="mistakes">Can <application>Privoxy</application> make mistakes?
276 This does not sound very scientific.</title>
278 Actually, it's a black art ;-) And yes, it is always possible to have a broad
279 rule accidentally block or change something by mistake. There is a good chance
280 you may run into such a situation at some point. It is tricky writing rules to
281 cover every conceivable possibility, and not occasionally get false positives.
285 But this should not be a big concern since the
286 <application>Privoxy</application> configuration is very flexible, and
287 includes tools to help identify these types of situations so they can be
288 addressed as needed, allowing you to customize your installation.
289 (<link linkend="badsite">See the Troubleshooting section below</link>.)
295 <sect2 renderas="sect3" id="browsers2"><title>My browser does the same things as
296 <application>Privoxy</application>. Why should I use
297 <application>Privoxy</application> at all?</title>
299 Modern browsers do indeed have <emphasis>some</emphasis> of the same
300 functionality as <application>Privoxy</application>. Maybe this is
301 adequate for you. But <application>Privoxy</application> is much more
302 versatile and powerful, and can do a number of things that browsers just can't.
305 In addition, a proxy is good choice if you use multiple browsers, or
306 have a LAN with multiple computers. This way all the configuration
307 is in one place, and you don't have to maintain a similar configuration
308 for possibly many browsers.
314 <sect2 renderas="sect3" id="license"><title>Is there is a license or fee? What about a
315 warranty? Registration?</title>
317 <application>Privoxy</application> is licensed under the <ulink
318 url="http://www.gnu.org/copyleft/gpl.html">GNU General Public License (GPL)</ulink>.
319 It is free to use, copy, modify or distribute as you wish under the terms of this
320 license. Please see the <link linkend="copyright">Copyright</link> section for more
321 information on the license and copyright. Or the <filename>LICENSE</filename> file
322 that should be included.
325 There is <emphasis>no warranty</emphasis> of any kind, expressed, implied or otherwise.
326 That is something that would cost real money ;-) There is no registration either.
327 <application>Privoxy</application> really is <emphasis>free</emphasis>
333 <sect2 renderas="sect3" id="jointeam"><title>I would like to help you, what do I do?</title>
335 <sect3 renderas="sect4" id="jointeam-money"><title>Money Money Money</title>
337 We, of course, welcome donations and could use money for domain registering,
338 buying software to test <application>Privoxy</application> with, and, of course,
339 for regular world-wide get-togethers (hahaha). If you enjoy the software and feel
340 like helping us with a donation, just <ulink
341 url="mailto:developers@privoxy.org">drop us a note</ulink>.
345 <sect3 renderas="sect4" id="jointeam-software"><title>Software</title>
347 If you are a vendor of a web-related software like a browser, web server
348 or proxy, and would like us to ensure that <application>Privoxy</application>
349 runs smoothly with your product, you might consider supplying us with a
350 copy or license. We can't, however, guarantee that we will fix all potential
351 compatibility issues as a result.
355 <sect3 renderas="sect4" id="jointeam-work"><title>You want to work with us?</title>
357 Well, helping the team is always a good idea. We welcome new developers,
358 packaging gurus or documentation writers. Simply <ulink
359 url="https://sourceforge.net/account/register.php">get an account on SourceForge.net</ulink>
360 and mail your id to the <ulink url="mailto:developers@privoxy.org">developers
361 mailing list</ulink>. Then read the <ulink
362 url="../developer-manual/index.html">Developer's Manual</ulink>.
365 Once we have added you to the team, you'll have write access to the <ulink
366 url="http://sourceforge.net/cvs/?group_id=11118">CVS repository</ulink>, and
367 together we'll find a suitable task for you.
376 <!-- ~~~~~ New section ~~~~~ -->
378 <sect1 id="installation"><title>Installation</title>
380 <sect2 renderas="sect3" id="whichbrowsers">
381 <title>Which browsers are supported by <application>Privoxy</application>?</title>
383 Any browser that can be configured to use a proxy, which
384 should be virtually all browsers. Direct browser support is not necessary
385 since <application>Privoxy</application> runs as a separate application and
386 talks to the browser in the standardized HTTP protocol, just like a web server
391 <sect2 renderas="sect3" id="whichos">
392 <title>Which operating systems are supported?</title>
394 Include supported.sgml here:
399 <sect2 renderas="sect3" id="email-client">
400 <title>Can I use <application>Privoxy</application> with my email client?</title>
402 As long as there is some way to set a HTTP proxy for the client, then yes,
403 any application can be used, whether it is strictly speaking a
404 <quote>browser</quote> or not. Though this may not be the best approach for
405 dealing with some of the common abuses of HTML in email. See <link
406 linkend="outlook">How can I configure <application>Privoxy</application>
407 with <application>Outlook Express</application>?</link> below for more on
411 Be aware that HTML email presents a number of unique security and privacy
412 related issues, that can require advanced skills to overcome. The developers
413 recommend using email clients that can be configured to convert HTML to plain
414 text for these reasons.
418 <sect2 renderas="sect3" id="newinstall"><title>Can I install
419 <application>Privoxy</application> over <application>Junkbuster</application>?</title>
421 We recommend you un-install <application>Junkbuster</application>
422 first to minimize conflicts and confusion. You may want to
423 save your old configuration files for future reference. The configuration
424 files and syntax have substantially changed, so you will need to manually
425 port your old patterns. See the <ulink url="../user-manual/upgradersnote.html">note
426 to upgraders</ulink> and <ulink url="../user-manual/installation.html">installation
427 chapter</ulink> in the <ulink url="../user-manual/index.html">user manual</ulink>
431 Note: Some installers may automatically un-install
432 <application>Junkbuster</application>, if present!
437 <sect2 renderas="sect3">
438 <title id="firststep">I just installed <application>Privoxy</application>. Is there anything
439 special I have to do now?</title>
442 All browsers must be told to use <application>Privoxy</application>
443 as a proxy by specifying the correct proxy address and port number
444 in the appropriate configuration area for the browser. See below.
445 You should also flush your browser's memory and disk cache to get rid of any
446 cached junk items, and remove any stored cookies.
453 <sect2 renderas="sect3" id="localhost"><title>What is the proxy address of <application>Privoxy</application>?</title>
455 If you set up the <application>Privoxy</application> to run on
456 the computer you browse from (rather than your ISP's server or some
457 networked computer on a LAN), the proxy will be on <literal>127.0.0.1</literal>
458 (sometimes referred to as <quote>localhost</quote>,
459 which is the special name used by every computer on the Internet to refer
460 to itself) and the port will be 8118 (unless you have <application>Privoxy</application>
461 to run on a different port with the <ulink
462 url="../user-manual/config.html#LISTEN-ADDRESS">listen-address</ulink> config option).
465 When configuring your browser's proxy settings you typically enter
466 the word <quote>localhost</quote> or the IP address <quote>127.0.0.1</quote>
467 in the boxes next to <quote>HTTP</quote> and <quote>Secure</quote> (HTTPS) and
468 then the number <quote>8118</quote> for <quote>port</quote>.
469 This tells your browser to send all web requests to <application>Privoxy</application>
470 instead of directly to the Internet.
473 <application>Privoxy</application> can also be used to proxy for
474 a Local Area Network. In this case, your would enter either the IP
475 address of the LAN host where <application>Privoxy</application>
476 is running, or the equivalent hostname. Port assignment would be
477 same as above. Note that <application>Privoxy</application> doesn't
478 listen on any LAN interfaces by default.
481 <application>Privoxy</application> does not currently handle
482 protocols such as FTP, SMTP, IM, IRC, ICQ, or other Internet
487 <sect2 renderas="sect3" id="nothing">
488 <title>I just installed <application>Privoxy</application>, and nothing is happening.
489 All the ads are there. What's wrong?</title>
492 Did you configure your browser to use <application>Privoxy</application>
493 as a proxy? It does not sound like it. See above. You might also try flushing
494 the browser's caches to force a full re-reading of pages. You can verify
495 that <application>Privoxy</application> is running, and your browser
496 is correctly configured by entering the special URL:
497 <ulink url="http://config.privoxy.org/">http://config.privoxy.org/</ulink>.
498 This should take you to a page titled <quote>This is Privoxy..</quote> with
499 access to <application>Privoxy's</application> internal configuration.
500 If you see this, then you are good to go. If you receive a page saying
501 <quote>Privoxy is not running</quote>, then the browser is not set up to use
502 your <application>Privoxy</application> installation.
503 If you receive anything else (probably nothing at all), it could either
504 be that the browser is not set up correctly, or that
505 <application>Privoxy</application> is not running at all. Check the <ulink
506 url="../user-manual/config.html#LOGFILE">log file</ulink>.
514 <!-- ~~~~~ New section ~~~~~ -->
516 <sect1 id="configuration"><title>Configuration</title>
518 <sect2 renderas="sect3" id="getupdates"><title>Where can I get updated Actions Files?</title>
520 Based on your feedback and the continuing development, updated actions files will be
521 made available on the <ulink
522 url="http://sourceforge.net/project/showfiles.php?group_id=11118">files section</ulink> of
523 our <ulink url="http://sf.net/projects/ijbswa/">project page</ulink>.
527 If you wish to receive an email notification whenever we release updates of
528 <application>Privoxy</application> or the actions file, <ulink
529 url="http://lists.sourceforge.net/lists/listinfo/ijbswa-announce/">subscribe
530 to our announce mailing list</ulink>, ijbswa-announce@lists.sourceforge.net.
535 <sect2 renderas="sect3" id="newconfig"><title>Can I use my old config files?</title>
537 The syntax, number, and purpose of configuration files has substantially
538 changed from <application>Junkbuster</application> and earlier versions
539 of <application>Privoxy</application>. The old files, like <filename>blocklist</filename>
540 will not work at all. If you are upgrading from a 2.0.x version, you will
541 need to port your configuration data to the new format. Note that even the
542 pattern syntax has changed! Even configuration files from the 2.9.x versions
543 will need to be adapted, as configuration syntax has been very much in flow
548 <sect2 renderas="sect3">
549 <title id="actionsfile">What is an <quote>actions</quote> file?</title>
552 <ulink url="../user-manual/actions-file.html">Actions files</ulink>
553 are where various <ulink url="../user-manual/actions-file.html#ACTIONS">actions</ulink>
554 that <application>Privoxy</application> might take while processing a certain
555 request, are configured. Typically, you would define a set of default actions
556 that apply to all URLs, then add exceptions to these defaults where needed.
560 Actions can be defined on a <ulink
561 url="../user-manual/actions-file.html#AF-PATTERNS">URL pattern</ulink> basis, i.e.
562 for single URLs, whole web sites, groups or parts thereof etc. Actions can also be
563 grouped together and then applied to requests matching one or more patterns.
564 There are many possible actions that might apply to any given site. As an example,
565 if you are blocking cookies as one of your default actions, but need to accept
566 cookies from a given site, you would need to define an exception for this
567 site in one of your actions files, preferably in <filename>user.action</filename>.
572 <sect2 renderas="sect3" id="actionss">
573 <title>The <quote>actions</quote> concept confuses me. Please list
574 some of these <quote>actions</quote>.</title>
576 For a comprehensive discussion of the actions concept, please refer
577 to the <ulink url="../user-manual/actions-file.html">actions file
578 chapter</ulink> in the <ulink url="../user-manual/index.html">user
579 manual</ulink>. It includes a <ulink
580 url="../user-manual/actions-file.html#ACTIONS">list of all actions</ulink>
581 and an <ulink url="../user-manual/actions-file.html#ACT-EXAMPLES">actions
582 file tutorial</ulink> to get you started.
587 <sect2 renderas="sect3">
588 <title id="actconfig">How are actions files configured? What is the easiest
589 way to do this?</title>
592 Actions files are just text files in a special syntax and can be edited
593 with a text editor. But probably the easiest way is to access
594 <application>Privoxy</application>'s user interface with your web browser
595 at <ulink url="http://config.privoxy.org/">http://config.privoxy.org/</ulink>
596 (Shortcut: <ulink url="http://p.p/">http://p.p/</ulink>) and then select
597 <quote><ulink url="http://config.privoxy.org/show-status">View &
598 change the current configuration</ulink></quote> from the menu.
603 <sect2 renderas="sect3">
604 <title>There are several different <quote>actions</quote> files. What are
605 the differences?</title>
607 As of <application>Privoxy</application> v2.9.15, three actions files
608 are being included, to be used for
609 different purposes: These are
610 <filename>default.action</filename>, the <quote>main</quote> actions file
611 which is actively maintained by the <application>Privoxy</application>
612 developers, <filename>user.action</filename>, where users are encouraged
613 to make their private customizations, and <filename>standard.action</filename>,
614 which is for internal <application>Privoxy</application> use only.
615 Please see <ulink url="../user-manual/actions-file.html">the actions chapter</ulink>
616 in the <ulink url="../user-manual/index.html">user manual</ulink> for a more
617 detailed explanation.
621 Earlier versions included three different versions of the
622 <filename>default.action</filename> file. The new scheme allows for
623 greater flexibility of local configuration, and for browser based
624 selection of pre-defined <quote>aggressiveness</quote> levels.
629 <sect2 renderas="sect3" id="yahoo"><title>How can I make my Yahoo/Hotmail/GMX account work?</title>
631 The default configuration shouldn't impact the usability of any of these services.
632 It will, however, make all cookies temporary, so that your browser will forget your
633 login credentials in between browser sessions. If you would like not to have to log
634 in manually each time you access those websites, simply turn off all cookie handling
635 for them in the <filename>user.action</filename> file. An example for yahoo might
639 <screen># Allow all cookies for Yahoo login:
641 { -<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> }
642 .login.yahoo.com</screen>
647 <sect2 renderas="sect3" id="configfiles"> <title>What's the difference between the
648 <quote>Cautious</quote>, <quote>Medium</quote> and <quote>Radical</quote> defaults?</title>
650 Configuring <application>Privoxy</application> is not entirely trivial. To
651 help you get started, we provide you with three different default action
652 <quote>profiles</quote> in the web based actions file editor at <ulink
653 url="http://config.privoxy.org/show-status">http://config.privoxy.org/show-status</ulink>.
654 See the <ulink url="../user-manual/actions-file.html"><citetitle>User
655 Manual</citetitle></ulink> for a list of actions, and how the default
660 Where the defaults are likely to break some sites, exceptions for
661 known popular <quote>problem</quote> sites are included, but in
662 general, the more aggressive your default settings are, the more exceptions
663 you will have to make later. See the <ulink
664 url="../user-manual/index.html"><citetitle>User Manual</citetitle></ulink>
665 for a more deatiled discussion.
669 It should be noted that the <quote>Radical</quote> profile (formerly known
670 as the <quote>Advanced</quote> profile) is not only more
671 aggressive, but also includes fun and, extreme usage of most of
672 <application>Privoxy's</application> features. Use at your own risk!
677 <sect2 renderas="sect3" id="browseconfig"> <title>Why can I change the configuration
678 with a browser? Does that not raise security issues?</title>
680 It may seem strange that regular users can edit the config files with their
681 browsers, although the whole <filename>/etc/privoxy</filename> hierarchy
682 belongs to the user <quote>privoxy</quote>, with only 644 permissions.
685 When you use the browser-based editor, <application>Privoxy</application>
686 itself is writing to the config files. Because
687 <application>Privoxy</application> is running as the user <quote>privoxy</quote>,
688 it can update the config files.
691 If you run <application>Privoxy</application> for multiple untrusted users (e.g. in
692 a LAN), you will probably want to turn the web-based editor and remote toggle
693 features off by setting <quote><literal><ulink
694 url="../user-manual/config.html#ENABLE-EDIT-ACTIONS">enable-edit-actions</ulink>
695 0</literal></quote> and <quote><literal><ulink
696 url="../user-manual/config.html#ENABLE-REMOTE-TOGGLE">enable-remote-toggle</ulink>
697 0</literal></quote> in the <ulink url="../user-manual/config.html">main configuration file</ulink>.
700 Note that in the default configuration, only local users (i.e. those on
701 <quote>localhost</quote>) can connect to <application>Privoxy</application>,
702 so this is not (normally) a security problem.
707 <sect2 renderas="sect3">
708 <title id="filterfile">What is the <filename>default.filter</filename> file? What is a <quote>filter</quote>?</title>
710 The <ulink url="../user-manual/filter-file.html"><filename>default.filter</filename></ulink>
711 file is where <emphasis>filters</emphasis> are defined, which can be used to modify or
712 remove, web page content on the fly. Filters apply to <emphasis>anything</emphasis>
713 in the page source, including HTML tags, and JavaScript. Regular expressions are used
714 to accomplish this. There are a number of pre-defined filters to deal with common
715 annoyances. The filters are only defined here, to invoke them, you need to use the
717 url="../user-manual/actions-file.html#FILTER"><literal>filter</literal>
718 action</ulink> in one of the actions files. Filtering is automatically
719 disabled for inappropriate MIME types.
723 If you are familiar with regular expressions, and HTML, you can look at
724 the provided <filename>default.filter</filename> with a text editor and define
725 your own filters. This is potentially a very powerful feature, but
726 requires some expertise in both regular expressions and HTML/HTTP.
730 Presently, there is no GUI editor option for this part of the configuration,
731 but you can disable/enable the various pre-defined filters of the included
732 <filename>default.filter</filename> file with the <ulink
733 url="http://config.privoxy.org/show-status">web-based actions file editor</ulink>.
738 <sect2 renderas="sect3">
739 <title id="lanconfig">How can I set up <application>Privoxy</application> to act as a proxy for my
742 By default, <application>Privoxy</application> only responds to requests
743 from <literal>127.0.0.1</literal> (localhost). To have it act as a server for
744 a network, this needs to be changed in the <ulink
745 url="../user-manual/config.html">main configuration file</ulink>. Look for
747 url="../user-manual/config.html#LISTEN-ADDRESS">listen-address</ulink></literal>
748 option, which may be commented out with a <quote>#</quote> symbol. Make sure
749 it is uncommented, and assign it the address of the LAN gateway interface,
750 and port number to use. Assuming your LAN address is 192.168.1.1 and you
751 wish to run <application>Privoxy</application> on port 8118, this line
757 listen-address 192.168.1.1:8118</screen>
761 Save the file, and restart <application>Privoxy</application>. Configure
762 all browsers on the network then to use this address and port number.
766 Alternately, you can have <application>Privoxy</application> listen on
767 all available interfaces:
772 listen-address :8118</screen>
776 And then use <application>Privoxy's</application>
778 url="../user-manual/config.html#PERMIT-ACCESS">permit-access</ulink>
779 feature to limit connections. A firewall in this situation is recommended
784 The above steps should be the same for any TCP network, regardless of
789 If you run <application>Privoxy</application> on a LAN with untrusted users,
790 we recommend that you double-check the <ulink
791 url="../user-manual/config.html#ACCESS-CONTROL">access control and security</ulink>
798 <sect2 renderas="sect3">
799 <title id="noseeum">Instead of ads, now I get a checkerboard pattern. I don't want to see anything.</title>
801 The replacement for blocked images can be controlled with the <ulink
802 url="../user-manual/actions-file.html#SET-IMAGE-BLOCKER"><literal>set-image-blocker</literal>
803 action</ulink>. You have the choice of a checkerboard pattern, a transparent 1x1 GIF
804 image (aka <quote>blank</quote>), or a redirect to a custom image of your choice.
805 Note that this choice only has effect for images which are blocked as images, i.e.
806 whose URLs match both a <literal><ulink
807 url="../user-manual/actions-file.html#HANDLE-AS-IMAGE">handle-as-image</ulink></literal>
808 <emphasis>and</emphasis> <literal><ulink
809 url="../user-manual/actions-file.html#BLOCK">block</ulink></literal> action.
812 If you want to see nothing, then change the <ulink
813 url="../user-manual/actions-file.html#SET-IMAGE-BLOCKER"><literal>set-image-blocker</literal>
814 action</ulink> to <quote>blank</quote>. This can be done by editing the
815 <filename>default.action</filename> file, or trough the <ulink
816 url="http://config.privoxy.org/show-status">web-based actions file editor</ulink>.
821 <sect2 renderas="sect3">
822 <title id="whyseeum">Why would anybody want to see a checkerboard pattern?</title>
824 Remember that <link linkend="whatsanad">telling which image is an ad and which
825 isn't</link>, is mostly guesswork. While we hope that the standard configuration
826 is rather smart, it can and will make errors. The checkerboard image is visually
827 decent, but it shows you that and where images were blocked, which can be very
828 helpful in case some navigation aid or otherwise innocent image was
829 erraneously blocked. Some people might also enjoy seeing how many banners
830 they <emphasis>don't</emphasis> have to see..
835 <!-- This has changed with the adaptive "blocked" page
837 <sect2 renderas="sect3">
838 <title id="blockedisugly">I see large red banners on some pages that say
839 <quote>Blocked</quote>. Why and how do I get rid of this?</title>
841 These are URLs that match something in one of
842 <application>Privoxy's</application> block actions
844 url="../user-manual/actions-file.html#BLOCK"><quote>+block</quote></ulink>).
845 It is meant to be a warning so that you know something has been blocked and
846 an easy way for you to see why. These are handled differently than what has
847 been defined explicitly as <quote>images</quote> (e.g. ads that are GIF image
848 files). Depending on the URL itself, it is sometimes hard for
849 <application>Privoxy</application> to really know whether there is indeed an
850 ad image there or not. And there are limitations as to what
851 <application>Privoxy</application> can do to <quote>fool</quote> the
856 For instance, if the ad is in a frame, then it is embedded in the separate
857 HTML page used for the frame. In this case, you cannot just substitute an
858 aribitrary image (like we would for a <quote>blank</quote> image), for an HTML
859 page. The browser is expecting an HTML page, and that is what it must have
860 for frames. Such situations can be a little trickier to deal with, and
861 <application>Privoxy</application> may show the <quote>Blocked</quote> page,
862 despite your best efforts.
866 If you want these to be treated as if they were images, so that they can be
867 made invisible, you can try moving the offending URL from the
868 <quote>+block</quote> section to the <quote>+imageblock</quote> section of
869 your actions file. Just be forewarned, if any URL is made
870 <quote>invisible</quote>, you may not have any inkling that something has
871 been removed from that page, or why. If this approach does not work, then you are
872 probably dealing with a frame (or <quote>ilayer</quote>), and the only thing
873 that can go there is an HTML page of some sort.
876 To deal with this situation, you could modify the
877 <quote><filename>block</filename></quote> HTML template that is used by
878 <application>Privoxy</application> to display this, and make it something
879 more to your liking. Currently, there is no configuration option for this.
880 You will have to modify, or create your own page, and use this to replace
881 <filename>templates/blocked</filename>, which is what
882 <application>Privoxy</application> uses to display the <quote>Blocked</quote>
886 Another way to deal with this is find why and where
887 <application>Privoxy</application> is blocking the frame, and
888 diable this. Then let the <quote>+set-image-blocker</quote> action
889 handle the ad that is embedded in the frame's HTML page.
894 <sect2 renderas="sect3" id="alliseeisred">
895 <title>I cannot see all of the <quote>Blocked</quote> page banner. Help.</title>
897 There is not enough available space to fit the entire Blocked page. Try right
898 clicking on the visible portion, and select <quote>Show Frame</quote>,
899 or equivalent. This will usually allow you to see the entire Privoxy
900 <quote>Blocked</quote> page, and from there you can see just what is being
904 As of Privoxy 2.9.14, the Blocked banner page is re-sizeable, and tries
905 to adjust to the allotted space. There may be occassions where there
906 just isn't enough room to display much of anything useful though.
913 <sect2 renderas="sect3">
914 <title id="blockedbytext">I see some images being replaced by a text
915 instead of the checkerboard image. Why and how do I get rid of this?</title>
917 This happens when the banners are not embedded in the HTML code of the
918 page itself, but in separate HTML (sub)documents that are loaded into (i)frames
919 or (i)layers, and these external HTML documents are blocked. Being non-images
920 they get replaced by a substitute HTML page rather than a substitute image,
921 which wouldn't work out technically, since the browser expects and accepts
922 only HTML when it has requested an HTML document.
925 The substitute page adapts to the available space and shows itself as a
926 miniature two-liner if loaded into small frames, or full-blown with a
927 large red "BLOCKED" banner if space allows.
930 If you prefer the banners to be blocked by images, you must see to it that
931 the HTML documents in which they are embedded are not blocked. Clicking
932 the <quote>See why</quote> link offered in the substitute page will show
933 you which rule blocked the page. After changing the rule and un-blocking
934 the HTML documents, the browser will try to load the actual banner images
935 and the usual image blocking will (hopefully!) kick in.
940 <sect2 renderas="sect3" id="srvany">
941 <title>Can <application>Privoxy</application> run as a service
944 Yes, it can run as a system service using <command>srvany.exe</command>.
945 See the discussion at <ulink
946 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>,
947 for details, and a sample configuration.
950 Version 3.0.1 fixes the problem where the icon and menu where not available
951 in the taskbar for this usage.
956 <sect2 renderas="sect3" id="otherproxy">
957 <title>How can I make <application>Privoxy</application> work with other
958 proxies like <application>Squid</application>?</title>
960 This can be done and is often useful to combine the benefits of
961 <application>Privoxy</application> with those of a caching proxy.
963 url="../user-manual/config.html#FORWARDING">forwarding chapter</ulink>
964 in the <ulink url="../user-manual/index.html">user manual</ulink> which
965 describes how to do this.
969 <sect2 renderas="sect3" id="port-80">
970 <title>Can I just set <application>Privoxy</application> to use port 80
971 and thus avoid individual browser configuration?</title>
974 No, its more complicated than that. This only works with special kinds
975 of proxies known as <quote>transparent</quote> proxies (see below).
980 <sect2 renderas="sect3" id="transparent">
981 <title>Can <application>Privoxy</application> run as a <quote>transparent
982 </quote> proxy?</title>
984 No, <application>Privoxy</application> currently does not have this ability,
985 though it is planned for a future release. Transparent proxies require
986 special handling of the request headers beyond what
987 <application>Privoxy</application> is now capable of.
991 Chaining <application>Privoxy</application> behind another proxy that has
992 this ability should work though.
994 url="../user-manual/config.html#FORWARDING">forwarding chapter</ulink>
995 in the <ulink url="../user-manual/index.html">user manual</ulink>. As
996 a transparent proxy to be used for chaining we recommend Transproxy
997 (<ulink url="http://www.transproxy.nlc.net.au/">http://www.transproxy.nlc.net.au/</ulink>).
1002 <sect2 renderas="sect3" id="outlook">
1003 <title>How can I configure <application>Privoxy</application> for use with <application>Outlook
1004 Express</application>?</title>
1006 <application>Outlook Express</application> uses <application>Internet Explorer</application>
1007 components to both render HTML, and fetch any HTTP requests that may be embedded in an HTML email.
1008 So however you have <application>Privoxy</application> configured to work
1009 with IE, this configuration should automatically be shared.
1013 <sect2 renderas="sect3" id="outlook-more">
1014 <title>How can I have separate rules just for HTML mail?</title>
1016 The short answer is, you can't. <application>Privoxy</application> has no way
1017 of knowing which particular application makes a request, so there is no way to
1018 distinguish between web pages and HTML mail.
1019 <application>Privoxy</application> just blindly proxies all requests. In the
1020 case of <application>Outlook Express</application> (see above), OE uses
1021 IE anyway, and there is no way for <application>Privoxy</application> to ever
1022 be able to distinguish between them (nor could any other proxy type application for
1026 For a good discussion of some of the issues involved (including privacy and
1027 security issues), see
1028 <ulink url="http://sourceforge.net/tracker/?func=detail&atid=211118&aid=629518&group_id=11118">http://sourceforge.net/tracker/?func=detail&atid=211118&aid=629518&group_id=11118</ulink>.
1032 <sect2 renderas="sect3" id="allow-cookies">
1033 <title>How can I allow permanent cookies for my trusted sites?</title>
1036 There are several actions that relate to cookies. The default behavior is to
1037 allow only <quote>session cookies</quote>, which means the cookies only last
1038 for the current browser session. This eliminates most kinds of abuse related
1039 to cookies. But there may be cases where we want cookies to last.
1042 To disable all cookie actions, so that cookies are allowed unrestricted,
1043 both in and out, for <literal>example.com</literal>:
1047 { -crunch-incoming-cookies -crunch-outgoing-cookies -session-cookies-only -filter{content-cookies} }
1048 .example.com</screen>
1051 Place the above in <filename>user.action</filename>. Note some of these may
1052 be off by default anyway, so this might be redundant, but there is no harm
1053 being explicit in what you want to happen. <filename>user.action</filename>
1054 includes an alias for this situation, called
1055 <literal>allow-cookies</literal>.
1061 <!-- ~ End section ~ -->
1064 <!-- ~~~~~ New section ~~~~~ -->
1066 <sect1 id="misc"><title>Miscellaneous</title>
1068 <sect2 renderas="sect3">
1069 <title id="slowsme">How much does <application>Privoxy</application> slow my browsing down? This
1070 has to add extra time to browsing.</title>
1072 It should not slow you down any in real terms, and may actually help
1073 speed things up since ads, banners and other junk are not being displayed.
1074 The actual processing time required by <application>Privoxy</application>
1075 itself for each page, is relatively small in the overall scheme of things,
1076 and happens very quickly. This is typically more than offset by time saved
1077 not downloading and rendering ad images.
1081 <quote>Filtering</quote> content via the <literal><ulink
1082 url="../user-manual/actions-file.html#FILTER">filter</ulink></literal> or
1084 url="../user-manual/actions-file.html#DEANIMATE-GIFS">deanimate-gifs</ulink></literal>
1085 actions may cause a perceived slowdown, since the entire document needs to be buffered
1086 before displaying. See below.
1092 <sect2 renderas="sect3" id="loadingtimes"><title>I noticed considerable
1093 delays in page requests compared to the old Junkbuster. What's wrong?</title>
1095 If you use any <literal><ulink
1096 url="../user-manual/actions-file.html#FILTER">filter</ulink></literal> action,
1097 such as filtering banners by size, web-bugs etc, or the <literal><ulink
1098 url="../user-manual/actions-file.html#DEANIMATE-GIFS">deanimate-gifs</ulink></literal>
1099 action, the entire document must be loaded into memory in order for the filtering
1100 mechanism to work, and nothing is sent to the browser during this time.
1103 The loading time does not really change in real numbers, but the feeling is
1104 different, because most browsers are able to start rendering incomplete
1105 content, giving the user a feeling of "it works". This effect is especially
1106 noticeable on slow dialup connections.
1109 Filtering is automatically disabled for inappropriate MIME types.
1115 <sect2 renderas="sect3" id="configurl"><title>What are "http://config.privoxy.org/" and
1116 "http://p.p/"?</title>
1118 <ulink url="http://config.privoxy.org/">http://config.privoxy.org/</ulink> is the
1119 address of <application>Privoxy</application>'s built-in user interface, and
1120 <ulink url="http://p.p/">http://p.p/</ulink> is a shortcut for it.
1123 Since <application>Privoxy</application> sits between your web browser and the Internet,
1124 it can simply intercept requests for these addresses and answer them with its built-in
1125 <quote>web server</quote>.
1128 This also makes for a good test for your browser configuration: If entering the
1129 URL <ulink url="http://config.privoxy.org/">http://config.privoxy.org/</ulink>
1130 takes you to a page saying <quote>This is Privoxy ...</quote>, everything is OK.
1131 If you get a page saying <quote>Privoxy is not working</quote> instead, then
1132 your browser didn't use <application>Privoxy</application> for the request,
1133 hence it could not be intercepted, and you have accessed the <emphasis>real</emphasis>
1134 web site at config.privoxy.org.
1137 With recent versions of <application>Privoxy</application> (version 2.9.x and
1138 later), the user interface features information on the run time status, the
1139 configuration, and even a built-in editor for the <ulink
1140 url="../user-manual/actions-file.html">actions files</ulink>.
1144 Note that the built-in URLs from earlier versions of <application>Junkbuster</application>
1145 / <application>Privoxy</application>, http://example.com/show-proxy-args and http://i.j.b/,
1146 are no longer supported. If you still use such an old version, you should really consider
1147 upgrading to &p-version;.
1152 FIXME: commented out until we have data. HB 03/18/02.
1154 <sect2 renderas="sect3" id="badfiledesc"><title>I get the message 'Bad File Descriptor', why?</title>
1162 <sect2 renderas="sect3" id="blocklist"><title>Do you still maintain the blocklists?</title>
1164 No. The patterns for blocking now reside (among other things) in the <ulink
1165 url="../user-manual/actions-file.html">actions files</ulink>, which are
1166 actively maintained instead. See next question ...
1170 <sect2 renderas="sect3" id="newads"><title>How can I submit new ads?</title>
1172 Yes, absolutely! Please see the <link linkend="contact">Contact section</link> for
1173 how to do that. Please note that you (technically) need the latest
1174 <application>Privoxy</application> version for this to work.
1179 <sect2 renderas="sect3" id="ip"><title>How can I hide my IP address?</title>
1181 If you run both the browser and the proxy locally, you cannot hide your IP
1182 address with <application>Privoxy</application> or any other software. The
1183 server needs to know your IP address to send the answers back to you.
1186 Fortunately there are many publicly usable anonymous proxies out there, which
1187 solve the problem by providing a further level of indirection between you and
1188 the web server, shared by many people, and thus letting your requests "drown"
1189 in white noise of unrelated requests as far as user tracking is concerned.
1192 Most of them will, however, log your IP address and make it available to the
1193 authorities in case you abuse that anonymity for criminal purposes. In fact
1194 you can't even rule out that some of them only exist to *collect* information
1195 on (those suspicious) people with a more than average preference for privacy.
1198 You can find a list of anonymous public proxies at <ulink
1199 url="http://www.multiproxy.org/anon_list.htm">multiproxy.org</ulink> and many
1200 more through Google. A particularly interesting project is the JAP service
1201 offered by the Technical University of Dresden (<ulink
1202 url="http://anon.inf.tu-dresden.de/index_en.html">http://anon.inf.tu-dresden.de/index_en.html</ulink>).
1205 There is, however, even in the single-machine case the possibility to make the
1206 server believe that your machine is in fact a shared proxy serving a whole big
1207 LAN, and we are looking into that.
1211 <sect2 renderas="sect3">
1212 <title id="anonforsure">Can <application>Privoxy</application> guarantee I am anonymous?</title>
1214 No. Your chances of remaining anonymous are greatly improved, but unless you
1215 are an expert on Internet security it would be safest to assume that
1216 everything you do on the Web can be traced back to you.
1219 <application>Privoxy</application> can remove various information about you,
1220 and allows <emphasis>you</emphasis> more freedom to decide which sites
1221 you can trust, and what details you want to reveal. But it's still possible
1222 that web sites can find out who you are. Here's one way this can happen.
1225 A few browsers disclose the user's email address in certain situations, such
1226 as when transferring a file by FTP. <application>Privoxy</application>
1227 does not filter FTP. If you need this feature, or are concerned about the
1228 mail handler of your browser disclosing your email address, you might
1229 consider products such as <application>NSClean</application>.
1232 Browsers available only as binaries could use non-standard headers to give
1233 out any information they can have access to: see the manufacturer's license
1234 agreement. It's impossible to anticipate and prevent every breach of privacy
1235 that might occur. The professionally paranoid prefer browsers available as
1236 source code, because anticipating their behavior is easier. Trust the source,
1242 <sect2 renderas="sect3">
1243 <title id="sitebreak">Might some things break because header information or
1244 content is being altered?</title>
1247 Definitely. More and more sites use HTTP header content to decide what to
1248 display and how to display it. There is many ways that this can be handled,
1249 so having hard and fast rules, is tricky.
1253 <quote>User-Agent</quote> in particular is often used in this way to identify
1254 the browser, and adjust content accordingly. Changing this now (at least not
1255 further than removing the OS information) is not recommended, since so many
1256 sites do look for it. You may get undesirable results by changing this.
1260 For instance, different browsers use different encodings of Russian and Czech
1261 characters, certain web servers convert pages on-the-fly according to the
1262 User Agent header. Giving a <quote>User Agent</quote> with the wrong
1263 operating system or browser manufacturer causes some sites in these languages
1264 to be garbled; Surfers to Eastern European sites should change it to
1265 something closer. And then some page access counters work by looking at the
1266 <quote>Referer</quote> header; they may fail or break if unavailable. The
1267 weather maps of Intellicast have been blocked by their server when no
1268 <quote>Referer</quote> or cookie is provided, is another example. (But you
1269 can forge both headers without giving information away). There are
1270 many other ways things can go wrong when trying to fool a web server.
1274 Similar thoughts apply to modifying JavaScript, and, to a lesser degree,
1279 If you have problems with a site, you will have to adjust your configuration
1280 accordingly. Cookies are probably the most likely adjustment that may
1281 be required, but by no means the only one.
1287 <sect2 renderas="sect3">
1288 <title id="caching">Can <application>Privoxy</application> act as a <quote>caching</quote> proxy to
1289 speed up web browsing?</title>
1291 No, it does not have this ability at all. You want something like
1292 <ulink url="http://www.squid-cache.org/">Squid</ulink> for this. And, yes,
1293 before you ask, <application>Privoxy</application> can co-exist
1294 with other kinds of proxies like <application>Squid</application>.
1295 See the <ulink url="../user-manual/config.html#FORWARDING">forwarding
1296 chapter</ulink> in the <ulink url="../user-manual/index.html">user
1297 manual</ulink> for details.
1301 <sect2 renderas="sect3">
1302 <title id="firewall">What about as a firewall? Can <application>Privoxy</application> protect me?</title>
1304 Not in the way you mean, or in the way a true firewall can.
1305 <application>Privoxy</application> can help protect your privacy, but not
1306 protect you from intrusion attempts. It is, of course, perfectly possible
1307 and recommended to use <emphasis>both</emphasis>.
1311 <!-- No longer needed
1312 <sect2 renderas="sect3">
1313 <title id="logo">The <application>Privoxy</application> logo that replaces ads is very blocky
1314 and ugly looking. Can't a better font be used?</title>
1317 This is not a font problem. The logo is an image that is created by
1318 <application>Privoxy</application> on the fly. So as to not waste
1319 memory, the image is rather small. The blockiness comes when the
1320 image is scaled to fill a largish area. There is not much to be done
1321 about this, other than to use one of the other
1322 <quote>imageblock</quote> directives: <emphasis>pattern</emphasis>,
1323 <emphasis>blank</emphasis>, or a URL of your choosing.
1326 Given the above problem, we have decided to remove the logo option entirely
1332 <sect2 renderas="sect3">
1333 <title id="wasted">I have large empty spaces / a checkerboard pattern now where
1334 ads used to be. Why?</title>
1336 It would be technically possible eliminate the banners in a way that frees
1337 their screen estate in many cases, by doing all banner blocking with filters,
1338 i.e. eliminating the whole image references from the HTML pages instead
1339 of letting them stay in, and blocking the resulting requests for the
1343 But this would consume considerable CPU resources, would likely destroy
1344 the layout of many web pages which rely on the banners consuming a certain
1345 amount of screen space, and would fail in other cases, where the screen space
1346 is reserved e.g. by tables anyway. Also, making the banners disappear without
1347 a visual trace complicates troubleshooting.
1350 So we won't support this in the default configuration, but you can of course
1351 define appropriate filters yourself.
1355 <sect2 renderas="sect3">
1356 <title id="ssl">How can <application>Privoxy</application> filter Secure (HTTPS) URLs?</title>
1358 Since secure HTTP connections are encrypted SSL sessions between your browser
1359 and the secure site, and are meant to be reliably <emphasis>secure</emphasis>,
1360 there is little that <application>Privoxy</application> can do but hand the raw
1361 gibberish data though from one end to the other unprocessed.
1364 The only exception to this is blocking by host patterns, as the client needs
1365 to tell <application>Privoxy</application> the name of the remote server,
1366 so that <application>Privoxy</application> can establish the connection.
1367 If that name matches a host-only pattern, the connection will be blocked.
1370 As far as ad blocking is concerned, this is less of a restriction than it may
1371 seem, since ad sources are often identifiable by the host name, and often
1372 the banners to be placed in an encrypted page come unencrypted nonetheless
1373 for efficiency reasons, which exposes them to the full power of
1374 <application>Privoxy</application>'s ad blocking.
1377 <quote>Content cookies</quote> (those that are embedded in the actual HTML or
1378 JS page content, see <literal><ulink
1379 url="../user-manual/actions-file.html#FILTER-CONTENT-COOKIES">filter{content-cookies}</ulink></literal>),
1380 in an SSL transaction will be impossible to block under these conditions.
1381 Fortunately, this does not seem to be a very common scenario since most
1382 cookies come by traditional means.
1387 <sect2 renderas="sect3">
1388 <title id="secure"><application>Privoxy</application> runs as a <quote>server</quote>. How
1389 secure is it? Do I need to take any special precautions?</title>
1391 There are no known exploits that might affect
1392 <application>Privoxy</application>. On Unix-like systems,
1393 <application>Privoxy</application> can run as a non-privileged
1394 user, which is how we recommend it be run. Also, by default
1395 <application>Privoxy</application> only listens to requests
1396 from <quote>localhost</quote> only. The server aspect of
1397 <application>Privoxy</application> is not itself directly exposed to the
1398 Internet in this configuration. If you want to have
1399 <application>Privoxy</application> serve as a LAN proxy, this will have to
1400 be opened up to allow for LAN requests. In this case, we'd recommend
1401 you specify only the LAN gateway address, e.g. 192.168.1.1, in the main
1402 <application>Privoxy</application> configuration file and check all <ulink
1403 url="../user-manual/config.html#ACCESS-CONTROL">access control and security
1404 options</ulink>. All LAN hosts can then use this as their proxy address
1405 in the browser proxy configuration, but <application>Privoxy</application>
1406 will not listen on any external interfaces. ACLs can be defined in addition,
1407 and using a firewall is always good too. Better safe than sorry.
1412 <sect2 renderas="sect3" id="turnoff">
1413 <title>How can I temporarily disable <application>Privoxy</application>?</title>
1415 The easiest way is to access <application>Privoxy</application> with your
1416 browser by using the remote toggle URL: <ulink
1417 url="http://config.privoxy.org/toggle">http://config.privoxy.org/toggle</ulink>.
1418 See the <ulink url="../user-manual/appendix.html#BOOKMARKLETS">Bookmarklets section</ulink>
1419 of the <citetitle>User Manual</citetitle> for an easy way to access this
1424 <sect2 renderas="sect3" id="reallyoff">
1425 <title>When <quote>disabled</quote> is <application>Privoxy</application> totally
1426 out of the picture?</title>
1428 No, this just means all filtering and actions are disabled.
1429 <application>Privoxy</application> is still acting as a proxy, but just not
1430 doing any of the things that <application>Privoxy</application> would
1431 normally be expected to do. It is still a <quote>middle-man</quote> in
1432 the interaction between your browser and web sites.
1436 <sect2 renderas="sect3" id="crunch">
1437 <title>My logs show <application>Privoxy</application> <quote>crunches</quote>
1438 ads, but also its own CGI pages. What is a <quote>crunch</quote>?</title>
1440 A <quote>crunch</quote> simply means <application>Privoxy</application> intercepted
1441 <emphasis>something</emphasis>, nothing more. Often this is indeed ads or
1442 banners, but <application>Privoxy</application> uses the same mechanism for
1443 trapping requests for its own internal pages. For instance, a request for
1444 <application>Privoxy's</application> configuration page at: <ulink
1445 url="http://config.privoxy.org">http://config.privoxy.org</ulink>, is
1446 intercepted (i.e. it does not go out to the 'net), and the familiar CGI
1447 configuration is returned to the browser, and the log consequently will show
1448 a <quote>crunch</quote>.
1452 <sect2 renderas="sect3" id="downloads">
1453 <title>Can <application>Privoxy</application> effect files that I download
1454 from a webserver? FTP server?</title>
1456 From the webserver's perspective, there is no difference between
1457 viewing a document (i.e. a page), and downloading a file. The same is true of
1458 <application>Privoxy</application>. If there is a match for a <literal><ulink
1459 url="../user-manual/actions-file.html#BLOCK">block</ulink></literal> pattern,
1460 it will still be blocked, and of course this is obvious. Filtering is
1461 potentially more of a concern since the results are not always so obvious.
1464 <application>Privoxy</application> knows the differences in files according
1465 to the <quote>Document Type</quote> as reported by the webserver. If this is
1466 reported accurately (e.g. <quote>application/zip</quote> for a zip archive),
1467 then <application>Privoxy</application> knows to ignore these where
1468 appropriate. It is possible, however, that documents that are of an unknown
1469 type (generally assumed to be <quote>text/plain</quote>) will be filtered, as
1470 will those that might be incorrectly reported by the webserver. If such a
1471 file is a downloaded file that is intended to be saved to disk, then any
1472 content that might have been altered by filtering, will be saved too, for
1473 these (probably very rare) cases.
1476 <application>Privoxy</application> does not do FTP at all, only HTTP
1482 <sect2 renderas="sect3" id="seealso">
1483 <title>Where can I find more information about <application>Privoxy</application>
1484 and related issues?</title>
1485 <!-- Include seealso.sgml boilerplate: -->
1487 <!-- end boilerplate -->
1492 <ulink url="../user-manual/seealso.html">user-manual</ulink> for
1498 <sect2 renderas="sect3" id="microsuck">
1499 <title>I've noticed that Privoxy changes <quote>Microsoft</quote> to
1500 <quote>MicroSuck</quote>! Why are you manipulating my browsing?</title>
1503 We're not. The text substitutions that you are seeing are disabled
1504 in the default configuration as shipped. You have either manually
1505 activated the <quote><literal>fun</literal></quote> filter which
1506 is clearly labeled <quote>Text replacements for subversive browsing
1507 fun!</quote> or you have implicitly activated it by choosing the
1508 <quote>Radical</quote> profile in the web-based editor (formerly known
1509 as the <application>Advanced</application> profile).
1516 <!-- ~~~~~ New section ~~~~~ -->
1518 <sect1 id="trouble">
1519 <title>Troubleshooting</title>
1521 <sect2 renderas="sect3">
1522 <title id="refused">I just upgraded and am getting <quote>connection refused</quote>
1523 with every web page?</title>
1525 Either <application>Privoxy</application> is not running, or your
1526 browser is configured for a different port than what
1527 <application>Privoxy</application> is using.
1531 The old <application>Privoxy</application> (and also
1532 <application>Junkbuster</application>) used port 8000 by
1533 default. This has been changed to port 8118 now, due to a conflict
1534 with NAS (Network Audio Service), which uses port 8000. If you haven't,
1535 you need to change your browser to the new port number, or alternately
1537 url="../user-manual/config.html#LISTEN-ADDRESS"><literal>listen-address</literal>
1538 option</ulink> in <application>Privoxy's</application> <ulink
1539 url="../user-manual/config.html">main configuration file</ulink>.
1544 <sect2 renderas="sect3">
1545 <title id="flushit">I just added a new rule, but the steenkin ad is
1546 still getting through. How?</title>
1548 If the ad had been displayed before you added its URL, it will probably be
1549 held in the browser's cache for some time, so it will be displayed without
1550 the need for any request to the server, and <application>Privoxy</application>
1551 will not be in the picture. The best thing to do is try flushing the browser's
1552 caches. And then try again.
1556 If this doesn't help, you probably have an error in the rule you
1557 applied. Try pasting the full URL of the offending ad into <ulink
1558 url="http://config.privoxy.org/show-url-info">http://config.privoxy.org/show-url-info</ulink>
1559 and see if it really matches your new rule.
1564 <sect2 id="badsite" renderas="sect3">
1565 <title >One of my favorite sites does not work with <application>Privoxy</application>.
1566 What can I do?</title>
1569 First verify that it is indeed a <application>Privoxy</application> problem,
1570 by toggling off <application>Privoxy</application> through <ulink
1571 url="http://config.privoxy.org/toggle">http://config.privoxy.org/toggle</ulink>,
1572 and then shift-reloading the problem page (i.e. holding down the shift key
1573 while clicking reload. Alternatively, flush your browser's disk and memory
1578 If still a problem, go to <ulink
1579 url="http://config.privoxy.org/show-url-info">http://config.privoxy.org/show-url-info</ulink>
1580 and paste the full URL of the page in question into the prompt. See which actions
1581 are being applied to the URL, and which matches in which actions files are
1582 responsible for that. Now, armed with this information, go to <ulink
1583 url="http://config.privoxy.org/show-status">http://config.privoxy.org/show-status</ulink>
1584 and select the appropriate actions files for editing.
1587 You can now either look for a section which disables the actions that
1588 you suspect to cause the problem and add a pattern for your site there,
1589 or make up a completely new section for your site. In any case, the recommended
1590 way is to disable only the prime suspect, reload the problem page, and only
1591 if the problem persists, disable more and more actions until you have
1592 identified the culprit. You may or may not want to turn the other actions
1593 on again. Remember to flush your browser's caches in between any such changes!
1596 Alternately, if you are comfortable with a text editor, you can accomplish
1597 the same thing by editing the appropriate actions file. Probably the easiest
1598 way to deal with such problems when editing by hand is to add your
1599 site to a <literal>{ fragile }</literal> section in <filename>user.action</filename>,
1600 which is an alias that turns off most <quote>dangerous</quote>
1601 actions, but is also likely to turn off more actions then needed, and thus lower
1602 your privacy and protection more than necessary,
1605 Troubleshooting actions is discussed in more detail in the <ulink
1606 url="../user-manual/appendix.html#ACTIONSANAT">user-manual appendix</ulink>.
1607 There is also an <ulink
1608 url="../user-manual/actions-file.html#ACT-EXAMPLES">actions tutorial</ulink>.
1614 <!-- ~~~~~ New section ~~~~~ -->
1615 <sect2 id="dun" renderas="sect3">
1616 <title>After installing <application>Privoxy</application>, I have to log in
1617 every time I start IE. What gives?</title>
1620 This is a quirk that effects the installation of
1621 <application>Privoxy</application>, in conjunction with Internet Explorer and
1622 Internet Connection Sharing on Windows 2000 and Windows XP. The symptoms may
1623 appear to be corrupted or invalid DUN settings, or passwords.
1627 When setting up an NT based Windows system with
1628 <application>Privoxy</application> you may find that things do not seem to be
1629 doing what you expect. When you set your system up you will probably have set
1630 up Internet Connection Sharing (ICS) with Dial up Networking (DUN) when
1631 logged in with administrator privileges. You will probably have made this DUN
1632 connection available to other accounts that you may have set-up on your
1633 system. E.g. Mum or Dad sets up the system and makes accounts suitably
1634 configured for the kids.
1638 When setting up <application>Privoxy</application> in this environment you
1639 will have to alter the proxy set-up of Internet Explorer (IE) for the
1640 specific DUN connection on which you wish to use
1641 <application>Privoxy</application>. When you do this the ICS DUN set-up
1642 becomes user specific. In this instance you will see no difference if you
1643 change the DUN connection under the account used to set-up the connection.
1644 However when you do this from another user you will notice that the DUN
1645 connection changes to make available to "Me only". You will also find that
1646 you have to store the password under each different user!
1650 The reason for this is that each user's set-up for IE is user specific. Each
1651 set-up DUN connection and each LAN connection in IE store the settings for
1652 each user individually. As such this enforces individual configurations
1653 rather than common ones. Hence the first time you use a DUN connection after
1654 re-booting your system it may not perform as you expect, and prompt you for
1655 the password. Just set and save the password again and all should be OK.
1659 [Thanks to Ray Griffith for this submission.]
1664 <!-- ~~~~~ New section ~~~~~ -->
1665 <sect2 id="ftp" renderas="sect3">
1666 <title>I cannot connect to any FTP sites. <application>Privoxy</application>
1667 seems to be blocking me.</title>
1669 <application>Privoxy</application> cannot act as a proxy for FTP traffic,
1670 so do not configure your browser to use <application>Privoxy</application>
1671 as an FTP proxy. The same is true for any protocol other than HTTP or HTTPS.
1674 Most browsers understand FTP as well as HTTP. If you connect to a site, with
1675 a URL like <literal>ftp://ftp.example.com</literal>, your browser is making
1676 an FTP connection, and not a HTTP connection. So while your browser may
1677 speak FTP, <application>Privoxy</application> does not, and cannot proxy
1682 <!-- ~~~~~ New section ~~~~~ -->
1683 <sect2 id="osxie" renderas="sect3">
1684 <title>In Mac OSX, I can't configure Microsoft Internet Explorer to use
1685 <application>Privoxy</application> as the HTTP proxy.</title>
1687 Microsoft Internet Explorer (in versions like 5.1) respects system-wide
1688 network settings. In order to change the HTTP proxy, open System
1689 Preferences, and click on the Network icon. In the settings pane that
1690 comes up, click on the Proxies tab. Ensure the "Web Proxy (HTTP)" checkbox
1691 is checked and enter <literal>127.0.0.1</literal> in the entry field.
1692 Enter <literal>8118</literal> in the Port field. The next time you start
1693 IE, it should reflect these values.
1697 <!-- ~~~~~ New section ~~~~~ -->
1698 <sect2 renderas="sect3" id="osxuninstall">
1699 <title>In Mac OSX, I dragged the Privoxy folder to the trash in order to
1700 uninstall it. Now the finder tells me I don't have sufficient privileges to
1701 empty the trash.</title>
1703 Just dragging the <application>Privoxy</application> folder to the trash is
1704 not enough to delete it. <application>Privoxy</application> supplies an
1705 <application>uninstall.command</application> file that takes care of
1706 these details. Open the trash, drag the <application>uninstall.command</application>
1707 file out of the trash and double-click on it. You will be prompted for
1708 confirmation and the administration password.
1711 The trash may still appear full after this command; emptying the trash
1712 from the desktop should make it appear empty again.
1717 <!-- ~~~~~ New section ~~~~~ -->
1718 <sect2 renderas="sect3" id="blankpage">
1719 <title>I get a completely blank page at one site. <quote>View Source</quote>
1720 shows only: <markup><![CDATA[<html><body></body></html>]]></markup>. Without
1721 <application>Privoxy</application> the page loads fine.</title>
1723 Chances are that the site suffers from a bug in
1724 <ulink url="http://www.php.net/"><application>PHP</application></ulink>,
1725 which results in empty pages being sent if the client explicitly requests
1726 an uncompressed page, like <application>Privoxy</application> does.
1727 This bug has been fixed in PHP 4.2.3.
1730 To find out if this is in fact the source of the problem, try adding
1731 the site to a <literal>-prevent-compression</literal> section in
1732 <filename>user.action</filename>:
1735 # Make exceptions for ill-behaved sites:
1737 {-prevent-compression}
1738 .example.com</screen>
1740 If that works, you may also want to report the problem to the
1741 site's webmasters, telling them to use zlib.output_compression
1742 instead of ob_gzhandler in their PHP applications (workaround)
1743 or upgrade to PHP 4.2.3 or later (fix).
1753 <!-- ~~~~~ New section ~~~~~ -->
1755 FIXME: Commented out until we have something to put here. HB 03/18/02.
1756 <sect1 id="knownissues"><title>Known Issues</title>
1763 <!-- ~~~~~ New section ~~~~~ -->
1764 <sect1 id="contact"><title>Contacting the developers, Bug Reporting and Feature Requests</title>
1765 <!-- Include contacting.sgml -->
1767 <!-- end contacting -->
1770 <!-- ~~~~~ New section ~~~~~ -->
1771 <sect1 id="copyright"><title>Privoxy Copyright, License and History</title>
1773 <!-- Include copyright.sgml -->
1778 Portions of this document are <quote>borrowed</quote> from the original
1779 <application>Junkbuster</application> (tm) FAQ, and modified as
1780 appropriate for <application>Privoxy</application>.
1783 <!-- ~~~~~ New section ~~~~~ -->
1784 <sect2><title>License</title>
1785 <!-- Include copyright.sgml: -->
1787 <!-- end copyright -->
1789 <!-- ~ End section ~ -->
1791 <!-- ~~~~~ New section ~~~~~ -->
1792 <sect2><title>History</title>
1793 <!-- Include history.sgml -->
1799 <!-- ~ End section ~ -->
1802 <!-- ~~~~~ New section ~~~~~ -->
1804 <sect1 id="seealso"><title>See also</title>
1806 <!-- Include seealso.sgml -->
1817 Tue 09/11/01 06:38:14 PM EST: Test SGML doc by Hal Burgiss.
1819 Last modified: Mon Sep 10 19:22:09 CEST 2001
1821 This program is free software; you can redistribute it
1822 and/or modify it under the terms of the GNU General
1823 Public License as published by the Free Software
1824 Foundation; either version 2 of the License, or (at
1825 your option) any later version.
1827 This program is distributed in the hope that it will
1828 be useful, but WITHOUT ANY WARRANTY; without even the
1829 implied warranty of MERCHANTABILITY or FITNESS FOR A
1830 PARTICULAR PURPOSE. See the GNU General Public
1831 License for more details.
1833 The GNU General Public License should be included with
1834 this file. If not, you can view it at
1835 http://www.gnu.org/copyleft/gpl.html
1836 or write to the Free Software Foundation, Inc., 59
1837 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
1840 Revision 1.61.2.25 2002/10/29 03:21:50 hal9
1841 Add 3 Q/A's relating to HTML in email. Other minor touchups.
1843 Revision 1.61.2.24 2002/10/15 12:50:22 oes
1844 s/Advanced/Radical/ (stupid me)
1846 Revision 1.61.2.23 2002/10/15 12:38:56 oes
1847 Added Microsuck faq; more detail for PHP problem
1849 Revision 1.61.2.22 2002/10/12 01:13:13 hal9
1850 Updates for demoronizer, more commentary on Radical profile, and update on
1851 the srvany.exe/icon fix.
1853 Revision 1.61.2.21 2002/10/10 04:09:35 hal9
1854 s/Advanced/Radical/ and added very brief note.
1856 Revision 1.61.2.20 2002/09/26 01:22:45 hal9
1857 Small additions for LAN setup, content-cookies/SSL, and FTP non-support.
1859 Revision 1.61.2.19 2002/08/25 23:31:56 hal9
1860 Fix one grammatical error. Add brief FAQ relating to tranparent proxies (ie
1861 port 80 setting). Add FAQ on effects of Privoxy on downloaded files
1862 (especially filtering).
1864 Revision 1.61.2.18 2002/08/14 16:39:37 hal9
1865 Fix wrong tag on FAQ addition.
1867 Revision 1.61.2.17 2002/08/14 00:01:18 hal9
1870 Revision 1.61.2.16 2002/08/13 00:10:38 hal9
1871 Add faq to troubleshooting re: blank page syndrome, ie {-prevent-compression}.
1873 Revision 1.61.2.15 2002/08/10 11:34:22 oes
1874 Add disclaimer about probably being out-of-date
1876 Revision 1.61.2.14 2002/08/07 02:53:43 hal9
1877 Fix some minor markup errors, and move one OSX Q/A to troubleshooting section.
1879 Revision 1.61.2.13 2002/08/06 11:55:32 oes
1880 Added missing close tag
1882 Revision 1.61.2.12 2002/08/06 11:43:46 david__schmidt
1883 Updated OSX uninstall FAQ... we have an uninstall script now.
1885 Revision 1.61.2.11 2002/08/06 08:54:03 oes
1886 Style police: Fixed formatting details
1888 Revision 1.61.2.10 2002/08/02 14:00:25 david__schmidt
1889 Made the OSX removal commands far less dangerous
1891 Revision 1.61.2.9 2002/08/02 13:14:45 oes
1892 Added warning about sudo rm -r for Mac OSX deinstallation; moved this item to install section
1894 Revision 1.61.2.8 2002/08/02 02:01:42 david__schmidt
1895 Add FAQ item for MSIE on OSX HTTP proxy confusion
1897 Revision 1.61.2.7 2002/08/02 01:46:01 david__schmidt
1898 Added FAQ item for Mac OSX uninstall woes
1900 Revision 1.61.2.6 2002/07/30 20:04:56 hal9
1901 Fix typo: 'schould'.
1903 Revision 1.61.2.5 2002/07/26 15:22:58 oes
1904 - Updated to reflect changes in standard.action
1905 - Added info on where to get updated actions files
1907 Revision 1.61.2.4 2002/07/25 21:42:29 hal9
1908 Add brief notes on not proxying non-HTTP protocols.
1910 Revision 1.61.2.3 2002/06/09 16:36:33 hal9
1911 Clarifications on filtering and MIME. Hardcode 'latest release' in index.html.
1913 Revision 1.61.2.2 2002/06/06 02:51:34 hal9
1914 Fix typo in URL http:/config.privoxy.org
1916 Revision 1.61.2.1 2002/06/05 23:10:43 hal9
1917 Add new FAQ re: DUN/IE. Change release date from May to June :)
1919 Revision 1.61 2002/05/25 12:37:25 hal9
1920 Various minor changes and edits.
1922 Revision 1.60 2002/05/22 17:17:48 oes
1923 Proofread & added more links into u-m
1925 Revision 1.59 2002/05/15 04:03:30 hal9
1926 Fix ulink -> link markup.
1928 Revision 1.58 2002/05/10 01:48:20 hal9
1929 This is mostly proposed copyright/licensing additions and changes. Docs
1930 are still GPL, but licensing and copyright are more visible. Also, copyright
1931 changed in doc header comments (eliminate references to JB except FAQ).
1933 Revision 1.57 2002/05/05 20:26:02 hal9
1934 Sorting out license vs copyright in these docs.
1936 Revision 1.56 2002/05/04 08:44:44 swa
1939 Revision 1.55 2002/05/04 00:41:56 hal9
1940 -Remove TOC/first page kludge in favor of proper handling via dsl file.
1942 Revision 1.54 2002/05/03 05:06:44 hal9
1943 Add brief Q/A on transparent proxies.
1945 Revision 1.53 2002/05/03 01:34:52 hal9
1946 Fix section numbering for new sections (due to TOC kludge).
1948 Revision 1.52 2002/04/29 03:08:43 hal9
1949 -Added new Q/A on new actions file set up (pointer to u-m)
1950 -Fixed a few broken links and converted old actions as a result of
1953 Revision 1.51 2002/04/26 17:24:31 swa
1954 bookmarks cleaned, changed structure of user manual, screen and programlisting cleanups, and numerous other changes that I forgot
1956 Revision 1.50 2002/04/26 05:25:23 hal9
1957 Mass commit to catch a few scattered fixes.
1959 Revision 1.49 2002/04/12 10:10:18 swa
1962 Revision 1.48 2002/04/10 18:45:15 swa
1965 Revision 1.47 2002/04/10 04:05:32 hal9
1968 Revision 1.45 2002/04/08 22:59:26 hal9
1969 Version update. Spell chkconfig correctly :)
1971 Revision 1.44 2002/04/07 21:24:29 hal9
1972 Touch up on name change.
1974 Revision 1.43 2002/04/04 21:59:53 hal9
1975 Added NT/W2K service/icon situation.
1977 Revision 1.42 2002/04/04 18:46:47 swa
1978 consistent look. reuse of copyright, history et. al.
1980 Revision 1.41 2002/04/04 06:48:37 hal9
1981 Structural changes to allow for conditional inclusion/exclusion of content
1982 based on entity toggles, e.g. 'entity % p-not-stable "INCLUDE"'. And
1983 definition of internal entities, e.g. 'entity p-version "2.9.13"' that will
1984 eventually be set by Makefile.
1985 More boilerplate text for use across multiple docs.
1987 Revision 1.40 2002/04/03 04:22:03 hal9
1988 Fixed several typos.
1990 Revision 1.39 2002/04/03 03:53:03 hal9
1991 Revert some changes, and then make some news, to layout, and appearance.
1993 Revision 1.38 2002/04/02 03:49:10 hal9
1994 Major changes to doc structure and layout. Sections are not automatically
1995 numbered now. TOC is on page by itself.
1997 Revision 1.37 2002/04/01 16:24:07 hal9
1998 -Rework of supported Q/A.
1999 -Set up entities to include boilerplate text.
2001 Revision 1.36 2002/03/31 23:18:47 hal9
2002 More on dealing with BLOCKED.
2004 Revision 1.35 2002/03/30 04:14:19 hal9
2005 Fix privoxy.org/config links.
2007 Revision 1.34 2002/03/29 04:35:56 hal9
2010 Revision 1.33 2002/03/29 01:31:48 hal9
2011 Several new Q/A's and other touch ups.
2013 Revision 1.32 2002/03/27 00:57:03 hal9
2014 Touch ups for name change.
2016 Revision 1.31 2002/03/26 22:29:55 swa
2017 we have a new homepage!
2019 Revision 1.30 2002/03/25 16:39:22 hal9
2020 A few new sections. Made all links relative to user-manual.
2022 Revision 1.29 2002/03/25 05:23:57 hal9
2023 Moved section, and touch ups.
2025 Revision 1.28 2002/03/25 04:27:33 hal9
2026 New section related to name change.
2028 Revision 1.25 2002/03/24 16:08:08 swa
2029 we are too lazy to make a block-built
2030 privoxy logo. hence removed the option.
2032 Revision 1.24 2002/03/24 15:46:20 swa
2033 name change related issue.
2035 Revision 1.23 2002/03/24 12:33:01 swa
2038 Revision 1.22 2002/03/24 11:51:00 swa
2039 name change. changed filenames.
2041 Revision 1.21 2002/03/24 11:01:06 swa
2044 Revision 1.20 2002/03/23 15:13:11 swa
2045 renamed every reference to the old name with foobar.
2046 fixed "application foobar application" tag, fixed
2047 "the foobar" with "foobar". left junkbustser in cvs
2048 comments and remarks to history untouched.
2050 Revision 1.19 2002/03/21 17:01:54 hal9
2053 Revision 1.18 2002/03/18 16:40:31 hal9
2056 Revision 1.17 2002/03/18 03:53:53 hal9
2059 Revision 1.16 2002/03/17 21:32:56 hal9
2060 A few more additions.
2062 Revision 1.15 2002/03/17 07:25:59 hal9
2063 Correcting some of my typos, and some additions.
2065 Revision 1.14 2002/03/17 02:39:13 hal9
2066 A little more added ...
2068 Revision 1.13 2002/03/17 00:22:20 hal9
2069 Adding new stuff, and trying to incorporate stuff from old faq.
2071 Revision 1.12 2002/03/11 20:13:21 swa
2074 Revision 1.11 2002/03/11 18:42:27 swa
2077 Revision 1.10 2002/03/11 13:13:27 swa
2078 correct feedback channels
2080 Revision 1.9 2002/03/10 23:34:04 swa
2081 more info on not hiding ip address
2083 Revision 1.8 2002/03/09 15:55:48 swa
2084 added default config section
2086 Revision 1.7 2002/03/07 18:16:55 swa
2089 Revision 1.6 2002/03/07 13:16:31 oes
2090 Committing changes by Stefan
2092 Revision 1.5 2002/03/02 15:50:04 swa
2093 2.9.11 version. more input for docs.
2095 Revision 1.4 2002/02/24 14:34:24 jongfoster
2096 Formatting changes. Now changing the doctype to DocBook XML 4.1
2097 will work - no other changes are needed.
2099 Revision 1.3 2001/09/23 10:13:48 swa
2100 upload process established. run make webserver and
2101 the documentation is moved to the webserver. documents
2102 are now linked correctly.
2104 Revision 1.2 2001/09/13 15:20:17 swa
2105 merged standards into developer manual
2107 Revision 1.1 2001/09/12 15:36:41 swa
2108 source files for junkbuster documentation
2110 Revision 1.3 2001/09/10 17:43:59 swa
2111 first proposal of a structure.
2113 Revision 1.2 2001/06/13 14:28:31 swa
2114 docs should have an author.
2116 Revision 1.1 2001/06/13 14:20:37 swa
2117 first import of project's documentation for the webserver.