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 -->
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.58 2002/05/10 01:48:20 hal9 Exp $
29 Copyright (C) 2001, 2002 Privoxy Developers <developers@privoxy.org>
32 Based partially on the Internet Junkbuster FAQ originally written by and
33 Copyright (C) 1997 Anonymous Coders and Junkbusters Corporation.
34 http://www.junkbusters.com
36 <Qandaset defaultlabel='qanda'>
51 ========================================================================
52 NOTE: Please read developer-manual/documentation.html before touching
53 anything in this, or other Privoxy documentation. You have been warned!
54 Failure to abide by this rule will result in the revocation of your license
55 to live a peaceful existence!
56 ========================================================================
62 <article id="index" class="faq">
64 <title>Privoxy Frequently Asked Questions</title>
68 <!-- Completely the wrong markup, but very little is allowed -->
69 <!-- in this part of an article. FIXME -->
70 <link linkend="copyright">Copyright</link> &my-copy; 2001, 2002 by
71 <ulink url="http://www.privoxy.org">Privoxy Developers</ulink>
75 <pubdate>$Id: faq.sgml,v 1.58 2002/05/10 01:48:20 hal9 Exp $</pubdate>
79 Note: this should generate a separate page, and a live link to it.
80 But it doesn't for some mysterious reason. Please leave commented
81 unless it can be fixed proper. For the time being, the copyright
82 statement will be in copyright.smgl.
86 <legalnotice id="legalnotice">
88 text goes here ........
98 <orgname>By: Privoxy Developers</orgname>
107 This is here to keep vim syntax file from breaking :/
108 If I knew enough to fix it, I would.
109 PLEASE DO NOT REMOVE! HB: hal@foobox.net
114 This FAQ gives users and developers alike answers to frequently asked
115 questions about <ulink url="http://www.privoxy.org">Privoxy</ulink>
116 <![%p-stable;[ v.&p-version]]>.
119 <!-- Include privoxy.sgml boilerplate: -->
121 <!-- end boilerplate -->
124 You can find the latest version of the document at <ulink
125 url="http://www.privoxy.org/faq/">http://www.privoxy.org/faq/</ulink>.
126 Please see the Contact section if you want to contact the developers.
130 <!-- Feel free to send a note to the developers at <email>ijbswa-developers@lists.sourceforge.net</email>. -->
136 <!-- ~~~~~ New section ~~~~~ -->
138 <sect1 id="general"><title>General Information</title>
140 <sect2 renderas="sect3" id="newjb"><title>What is this new version of <application>Privoxy</application>?</title>
142 The original <application><trademark>Internet
143 Junkbuster</trademark></application> (tm) is a copyrighted product of <ulink
144 url="http://www.junkbusters.com">Junkbusters Corporation</ulink>.
145 Development of this effort stopped some time ago as of version 2.0.2. Stefan
146 Waldherr started the ijbswa project on <ulink
147 url="http://sourceforge.net/projects/ijbswa/">Sourceforge</ulink> to
148 rekindle development. Other developers subsequently joined with Stefan, and
149 have since added many new features, refinements and enhancements. The result
150 of this effort is <application>Privoxy</application>.
153 <application>Privoxy</application> has evolved from the
154 <application>Junkbuster 2.0.2</application> code base, and has advanced
155 significantly at this point.
158 Please see the <link linkend="copyright">History section</link> for more
159 information on the history of <application>Junkbuster</application> and
160 <application>Privoxy</application>.
166 <sect2 renderas="sect3">
167 <title id="whyprivoxy">Why <quote>Privoxy</quote>? Why a name change at all?</title>
169 <application>Privoxy</application> is the
170 <quote><emphasis>Privacy Enhancing Proxy</emphasis></quote>.
173 There are potential legal complications from the continued use of the
174 <application>Junkbuster</application> name, which is a registered trademark of
175 <ulink url="http://junkbusters.com">Junkbusters Corporation</ulink>.
176 And thus they <quote>own</quote> the rights to the name.
177 (There are, however, no objections from Junkbusters Corporation to the
178 <application>Privoxy</application> project itself, and they, in fact, still
179 share our ideals and goals.)
183 The developers also believed that there are so many changes from the original
184 code, that it was time to make a clean break from the past and make
185 a name in their own right<![%p-not-stable;[, especially now with the pending
186 release of version 3.0]]>.
191 <sect2 renderas="sect3" id="differs"><title>How does <application>Privoxy</application> differ
192 from the old <application>Junkbuster?</application></title>
194 <application>Privoxy</application> picks up where
195 <application>Junkbuster</application> left off. All the old features remain.
196 The new <application>Privoxy</application> still blocks ads and banners,
197 still manages cookies, and still helps protect your privacy. But, these are
198 all enhanced, and many new features have been added, all in the same vein.
201 The configuration has changed significantly as well. This is something that
202 users will notice right off the bat if you are upgrading from
203 <application>Junkbuster</application> 2.0.x. The <quote>blocklist</quote>
204 file does not exist any more. This is replaced by <quote>actions</quote>
205 files, such as <filename>default.actions</filename>. This is where most of
206 the per site configuration is now.
210 <sect2 renderas="sect3" id="features"><title>What are some of the new features?</title>
211 <!-- Include newfeatures.sgml: -->
217 <sect2 renderas="sect3" id="proxymoron"><title>What is a <quote>proxy</quote>? How does
218 <application>Privoxy</application> work? </title>
220 When you connect to a web site with <application>Privoxy</application>,
221 you are really connecting to your locally running version of
222 <application>Privoxy</application>. <application>Privoxy</application>
223 intercepts your requests for the web page, and relays that to the
224 <quote>real</quote> web site. The web site sends the HTTP data stream
225 back to <application>Privoxy</application>, where
226 <application>Privoxy</application> can work its magic before it
227 relays this data back to your web browser.
231 Since <application>Privoxy</application> sits between you and the
232 WWW, it is in a position to intercept and completely manage all web traffic and
233 HTTP content before it gets to your browser.
234 <application>Privoxy</application> uses various programming methods to do
235 this, all of which is under your control via the various configuration
240 There are many kinds of proxies. <application>Privoxy</application> best
241 fits the <quote>filtering proxy</quote> category.
247 <sect2 renderas="sect3">
248 <title id="knows">How does <application>Privoxy</application> know what is
249 an ad, and what is not?</title>
251 <application>Privoxy</application> processes all the raw content of every
252 web page. So it reads everything on each page. It then compares this to the
253 rules as set up in the configuration files, and looks for any matches to
254 these rules. <application>Privoxy</application> makes heavy use of
255 <quote>regular expressions</quote>. (If you are not familiar with regular
256 expressions, it is explained briefly in <ulink
257 url="../user-manual/appendix.html">the user manual</ulink>.) Regular
258 expressions facilitate matching of one text string against another, using
259 wildcards to build complex patterns. So <application>Privoxy</application>
260 will typically look for URLs and other content that match certain key words
261 and expressions as defined in the configuration files. For instance a URL
262 that contains <quote>/banners</quote>, has a high probability of containing
263 ad banners, and thus would be a prime candidate to have a matching rule.
266 So <application>Privoxy</application> will look for these kinds of obvious
267 looking culprits. And also, will use lists of known organizations that
268 specialize in ads. Again, using complex patterns to match as many potential
269 combinations as possible since there tend to be many, many variations used by
270 advertisers, and new ones are being introduced all the time.
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 rule
279 accidentally block something by mistake. There is a good chance you may run
280 into such a situation at some point. It is tricky writing rules to cover
281 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.
315 <sect2 renderas="sect3" id="license"><title>Is there is a license or fee? What about a
316 warranty? Registration?</title>
318 <application>Privoxy</application> is licensed under the GNU General Public
319 License (GPL). It is free to use, copy, modify or distribute as you wish
320 under the terms of this license. Please see the <link
321 linkend="copyright">Copyright</link> section for more information on the
322 license and copyright. Or the <filename>LICENSE</filename> file
323 that should be included.
327 There is no warranty of any kind, expressed, implied or otherwise. That is
328 something that would cost real money ;-) There is no registration either.
329 <application>Privoxy</application> really is <emphasis>free</emphasis>
336 <sect2 renderas="sect3" id="jointeam"><title>I would like to help you, what do I do?</title>
338 <sect3 renderas="sect4" id="jointeam-money"><title>Money Money Money</title>
340 We, of course, welcome donations and use the money for domain registering,
341 regular world-wide get-togethers (hahaha). Anyway, we'll soon describe the
342 process how to donate money to the team.
346 <sect3 renderas="sect4" id="jointeam-work"><title>You want to work with us?</title>
348 Well, helping the team is always a good idea. We welcome new developers,
349 RPM gurus or documentation makers. Simply get an account on sourceforge.net
350 and mail your id to the developer mailing list. Then read the
351 section Quickstart in the <ulink url="../developer-manual/quickstart.html">
352 Developer's Manual</ulink>.
355 Once we have added you to the team, you'll have write access to the CVS
356 repository, and together we'll find a suitable task for you.
365 <!-- ~~~~~ New section ~~~~~ -->
367 <sect1 id="installation"><title>Installation</title>
369 <sect2 renderas="sect3" id="whichbrowsers">
370 <title>Which browsers are supported by <application>Privoxy</application>?</title>
372 Any browser that can be configured to use a <quote>proxy</quote>, which
373 should be virtually all browsers. Direct browser support is not necessary
374 since <application>Privoxy</application> runs as a separate application and
375 just exchanges standard HTML data with your browser, just like a web server
380 <sect2 renderas="sect3" id="whichos">
381 <title>Which operating systems are supported?</title>
383 Include supported.sgml here:
388 <sect2 renderas="sect3" id="newinstall"><title>Can I install
389 <application>Privoxy</application> over <application>Junkbuster</application>?</title>
391 We recommend you uninstall <application>Junkbuster</application>
392 first to minimize conflicts and confusion. You may want to
393 save your old configuration files for future reference. The configuration
394 is substantially changed.
398 url="../user-manual/index.html">user-manual</ulink> for
399 platform specific installation instructions.
402 Note: Some installers may automatically uninstall
403 <application>Junkbuster</application>, if present!
408 <sect2 renderas="sect3">
409 <title id="firststep">I just installed <application>Privoxy</application>. Is there anything
410 special I have to do now?</title>
413 All browsers must be told to use <application>Privoxy</application>
414 as a proxy by specifying the correct proxy address and port number
415 in the appropriate configuration area for the browser. See below.
416 Also, you should flush your browser's memory and disk cache to get rid of any
424 <sect2 renderas="sect3" id="localhost"><title>What is the proxy address of <application>Privoxy</application>?</title>
426 If you set up the <application>Privoxy</application> to run on
427 the computer you browse from (rather than your ISP's server or some
428 networked computer on a LAN), the proxy will be on <quote>localhost</quote>
429 (which is the special name used by every computer on the Internet to refer
430 to itself) and the port will be 8118 (unless you have <application>Privoxy</application> to run on a different port with the
431 <emphasis>listen-address</emphasis> config option).
434 When configuring your browser's proxy settings you typically enter
435 the word <quote>localhost</quote> in the boxes next to <quote>HTTP</quote>
436 and <quote>Secure</quote> (HTTPS) and then the number <quote>8118</quote>
437 for <quote>port</quote>. This tells your browser to send all web
438 requests to <application>Privoxy</application> instead of directly to the
442 <application>Privoxy</application> can also be used to proxy for
443 a Local Area Network. In this case, your would enter either the IP
444 address of the LAN host where <application>Privoxy</application>
445 is running, or the equivalent hostname. Port assignment would be
449 <application>Privoxy</application> does not currently handle
450 protocols such as FTP, SMTP, IM, IRC, ICQ, or other Internet
455 <sect2 renderas="sect3">
456 <title id="nothing">I just installed <application>Privoxy</application>, and nothing is happening.
457 All the ads are there. What's wrong?</title>
460 Did you configure your browser to use <application>Privoxy</application>
461 as a proxy? It does not sound like it. See above. You might also try flushing
462 the browser's caches to force a full re-reading of pages. You can verify
463 that <application>Privoxy</application> is running, and your browser
464 is correctly configured by entering the special URL:
465 <ulink url="http://p.p/">http://p.p/</ulink>. This should give you
466 a banner that says <quote>This is Privoxy</quote> and
467 access to <application>Privoxy's</application> internal configuration.
468 If you see this, then you are good to go. If not, the browser or
469 <application>Privoxy</application> are not set up correctly.
478 <!-- ~~~~~ New section ~~~~~ -->
480 <sect1 id="configuration"><title>Configuration</title>
482 <sect2 renderas="sect3" id="newconfig"><title>Can I use my old config files?</title>
484 There are major changes to <application>Junkbuster</application>/
485 <application>Privoxy</application> configuration from version 2.0.x to
486 2.9.x and later. Most of the older files will not work at all. This is
487 especially true of <filename>blocklist</filename>. If this is the case, you
488 will need to re-enter your old data into the new configuration structure.
489 This is probably also a good recommendation even if upgrading from 2.9.x to
490 3.x since there were many minor changes along the way.
494 <sect2 renderas="sect3">
495 <title id="actionsfile">What is an <quote>actions</quote> file?</title>
498 <quote>actions</quote> files are where various actions that
499 <application>Privoxy</application> might take, are configured.
500 Typically, you would define a set of default actions that apply
501 to all URLs, then add exceptions to these defaults where needed.
505 Actions can be defined on a per site basis, or for groups of sites. Actions
506 can also be grouped together and then applied to one or more sites. There
507 are many possible actions that might apply to any given site. As an example,
508 if we are blocking cookies as one of our default
509 <application>actions</application>, but need to accept cookies from a given
510 site, we would define this in our <quote>actions</quote> file.
514 No longer appropriate 04/28/02 hal.
517 <application>Privoxy</application> comes with several default
518 <application>actions</application> files, with varying degrees
519 of filtering and blocking, as starting points for your own
520 configuration (see below).
525 <sect2 renderas="sect3" id="actionss">
526 <title>The <quote>actions</quote> concept confuses me. Please list
527 some of these <quote>actions</quote>.</title>
529 These are all explained in the
530 <ulink url="../user-manual/actions-file.html">user-manual</ulink>.
531 Please refer to that.
536 <sect2 renderas="sect3">
537 <title id="actconfig">How are actions files configured? What is the easiest
538 way to do this?</title>
541 The easiest way to do this, is to access <application>Privoxy</application>
542 with your web browser at <ulink url="http://p.p/">http://p.p/</ulink>,
544 "<ulink url="http://config.privoxy.org">View & change the current configuration</ulink>"
545 from the selection list. You can also do this by editing the appropriate
546 file with a text editor.
552 url="../user-manual/actions-file.html">user-manual</ulink> for a
553 detailed explanation of these and other configuration files, and their
554 various options and syntax.
559 <!-- ~~~~~ New section ~~~~~ -->
560 <sect2 renderas="sect3">
561 <title>There are several different <quote>actions</quote> files. What are
562 the differences?</title>
564 As of <application>Privoxy</application> v2.9.15, three actions files
565 are being included, to be used for
566 different purposes. These are
567 <filename>default.action</filename>, <filename>standard.action</filename>,
568 and <filename>user.action</filename>. Please see
569 <ulink url="../user-manual/actions-file.html">the User Manual</ulink>
570 for an explanation of each.
574 Earlier versions included three different versions
575 <filename>default.action</filename> files. The new scheme allows for
576 greater flexibility of local configuration, and for browser based
583 FIXME: Commenting these out until we have some data there. HB 03/17/02.
585 <sect2 renderas="sect3" id="yahoo"><title>How can I make my Yahoo account work?</title>
591 <sect2 renderas="sect3" id="hotmail"> <title>How can I make my Hotmail account work?</title>
597 <sect2 renderas="sect3" id="gmx"> <title>How can I make my GMX account work?</title>
605 <sect2 renderas="sect3" id="configfiles"> <title>What are the differences between
606 intermediate.action, basic.action, etc.?</title>
608 Configuring <application>Privoxy</application> is not easy. To help you get
609 started, we provide you with three different default configurations. The
610 following table shows you, which features are enabled in each configuration.
613 <table frame=all><title>Default Configurations</title>
614 <tgroup cols=5 align=left colsep=1 rowsep=1>
622 <entry>Feature</entry>
623 <entry>default.action</entry>
624 <entry>basic.action</entry>
625 <entry>intermediate.action</entry>
626 <entry>advanced.action</entry>
632 <!-- <entry>f1</entry> -->
633 <!-- <entry>f2</entry> -->
634 <!-- <entry>f3</entry> -->
635 <!-- <entry>f4</entry> -->
636 <!-- <entry>f5</entry> -->
643 <entry>ad-filtering</entry>
651 <entry>blank image</entry>
659 <entry>de-animate GIFs</entry>
667 <entry>referer forging</entry>
675 <entry>jon's +no-cookies-keep (i.e. session cookies only)</entry>
683 <entry>no-popup windows</entry>
691 <entry>fast redirects</entry>
699 <entry>hide-referrer</entry>
707 <entry>hide-useragent</entry>
715 <entry>content-modification</entry>
723 <entry>feature-x</entry>
731 <entry>feature-y</entry>
739 <entry>feature-z</entry>
754 <sect2 renderas="sect3" id="browseconfig"> <title>Why can I change the configuration with a
755 browser? Does that not raise security issues?</title>
757 What I don't understand, is how I can browser edit the config file as a
758 regular user, while the whole <filename>/etc/privoxy</filename> hierarchy
759 belongs to the user <quote>privoxy</quote>, with only 644 permissions.
762 When you use the browser-based editor, <application>Privoxy</application>
763 itself is writing to the config files. Because
764 <application>Privoxy</application> is running as the user <quote>privoxy</quote>, it can
765 update the config files.
768 If you don't like this, setting <quote>enable-edit-actions 0</quote> in the
769 config file will disable the browser-based editor. If you're that paranoid,
770 you should also consider setting <quote>enable-remote-toggle 0</quote> to prevent
771 browser-based enabling/disabling of <application>Privoxy</application>.
774 Note that normally only local users can connect to
775 <application>Privoxy</application>, so this is not (normally) a security
781 <sect2 renderas="sect3">
782 <title id="filterfile">What is <quote>default.filter</quote>?</title>
784 The <quote>default.filter</quote> file is where <quote>filters</quote>
785 are defined, which are used to <quote>filter</quote> any
786 web page content. By <quote>filtering</quote> we mean it can modify, remove,
787 or change <emphasis>anything</emphasis> on the page, including HTML tags, and
788 JavaScript. Regular expressions are used to accomplish this, and operate
789 on a line by line basis. This is potentially a very powerful feature, but
790 requires some expertise.
794 If you are familiar with regular expressions, and HTML, you can look at
795 the provided <filename>default.filter</filename> with a text editor and see
796 some of things it can be used for.
800 Presently, there is no GUI editor option for this part of the configuration,
801 but you can disable/enable various sections of the included default
802 file with the <quote>View & change the current configuration</quote> from
808 <sect2 renderas="sect3">
809 <title id="lanconfig">How can I set up <application>Privoxy</application> to act as a proxy for my
812 By default, <application>Privoxy</application> only responds to requests
813 from localhost. To have it act as a server for a network, this needs to be
814 changed in the main config file where the <application>Privoxy</application>
815 configuration is located. In that file is a <quote>listen-address</quote>
816 option. It may be commented out with a <quote>#</quote> symbol. Make sure
817 it is uncommented, and assign it the address of the LAN gateway interface,
818 and port number to use:
823 listen-address 192.168.1.1:8118
828 Save the file, and restart <application>Privoxy</application>. Configure
829 all browsers on the network then to use this address and port number.
835 <sect2 renderas="sect3">
836 <title id="noseeum">Instead of ads, now I get a checkerboard pattern. I don't want to see anything.</title>
838 This is a configuration option for images that
839 <application>Privoxy</application> is stopping. You have the choice of a
840 checkerboard pattern, a transparent 1x1 GIF image (aka <quote>blank</quote>),
841 or a custom URL of your choice. Note that to fit this category, the URL must
842 match both the <ulink url="../user-manual/actions-file.html#HANDLE-AS-IMAGE"><quote>+handle-as-image</quote></ulink>
843 <emphasis>and</emphasis>
844 <ulink url="../user-manual/actions-file.html#BLOCK"><quote>+block</quote></ulink> actions.
847 If you want to see nothing, then change the
848 <ulink url="../user-manual/actions-file.html#SET-IMAGE-BLOCKER"><quote>+set-image-blocker</quote></ulink>
849 action to <quote>+image-blocker{blank}</quote>. This can be done from the
850 <quote>View & change the current configuration</quote> selection at <ulink
851 url="http://p.p/">http://p.p/</ulink>. Or by hand editing the appropriate
852 actions file. This will only effect what is defined as <quote>images</quote>
853 though. Also, some URLs that generate the bright red <quote>Blocked</quote>
854 banner, can be moved to the <quote>+set-image-blocker</quote> section for the
855 same reason, but there are some limits and risks to this (see below).
861 <sect2 renderas="sect3">
862 <title id="whyseeum">Why would anybody want to see a checkerboard pattern?</title>
864 This can be helpful for troubleshooting problems. It might also be good
865 for anyone new to <application>Privoxy</application> so that they can
866 see if their favorite pages are displaying correctly, and
867 <application>Privoxy</application> is not inadvertently removing something
873 <sect2 renderas="sect3">
874 <title id="blockedisugly">I see large red banners on some pages that say
875 <quote>Blocked</quote>. Why and how do I get rid of this?</title>
877 These are URLs that match something in one of
878 <application>Privoxy's</application> block actions
880 url="../user-manual/actions-file.html#BLOCK"><quote>+block</quote></ulink>).
881 It is meant to be a warning so that you know something has been blocked and
882 an easy way for you to see why. These are handled differently than what has
883 been defined explicitly as <quote>images</quote> (e.g. ads that are GIF image
884 files). Depending on the URL itself, it is sometimes hard for
885 <application>Privoxy</application> to really know whether there is indeed an
886 ad image there or not. And there are limitations as to what
887 <application>Privoxy</application> can do to <quote>fool</quote> the
892 For instance, if the ad is in a frame, then it is embedded in the separate
893 HTML page used for the frame. In this case, you cannot just substitute an
894 aribitrary image (like we would for a <quote>blank</quote> image), for an HTML
895 page. The browser is expecting an HTML page, and that is what it must have
896 for frames. Such situations can be a little trickier to deal with, and
897 <application>Privoxy</application> may show the <quote>Blocked</quote> page,
898 despite your best efforts.
902 If you want these to be treated as if they were images, so that they can be
903 made invisible, you can try moving the offending URL from the
904 <quote>+block</quote> section to the <quote>+imageblock</quote> section of
905 your actions file. Just be forewarned, if any URL is made
906 <quote>invisible</quote>, you may not have any inkling that something has
907 been removed from that page, or why. If this approach does not work, then you are
908 probably dealing with a frame (or <quote>ilayer</quote>), and the only thing
909 that can go there is an HTML page of some sort.
912 To deal with this situation, you could modify the
913 <quote><filename>block</filename></quote> HTML template that is used by
914 <application>Privoxy</application> to display this, and make it something
915 more to your liking. Currently, there is no configuration option for this.
916 You will have to modify, or create your own page, and use this to replace
917 <filename>templates/blocked</filename>, which is what
918 <application>Privoxy</application> uses to display the <quote>Blocked</quote>
922 Another way to deal with this is find why and where
923 <application>Privoxy</application> is blocking the frame, and
924 diable this. Then let the <quote>+set-image-blocker</quote> action
925 handle the ad that is embedded in the frame's HTML page.
930 <sect2 renderas="sect3" id="alliseeisred">
931 <title>I cannot see all of the <quote>Blocked</quote> page banner. Help.</title>
933 There is not enough available space to fit the entire Blocked page. Try right
934 clicking on the visible portion, and select <quote>Show Frame</quote>,
935 or equivalent. This will usually allow you to see the entire Privoxy
936 <quote>Blocked</quote> page, and from there you can see just what is being
940 As of Privoxy 2.9.14, the Blocked banner page is re-sizeable, and tries
941 to adjust to the allotted space. There may be occassions where there
942 just isn't enough room to display much of anything useful though.
947 <sect2 renderas="sect3" id="srvany">
948 <title>Can <application>Privoxy</application> run as a service
951 Yes, it can run as a system service using <command>srvany.exe</command>.
952 The only catch is that this will effectively disable the
953 <application>Privoxy</application> icon in the taskbar. You can have
954 one or the other, but not both at this time :(
957 There is a pending feature request for this functionality. See
959 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>,
960 for details, and a sample configuration.
966 <sect2 renderas="sect3" id="otherproxy">
967 <title>How can I make <application>Privoxy</application> work with other
968 proxies like <application>Squid</application>?</title>
970 This can be done. See the <ulink
971 url="../user-manual/config.html#FORWARDING">user manual</ulink>,
972 which describes how to do this.
976 <sect2 renderas="sect3" id="transparent">
977 <title>Can <application>Privoxy</application> run as a <quote>transparent
978 </quote> proxy?</title>
980 No, <application>Privoxy</application> currently does not have this ability,
981 though it is planned for a future release. Transparent proxies require
982 special handling of the request headers beyond what
983 <application>Privoxy</application> is now capable of.
987 Chaining <application>Privoxy</application> with another proxy that has
988 this ability should work though.
989 See the <ulink url="../user-manual/config.html#FORWARDING">user
990 manual</ulink>, which describes this, and also <ulink
991 url="http://www.transproxy.nlc.net.au/">http://www.transproxy.nlc.net.au/</ulink>.
998 <!-- ~ End section ~ -->
1001 <!-- ~~~~~ New section ~~~~~ -->
1003 <sect1 id="misc"><title>Miscellaneous</title>
1005 <sect2 renderas="sect3">
1006 <title id="slowsme">How much does <application>Privoxy</application> slow my browsing down? This
1007 has to add extra time to browsing.</title>
1009 It should not slow you down any in real terms, and may actually help
1010 speed things up since ads, banners and other junk are not being displayed.
1011 The actual processing time required by <application>Privoxy</application>
1012 itself for each page, is relatively small in the overall scheme of things,
1013 and happens very quickly. This is typically more than offset by time saved
1014 not downloading and rendering ad images.
1018 <quote>Filtering</quote> via the <filename>filterfile</filename>
1019 mechanism may cause a perceived slowdown, since the entire page is buffered
1020 before displaying. See below.
1026 <sect2 renderas="sect3" id="loadingtimes"><title>I noticed considerable
1027 delays in page requests compared to the old Junkbuster. What's wrong?</title>
1029 The entire page content must be loaded into memory in order for the filtering
1030 mechanism to work, and nothing is sent to the browser during this time. The
1031 loading time does not really change in real numbers, but the feeling is
1032 different, because most browsers are able to start rendering incomplete
1033 content, giving the user a feeling of "it works".
1036 To modify the content of a page (i.e. make frames resizeable again, etc.) and
1037 not just replace ads, <application>Privoxy</application> needs to download
1038 the entire page first, do its content magic and then send the page to the
1044 <sect2 renderas="sect3" id="configurl"><title>What is the "http://p.p/"?</title>
1046 Since <application>Privoxy</application> sits between your web browser and the Internet, it can be
1047 programmed to handle certain pages specially.
1051 With recent versions of <application>Privoxy</application> (version 2.9.x and
1052 greater), you can get some information about
1053 <application>Privoxy</application> and change some settings by going to
1054 <ulink url="http://p.p/">http://p.p/</ulink> or, equivalently, <ulink
1055 url="http://config.privoxy.org/">http://config.privoxy.org/</ulink> (Note
1056 that p.p is far easier to type but may not work in some configurations. With
1057 the name change to <application>Privoxy</application>, this is changed from
1058 the previous http://i.j.b/ and earlier 2.9.x versions).
1062 These pages are <emphasis>not</emphasis> forwarded to a server on the
1063 Internet - instead they are handled by a special web server which is built in to
1064 <application>Privoxy</application>.
1068 If you are not running <application>Privoxy</application>, then <ulink
1069 url="http://p.p/">http://p.p/</ulink> will fail, and <ulink
1070 url="http://config.privoxy.org/">http://config.privoxy.org/</ulink> will
1071 return a web page telling you you're not running
1072 <application>Privoxy</application>.
1076 If you have version 2.0.2, then the equivalent is
1077 http://example.com/show-proxy-args (but you get far less information, and
1078 you should really consider upgrading to &p-version;).
1083 FIXME: commented out until we have data. HB 03/18/02.
1085 <sect2 renderas="sect3" id="badfiledesc"><title>I get the message 'Bad File Descriptor', why?</title>
1093 <sect2 renderas="sect3" id="blocklist"><title>Do you still maintain the blocklists?</title>
1095 No, not by this name. The format of the blocklists has changed
1096 significantly in versions 2.9.x and later. This functionality
1097 is done by the <quote>actions</quote> file now. See next question ...
1101 <sect2 renderas="sect3" id="newads"><title>How can I submit new ads?</title>
1103 Please see the <link linkend="contact">Contact section</link>.
1107 This process does not work with earlier versions of <application>Privoxy</application>
1108 or <application>Junkbuster</application>.
1113 <sect2 renderas="sect3" id="ip"><title>How can I hide my IP address?</title>
1115 You cannot hide your IP address with <application>Privoxy</application> or any other software, since
1116 the server needs to know your IP address to send the answers back to you.
1119 Fortunately there are many publicly usable anonymous proxies out there, which
1120 solve the problem by providing a further level of indirection between you and
1121 the web server, shared by many people and thus letting your requests "drown"
1122 in white noise of unrelated requests as far as user tracking is concerned.
1125 Most of them will, however, log your IP address and make it available to the
1126 authorities in case you abuse that anonymity for criminal purposes. In fact
1127 you can't even rule out that some of them only exist to *collect* information
1128 on (those suspicious) people with a more than average preference for privacy.
1131 You can find a list of anonymous public proxies at <ulink
1132 url="http://www.multiproxy.org/anon_list.htm">multiproxy.org</ulink> and many
1133 more through Google.
1137 <!-- <sect2 renderas="sect3" id="image"><title>What is the imagefile (simage.ini, etc.) for?</title> -->
1139 <!-- Anytime <application>Privoxy</application> determines (with the help of the blocklist) that a URL -->
1140 <!-- contains an advertisement, it has to decide whether this advertisement is an -->
1141 <!-- image or not. <application>Privoxy</application> uses the imagefile for that purpose. -->
1145 <sect2 renderas="sect3">
1146 <title id="anonforsure">Can <application>Privoxy</application> guarantee I am anonymous?</title>
1148 No. Your chances of remaining anonymous are greatly improved, but unless you
1149 are an expert on Internet security it would be safest to assume that
1150 everything you do on the Web can be traced back to you.
1153 <application>Privoxy</application> can remove various information about you,
1154 and allows <emphasis>you</emphasis> more freedom to decide which sites
1155 you can trust, and what details you want to reveal. But it's still possible
1156 that web sites can find out who you are. Here's one way this can happen.
1159 A few browsers disclose the user's email address in certain situations, such
1160 as when transferring a file by FTP. <application>Privoxy</application>
1161 does not filter FTP. If you need this feature, or are concerned about the
1162 mail handler of your browser disclosing your email address, you might
1163 consider products such as <application>NSClean</application>.
1166 Browsers available only as binaries could use non-standard headers to give
1167 out any information they can have access to: see the manufacturer's license
1168 agreement. It's impossible to anticipate and prevent every breach of privacy
1169 that might occur. The professionally paranoid prefer browsers available as
1170 source code, because anticipating their behavior is easier. Trust the source,
1176 <sect2 renderas="sect3">
1177 <title id="sitebreak">Might some things break because header information is
1178 being altered?</title>
1181 Definitely. More and more sites use HTTP header content to decide what to
1182 display and how to display it. There is many ways that this can be handled,
1183 so having hard and fast rules, is tricky.
1187 <quote>USER AGENT</quote> in particular is often used in this way to identify
1188 the browser, and adjust content accordingly. Changing this now is not
1189 recommended, since so many sites do look for this. You may get undesirable
1190 results by changing this.
1194 For instance, different browsers use different encodings of Russian and Czech
1195 characters, certain web servers convert pages on-the-fly according to the
1196 User Agent header. Giving a <quote>User Agent</quote> with the wrong
1197 operating system or browser manufacturer causes some sites in these languages
1198 to be garbled; Surfers to Eastern European sites should change it to
1199 something closer. And then some page access counters work by looking at the
1200 <quote>REFERER</quote> header; they may fail or break if unavailable. The
1201 weather maps of Intellicast have been blocked by their server when no
1202 <quote>REFERER</quote> or cookie is provided, is another example. There are
1203 many, many other ways things can go wrong when trying to fool a web server.
1207 If you have problems with a site, you will have to adjust your configuration
1208 accordingly. Cookies are probably the most likely adjustment that may
1209 be required, but by no means the only one.
1215 <sect2 renderas="sect3">
1216 <title id="caching">Can <application>Privoxy</application> act as a <quote>caching</quote> proxy to
1217 speed up web browsing?</title>
1219 No, it does not have this ability at all. You want something like
1220 <ulink url="http://www.squid-cache.org/">Squid</ulink> for this. And, yes,
1221 before you ask, <application>Privoxy</application> can co-exist
1222 with other kinds of proxies like <application>Squid</application>.
1226 <sect2 renderas="sect3">
1227 <title id="firewall">What about as a firewall? Can <application>Privoxy</application> protect me?</title>
1229 Not in the way you mean, or in the way a true firewall can, or a proxy that
1230 has this specific capability. <application>Privoxy</application> can help
1231 protect your privacy, but not really protect you from intrusion attempts.
1236 <sect2 renderas="sect3">
1237 <title id="logo">The <application>Privoxy</application> logo that replaces ads is very blocky
1238 and ugly looking. Can't a better font be used?</title>
1241 This is not a font problem. The logo is an image that is created by
1242 <application>Privoxy</application> on the fly. So as to not waste
1243 memory, the image is rather small. The blockiness comes when the
1244 image is scaled to fill a largish area. There is not much to be done
1245 about this, other than to use one of the other
1246 <quote>imageblock</quote> directives: <emphasis>pattern</emphasis>,
1247 <emphasis>blank</emphasis>, or a URL of your choosing.
1250 Given the above problem, we have decided to remove the logo option entirely
1256 <sect2 renderas="sect3">
1257 <title id="wasted">I have large empty spaces now where ads used to be.
1260 It would be easy enough to just eliminate this space altogether, rather than
1261 fill it with blank space. But, this would create problems with many pages
1262 that use the overall size of the ad to help organize the page layout and
1263 position the various components of the page where they were intended to be.
1264 It is best left this way.
1269 <sect2 renderas="sect3">
1270 <title id="ssl">How can <application>Privoxy</application> filter Secure (HTTPS) URLs?</title>
1272 This is a limitation since HTTPS transactions are encrypted SSL sessions
1273 between your browser and the secure site, and are meant to be reliably
1274 <emphasis>secure</emphasis> and private. This means that all cookies and HTTP
1275 header information are also encrypted from the time they leave your browser,
1276 to the site, and vice versa. <application>Privoxy</application> does not
1277 try to unencrypt this information, so it just passes through as is.
1278 <application>Privoxy</application> can still catch images and ads that
1279 are embedded in the SSL stream though.
1285 <sect2 renderas="sect3">
1286 <title id="secure"><application>Privoxy</application> runs as a <quote>server</quote>. How
1287 secure is it? Do I need to take any special precautions?</title>
1289 There are no known exploits that might effect
1290 <application>Privoxy</application>. On Unix-like systems,
1291 <application>Privoxy</application> can run as a non-privileged
1292 user, which is how we recommend it be run. Also, by default
1293 <application>Privoxy</application> only listens to requests
1294 from <quote>localhost</quote>. The server aspect of
1295 <application>Privoxy</application> is not itself directly exposed to the
1296 Internet in this configuration. If you want to have
1297 <application>Privoxy</application> serve as a LAN proxy, this will have to
1298 be opened up to allow for LAN requests. In this case, we'd recommend
1299 you specify only the LAN gateway address, e.g. 192.168.1.1, in the main
1300 <application>Privoxy</application> config file. All LAN hosts can then use
1301 this as their proxy address in the browser proxy configuration. In this way,
1302 <application>Privoxy</application> will not listen on any external ports.
1303 Of course, a firewall is always good too. Better safe than sorry.
1308 <sect2 renderas="sect3" id="turnoff">
1309 <title>How can I temporarily disable <application>Privoxy</application>?</title>
1311 The easiest way is to access <application>Privoxy</application> with your
1312 browser by using the special URL: <ulink url="http://p.p/">http://p.p/</ulink>
1313 and select "Toggle Privoxy on or off" from that page.
1318 <sect2 renderas="sect3" id="seealso">
1319 <title>Where can I find more information about <application>Privoxy</application>
1320 and related issues?</title>
1321 <!-- Include seealso.sgml boilerplate: -->
1323 <!-- end boilerplate -->
1328 <ulink url="../user-manual/seealso.html">user-manual</ulink> for
1337 <!-- ~~~~~ New section ~~~~~ -->
1339 <sect1 id="trouble">
1340 <title>Troubleshooting</title>
1342 <sect2 renderas="sect3">
1343 <title id="refused">I just upgraded and am getting <quote>connection refused</quote>
1344 with every web page?</title>
1346 Either <application>Privoxy</application> is not running, or your
1347 browser is configured for a different port than what
1348 <application>Privoxy</application> is using.
1352 The old <application>Privoxy</application> (and also
1353 <application>Junkbuster</application>) used port 8000 by
1354 default. This has been changed to port 8118 now, due to a conflict
1355 with NAS (Network Audio Service), which uses port 8000. If you haven't,
1356 you need to change your browser to the new port number, or alternately
1357 change <application>Privoxy's</application> <quote>listen-address</quote>
1358 setting in the <filename>config</filename> file used to start
1359 <application>Privoxy</application>.
1364 <sect2 renderas="sect3">
1365 <title id="flushit">I just added a new rule, but the steenkin ad is
1366 still getting through. How?</title>
1368 If the ad had been displayed before you added its URL, it will probably be
1369 held in the browser's cache for some time, so it will be displayed without
1370 the need for any request to the server, and <application>Privoxy</application>
1371 will not be in the picture. The best thing to do is try flushing the browser's
1372 caches. And then try again.
1376 If this doesn't help, you probably have an error in the rule you
1377 applied. Try pasting the full URL of the offending ad into <ulink
1378 url="http://config.privoxy.org/show-url-info">http://config.privoxy.org/show-url-info</ulink>
1379 and see if any actions match your new rule.
1384 <sect2 renderas="sect3">
1385 <title id="badsite">One of my favorite sites does not work with <application>Privoxy</application>.
1386 What can I do?</title>
1389 First verify that it is indeed a <application>Privoxy</application> problem,
1390 by disabling <application>Privoxy</application> filtering and blocking.
1391 Go to <ulink url="http://p.p/">http://p.p/</ulink> and click on
1392 <quote>Toggle Privoxy On or Off</quote>, then disable it. Now try that
1393 page again. It's probably a good idea to flush the browser cache as well
1394 with <literal>Shift+Reload</literal> to flush caches.
1398 If still a problem, go to <quote>Show which actions apply to a URL and
1399 why</quote> from <ulink url="http://p.p/">http://p.p/</ulink> and paste
1400 the full URL of the page in question into the prompt. See which actions are
1401 being applied to the URL. Now, armed with this information, go to
1402 <quote>View & change the current configuration</quote>. Here you should see various sections that have
1403 various <application>Privoxy</application> features disabled for specific
1404 sites. Most disabled <quote>actions</quote> will have a <quote>-</quote> (minus
1405 sign) in front of them. Some aliases are used just to disable other actions,
1406 e.g. <quote>shop</quote> and <quote>fragile</quote>, and won't necessarily
1407 use a <quote>+</quote> or <quote>-</quote> sign. Add your problem page
1408 URL to one of these sections that looks like it is disabling the feature that
1409 is causing the problem. Rember to flush your browser's caches when making
1410 such changes! As a last resort, try <quote>fragile</quote> which
1411 disables most actions. Now re-try the page. There might be some trial and
1412 error involved. This is discussed in more detail in the <ulink
1413 url="../user-manual/appendix.html#ACTIONSANAT">user-manual appendix</ulink>.
1418 Alternately, if you are comfortable with a text editor, you can accomplish
1419 the same thing by editing the appropriate <quote>actions</quote> file.
1429 <!-- ~~~~~ New section ~~~~~ -->
1431 FIXME: Commented out until we have something to put here. HB 03/18/02.
1432 <sect1 id="knownissues"><title>Known Issues</title>
1439 <!-- ~~~~~ New section ~~~~~ -->
1440 <sect1 id="contact"><title>Contacting the developers, Bug Reporting and Feature Requests</title>
1441 <!-- Include contacting.sgml -->
1443 <!-- end contacting -->
1446 <!-- ~~~~~ New section ~~~~~ -->
1447 <sect1 id="copyright"><title>Privoxy Copyright, License and History</title>
1449 <!-- Include copyright.sgml -->
1454 Portions of this document are <quote>borrowed</quote> from the original
1455 <application>Junkbuster</application> (tm) FAQ, and modified as
1456 appropriate for <application>Privoxy</application>.
1459 <!-- ~~~~~ New section ~~~~~ -->
1460 <sect2><title>License</title>
1461 <!-- Include copyright.sgml: -->
1463 <!-- end copyright -->
1465 <!-- ~ End section ~ -->
1467 <!-- ~~~~~ New section ~~~~~ -->
1468 <sect2><title>History</title>
1469 <!-- Include history.sgml -->
1475 <!-- ~ End section ~ -->
1478 <!-- ~~~~~ New section ~~~~~ -->
1480 <sect1 id="seealso"><title>See also</title>
1482 <!-- Include seealso.sgml -->
1493 Tue 09/11/01 06:38:14 PM EST: Test SGML doc by Hal Burgiss.
1495 Last modified: Mon Sep 10 19:22:09 CEST 2001
1497 This program is free software; you can redistribute it
1498 and/or modify it under the terms of the GNU General
1499 Public License as published by the Free Software
1500 Foundation; either version 2 of the License, or (at
1501 your option) any later version.
1503 This program is distributed in the hope that it will
1504 be useful, but WITHOUT ANY WARRANTY; without even the
1505 implied warranty of MERCHANTABILITY or FITNESS FOR A
1506 PARTICULAR PURPOSE. See the GNU General Public
1507 License for more details.
1509 The GNU General Public License should be included with
1510 this file. If not, you can view it at
1511 http://www.gnu.org/copyleft/gpl.html
1512 or write to the Free Software Foundation, Inc., 59
1513 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
1516 Revision 1.58 2002/05/10 01:48:20 hal9
1517 This is mostly proposed copyright/licensing additions and changes. Docs
1518 are still GPL, but licensing and copyright are more visible. Also, copyright
1519 changed in doc header comments (eliminate references to JB except FAQ).
1521 Revision 1.57 2002/05/05 20:26:02 hal9
1522 Sorting out license vs copyright in these docs.
1524 Revision 1.56 2002/05/04 08:44:44 swa
1527 Revision 1.55 2002/05/04 00:41:56 hal9
1528 -Remove TOC/first page kludge in favor of proper handling via dsl file.
1530 Revision 1.54 2002/05/03 05:06:44 hal9
1531 Add brief Q/A on transparent proxies.
1533 Revision 1.53 2002/05/03 01:34:52 hal9
1534 Fix section numbering for new sections (due to TOC kludge).
1536 Revision 1.52 2002/04/29 03:08:43 hal9
1537 -Added new Q/A on new actions file set up (pointer to u-m)
1538 -Fixed a few broken links and converted old actions as a result of
1541 Revision 1.51 2002/04/26 17:24:31 swa
1542 bookmarks cleaned, changed structure of user manual, screen and programlisting cleanups, and numerous other changes that I forgot
1544 Revision 1.50 2002/04/26 05:25:23 hal9
1545 Mass commit to catch a few scattered fixes.
1547 Revision 1.49 2002/04/12 10:10:18 swa
1550 Revision 1.48 2002/04/10 18:45:15 swa
1553 Revision 1.47 2002/04/10 04:05:32 hal9
1556 Revision 1.45 2002/04/08 22:59:26 hal9
1557 Version update. Spell chkconfig correctly :)
1559 Revision 1.44 2002/04/07 21:24:29 hal9
1560 Touch up on name change.
1562 Revision 1.43 2002/04/04 21:59:53 hal9
1563 Added NT/W2K service/icon situation.
1565 Revision 1.42 2002/04/04 18:46:47 swa
1566 consistent look. reuse of copyright, history et. al.
1568 Revision 1.41 2002/04/04 06:48:37 hal9
1569 Structural changes to allow for conditional inclusion/exclusion of content
1570 based on entity toggles, e.g. 'entity % p-not-stable "INCLUDE"'. And
1571 definition of internal entities, e.g. 'entity p-version "2.9.13"' that will
1572 eventually be set by Makefile.
1573 More boilerplate text for use across multiple docs.
1575 Revision 1.40 2002/04/03 04:22:03 hal9
1576 Fixed several typos.
1578 Revision 1.39 2002/04/03 03:53:03 hal9
1579 Revert some changes, and then make some news, to layout, and appearance.
1581 Revision 1.38 2002/04/02 03:49:10 hal9
1582 Major changes to doc structure and layout. Sections are not automatically
1583 numbered now. TOC is on page by itself.
1585 Revision 1.37 2002/04/01 16:24:07 hal9
1586 -Rework of supported Q/A.
1587 -Set up entities to include boilerplate text.
1589 Revision 1.36 2002/03/31 23:18:47 hal9
1590 More on dealing with BLOCKED.
1592 Revision 1.35 2002/03/30 04:14:19 hal9
1593 Fix privoxy.org/config links.
1595 Revision 1.34 2002/03/29 04:35:56 hal9
1598 Revision 1.33 2002/03/29 01:31:48 hal9
1599 Several new Q/A's and other touch ups.
1601 Revision 1.32 2002/03/27 00:57:03 hal9
1602 Touch ups for name change.
1604 Revision 1.31 2002/03/26 22:29:55 swa
1605 we have a new homepage!
1607 Revision 1.30 2002/03/25 16:39:22 hal9
1608 A few new sections. Made all links relative to user-manual.
1610 Revision 1.29 2002/03/25 05:23:57 hal9
1611 Moved section, and touch ups.
1613 Revision 1.28 2002/03/25 04:27:33 hal9
1614 New section related to name change.
1616 Revision 1.25 2002/03/24 16:08:08 swa
1617 we are too lazy to make a block-built
1618 privoxy logo. hence removed the option.
1620 Revision 1.24 2002/03/24 15:46:20 swa
1621 name change related issue.
1623 Revision 1.23 2002/03/24 12:33:01 swa
1626 Revision 1.22 2002/03/24 11:51:00 swa
1627 name change. changed filenames.
1629 Revision 1.21 2002/03/24 11:01:06 swa
1632 Revision 1.20 2002/03/23 15:13:11 swa
1633 renamed every reference to the old name with foobar.
1634 fixed "application foobar application" tag, fixed
1635 "the foobar" with "foobar". left junkbustser in cvs
1636 comments and remarks to history untouched.
1638 Revision 1.19 2002/03/21 17:01:54 hal9
1641 Revision 1.18 2002/03/18 16:40:31 hal9
1644 Revision 1.17 2002/03/18 03:53:53 hal9
1647 Revision 1.16 2002/03/17 21:32:56 hal9
1648 A few more additions.
1650 Revision 1.15 2002/03/17 07:25:59 hal9
1651 Correcting some of my typos, and some additions.
1653 Revision 1.14 2002/03/17 02:39:13 hal9
1654 A little more added ...
1656 Revision 1.13 2002/03/17 00:22:20 hal9
1657 Adding new stuff, and trying to incorporate stuff from old faq.
1659 Revision 1.12 2002/03/11 20:13:21 swa
1662 Revision 1.11 2002/03/11 18:42:27 swa
1665 Revision 1.10 2002/03/11 13:13:27 swa
1666 correct feedback channels
1668 Revision 1.9 2002/03/10 23:34:04 swa
1669 more info on not hiding ip address
1671 Revision 1.8 2002/03/09 15:55:48 swa
1672 added default config section
1674 Revision 1.7 2002/03/07 18:16:55 swa
1677 Revision 1.6 2002/03/07 13:16:31 oes
1678 Committing changes by Stefan
1680 Revision 1.5 2002/03/02 15:50:04 swa
1681 2.9.11 version. more input for docs.
1683 Revision 1.4 2002/02/24 14:34:24 jongfoster
1684 Formatting changes. Now changing the doctype to DocBook XML 4.1
1685 will work - no other changes are needed.
1687 Revision 1.3 2001/09/23 10:13:48 swa
1688 upload process established. run make webserver and
1689 the documentation is moved to the webserver. documents
1690 are now linked correctly.
1692 Revision 1.2 2001/09/13 15:20:17 swa
1693 merged standards into developer manual
1695 Revision 1.1 2001/09/12 15:36:41 swa
1696 source files for junkbuster documentation
1698 Revision 1.3 2001/09/10 17:43:59 swa
1699 first proposal of a structure.
1701 Revision 1.2 2001/06/13 14:28:31 swa
1702 docs should have an author.
1704 Revision 1.1 2001/06/13 14:20:37 swa
1705 first import of project's documentation for the webserver.