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 "2.9.15">
12 <!entity p-status "beta">
13 <!entity % p-not-stable "INCLUDE">
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 -->
20 File : $Source: /cvsroot/ijbswa/current/doc/source/faq.sgml,v $
23 This file belongs into
24 ijbswa.sourceforge.net:/home/groups/i/ij/ijbswa/htdocs/
26 $Id: faq.sgml,v 1.56 2002/05/04 08:44:44 swa Exp $
28 Written by and Copyright (C) 2001 the SourceForge
29 Privoxy team. http://www.privoxy.org/
31 Based on the Internet Junkbuster originally written
32 by and Copyright (C) 1997 Anonymous Coders and
33 Junkbusters Corporation. http://www.junkbusters.com
35 <Qandaset defaultlabel='qanda'>
50 ========================================================================
51 NOTE: Please read developer-manual/documentation.html before touching
52 anything in this, or other Privoxy documentation. You have been warned!
53 Failure to abide by this rule will result in the revocation of your license
54 to live a peaceful existence!
55 ========================================================================
61 <article id="index" class="faq">
63 <title>Privoxy Frequently Asked Questions</title>
65 <pubdate>$Id: faq.sgml,v 1.56 2002/05/04 08:44:44 swa Exp $</pubdate>
71 <holder>Privoxy Developers</holder>
76 Note: this should generate a separate page, and a live link to it.
77 But it doesn't for some mysterious reason. Please leave commented
78 unless it can be fixed proper. For the time being, the copyright
79 statement will be in copyright.smgl.
83 <legalnotice id="legalnotice">
85 text goes here ........
95 <orgname>By: Privoxy Developers</orgname>
104 This is here to keep vim syntax file from breaking :/
105 If I knew enough to fix it, I would.
106 PLEASE DO NOT REMOVE! HB: hal@foobox.net
111 This FAQ gives users and developers alike answers to frequently asked
112 questions about <ulink url="http://www.privoxy.org">Privoxy</ulink>
113 <![%p-stable;[ v.&p-version]]>.
116 <!-- Include privoxy.sgml boilerplate: -->
118 <!-- end boilerplate -->
121 You can find the latest version of the document at <ulink
122 url="http://www.privoxy.org/faq/">http://www.privoxy.org/faq/</ulink>.
123 Please see the Contact section if you want to contact the developers.
127 <!-- Feel free to send a note to the developers at <email>ijbswa-developers@lists.sourceforge.net</email>. -->
133 <!-- ~~~~~ New section ~~~~~ -->
135 <sect1 id="general"><title>General Information</title>
137 <sect2 renderas="sect3" id="newjb"><title>What is this new version of <application>Privoxy</application>?</title>
139 The original <application><trademark>Internet
140 Junkbuster</trademark></application> (tm) is a copyrighted product of <ulink
141 url="http://www.junkbusters.com">Junkbusters Corporation</ulink>.
142 Development of this effort stopped some time ago as of version 2.0.2. Stefan
143 Waldherr started the ijbswa project on <ulink
144 url="http://sourceforge.net/projects/ijbswa/">Sourceforge</ulink> to
145 rekindle development. Other developers subsequently joined with Stefan, and
146 have since added many new features, refinements and enhancements. The result
147 of this effort is <application>Privoxy</application>.
150 <application>Privoxy</application> has evolved from the
151 <application>Junkbuster 2.0.2</application> code base, and has advanced
152 significantly at this point.
155 Please see the <link linkend="copyright">History section</link> for more
156 information on the history of <application>Junkbuster</application> and
157 <application>Privoxy</application>.
163 <sect2 renderas="sect3">
164 <title id="whyprivoxy">Why <quote>Privoxy</quote>? Why a name change at all?</title>
166 <application>Privoxy</application> is the
167 <quote><emphasis>Privacy Enhancing Proxy</emphasis></quote>.
170 There are potential legal complications from the continued use of the
171 <application>Junkbuster</application> name, which is a registered trademark of
172 <ulink url="http://junkbusters.com">Junkbusters Corporation</ulink>.
173 And thus they <quote>own</quote> the rights to the name.
174 (There are, however, no objections from Junkbusters Corporation to the
175 <application>Privoxy</application> project itself, and they, in fact, still
176 share our ideals and goals.)
180 The developers also believed that there are so many changes from the original
181 code, that it was time to make a clean break from the past and make
182 a name in their own right<![%p-not-stable;[, especially now with the pending
183 release of version 3.0]]>.
188 <sect2 renderas="sect3" id="differs"><title>How does <application>Privoxy</application> differ
189 from the old <application>Junkbuster?</application></title>
191 <application>Privoxy</application> picks up where
192 <application>Junkbuster</application> left off. All the old features remain.
193 The new <application>Privoxy</application> still blocks ads and banners,
194 still manages cookies, and still helps protect your privacy. But, these are
195 all enhanced, and many new features have been added, all in the same vein.
198 The configuration has changed significantly as well. This is something that
199 users will notice right off the bat if you are upgrading from
200 <application>Junkbuster</application> 2.0.x. The <quote>blocklist</quote>
201 file does not exist any more. This is replaced by <quote>actions</quote>
202 files, such as <filename>default.actions</filename>. This is where most of
203 the per site configuration is now.
207 <sect2 renderas="sect3" id="features"><title>What are some of the new features?</title>
208 <!-- Include newfeatures.sgml: -->
214 <sect2 renderas="sect3" id="proxymoron"><title>What is a <quote>proxy</quote>? How does
215 <application>Privoxy</application> work? </title>
217 When you connect to a web site with <application>Privoxy</application>,
218 you are really connecting to your locally running version of
219 <application>Privoxy</application>. <application>Privoxy</application>
220 intercepts your requests for the web page, and relays that to the
221 <quote>real</quote> web site. The web site sends the HTTP data stream
222 back to <application>Privoxy</application>, where
223 <application>Privoxy</application> can work its magic before it
224 relays this data back to your web browser.
228 Since <application>Privoxy</application> sits between you and the
229 WWW, it is in a position to intercept and completely manage all web traffic and
230 HTTP content before it gets to your browser.
231 <application>Privoxy</application> uses various programming methods to do
232 this, all of which is under your control via the various configuration
237 There are many kinds of proxies. <application>Privoxy</application> best
238 fits the <quote>filtering proxy</quote> category.
244 <sect2 renderas="sect3">
245 <title id="knows">How does <application>Privoxy</application> know what is
246 an ad, and what is not?</title>
248 <application>Privoxy</application> processes all the raw content of every
249 web page. So it reads everything on each page. It then compares this to the
250 rules as set up in the configuration files, and looks for any matches to
251 these rules. <application>Privoxy</application> makes heavy use of
252 <quote>regular expressions</quote>. (If you are not familiar with regular
253 expressions, it is explained briefly in <ulink
254 url="../user-manual/appendix.html">the user manual</ulink>.) Regular
255 expressions facilitate matching of one text string against another, using
256 wildcards to build complex patterns. So <application>Privoxy</application>
257 will typically look for URLs and other content that match certain key words
258 and expressions as defined in the configuration files. For instance a URL
259 that contains <quote>/banners</quote>, has a high probability of containing
260 ad banners, and thus would be a prime candidate to have a matching rule.
263 So <application>Privoxy</application> will look for these kinds of obvious
264 looking culprits. And also, will use lists of known organizations that
265 specialize in ads. Again, using complex patterns to match as many potential
266 combinations as possible since there tend to be many, many variations used by
267 advertisers, and new ones are being introduced all the time.
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 rule
276 accidentally block something by mistake. There is a good chance you may run
277 into such a situation at some point. It is tricky writing rules to cover
278 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.
312 <sect2 renderas="sect3" id="license"><title>Is there is a license or fee? What about a
313 warranty? Registration?</title>
315 <application>Privoxy</application> is licensed under the GNU General Public
316 License (GPL). It is free to use, copy, modify or distribute as you wish
317 under the terms of this license. Please see the <link
318 linkend="copyright">Copyright</link> section for more information on the
319 license and copyright.
323 There is no warranty of any kind, expressed, implied or otherwise. That is
324 something that would cost real money ;-) There is no registration either.
325 <application>Privoxy</application> really is <emphasis>free</emphasis>
332 <sect2 renderas="sect3" id="jointeam"><title>I would like to help you, what do I do?</title>
334 <sect3 renderas="sect4" id="jointeam-money"><title>Money Money Money</title>
336 We, of course, welcome donations and use the money for domain registering,
337 regular world-wide get-togethers (hahaha). Anyway, we'll soon describe the
338 process how to donate money to the team.
342 <sect3 renderas="sect4" id="jointeam-work"><title>You want to work with us?</title>
344 Well, helping the team is always a good idea. We welcome new developers,
345 RPM gurus or documentation makers. Simply get an account on sourceforge.net
346 and mail your id to the developer mailing list. Then read the
347 section Quickstart in the <ulink url="../developer-manual/quickstart.html">
348 Developer's Manual</ulink>.
351 Once we have added you to the team, you'll have write access to the CVS
352 repository, and together we'll find a suitable task for you.
361 <!-- ~~~~~ New section ~~~~~ -->
363 <sect1 id="installation"><title>Installation</title>
365 <sect2 renderas="sect3" id="whichbrowsers">
366 <title>Which browsers are supported by <application>Privoxy</application>?</title>
368 Any browser that can be configured to use a <quote>proxy</quote>, which
369 should be virtually all browsers. Direct browser support is not necessary
370 since <application>Privoxy</application> runs as a separate application and
371 just exchanges standard HTML data with your browser, just like a web server
376 <sect2 renderas="sect3" id="whichos">
377 <title>Which operating systems are supported?</title>
379 Include supported.sgml here:
384 <sect2 renderas="sect3" id="newinstall"><title>Can I install
385 <application>Privoxy</application> over <application>Junkbuster</application>?</title>
387 We recommend you uninstall <application>Junkbuster</application>
388 first to minimize conflicts and confusion. You may want to
389 save your old configuration files for future reference. The configuration
390 is substantially changed.
394 url="../user-manual/index.html">user-manual</ulink> for
395 platform specific installation instructions.
398 Note: Some installers may automatically uninstall
399 <application>Junkbuster</application>, if present!
404 <sect2 renderas="sect3">
405 <title id="firststep">I just installed <application>Privoxy</application>. Is there anything
406 special I have to do now?</title>
409 All browsers must be told to use <application>Privoxy</application>
410 as a proxy by specifying the correct proxy address and port number
411 in the appropriate configuration area for the browser. See below.
412 Also, you should flush your browser's memory and disk cache to get rid of any
420 <sect2 renderas="sect3" id="localhost"><title>What is the proxy address of <application>Privoxy</application>?</title>
422 If you set up the <application>Privoxy</application> to run on
423 the computer you browse from (rather than your ISP's server or some
424 networked computer on a LAN), the proxy will be on <quote>localhost</quote>
425 (which is the special name used by every computer on the Internet to refer
426 to itself) and the port will be 8118 (unless you have <application>Privoxy</application> to run on a different port with the
427 <emphasis>listen-address</emphasis> config option).
430 When configuring your browser's proxy settings you typically enter
431 the word <quote>localhost</quote> in the boxes next to <quote>HTTP</quote>
432 and <quote>Secure</quote> (HTTPS) and then the number <quote>8118</quote>
433 for <quote>port</quote>. This tells your browser to send all web
434 requests to <application>Privoxy</application> instead of directly to the
438 <application>Privoxy</application> can also be used to proxy for
439 a Local Area Network. In this case, your would enter either the IP
440 address of the LAN host where <application>Privoxy</application>
441 is running, or the equivalent hostname. Port assignment would be
445 <application>Privoxy</application> does not currently handle
446 protocols such as FTP, SMTP, IM, IRC, ICQ, or other Internet
451 <sect2 renderas="sect3">
452 <title id="nothing">I just installed <application>Privoxy</application>, and nothing is happening.
453 All the ads are there. What's wrong?</title>
456 Did you configure your browser to use <application>Privoxy</application>
457 as a proxy? It does not sound like it. See above. You might also try flushing
458 the browser's caches to force a full re-reading of pages. You can verify
459 that <application>Privoxy</application> is running, and your browser
460 is correctly configured by entering the special URL:
461 <ulink url="http://p.p/">http://p.p/</ulink>. This should give you
462 a banner that says <quote>This is Privoxy</quote> and
463 access to <application>Privoxy's</application> internal configuration.
464 If you see this, then you are good to go. If not, the browser or
465 <application>Privoxy</application> are not set up correctly.
474 <!-- ~~~~~ New section ~~~~~ -->
476 <sect1 id="configuration"><title>Configuration</title>
478 <sect2 renderas="sect3" id="newconfig"><title>Can I use my old config files?</title>
480 There are major changes to <application>Junkbuster</application>/
481 <application>Privoxy</application> configuration from version 2.0.x to
482 2.9.x and later. Most of the older files will not work at all. This is
483 especially true of <filename>blocklist</filename>. If this is the case, you
484 will need to re-enter your old data into the new configuration structure.
485 This is probably also a good recommendation even if upgrading from 2.9.x to
486 3.x since there were many minor changes along the way.
490 <sect2 renderas="sect3">
491 <title id="actionsfile">What is an <quote>actions</quote> file?</title>
494 <quote>actions</quote> files are where various actions that
495 <application>Privoxy</application> might take, are configured.
496 Typically, you would define a set of default actions that apply
497 to all URLs, then add exceptions to these defaults where needed.
501 Actions can be defined on a per site basis, or for groups of sites. Actions
502 can also be grouped together and then applied to one or more sites. There
503 are many possible actions that might apply to any given site. As an example,
504 if we are blocking cookies as one of our default
505 <application>actions</application>, but need to accept cookies from a given
506 site, we would define this in our <quote>actions</quote> file.
510 No longer appropriate 04/28/02 hal.
513 <application>Privoxy</application> comes with several default
514 <application>actions</application> files, with varying degrees
515 of filtering and blocking, as starting points for your own
516 configuration (see below).
521 <sect2 renderas="sect3" id="actionss">
522 <title>The <quote>actions</quote> concept confuses me. Please list
523 some of these <quote>actions</quote>.</title>
525 These are all explained in the
526 <ulink url="../user-manual/actions-file.html">user-manual</ulink>.
527 Please refer to that.
532 <sect2 renderas="sect3">
533 <title id="actconfig">How are actions files configured? What is the easiest
534 way to do this?</title>
537 The easiest way to do this, is to access <application>Privoxy</application>
538 with your web browser at <ulink url="http://p.p/">http://p.p/</ulink>,
540 "<ulink url="http://config.privoxy.org">View & change the current configuration</ulink>"
541 from the selection list. You can also do this by editing the appropriate
542 file with a text editor.
548 url="../user-manual/actions-file.html">user-manual</ulink> for a
549 detailed explanation of these and other configuration files, and their
550 various options and syntax.
555 <!-- ~~~~~ New section ~~~~~ -->
556 <sect2 renderas="sect3">
557 <title>There are several different <quote>actions</quote> files. What are
558 the differences?</title>
560 As of <application>Privoxy</application> v2.9.15, three actions files
561 are being included, to be used for
562 different purposes. These are
563 <filename>default.action</filename>, <filename>standard.action</filename>,
564 and <filename>user.action</filename>. Please see
565 <ulink url="../user-manual/actions-file.html">the User Manual</ulink>
566 for an explanation of each.
570 Earlier versions included three different versions
571 <filename>default.action</filename> files. The new scheme allows for
572 greater flexibility of local configuration, and for browser based
579 FIXME: Commenting these out until we have some data there. HB 03/17/02.
581 <sect2 renderas="sect3" id="yahoo"><title>How can I make my Yahoo account work?</title>
587 <sect2 renderas="sect3" id="hotmail"> <title>How can I make my Hotmail account work?</title>
593 <sect2 renderas="sect3" id="gmx"> <title>How can I make my GMX account work?</title>
601 <sect2 renderas="sect3" id="configfiles"> <title>What are the differences between
602 intermediate.action, basic.action, etc.?</title>
604 Configuring <application>Privoxy</application> is not easy. To help you get
605 started, we provide you with three different default configurations. The
606 following table shows you, which features are enabled in each configuration.
609 <table frame=all><title>Default Configurations</title>
610 <tgroup cols=5 align=left colsep=1 rowsep=1>
618 <entry>Feature</entry>
619 <entry>default.action</entry>
620 <entry>basic.action</entry>
621 <entry>intermediate.action</entry>
622 <entry>advanced.action</entry>
628 <!-- <entry>f1</entry> -->
629 <!-- <entry>f2</entry> -->
630 <!-- <entry>f3</entry> -->
631 <!-- <entry>f4</entry> -->
632 <!-- <entry>f5</entry> -->
639 <entry>ad-filtering</entry>
647 <entry>blank image</entry>
655 <entry>de-animate GIFs</entry>
663 <entry>referer forging</entry>
671 <entry>jon's +no-cookies-keep (i.e. session cookies only)</entry>
679 <entry>no-popup windows</entry>
687 <entry>fast redirects</entry>
695 <entry>hide-referrer</entry>
703 <entry>hide-useragent</entry>
711 <entry>content-modification</entry>
719 <entry>feature-x</entry>
727 <entry>feature-y</entry>
735 <entry>feature-z</entry>
750 <sect2 renderas="sect3" id="browseconfig"> <title>Why can I change the configuration with a
751 browser? Does that not raise security issues?</title>
753 What I don't understand, is how I can browser edit the config file as a
754 regular user, while the whole <filename>/etc/privoxy</filename> hierarchy
755 belongs to the user <quote>privoxy</quote>, with only 644 permissions.
758 When you use the browser-based editor, <application>Privoxy</application>
759 itself is writing to the config files. Because
760 <application>Privoxy</application> is running as the user <quote>privoxy</quote>, it can
761 update the config files.
764 If you don't like this, setting <quote>enable-edit-actions 0</quote> in the
765 config file will disable the browser-based editor. If you're that paranoid,
766 you should also consider setting <quote>enable-remote-toggle 0</quote> to prevent
767 browser-based enabling/disabling of <application>Privoxy</application>.
770 Note that normally only local users can connect to
771 <application>Privoxy</application>, so this is not (normally) a security
777 <sect2 renderas="sect3">
778 <title id="filterfile">What is <quote>default.filter</quote>?</title>
780 The <quote>default.filter</quote> file is where <quote>filters</quote>
781 are defined, which are used to <quote>filter</quote> any
782 web page content. By <quote>filtering</quote> we mean it can modify, remove,
783 or change <emphasis>anything</emphasis> on the page, including HTML tags, and
784 JavaScript. Regular expressions are used to accomplish this, and operate
785 on a line by line basis. This is potentially a very powerful feature, but
786 requires some expertise.
790 If you are familiar with regular expressions, and HTML, you can look at
791 the provided <filename>default.filter</filename> with a text editor and see
792 some of things it can be used for.
796 Presently, there is no GUI editor option for this part of the configuration,
797 but you can disable/enable various sections of the included default
798 file with the <quote>View & change the current configuration</quote> from
804 <sect2 renderas="sect3">
805 <title id="lanconfig">How can I set up <application>Privoxy</application> to act as a proxy for my
808 By default, <application>Privoxy</application> only responds to requests
809 from localhost. To have it act as a server for a network, this needs to be
810 changed in the main config file where the <application>Privoxy</application>
811 configuration is located. In that file is a <quote>listen-address</quote>
812 option. It may be commented out with a <quote>#</quote> symbol. Make sure
813 it is uncommented, and assign it the address of the LAN gateway interface,
814 and port number to use:
819 listen-address 192.168.1.1:8118
824 Save the file, and restart <application>Privoxy</application>. Configure
825 all browsers on the network then to use this address and port number.
831 <sect2 renderas="sect3">
832 <title id="noseeum">Instead of ads, now I get a checkerboard pattern. I don't want to see anything.</title>
834 This is a configuration option for images that
835 <application>Privoxy</application> is stopping. You have the choice of a
836 checkerboard pattern, a transparent 1x1 GIF image (aka <quote>blank</quote>),
837 or a custom URL of your choice. Note that to fit this category, the URL must
838 match both the <ulink url="../user-manual/actions-file.html#HANDLE-AS-IMAGE"><quote>+handle-as-image</quote></ulink>
839 <emphasis>and</emphasis>
840 <ulink url="../user-manual/actions-file.html#BLOCK"><quote>+block</quote></ulink> actions.
843 If you want to see nothing, then change the
844 <ulink url="../user-manual/actions-file.html#SET-IMAGE-BLOCKER"><quote>+set-image-blocker</quote></ulink>
845 action to <quote>+image-blocker{blank}</quote>. This can be done from the
846 <quote>View & change the current configuration</quote> selection at <ulink
847 url="http://p.p/">http://p.p/</ulink>. Or by hand editing the appropriate
848 actions file. This will only effect what is defined as <quote>images</quote>
849 though. Also, some URLs that generate the bright red <quote>Blocked</quote>
850 banner, can be moved to the <quote>+set-image-blocker</quote> section for the
851 same reason, but there are some limits and risks to this (see below).
857 <sect2 renderas="sect3">
858 <title id="whyseeum">Why would anybody want to see a checkerboard pattern?</title>
860 This can be helpful for troubleshooting problems. It might also be good
861 for anyone new to <application>Privoxy</application> so that they can
862 see if their favorite pages are displaying correctly, and
863 <application>Privoxy</application> is not inadvertently removing something
869 <sect2 renderas="sect3">
870 <title id="blockedisugly">I see large red banners on some pages that say
871 <quote>Blocked</quote>. Why and how do I get rid of this?</title>
873 These are URLs that match something in one of
874 <application>Privoxy's</application> block actions
876 url="../user-manual/actions-file.html#BLOCK"><quote>+block</quote></ulink>).
877 It is meant to be a warning so that you know something has been blocked and
878 an easy way for you to see why. These are handled differently than what has
879 been defined explicitly as <quote>images</quote> (e.g. ads that are GIF image
880 files). Depending on the URL itself, it is sometimes hard for
881 <application>Privoxy</application> to really know whether there is indeed an
882 ad image there or not. And there are limitations as to what
883 <application>Privoxy</application> can do to <quote>fool</quote> the
888 For instance, if the ad is in a frame, then it is embedded in the separate
889 HTML page used for the frame. In this case, you cannot just substitute an
890 aribitrary image (like we would for a <quote>blank</quote> image), for an HTML
891 page. The browser is expecting an HTML page, and that is what it must have
892 for frames. Such situations can be a little trickier to deal with, and
893 <application>Privoxy</application> may show the <quote>Blocked</quote> page,
894 despite your best efforts.
898 If you want these to be treated as if they were images, so that they can be
899 made invisible, you can try moving the offending URL from the
900 <quote>+block</quote> section to the <quote>+imageblock</quote> section of
901 your actions file. Just be forewarned, if any URL is made
902 <quote>invisible</quote>, you may not have any inkling that something has
903 been removed from that page, or why. If this approach does not work, then you are
904 probably dealing with a frame (or <quote>ilayer</quote>), and the only thing
905 that can go there is an HTML page of some sort.
908 To deal with this situation, you could modify the
909 <quote><filename>block</filename></quote> HTML template that is used by
910 <application>Privoxy</application> to display this, and make it something
911 more to your liking. Currently, there is no configuration option for this.
912 You will have to modify, or create your own page, and use this to replace
913 <filename>templates/blocked</filename>, which is what
914 <application>Privoxy</application> uses to display the <quote>Blocked</quote>
918 Another way to deal with this is find why and where
919 <application>Privoxy</application> is blocking the frame, and
920 diable this. Then let the <quote>+set-image-blocker</quote> action
921 handle the ad that is embedded in the frame's HTML page.
926 <sect2 renderas="sect3" id="alliseeisred">
927 <title>I cannot see all of the <quote>Blocked</quote> page banner. Help.</title>
929 There is not enough available space to fit the entire Blocked page. Try right
930 clicking on the visible portion, and select <quote>Show Frame</quote>,
931 or equivalent. This will usually allow you to see the entire Privoxy
932 <quote>Blocked</quote> page, and from there you can see just what is being
936 As of Privoxy 2.9.14, the Blocked banner page is re-sizeable, and tries
937 to adjust to the allotted space. There may be occassions where there
938 just isn't enough room to display much of anything useful though.
943 <sect2 renderas="sect3" id="srvany">
944 <title>Can <application>Privoxy</application> run as a service
947 Yes, it can run as a system service using <command>srvany.exe</command>.
948 The only catch is that this will effectively disable the
949 <application>Privoxy</application> icon in the taskbar. You can have
950 one or the other, but not both at this time :(
953 There is a pending feature request for this functionality. See
955 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>,
956 for details, and a sample configuration.
962 <sect2 renderas="sect3" id="otherproxy">
963 <title>How can I make <application>Privoxy</application> work with other
964 proxies like <application>Squid</application>?</title>
966 This can be done. See the <ulink
967 url="../user-manual/config.html#FORWARDING">user manual</ulink>,
968 which describes how to do this.
972 <sect2 renderas="sect3" id="transparent">
973 <title>Can <application>Privoxy</application> run as a <quote>transparent
974 </quote> proxy?</title>
976 No, <application>Privoxy</application> currently does not have this ability,
977 though it is planned for a future release. Transparent proxies require
978 special handling of the request headers beyond what
979 <application>Privoxy</application> is now capable of.
983 Chaining <application>Privoxy</application> with another proxy that has
984 this ability should work though.
985 See the <ulink url="../user-manual/config.html#FORWARDING">user
986 manual</ulink>, which describes this, and also <ulink
987 url="http://www.transproxy.nlc.net.au/">http://www.transproxy.nlc.net.au/</ulink>.
994 <!-- ~ End section ~ -->
997 <!-- ~~~~~ New section ~~~~~ -->
999 <sect1 id="misc"><title>Miscellaneous</title>
1001 <sect2 renderas="sect3">
1002 <title id="slowsme">How much does <application>Privoxy</application> slow my browsing down? This
1003 has to add extra time to browsing.</title>
1005 It should not slow you down any in real terms, and may actually help
1006 speed things up since ads, banners and other junk are not being displayed.
1007 The actual processing time required by <application>Privoxy</application>
1008 itself for each page, is relatively small in the overall scheme of things,
1009 and happens very quickly. This is typically more than offset by time saved
1010 not downloading and rendering ad images.
1014 <quote>Filtering</quote> via the <filename>filterfile</filename>
1015 mechanism may cause a perceived slowdown, since the entire page is buffered
1016 before displaying. See below.
1022 <sect2 renderas="sect3" id="loadingtimes"><title>I noticed considerable
1023 delays in page requests compared to the old Junkbuster. What's wrong?</title>
1025 The entire page content must be loaded into memory in order for the filtering
1026 mechanism to work, and nothing is sent to the browser during this time. The
1027 loading time does not really change in real numbers, but the feeling is
1028 different, because most browsers are able to start rendering incomplete
1029 content, giving the user a feeling of "it works".
1032 To modify the content of a page (i.e. make frames resizeable again, etc.) and
1033 not just replace ads, <application>Privoxy</application> needs to download
1034 the entire page first, do its content magic and then send the page to the
1040 <sect2 renderas="sect3" id="configurl"><title>What is the "http://p.p/"?</title>
1042 Since <application>Privoxy</application> sits between your web browser and the Internet, it can be
1043 programmed to handle certain pages specially.
1047 With recent versions of <application>Privoxy</application> (version 2.9.x and
1048 greater), you can get some information about
1049 <application>Privoxy</application> and change some settings by going to
1050 <ulink url="http://p.p/">http://p.p/</ulink> or, equivalently, <ulink
1051 url="http://config.privoxy.org/">http://config.privoxy.org/</ulink> (Note
1052 that p.p is far easier to type but may not work in some configurations. With
1053 the name change to <application>Privoxy</application>, this is changed from
1054 the previous http://i.j.b/ and earlier 2.9.x versions).
1058 These pages are <emphasis>not</emphasis> forwarded to a server on the
1059 Internet - instead they are handled by a special web server which is built in to
1060 <application>Privoxy</application>.
1064 If you are not running <application>Privoxy</application>, then <ulink
1065 url="http://p.p/">http://p.p/</ulink> will fail, and <ulink
1066 url="http://config.privoxy.org/">http://config.privoxy.org/</ulink> will
1067 return a web page telling you you're not running
1068 <application>Privoxy</application>.
1072 If you have version 2.0.2, then the equivalent is
1073 http://example.com/show-proxy-args (but you get far less information, and
1074 you should really consider upgrading to &p-version;).
1079 FIXME: commented out until we have data. HB 03/18/02.
1081 <sect2 renderas="sect3" id="badfiledesc"><title>I get the message 'Bad File Descriptor', why?</title>
1089 <sect2 renderas="sect3" id="blocklist"><title>Do you still maintain the blocklists?</title>
1091 No, not by this name. The format of the blocklists has changed
1092 significantly in versions 2.9.x and later. This functionality
1093 is done by the <quote>actions</quote> file now. See next question ...
1097 <sect2 renderas="sect3" id="newads"><title>How can I submit new ads?</title>
1099 Please see the <ulink url="contact.html">Contact section</ulink>.
1103 This process does not work with earlier versions of <application>Privoxy</application>
1104 or <application>Junkbuster</application>.
1109 <sect2 renderas="sect3" id="ip"><title>How can I hide my IP address?</title>
1111 You cannot hide your IP address with <application>Privoxy</application> or any other software, since
1112 the server needs to know your IP address to send the answers back to you.
1115 Fortunately there are many publicly usable anonymous proxies out there, which
1116 solve the problem by providing a further level of indirection between you and
1117 the web server, shared by many people and thus letting your requests "drown"
1118 in white noise of unrelated requests as far as user tracking is concerned.
1121 Most of them will, however, log your IP address and make it available to the
1122 authorities in case you abuse that anonymity for criminal purposes. In fact
1123 you can't even rule out that some of them only exist to *collect* information
1124 on (those suspicious) people with a more than average preference for privacy.
1127 You can find a list of anonymous public proxies at <ulink
1128 url="http://www.multiproxy.org/anon_list.htm">multiproxy.org</ulink> and many
1129 more through Google.
1133 <!-- <sect2 renderas="sect3" id="image"><title>What is the imagefile (simage.ini, etc.) for?</title> -->
1135 <!-- Anytime <application>Privoxy</application> determines (with the help of the blocklist) that a URL -->
1136 <!-- contains an advertisement, it has to decide whether this advertisement is an -->
1137 <!-- image or not. <application>Privoxy</application> uses the imagefile for that purpose. -->
1141 <sect2 renderas="sect3">
1142 <title id="anonforsure">Can <application>Privoxy</application> guarantee I am anonymous?</title>
1144 No. Your chances of remaining anonymous are greatly improved, but unless you
1145 are an expert on Internet security it would be safest to assume that
1146 everything you do on the Web can be traced back to you.
1149 <application>Privoxy</application> can remove various information about you,
1150 and allows <emphasis>you</emphasis> more freedom to decide which sites
1151 you can trust, and what details you want to reveal. But it's still possible
1152 that web sites can find out who you are. Here's one way this can happen.
1155 A few browsers disclose the user's email address in certain situations, such
1156 as when transferring a file by FTP. <application>Privoxy</application>
1157 does not filter FTP. If you need this feature, or are concerned about the
1158 mail handler of your browser disclosing your email address, you might
1159 consider products such as <application>NSClean</application>.
1162 Browsers available only as binaries could use non-standard headers to give
1163 out any information they can have access to: see the manufacturer's license
1164 agreement. It's impossible to anticipate and prevent every breach of privacy
1165 that might occur. The professionally paranoid prefer browsers available as
1166 source code, because anticipating their behavior is easier. Trust the source,
1172 <sect2 renderas="sect3">
1173 <title id="sitebreak">Might some things break because header information is
1174 being altered?</title>
1177 Definitely. More and more sites use HTTP header content to decide what to
1178 display and how to display it. There is many ways that this can be handled,
1179 so having hard and fast rules, is tricky.
1183 <quote>USER AGENT</quote> in particular is often used in this way to identify
1184 the browser, and adjust content accordingly. Changing this now is not
1185 recommended, since so many sites do look for this. You may get undesirable
1186 results by changing this.
1190 For instance, different browsers use different encodings of Russian and Czech
1191 characters, certain web servers convert pages on-the-fly according to the
1192 User Agent header. Giving a <quote>User Agent</quote> with the wrong
1193 operating system or browser manufacturer causes some sites in these languages
1194 to be garbled; Surfers to Eastern European sites should change it to
1195 something closer. And then some page access counters work by looking at the
1196 <quote>REFERER</quote> header; they may fail or break if unavailable. The
1197 weather maps of Intellicast have been blocked by their server when no
1198 <quote>REFERER</quote> or cookie is provided, is another example. There are
1199 many, many other ways things can go wrong when trying to fool a web server.
1203 If you have problems with a site, you will have to adjust your configuration
1204 accordingly. Cookies are probably the most likely adjustment that may
1205 be required, but by no means the only one.
1211 <sect2 renderas="sect3">
1212 <title id="caching">Can <application>Privoxy</application> act as a <quote>caching</quote> proxy to
1213 speed up web browsing?</title>
1215 No, it does not have this ability at all. You want something like
1216 <ulink url="http://www.squid-cache.org/">Squid</ulink> for this. And, yes,
1217 before you ask, <application>Privoxy</application> can co-exist
1218 with other kinds of proxies like <application>Squid</application>.
1222 <sect2 renderas="sect3">
1223 <title id="firewall">What about as a firewall? Can <application>Privoxy</application> protect me?</title>
1225 Not in the way you mean, or in the way a true firewall can, or a proxy that
1226 has this specific capability. <application>Privoxy</application> can help
1227 protect your privacy, but not really protect you from intrusion attempts.
1232 <sect2 renderas="sect3">
1233 <title id="logo">The <application>Privoxy</application> logo that replaces ads is very blocky
1234 and ugly looking. Can't a better font be used?</title>
1237 This is not a font problem. The logo is an image that is created by
1238 <application>Privoxy</application> on the fly. So as to not waste
1239 memory, the image is rather small. The blockiness comes when the
1240 image is scaled to fill a largish area. There is not much to be done
1241 about this, other than to use one of the other
1242 <quote>imageblock</quote> directives: <emphasis>pattern</emphasis>,
1243 <emphasis>blank</emphasis>, or a URL of your choosing.
1246 Given the above problem, we have decided to remove the logo option entirely
1252 <sect2 renderas="sect3">
1253 <title id="wasted">I have large empty spaces now where ads used to be.
1256 It would be easy enough to just eliminate this space altogether, rather than
1257 fill it with blank space. But, this would create problems with many pages
1258 that use the overall size of the ad to help organize the page layout and
1259 position the various components of the page where they were intended to be.
1260 It is best left this way.
1265 <sect2 renderas="sect3">
1266 <title id="ssl">How can <application>Privoxy</application> filter Secure (HTTPS) URLs?</title>
1268 This is a limitation since HTTPS transactions are encrypted SSL sessions
1269 between your browser and the secure site, and are meant to be reliably
1270 <emphasis>secure</emphasis> and private. This means that all cookies and HTTP
1271 header information are also encrypted from the time they leave your browser,
1272 to the site, and vice versa. <application>Privoxy</application> does not
1273 try to unencrypt this information, so it just passes through as is.
1274 <application>Privoxy</application> can still catch images and ads that
1275 are embedded in the SSL stream though.
1281 <sect2 renderas="sect3">
1282 <title id="secure"><application>Privoxy</application> runs as a <quote>server</quote>. How
1283 secure is it? Do I need to take any special precautions?</title>
1285 There are no known exploits that might effect
1286 <application>Privoxy</application>. On Unix-like systems,
1287 <application>Privoxy</application> can run as a non-privileged
1288 user, which is how we recommend it be run. Also, by default
1289 <application>Privoxy</application> only listens to requests
1290 from <quote>localhost</quote>. The server aspect of
1291 <application>Privoxy</application> is not itself directly exposed to the
1292 Internet in this configuration. If you want to have
1293 <application>Privoxy</application> serve as a LAN proxy, this will have to
1294 be opened up to allow for LAN requests. In this case, we'd recommend
1295 you specify only the LAN gateway address, e.g. 192.168.1.1, in the main
1296 <application>Privoxy</application> config file. All LAN hosts can then use
1297 this as their proxy address in the browser proxy configuration. In this way,
1298 <application>Privoxy</application> will not listen on any external ports.
1299 Of course, a firewall is always good too. Better safe than sorry.
1304 <sect2 renderas="sect3" id="turnoff">
1305 <title>How can I temporarily disable <application>Privoxy</application>?</title>
1307 The easiest way is to access <application>Privoxy</application> with your
1308 browser by using the special URL: <ulink url="http://p.p/">http://p.p/</ulink>
1309 and select "Toggle Privoxy on or off" from that page.
1314 <sect2 renderas="sect3" id="seealso">
1315 <title>Where can I find more information about <application>Privoxy</application>
1316 and related issues?</title>
1317 <!-- Include seealso.sgml boilerplate: -->
1319 <!-- end boilerplate -->
1324 <ulink url="../user-manual/seealso.html">user-manual</ulink> for
1333 <!-- ~~~~~ New section ~~~~~ -->
1335 <sect1 id="trouble">
1336 <title>Troubleshooting</title>
1338 <sect2 renderas="sect3">
1339 <title id="refused">I just upgraded and am getting <quote>connection refused</quote>
1340 with every web page?</title>
1342 Either <application>Privoxy</application> is not running, or your
1343 browser is configured for a different port than what
1344 <application>Privoxy</application> is using.
1348 The old <application>Privoxy</application> (and also
1349 <application>Junkbuster</application>) used port 8000 by
1350 default. This has been changed to port 8118 now, due to a conflict
1351 with NAS (Network Audio Service), which uses port 8000. If you haven't,
1352 you need to change your browser to the new port number, or alternately
1353 change <application>Privoxy's</application> <quote>listen-address</quote>
1354 setting in the <filename>config</filename> file used to start
1355 <application>Privoxy</application>.
1360 <sect2 renderas="sect3">
1361 <title id="flushit">I just added a new rule, but the steenkin ad is
1362 still getting through. How?</title>
1364 If the ad had been displayed before you added its URL, it will probably be
1365 held in the browser's cache for some time, so it will be displayed without
1366 the need for any request to the server, and <application>Privoxy</application>
1367 will not be in the picture. The best thing to do is try flushing the browser's
1368 caches. And then try again.
1372 If this doesn't help, you probably have an error in the rule you
1373 applied. Try pasting the full URL of the offending ad into <ulink
1374 url="http://config.privoxy.org/show-url-info">http://config.privoxy.org/show-url-info</ulink>
1375 and see if any actions match your new rule.
1380 <sect2 renderas="sect3">
1381 <title id="badsite">One of my favorite sites does not work with <application>Privoxy</application>.
1382 What can I do?</title>
1385 First verify that it is indeed a <application>Privoxy</application> problem,
1386 by disabling <application>Privoxy</application> filtering and blocking.
1387 Go to <ulink url="http://p.p/">http://p.p/</ulink> and click on
1388 <quote>Toggle Privoxy On or Off</quote>, then disable it. Now try that
1389 page again. It's probably a good idea to flush the browser cache as well
1390 with <literal>Shift+Reload</literal> to flush caches.
1394 If still a problem, go to <quote>Show which actions apply to a URL and
1395 why</quote> from <ulink url="http://p.p/">http://p.p/</ulink> and paste
1396 the full URL of the page in question into the prompt. See which actions are
1397 being applied to the URL. Now, armed with this information, go to
1398 <quote>View & change the current configuration</quote>. Here you should see various sections that have
1399 various <application>Privoxy</application> features disabled for specific
1400 sites. Most disabled <quote>actions</quote> will have a <quote>-</quote> (minus
1401 sign) in front of them. Some aliases are used just to disable other actions,
1402 e.g. <quote>shop</quote> and <quote>fragile</quote>, and won't necessarily
1403 use a <quote>+</quote> or <quote>-</quote> sign. Add your problem page
1404 URL to one of these sections that looks like it is disabling the feature that
1405 is causing the problem. Rember to flush your browser's caches when making
1406 such changes! As a last resort, try <quote>fragile</quote> which
1407 disables most actions. Now re-try the page. There might be some trial and
1408 error involved. This is discussed in more detail in the <ulink
1409 url="../user-manual/appendix.html#ACTIONSANAT">user-manual appendix</ulink>.
1414 Alternately, if you are comfortable with a text editor, you can accomplish
1415 the same thing by editing the appropriate <quote>actions</quote> file.
1425 <!-- ~~~~~ New section ~~~~~ -->
1427 FIXME: Commented out until we have something to put here. HB 03/18/02.
1428 <sect1 id="knownissues"><title>Known Issues</title>
1435 <!-- ~~~~~ New section ~~~~~ -->
1436 <sect1 id="contact"><title>Contacting the developers, Bug Reporting and Feature Requests</title>
1437 <!-- Include contacting.sgml -->
1439 <!-- end contacting -->
1442 <!-- ~~~~~ New section ~~~~~ -->
1443 <sect1 id="copyright"><title>Copyright, License and History</title>
1445 <sect2><title>Copyright</title>
1446 <!-- Include copyright.sgml -->
1450 Portions of this document are <quote>borrowed</quote> from the original
1451 <application>Junkbuster</application> (tm) FAQ, and modified as
1452 appropriate for <application>Privoxy</application>.
1456 <!-- ~~~~~ New section ~~~~~ -->
1457 <sect2><title>License</title>
1458 <!-- Include copyright.sgml: -->
1460 <!-- end copyright -->
1462 <!-- ~ End section ~ -->
1464 <!-- ~~~~~ New section ~~~~~ -->
1465 <sect2><title>History</title>
1466 <!-- Include history.sgml -->
1472 <!-- ~ End section ~ -->
1475 <!-- ~~~~~ New section ~~~~~ -->
1477 <sect1 id="seealso"><title>See also</title>
1479 <!-- Include seealso.sgml -->
1490 Tue 09/11/01 06:38:14 PM EST: Test SGML doc by Hal Burgiss.
1492 Last modified: Mon Sep 10 19:22:09 CEST 2001
1494 This program is free software; you can redistribute it
1495 and/or modify it under the terms of the GNU General
1496 Public License as published by the Free Software
1497 Foundation; either version 2 of the License, or (at
1498 your option) any later version.
1500 This program is distributed in the hope that it will
1501 be useful, but WITHOUT ANY WARRANTY; without even the
1502 implied warranty of MERCHANTABILITY or FITNESS FOR A
1503 PARTICULAR PURPOSE. See the GNU General Public
1504 License for more details.
1506 The GNU General Public License should be included with
1507 this file. If not, you can view it at
1508 http://www.gnu.org/copyleft/gpl.html
1509 or write to the Free Software Foundation, Inc., 59
1510 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
1513 Revision 1.56 2002/05/04 08:44:44 swa
1516 Revision 1.55 2002/05/04 00:41:56 hal9
1517 -Remove TOC/first page kludge in favor of proper handling via dsl file.
1519 Revision 1.54 2002/05/03 05:06:44 hal9
1520 Add brief Q/A on transparent proxies.
1522 Revision 1.53 2002/05/03 01:34:52 hal9
1523 Fix section numbering for new sections (due to TOC kludge).
1525 Revision 1.52 2002/04/29 03:08:43 hal9
1526 -Added new Q/A on new actions file set up (pointer to u-m)
1527 -Fixed a few broken links and converted old actions as a result of
1530 Revision 1.51 2002/04/26 17:24:31 swa
1531 bookmarks cleaned, changed structure of user manual, screen and programlisting cleanups, and numerous other changes that I forgot
1533 Revision 1.50 2002/04/26 05:25:23 hal9
1534 Mass commit to catch a few scattered fixes.
1536 Revision 1.49 2002/04/12 10:10:18 swa
1539 Revision 1.48 2002/04/10 18:45:15 swa
1542 Revision 1.47 2002/04/10 04:05:32 hal9
1545 Revision 1.45 2002/04/08 22:59:26 hal9
1546 Version update. Spell chkconfig correctly :)
1548 Revision 1.44 2002/04/07 21:24:29 hal9
1549 Touch up on name change.
1551 Revision 1.43 2002/04/04 21:59:53 hal9
1552 Added NT/W2K service/icon situation.
1554 Revision 1.42 2002/04/04 18:46:47 swa
1555 consistent look. reuse of copyright, history et. al.
1557 Revision 1.41 2002/04/04 06:48:37 hal9
1558 Structural changes to allow for conditional inclusion/exclusion of content
1559 based on entity toggles, e.g. 'entity % p-not-stable "INCLUDE"'. And
1560 definition of internal entities, e.g. 'entity p-version "2.9.13"' that will
1561 eventually be set by Makefile.
1562 More boilerplate text for use across multiple docs.
1564 Revision 1.40 2002/04/03 04:22:03 hal9
1565 Fixed several typos.
1567 Revision 1.39 2002/04/03 03:53:03 hal9
1568 Revert some changes, and then make some news, to layout, and appearance.
1570 Revision 1.38 2002/04/02 03:49:10 hal9
1571 Major changes to doc structure and layout. Sections are not automatically
1572 numbered now. TOC is on page by itself.
1574 Revision 1.37 2002/04/01 16:24:07 hal9
1575 -Rework of supported Q/A.
1576 -Set up entities to include boilerplate text.
1578 Revision 1.36 2002/03/31 23:18:47 hal9
1579 More on dealing with BLOCKED.
1581 Revision 1.35 2002/03/30 04:14:19 hal9
1582 Fix privoxy.org/config links.
1584 Revision 1.34 2002/03/29 04:35:56 hal9
1587 Revision 1.33 2002/03/29 01:31:48 hal9
1588 Several new Q/A's and other touch ups.
1590 Revision 1.32 2002/03/27 00:57:03 hal9
1591 Touch ups for name change.
1593 Revision 1.31 2002/03/26 22:29:55 swa
1594 we have a new homepage!
1596 Revision 1.30 2002/03/25 16:39:22 hal9
1597 A few new sections. Made all links relative to user-manual.
1599 Revision 1.29 2002/03/25 05:23:57 hal9
1600 Moved section, and touch ups.
1602 Revision 1.28 2002/03/25 04:27:33 hal9
1603 New section related to name change.
1605 Revision 1.25 2002/03/24 16:08:08 swa
1606 we are too lazy to make a block-built
1607 privoxy logo. hence removed the option.
1609 Revision 1.24 2002/03/24 15:46:20 swa
1610 name change related issue.
1612 Revision 1.23 2002/03/24 12:33:01 swa
1615 Revision 1.22 2002/03/24 11:51:00 swa
1616 name change. changed filenames.
1618 Revision 1.21 2002/03/24 11:01:06 swa
1621 Revision 1.20 2002/03/23 15:13:11 swa
1622 renamed every reference to the old name with foobar.
1623 fixed "application foobar application" tag, fixed
1624 "the foobar" with "foobar". left junkbustser in cvs
1625 comments and remarks to history untouched.
1627 Revision 1.19 2002/03/21 17:01:54 hal9
1630 Revision 1.18 2002/03/18 16:40:31 hal9
1633 Revision 1.17 2002/03/18 03:53:53 hal9
1636 Revision 1.16 2002/03/17 21:32:56 hal9
1637 A few more additions.
1639 Revision 1.15 2002/03/17 07:25:59 hal9
1640 Correcting some of my typos, and some additions.
1642 Revision 1.14 2002/03/17 02:39:13 hal9
1643 A little more added ...
1645 Revision 1.13 2002/03/17 00:22:20 hal9
1646 Adding new stuff, and trying to incorporate stuff from old faq.
1648 Revision 1.12 2002/03/11 20:13:21 swa
1651 Revision 1.11 2002/03/11 18:42:27 swa
1654 Revision 1.10 2002/03/11 13:13:27 swa
1655 correct feedback channels
1657 Revision 1.9 2002/03/10 23:34:04 swa
1658 more info on not hiding ip address
1660 Revision 1.8 2002/03/09 15:55:48 swa
1661 added default config section
1663 Revision 1.7 2002/03/07 18:16:55 swa
1666 Revision 1.6 2002/03/07 13:16:31 oes
1667 Committing changes by Stefan
1669 Revision 1.5 2002/03/02 15:50:04 swa
1670 2.9.11 version. more input for docs.
1672 Revision 1.4 2002/02/24 14:34:24 jongfoster
1673 Formatting changes. Now changing the doctype to DocBook XML 4.1
1674 will work - no other changes are needed.
1676 Revision 1.3 2001/09/23 10:13:48 swa
1677 upload process established. run make webserver and
1678 the documentation is moved to the webserver. documents
1679 are now linked correctly.
1681 Revision 1.2 2001/09/13 15:20:17 swa
1682 merged standards into developer manual
1684 Revision 1.1 2001/09/12 15:36:41 swa
1685 source files for junkbuster documentation
1687 Revision 1.3 2001/09/10 17:43:59 swa
1688 first proposal of a structure.
1690 Revision 1.2 2001/06/13 14:28:31 swa
1691 docs should have an author.
1693 Revision 1.1 2001/06/13 14:20:37 swa
1694 first import of project's documentation for the webserver.