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 p-version "2.9.14">
11 <!entity p-status "beta">
12 <!entity % p-not-stable "INCLUDE">
13 <!entity % p-stable "IGNORE">
14 <!entity % p-text "IGNORE"> <!-- define we are not a text only doc -->
15 <!entity % p-doc "INCLUDE"> <!-- and we are a formal doc -->
16 <!entity % p-supp-userman "INCLUDE"> <!-- Include all from supported.sgml -->
19 File : $Source: /cvsroot/ijbswa/current/doc/source/faq.sgml,v $
22 This file belongs into
23 ijbswa.sourceforge.net:/home/groups/i/ij/ijbswa/htdocs/
25 $Id: faq.sgml,v 1.54 2002/05/03 05:06:44 hal9 Exp $
27 Written by and Copyright (C) 2001 the SourceForge
28 Privoxy team. http://www.privoxy.org/
30 Based on the Internet Junkbuster originally written
31 by and Copyright (C) 1997 Anonymous Coders and
32 Junkbusters Corporation. http://www.junkbusters.com
34 <Qandaset defaultlabel='qanda'>
49 ========================================================================
50 NOTE: Please read developer-manual/documentation.html before touching
51 anything in this, or other Privoxy documentation. You have been warned!
52 Failure to abide by this rule will result in the revocation of your license
53 to live a peaceful existence!
54 ========================================================================
60 <article id="index" class="faq">
62 <title>Privoxy Frequently Asked Questions</title>
64 <pubdate>$Id: faq.sgml,v 1.54 2002/05/03 05:06:44 hal9 Exp $</pubdate>
69 <orgname>By: Privoxy Developers</orgname>
78 This is here to keep vim syntax file from breaking :/
79 If I knew enough to fix it, I would.
80 PLEASE DO NOT REMOVE! HB: hal@foobox.net
85 This FAQ gives users and developers alike answers to frequently asked
86 questions about <ulink url="http://www.privoxy.org">Privoxy</ulink>
87 <![%p-stable;[ v.&p-version]]>.
90 <!-- Include privoxy.sgml boilerplate: -->
92 <!-- end boilerplate -->
95 You can find the latest version of the document at <ulink
96 url="http://www.privoxy.org/faq/">http://www.privoxy.org/faq/</ulink>.
97 Please see the Contact section if you want to contact the developers.
101 <!-- Feel free to send a note to the developers at <email>ijbswa-developers@lists.sourceforge.net</email>. -->
107 <!-- ~~~~~ New section ~~~~~ -->
109 <sect1 id="general"><title>General Information</title>
111 <sect2 renderas="sect3" id="newjb"><title>What is this new version of <application>Privoxy</application>?</title>
113 The original <application><trademark>Internet
114 Junkbuster</trademark></application> (tm) is a copyrighted product of <ulink
115 url="http://www.junkbusters.com">Junkbusters Corporation</ulink>.
116 Development of this effort stopped some time ago as of version 2.0.2. Stefan
117 Waldherr started the ijbswa project on <ulink
118 url="http://sourceforge.net/projects/ijbswa/">Sourceforge</ulink> to
119 rekindle development. Other developers subsequently joined with Stefan, and
120 have since added many new features, refinements and enhancements. The result
121 of this effort is <application>Privoxy</application>.
124 <application>Privoxy</application> has evolved from the
125 <application>Junkbuster 2.0.2</application> code base, and has advanced
126 significantly at this point.
129 Please see the <link linkend="copyright">History section</link> for more
130 information on the history of <application>Junkbuster</application> and
131 <application>Privoxy</application>.
137 <sect2 renderas="sect3">
138 <title id="whyprivoxy">Why <quote>Privoxy</quote>? Why a name change at all?</title>
140 <application>Privoxy</application> is the
141 <quote><emphasis>Privacy Enhancing Proxy</emphasis></quote>.
144 There are potential legal complications from the continued use of the
145 <application>Junkbuster</application> name, which is a registered trademark of
146 <ulink url="http://junkbusters.com">Junkbusters Corporation</ulink>.
147 And thus they <quote>own</quote> the rights to the name.
148 (There are, however, no objections from Junkbusters Corporation to the
149 <application>Privoxy</application> project itself, and they, in fact, still
150 share our ideals and goals.)
154 The developers also believed that there are so many changes from the original
155 code, that it was time to make a clean break from the past and make
156 a name in their own right<![%p-not-stable;[, especially now with the pending
157 release of version 3.0]]>.
162 <sect2 renderas="sect3" id="differs"><title>How does <application>Privoxy</application> differ
163 from the old <application>Junkbuster?</application></title>
165 <application>Privoxy</application> picks up where
166 <application>Junkbuster</application> left off. All the old features remain.
167 The new <application>Privoxy</application> still blocks ads and banners,
168 still manages cookies, and still helps protect your privacy. But, these are
169 all enhanced, and many new features have been added, all in the same vein.
172 The configuration has changed significantly as well. This is something that
173 users will notice right off the bat if you are upgrading from
174 <application>Junkbuster</application> 2.0.x. The <quote>blocklist</quote>
175 file does not exist any more. This is replaced by <quote>actions</quote>
176 files, such as <filename>default.actions</filename>. This is where most of
177 the per site configuration is now.
181 <sect2 renderas="sect3" id="features"><title>What are some of the new features?</title>
182 <!-- Include newfeatures.sgml: -->
188 <sect2 renderas="sect3" id="proxymoron"><title>What is a <quote>proxy</quote>? How does
189 <application>Privoxy</application> work? </title>
191 When you connect to a web site with <application>Privoxy</application>,
192 you are really connecting to your locally running version of
193 <application>Privoxy</application>. <application>Privoxy</application>
194 intercepts your requests for the web page, and relays that to the
195 <quote>real</quote> web site. The web site sends the HTTP data stream
196 back to <application>Privoxy</application>, where
197 <application>Privoxy</application> can work its magic before it
198 relays this data back to your web browser.
202 Since <application>Privoxy</application> sits between you and the
203 WWW, it is in a position to intercept and completely manage all web traffic and
204 HTTP content before it gets to your browser.
205 <application>Privoxy</application> uses various programming methods to do
206 this, all of which is under your control via the various configuration
211 There are many kinds of proxies. <application>Privoxy</application> best
212 fits the <quote>filtering proxy</quote> category.
218 <sect2 renderas="sect3">
219 <title id="knows">How does <application>Privoxy</application> know what is
220 an ad, and what is not?</title>
222 <application>Privoxy</application> processes all the raw content of every
223 web page. So it reads everything on each page. It then compares this to the
224 rules as set up in the configuration files, and looks for any matches to
225 these rules. <application>Privoxy</application> makes heavy use of
226 <quote>regular expressions</quote>. (If you are not familiar with regular
227 expressions, it is explained briefly in <ulink
228 url="../user-manual/appendix.html">the user manual</ulink>.) Regular
229 expressions facilitate matching of one text string against another, using
230 wildcards to build complex patterns. So <application>Privoxy</application>
231 will typically look for URLs and other content that match certain key words
232 and expressions as defined in the configuration files. For instance a URL
233 that contains <quote>/banners</quote>, has a high probability of containing
234 ad banners, and thus would be a prime candidate to have a matching rule.
237 So <application>Privoxy</application> will look for these kinds of obvious
238 looking culprits. And also, will use lists of known organizations that
239 specialize in ads. Again, using complex patterns to match as many potential
240 combinations as possible since there tend to be many, many variations used by
241 advertisers, and new ones are being introduced all the time.
245 <sect2 renderas="sect3">
246 <title id="mistakes">Can <application>Privoxy</application> make mistakes?
247 This does not sound very scientific.</title>
249 Actually, it's a black art ;-) And yes, it is always possible to have a broad rule
250 accidentally block something by mistake. There is a good chance you may run
251 into such a situation at some point. It is tricky writing rules to cover
252 every conceivable possibility, and not occasionally get false positives.
256 But this should not be a big concern since the
257 <application>Privoxy</application> configuration is very flexible, and
258 includes tools to help identify these types of situations so they can be
259 addressed as needed, allowing you to customize your installation.
260 (<link linkend="badsite">See the Troubleshooting section below</link>.)
266 <sect2 renderas="sect3" id="browsers2"><title>My browser does the same things as
267 <application>Privoxy</application>. Why should I use
268 <application>Privoxy</application> at all?</title>
270 Modern browsers do indeed have <emphasis>some</emphasis> of the same
271 functionality as <application>Privoxy</application>. Maybe this is
272 adequate for you. But <application>Privoxy</application> is much more
273 versatile and powerful, and can do a number of things that browsers just can't.
276 In addition, a proxy is good choice if you use multiple browsers, or
277 have a LAN with multiple computers. This way all the configuration
278 is in one place, and you don't have to maintain a similar configuration
279 for possibly many browsers.
286 <sect2 renderas="sect3" id="license"><title>Is there is a license or fee? What about a
287 warranty? Registration?</title>
289 <application>Privoxy</application> is licensed under the GNU General Public
290 License (GPL). It is free to use, copy, modify or distribute as you wish
291 under the terms of this license. Please see the Copyright section for more
292 information on the license and copyright.
296 There is no warranty of any kind, expressed, implied or otherwise. That is
297 something that would cost real money ;-) There is no registration either.
298 <application>Privoxy</application> really is <emphasis>free</emphasis>
305 <sect2 renderas="sect3" id="jointeam"><title>I would like to help you, what do I do?</title>
307 <sect3 renderas="sect4" id="jointeam-money"><title>Money Money Money</title>
309 We, of course, welcome donations and use the money for domain registering,
310 regular world-wide get-togethers (hahaha). Anyway, we'll soon describe the
311 process how to donate money to the team.
315 <sect3 renderas="sect4" id="jointeam-work"><title>You want to work with us?</title>
317 Well, helping the team is always a good idea. We welcome new developers,
318 RPM gurus or documentation makers. Simply get an account on sourceforge.net
319 and mail your id to the developer mailing list. Then read the
320 section Quickstart in the <ulink url="../developer-manual/quickstart.html">
321 Developer's Manual</ulink>.
324 Once we have added you to the team, you'll have write access to the CVS
325 repository, and together we'll find a suitable task for you.
334 <!-- ~~~~~ New section ~~~~~ -->
336 <sect1 id="installation"><title>Installation</title>
338 <sect2 renderas="sect3" id="whichbrowsers">
339 <title>Which browsers are supported by <application>Privoxy</application>?</title>
341 Any browser that can be configured to use a <quote>proxy</quote>, which
342 should be virtually all browsers. Direct browser support is not necessary
343 since <application>Privoxy</application> runs as a separate application and
344 just exchanges standard HTML data with your browser, just like a web server
349 <sect2 renderas="sect3" id="whichos">
350 <title>Which operating systems are supported?</title>
352 Include supported.sgml here:
357 <sect2 renderas="sect3" id="newinstall"><title>Can I install
358 <application>Privoxy</application> over <application>Junkbuster</application>?</title>
360 We recommend you uninstall <application>Junkbuster</application>
361 first to minimize conflicts and confusion. You may want to
362 save your old configuration files for future reference. The configuration
363 is substantially changed.
367 url="../user-manual/index.html">user-manual</ulink> for
368 platform specific installation instructions.
371 Note: Some installers may automatically uninstall
372 <application>Junkbuster</application>, if present!
377 <sect2 renderas="sect3">
378 <title id="firststep">I just installed <application>Privoxy</application>. Is there anything
379 special I have to do now?</title>
382 All browsers must be told to use <application>Privoxy</application>
383 as a proxy by specifying the correct proxy address and port number
384 in the appropriate configuration area for the browser. See below.
385 Also, you should flush your browser's memory and disk cache to get rid of any
393 <sect2 renderas="sect3" id="localhost"><title>What is the proxy address of <application>Privoxy</application>?</title>
395 If you set up the <application>Privoxy</application> to run on
396 the computer you browse from (rather than your ISP's server or some
397 networked computer on a LAN), the proxy will be on <quote>localhost</quote>
398 (which is the special name used by every computer on the Internet to refer
399 to itself) and the port will be 8118 (unless you have <application>Privoxy</application> to run on a different port with the
400 <emphasis>listen-address</emphasis> config option).
403 When configuring your browser's proxy settings you typically enter
404 the word <quote>localhost</quote> in the boxes next to <quote>HTTP</quote>
405 and <quote>Secure</quote> (HTTPS) and then the number <quote>8118</quote>
406 for <quote>port</quote>. This tells your browser to send all web
407 requests to <application>Privoxy</application> instead of directly to the
411 <application>Privoxy</application> can also be used to proxy for
412 a Local Area Network. In this case, your would enter either the IP
413 address of the LAN host where <application>Privoxy</application>
414 is running, or the equivalent hostname. Port assignment would be
418 <application>Privoxy</application> does not currently handle
419 protocols such as FTP, SMTP, IM, IRC, ICQ, or other Internet
424 <sect2 renderas="sect3">
425 <title id="nothing">I just installed <application>Privoxy</application>, and nothing is happening.
426 All the ads are there. What's wrong?</title>
429 Did you configure your browser to use <application>Privoxy</application>
430 as a proxy? It does not sound like it. See above. You might also try flushing
431 the browser's caches to force a full re-reading of pages. You can verify
432 that <application>Privoxy</application> is running, and your browser
433 is correctly configured by entering the special URL:
434 <ulink url="http://p.p/">http://p.p/</ulink>. This should give you
435 a banner that says <quote>This is Privoxy</quote> and
436 access to <application>Privoxy's</application> internal configuration.
437 If you see this, then you are good to go. If not, the browser or
438 <application>Privoxy</application> are not set up correctly.
447 <!-- ~~~~~ New section ~~~~~ -->
449 <sect1 id="configuration"><title>Configuration</title>
451 <sect2 renderas="sect3" id="newconfig"><title>Can I use my old config files?</title>
453 There are major changes to <application>Junkbuster</application>/
454 <application>Privoxy</application> configuration from version 2.0.x to
455 2.9.x and later. Most of the older files will not work at all. This is
456 especially true of <filename>blocklist</filename>. If this is the case, you
457 will need to re-enter your old data into the new configuration structure.
458 This is probably also a good recommendation even if upgrading from 2.9.x to
459 3.x since there were many minor changes along the way.
463 <sect2 renderas="sect3">
464 <title id="actionsfile">What is an <quote>actions</quote> file?</title>
467 <quote>actions</quote> files are where various actions that
468 <application>Privoxy</application> might take, are configured.
469 Typically, you would define a set of default actions that apply
470 to all URLs, then add exceptions to these defaults where needed.
474 Actions can be defined on a per site basis, or for groups of sites. Actions
475 can also be grouped together and then applied to one or more sites. There
476 are many possible actions that might apply to any given site. As an example,
477 if we are blocking cookies as one of our default
478 <application>actions</application>, but need to accept cookies from a given
479 site, we would define this in our <quote>actions</quote> file.
483 No longer appropriate 04/28/02 hal.
486 <application>Privoxy</application> comes with several default
487 <application>actions</application> files, with varying degrees
488 of filtering and blocking, as starting points for your own
489 configuration (see below).
494 <sect2 renderas="sect3" id="actionss">
495 <title>The <quote>actions</quote> concept confuses me. Please list
496 some of these <quote>actions</quote>.</title>
498 These are all explained in the
499 <ulink url="../user-manual/actions-file.html">user-manual</ulink>.
500 Please refer to that.
505 <sect2 renderas="sect3">
506 <title id="actconfig">How are actions files configured? What is the easiest
507 way to do this?</title>
510 The easiest way to do this, is to access <application>Privoxy</application>
511 with your web browser at <ulink url="http://p.p/">http://p.p/</ulink>,
513 "<ulink url="http://config.privoxy.org">View & change the current configuration</ulink>"
514 from the selection list. You can also do this by editing the appropriate
515 file with a text editor.
521 url="../user-manual/actions-file.html">user-manual</ulink> for a
522 detailed explanation of these and other configuration files, and their
523 various options and syntax.
528 <!-- ~~~~~ New section ~~~~~ -->
529 <sect2 renderas="sect3">
530 <title>There are several different <quote>actions</quote> files. What are
531 the differences?</title>
533 As of <application>Privoxy</application> v2.9.15, three actions files
534 are being included, to be used for
535 different purposes. These are
536 <filename>default.action</filename>, <filename>standard.action</filename>,
537 and <filename>user.action</filename>. Please see
538 <ulink url="../user-manual/actions-file.html">the User Manual</ulink>
539 for an explanation of each.
543 Earlier versions included three different versions
544 <filename>default.action</filename> files. The new scheme allows for
545 greater flexibility of local configuration, and for browser based
552 FIXME: Commenting these out until we have some data there. HB 03/17/02.
554 <sect2 renderas="sect3" id="yahoo"><title>How can I make my Yahoo account work?</title>
560 <sect2 renderas="sect3" id="hotmail"> <title>How can I make my Hotmail account work?</title>
566 <sect2 renderas="sect3" id="gmx"> <title>How can I make my GMX account work?</title>
574 <sect2 renderas="sect3" id="configfiles"> <title>What are the differences between
575 intermediate.action, basic.action, etc.?</title>
577 Configuring <application>Privoxy</application> is not easy. To help you get
578 started, we provide you with three different default configurations. The
579 following table shows you, which features are enabled in each configuration.
582 <table frame=all><title>Default Configurations</title>
583 <tgroup cols=5 align=left colsep=1 rowsep=1>
591 <entry>Feature</entry>
592 <entry>default.action</entry>
593 <entry>basic.action</entry>
594 <entry>intermediate.action</entry>
595 <entry>advanced.action</entry>
601 <!-- <entry>f1</entry> -->
602 <!-- <entry>f2</entry> -->
603 <!-- <entry>f3</entry> -->
604 <!-- <entry>f4</entry> -->
605 <!-- <entry>f5</entry> -->
612 <entry>ad-filtering</entry>
620 <entry>blank image</entry>
628 <entry>de-animate GIFs</entry>
636 <entry>referer forging</entry>
644 <entry>jon's +no-cookies-keep (i.e. session cookies only)</entry>
652 <entry>no-popup windows</entry>
660 <entry>fast redirects</entry>
668 <entry>hide-referrer</entry>
676 <entry>hide-useragent</entry>
684 <entry>content-modification</entry>
692 <entry>feature-x</entry>
700 <entry>feature-y</entry>
708 <entry>feature-z</entry>
723 <sect2 renderas="sect3" id="browseconfig"> <title>Why can I change the configuration with a
724 browser? Does that not raise security issues?</title>
726 What I don't understand, is how I can browser edit the config file as a
727 regular user, while the whole <filename>/etc/privoxy</filename> hierarchy
728 belongs to the user <quote>privoxy</quote>, with only 644 permissions.
731 When you use the browser-based editor, <application>Privoxy</application>
732 itself is writing to the config files. Because
733 <application>Privoxy</application> is running as the user <quote>privoxy</quote>, it can
734 update the config files.
737 If you don't like this, setting <quote>enable-edit-actions 0</quote> in the
738 config file will disable the browser-based editor. If you're that paranoid,
739 you should also consider setting <quote>enable-remote-toggle 0</quote> to prevent
740 browser-based enabling/disabling of <application>Privoxy</application>.
743 Note that normally only local users can connect to
744 <application>Privoxy</application>, so this is not (normally) a security
750 <sect2 renderas="sect3">
751 <title id="filterfile">What is <quote>default.filter</quote>?</title>
753 The <quote>default.filter</quote> file is where <quote>filters</quote>
754 are defined, which are used to <quote>filter</quote> any
755 web page content. By <quote>filtering</quote> we mean it can modify, remove,
756 or change <emphasis>anything</emphasis> on the page, including HTML tags, and
757 JavaScript. Regular expressions are used to accomplish this, and operate
758 on a line by line basis. This is potentially a very powerful feature, but
759 requires some expertise.
763 If you are familiar with regular expressions, and HTML, you can look at
764 the provided <filename>default.filter</filename> with a text editor and see
765 some of things it can be used for.
769 Presently, there is no GUI editor option for this part of the configuration,
770 but you can disable/enable various sections of the included default
771 file with the <quote>View & change the current configuration</quote> from
777 <sect2 renderas="sect3">
778 <title id="lanconfig">How can I set up <application>Privoxy</application> to act as a proxy for my
781 By default, <application>Privoxy</application> only responds to requests
782 from localhost. To have it act as a server for a network, this needs to be
783 changed in the main config file where the <application>Privoxy</application>
784 configuration is located. In that file is a <quote>listen-address</quote>
785 option. It may be commented out with a <quote>#</quote> symbol. Make sure
786 it is uncommented, and assign it the address of the LAN gateway interface,
787 and port number to use:
792 listen-address 192.168.1.1:8118
797 Save the file, and restart <application>Privoxy</application>. Configure
798 all browsers on the network then to use this address and port number.
804 <sect2 renderas="sect3">
805 <title id="noseeum">Instead of ads, now I get a checkerboard pattern. I don't want to see anything.</title>
807 This is a configuration option for images that
808 <application>Privoxy</application> is stopping. You have the choice of a
809 checkerboard pattern, a transparent 1x1 GIF image (aka <quote>blank</quote>),
810 or a custom URL of your choice. Note that to fit this category, the URL must
811 match both the <ulink url="../user-manual/actions-file.html#HANDLE-AS-IMAGE"><quote>+handle-as-image</quote></ulink>
812 <emphasis>and</emphasis>
813 <ulink url="../user-manual/actions-file.html#BLOCK"><quote>+block</quote></ulink> actions.
816 If you want to see nothing, then change the
817 <ulink url="../user-manual/actions-file.html#SET-IMAGE-BLOCKER"><quote>+set-image-blocker</quote></ulink>
818 action to <quote>+image-blocker{blank}</quote>. This can be done from the
819 <quote>View & change the current configuration</quote> selection at <ulink
820 url="http://p.p/">http://p.p/</ulink>. Or by hand editing the appropriate
821 actions file. This will only effect what is defined as <quote>images</quote>
822 though. Also, some URLs that generate the bright red <quote>Blocked</quote>
823 banner, can be moved to the <quote>+set-image-blocker</quote> section for the
824 same reason, but there are some limits and risks to this (see below).
830 <sect2 renderas="sect3">
831 <title id="whyseeum">Why would anybody want to see a checkerboard pattern?</title>
833 This can be helpful for troubleshooting problems. It might also be good
834 for anyone new to <application>Privoxy</application> so that they can
835 see if their favorite pages are displaying correctly, and
836 <application>Privoxy</application> is not inadvertently removing something
842 <sect2 renderas="sect3">
843 <title id="blockedisugly">I see large red banners on some pages that say
844 <quote>Blocked</quote>. Why and how do I get rid of this?</title>
846 These are URLs that match something in one of
847 <application>Privoxy's</application> block actions
849 url="../user-manual/actions-file.html#BLOCK"><quote>+block</quote></ulink>).
850 It is meant to be a warning so that you know something has been blocked and
851 an easy way for you to see why. These are handled differently than what has
852 been defined explicitly as <quote>images</quote> (e.g. ads that are GIF image
853 files). Depending on the URL itself, it is sometimes hard for
854 <application>Privoxy</application> to really know whether there is indeed an
855 ad image there or not. And there are limitations as to what
856 <application>Privoxy</application> can do to <quote>fool</quote> the
861 For instance, if the ad is in a frame, then it is embedded in the separate
862 HTML page used for the frame. In this case, you cannot just substitute an
863 aribitrary image (like we would for a <quote>blank</quote> image), for an HTML
864 page. The browser is expecting an HTML page, and that is what it must have
865 for frames. Such situations can be a little trickier to deal with, and
866 <application>Privoxy</application> may show the <quote>Blocked</quote> page,
867 despite your best efforts.
871 If you want these to be treated as if they were images, so that they can be
872 made invisible, you can try moving the offending URL from the
873 <quote>+block</quote> section to the <quote>+imageblock</quote> section of
874 your actions file. Just be forewarned, if any URL is made
875 <quote>invisible</quote>, you may not have any inkling that something has
876 been removed from that page, or why. If this approach does not work, then you are
877 probably dealing with a frame (or <quote>ilayer</quote>), and the only thing
878 that can go there is an HTML page of some sort.
881 To deal with this situation, you could modify the
882 <quote><filename>block</filename></quote> HTML template that is used by
883 <application>Privoxy</application> to display this, and make it something
884 more to your liking. Currently, there is no configuration option for this.
885 You will have to modify, or create your own page, and use this to replace
886 <filename>templates/blocked</filename>, which is what
887 <application>Privoxy</application> uses to display the <quote>Blocked</quote>
891 Another way to deal with this is find why and where
892 <application>Privoxy</application> is blocking the frame, and
893 diable this. Then let the <quote>+set-image-blocker</quote> action
894 handle the ad that is embedded in the frame's HTML page.
899 <sect2 renderas="sect3" id="alliseeisred">
900 <title>I cannot see all of the <quote>Blocked</quote> page banner. Help.</title>
902 There is not enough available space to fit the entire Blocked page. Try right
903 clicking on the visible portion, and select <quote>Show Frame</quote>,
904 or equivalent. This will usually allow you to see the entire Privoxy
905 <quote>Blocked</quote> page, and from there you can see just what is being
909 As of Privoxy 2.9.14, the Blocked banner page is re-sizeable, and tries
910 to adjust to the allotted space. There may be occassions where there
911 just isn't enough room to display much of anything useful though.
916 <sect2 renderas="sect3" id="srvany">
917 <title>Can <application>Privoxy</application> run as a service
920 Yes, it can run as a system service using <command>srvany.exe</command>.
921 The only catch is that this will effectively disable the
922 <application>Privoxy</application> icon in the taskbar. You can have
923 one or the other, but not both at this time :(
926 There is a pending feature request for this functionality. See
928 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>,
929 for details, and a sample configuration.
935 <sect2 renderas="sect3" id="otherproxy">
936 <title>How can I make <application>Privoxy</application> work with other
937 proxies like <application>Squid</application>?</title>
939 This can be done. See the <ulink
940 url="../user-manual/config.html#FORWARDING">user manual</ulink>,
941 which describes how to do this.
945 <sect2 renderas="sect3" id="transparent">
946 <title>Can <application>Privoxy</application> run as a <quote>transparent
947 </quote> proxy?</title>
949 No, <application>Privoxy</application> currently does not have this ability,
950 though it is planned for a future release. Transparent proxies require
951 special handling of the request headers beyond what
952 <application>Privoxy</application> is now capable of.
956 Chaining <application>Privoxy</application> with another proxy that has
957 this ability should work though.
958 See the <ulink url="../user-manual/config.html#FORWARDING">user
959 manual</ulink>, which describes this, and also <ulink
960 url="http://www.transproxy.nlc.net.au/">http://www.transproxy.nlc.net.au/</ulink>.
967 <!-- ~ End section ~ -->
970 <!-- ~~~~~ New section ~~~~~ -->
972 <sect1 id="misc"><title>Miscellaneous</title>
974 <sect2 renderas="sect3">
975 <title id="slowsme">How much does <application>Privoxy</application> slow my browsing down? This
976 has to add extra time to browsing.</title>
978 It should not slow you down any in real terms, and may actually help
979 speed things up since ads, banners and other junk are not being displayed.
980 The actual processing time required by <application>Privoxy</application>
981 itself for each page, is relatively small in the overall scheme of things,
982 and happens very quickly. This is typically more than offset by time saved
983 not downloading and rendering ad images.
987 <quote>Filtering</quote> via the <filename>filterfile</filename>
988 mechanism may cause a perceived slowdown, since the entire page is buffered
989 before displaying. See below.
995 <sect2 renderas="sect3" id="loadingtimes"><title>I noticed considerable
996 delays in page requests compared to the old Junkbuster. What's wrong?</title>
998 The entire page content must be loaded into memory in order for the filtering
999 mechanism to work, and nothing is sent to the browser during this time. The
1000 loading time does not really change in real numbers, but the feeling is
1001 different, because most browsers are able to start rendering incomplete
1002 content, giving the user a feeling of "it works".
1005 To modify the content of a page (i.e. make frames resizeable again, etc.) and
1006 not just replace ads, <application>Privoxy</application> needs to download
1007 the entire page first, do its content magic and then send the page to the
1013 <sect2 renderas="sect3" id="configurl"><title>What is the "http://p.p/"?</title>
1015 Since <application>Privoxy</application> sits between your web browser and the Internet, it can be
1016 programmed to handle certain pages specially.
1020 With recent versions of <application>Privoxy</application> (version 2.9.x and
1021 greater), you can get some information about
1022 <application>Privoxy</application> and change some settings by going to
1023 <ulink url="http://p.p/">http://p.p/</ulink> or, equivalently, <ulink
1024 url="http://config.privoxy.org/">http://config.privoxy.org/</ulink> (Note
1025 that p.p is far easier to type but may not work in some configurations. With
1026 the name change to <application>Privoxy</application>, this is changed from
1027 the previous http://i.j.b/ and earlier 2.9.x versions).
1031 These pages are <emphasis>not</emphasis> forwarded to a server on the
1032 Internet - instead they are handled by a special web server which is built in to
1033 <application>Privoxy</application>.
1037 If you are not running <application>Privoxy</application>, then <ulink
1038 url="http://p.p/">http://p.p/</ulink> will fail, and <ulink
1039 url="http://config.privoxy.org/">http://config.privoxy.org/</ulink> will
1040 return a web page telling you you're not running
1041 <application>Privoxy</application>.
1045 If you have version 2.0.2, then the equivalent is
1046 http://example.com/show-proxy-args (but you get far less information, and
1047 you should really consider upgrading to &p-version;).
1052 FIXME: commented out until we have data. HB 03/18/02.
1054 <sect2 renderas="sect3" id="badfiledesc"><title>I get the message 'Bad File Descriptor', why?</title>
1062 <sect2 renderas="sect3" id="blocklist"><title>Do you still maintain the blocklists?</title>
1064 No, not by this name. The format of the blocklists has changed
1065 significantly in versions 2.9.x and later. This functionality
1066 is done by the <quote>actions</quote> file now. See next question ...
1070 <sect2 renderas="sect3" id="newads"><title>How can I submit new ads?</title>
1072 Please see the <ulink url="contact.html">Contact section</ulink>.
1076 This process does not work with earlier versions of <application>Privoxy</application>
1077 or <application>Junkbuster</application>.
1082 <sect2 renderas="sect3" id="ip"><title>How can I hide my IP address?</title>
1084 You cannot hide your IP address with <application>Privoxy</application> or any other software, since
1085 the server needs to know your IP address to send the answers back to you.
1088 Fortunately there are many publicly usable anonymous proxies out there, which
1089 solve the problem by providing a further level of indirection between you and
1090 the web server, shared by many people and thus letting your requests "drown"
1091 in white noise of unrelated requests as far as user tracking is concerned.
1094 Most of them will, however, log your IP address and make it available to the
1095 authorities in case you abuse that anonymity for criminal purposes. In fact
1096 you can't even rule out that some of them only exist to *collect* information
1097 on (those suspicious) people with a more than average preference for privacy.
1100 You can find a list of anonymous public proxies at <ulink
1101 url="http://www.multiproxy.org/anon_list.htm">multiproxy.org</ulink> and many
1102 more through Google.
1106 <!-- <sect2 renderas="sect3" id="image"><title>What is the imagefile (simage.ini, etc.) for?</title> -->
1108 <!-- Anytime <application>Privoxy</application> determines (with the help of the blocklist) that a URL -->
1109 <!-- contains an advertisement, it has to decide whether this advertisement is an -->
1110 <!-- image or not. <application>Privoxy</application> uses the imagefile for that purpose. -->
1114 <sect2 renderas="sect3">
1115 <title id="anonforsure">Can <application>Privoxy</application> guarantee I am anonymous?</title>
1117 No. Your chances of remaining anonymous are greatly improved, but unless you
1118 are an expert on Internet security it would be safest to assume that
1119 everything you do on the Web can be traced back to you.
1122 <application>Privoxy</application> can remove various information about you,
1123 and allows <emphasis>you</emphasis> more freedom to decide which sites
1124 you can trust, and what details you want to reveal. But it's still possible
1125 that web sites can find out who you are. Here's one way this can happen.
1128 A few browsers disclose the user's email address in certain situations, such
1129 as when transferring a file by FTP. <application>Privoxy</application>
1130 does not filter FTP. If you need this feature, or are concerned about the
1131 mail handler of your browser disclosing your email address, you might
1132 consider products such as <application>NSClean</application>.
1135 Browsers available only as binaries could use non-standard headers to give
1136 out any information they can have access to: see the manufacturer's license
1137 agreement. It's impossible to anticipate and prevent every breach of privacy
1138 that might occur. The professionally paranoid prefer browsers available as
1139 source code, because anticipating their behavior is easier. Trust the source,
1145 <sect2 renderas="sect3">
1146 <title id="sitebreak">Might some things break because header information is
1147 being altered?</title>
1150 Definitely. More and more sites use HTTP header content to decide what to
1151 display and how to display it. There is many ways that this can be handled,
1152 so having hard and fast rules, is tricky.
1156 <quote>USER AGENT</quote> in particular is often used in this way to identify
1157 the browser, and adjust content accordingly. Changing this now is not
1158 recommended, since so many sites do look for this. You may get undesirable
1159 results by changing this.
1163 For instance, different browsers use different encodings of Russian and Czech
1164 characters, certain web servers convert pages on-the-fly according to the
1165 User Agent header. Giving a <quote>User Agent</quote> with the wrong
1166 operating system or browser manufacturer causes some sites in these languages
1167 to be garbled; Surfers to Eastern European sites should change it to
1168 something closer. And then some page access counters work by looking at the
1169 <quote>REFERER</quote> header; they may fail or break if unavailable. The
1170 weather maps of Intellicast have been blocked by their server when no
1171 <quote>REFERER</quote> or cookie is provided, is another example. There are
1172 many, many other ways things can go wrong when trying to fool a web server.
1176 If you have problems with a site, you will have to adjust your configuration
1177 accordingly. Cookies are probably the most likely adjustment that may
1178 be required, but by no means the only one.
1184 <sect2 renderas="sect3">
1185 <title id="caching">Can <application>Privoxy</application> act as a <quote>caching</quote> proxy to
1186 speed up web browsing?</title>
1188 No, it does not have this ability at all. You want something like
1189 <ulink url="http://www.squid-cache.org/">Squid</ulink> for this. And, yes,
1190 before you ask, <application>Privoxy</application> can co-exist
1191 with other kinds of proxies like <application>Squid</application>.
1195 <sect2 renderas="sect3">
1196 <title id="firewall">What about as a firewall? Can <application>Privoxy</application> protect me?</title>
1198 Not in the way you mean, or in the way a true firewall can, or a proxy that
1199 has this specific capability. <application>Privoxy</application> can help
1200 protect your privacy, but not really protect you from intrusion attempts.
1205 <sect2 renderas="sect3">
1206 <title id="logo">The <application>Privoxy</application> logo that replaces ads is very blocky
1207 and ugly looking. Can't a better font be used?</title>
1210 This is not a font problem. The logo is an image that is created by
1211 <application>Privoxy</application> on the fly. So as to not waste
1212 memory, the image is rather small. The blockiness comes when the
1213 image is scaled to fill a largish area. There is not much to be done
1214 about this, other than to use one of the other
1215 <quote>imageblock</quote> directives: <emphasis>pattern</emphasis>,
1216 <emphasis>blank</emphasis>, or a URL of your choosing.
1219 Given the above problem, we have decided to remove the logo option entirely
1225 <sect2 renderas="sect3">
1226 <title id="wasted">I have large empty spaces now where ads used to be.
1229 It would be easy enough to just eliminate this space altogether, rather than
1230 fill it with blank space. But, this would create problems with many pages
1231 that use the overall size of the ad to help organize the page layout and
1232 position the various components of the page where they were intended to be.
1233 It is best left this way.
1238 <sect2 renderas="sect3">
1239 <title id="ssl">How can <application>Privoxy</application> filter Secure (HTTPS) URLs?</title>
1241 This is a limitation since HTTPS transactions are encrypted SSL sessions
1242 between your browser and the secure site, and are meant to be reliably
1243 <emphasis>secure</emphasis> and private. This means that all cookies and HTTP
1244 header information are also encrypted from the time they leave your browser,
1245 to the site, and vice versa. <application>Privoxy</application> does not
1246 try to unencrypt this information, so it just passes through as is.
1247 <application>Privoxy</application> can still catch images and ads that
1248 are embedded in the SSL stream though.
1254 <sect2 renderas="sect3">
1255 <title id="secure"><application>Privoxy</application> runs as a <quote>server</quote>. How
1256 secure is it? Do I need to take any special precautions?</title>
1258 There are no known exploits that might effect
1259 <application>Privoxy</application>. On Unix-like systems,
1260 <application>Privoxy</application> can run as a non-privileged
1261 user, which is how we recommend it be run. Also, by default
1262 <application>Privoxy</application> only listens to requests
1263 from <quote>localhost</quote>. The server aspect of
1264 <application>Privoxy</application> is not itself directly exposed to the
1265 Internet in this configuration. If you want to have
1266 <application>Privoxy</application> serve as a LAN proxy, this will have to
1267 be opened up to allow for LAN requests. In this case, we'd recommend
1268 you specify only the LAN gateway address, e.g. 192.168.1.1, in the main
1269 <application>Privoxy</application> config file. All LAN hosts can then use
1270 this as their proxy address in the browser proxy configuration. In this way,
1271 <application>Privoxy</application> will not listen on any external ports.
1272 Of course, a firewall is always good too. Better safe than sorry.
1277 <sect2 renderas="sect3" id="turnoff">
1278 <title>How can I temporarily disable <application>Privoxy</application>?</title>
1280 The easiest way is to access <application>Privoxy</application> with your
1281 browser by using the special URL: <ulink url="http://p.p/">http://p.p/</ulink>
1282 and select "Toggle Privoxy on or off" from that page.
1287 <sect2 renderas="sect3" id="seealso">
1288 <title>Where can I find more information about <application>Privoxy</application>
1289 and related issues?</title>
1290 <!-- Include seealso.sgml boilerplate: -->
1292 <!-- end boilerplate -->
1297 <ulink url="../user-manual/seealso.html">user-manual</ulink> for
1306 <!-- ~~~~~ New section ~~~~~ -->
1308 <sect1 id="trouble">
1309 <title>Troubleshooting</title>
1311 <sect2 renderas="sect3">
1312 <title id="refused">I just upgraded and am getting <quote>connection refused</quote>
1313 with every web page?</title>
1315 Either <application>Privoxy</application> is not running, or your
1316 browser is configured for a different port than what
1317 <application>Privoxy</application> is using.
1321 The old <application>Privoxy</application> (and also
1322 <application>Junkbuster</application>) used port 8000 by
1323 default. This has been changed to port 8118 now, due to a conflict
1324 with NAS (Network Audio Service), which uses port 8000. If you haven't,
1325 you need to change your browser to the new port number, or alternately
1326 change <application>Privoxy's</application> <quote>listen-address</quote>
1327 setting in the <filename>config</filename> file used to start
1328 <application>Privoxy</application>.
1333 <sect2 renderas="sect3">
1334 <title id="flushit">I just added a new rule, but the steenkin ad is
1335 still getting through. How?</title>
1337 If the ad had been displayed before you added its URL, it will probably be
1338 held in the browser's cache for some time, so it will be displayed without
1339 the need for any request to the server, and <application>Privoxy</application>
1340 will not be in the picture. The best thing to do is try flushing the browser's
1341 caches. And then try again.
1345 If this doesn't help, you probably have an error in the rule you
1346 applied. Try pasting the full URL of the offending ad into <ulink
1347 url="http://config.privoxy.org/show-url-info">http://config.privoxy.org/show-url-info</ulink>
1348 and see if any actions match your new rule.
1353 <sect2 renderas="sect3">
1354 <title id="badsite">One of my favorite sites does not work with <application>Privoxy</application>.
1355 What can I do?</title>
1358 First verify that it is indeed a <application>Privoxy</application> problem,
1359 by disabling <application>Privoxy</application> filtering and blocking.
1360 Go to <ulink url="http://p.p/">http://p.p/</ulink> and click on
1361 <quote>Toggle Privoxy On or Off</quote>, then disable it. Now try that
1362 page again. It's probably a good idea to flush the browser cache as well
1363 with <literal>Shift+Reload</literal> to flush caches.
1367 If still a problem, go to <quote>Show which actions apply to a URL and
1368 why</quote> from <ulink url="http://p.p/">http://p.p/</ulink> and paste
1369 the full URL of the page in question into the prompt. See which actions are
1370 being applied to the URL. Now, armed with this information, go to
1371 <quote>View & change the current configuration</quote>. Here you should see various sections that have
1372 various <application>Privoxy</application> features disabled for specific
1373 sites. Most disabled <quote>actions</quote> will have a <quote>-</quote> (minus
1374 sign) in front of them. Some aliases are used just to disable other actions,
1375 e.g. <quote>shop</quote> and <quote>fragile</quote>, and won't necessarily
1376 use a <quote>+</quote> or <quote>-</quote> sign. Add your problem page
1377 URL to one of these sections that looks like it is disabling the feature that
1378 is causing the problem. Rember to flush your browser's caches when making
1379 such changes! As a last resort, try <quote>fragile</quote> which
1380 disables most actions. Now re-try the page. There might be some trial and
1381 error involved. This is discussed in more detail in the <ulink
1382 url="../user-manual/appendix.html#ACTIONSANAT">user-manual appendix</ulink>.
1387 Alternately, if you are comfortable with a text editor, you can accomplish
1388 the same thing by editing the appropriate <quote>actions</quote> file.
1398 <!-- ~~~~~ New section ~~~~~ -->
1400 FIXME: Commented out until we have something to put here. HB 03/18/02.
1401 <sect1 id="knownissues"><title>Known Issues</title>
1408 <!-- ~~~~~ New section ~~~~~ -->
1409 <sect1 id="contact"><title>Contacting the developers, Bug Reporting and Feature Requests</title>
1410 <!-- Include contacting.sgml -->
1412 <!-- end contacting -->
1415 <!-- ~~~~~ New section ~~~~~ -->
1416 <sect1 id="copyright"><title>Copyright and History</title>
1418 <sect2><title>Copyright</title>
1419 <!-- Include copyright.sgml -->
1424 <sect2><title>History</title>
1425 <!-- Include history.sgml -->
1432 <!-- ~~~~~ New section ~~~~~ -->
1434 <sect1 id="seealso"><title>See also</title>
1436 <!-- Include seealso.sgml -->
1447 Tue 09/11/01 06:38:14 PM EST: Test SGML doc by Hal Burgiss.
1449 Last modified: Mon Sep 10 19:22:09 CEST 2001
1451 This program is free software; you can redistribute it
1452 and/or modify it under the terms of the GNU General
1453 Public License as published by the Free Software
1454 Foundation; either version 2 of the License, or (at
1455 your option) any later version.
1457 This program is distributed in the hope that it will
1458 be useful, but WITHOUT ANY WARRANTY; without even the
1459 implied warranty of MERCHANTABILITY or FITNESS FOR A
1460 PARTICULAR PURPOSE. See the GNU General Public
1461 License for more details.
1463 The GNU General Public License should be included with
1464 this file. If not, you can view it at
1465 http://www.gnu.org/copyleft/gpl.html
1466 or write to the Free Software Foundation, Inc., 59
1467 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
1470 Revision 1.54 2002/05/03 05:06:44 hal9
1471 Add brief Q/A on transparent proxies.
1473 Revision 1.53 2002/05/03 01:34:52 hal9
1474 Fix section numbering for new sections (due to TOC kludge).
1476 Revision 1.52 2002/04/29 03:08:43 hal9
1477 -Added new Q/A on new actions file set up (pointer to u-m)
1478 -Fixed a few broken links and converted old actions as a result of
1481 Revision 1.51 2002/04/26 17:24:31 swa
1482 bookmarks cleaned, changed structure of user manual, screen and programlisting cleanups, and numerous other changes that I forgot
1484 Revision 1.50 2002/04/26 05:25:23 hal9
1485 Mass commit to catch a few scattered fixes.
1487 Revision 1.49 2002/04/12 10:10:18 swa
1490 Revision 1.48 2002/04/10 18:45:15 swa
1493 Revision 1.47 2002/04/10 04:05:32 hal9
1496 Revision 1.45 2002/04/08 22:59:26 hal9
1497 Version update. Spell chkconfig correctly :)
1499 Revision 1.44 2002/04/07 21:24:29 hal9
1500 Touch up on name change.
1502 Revision 1.43 2002/04/04 21:59:53 hal9
1503 Added NT/W2K service/icon situation.
1505 Revision 1.42 2002/04/04 18:46:47 swa
1506 consistent look. reuse of copyright, history et. al.
1508 Revision 1.41 2002/04/04 06:48:37 hal9
1509 Structural changes to allow for conditional inclusion/exclusion of content
1510 based on entity toggles, e.g. 'entity % p-not-stable "INCLUDE"'. And
1511 definition of internal entities, e.g. 'entity p-version "2.9.13"' that will
1512 eventually be set by Makefile.
1513 More boilerplate text for use across multiple docs.
1515 Revision 1.40 2002/04/03 04:22:03 hal9
1516 Fixed several typos.
1518 Revision 1.39 2002/04/03 03:53:03 hal9
1519 Revert some changes, and then make some news, to layout, and appearance.
1521 Revision 1.38 2002/04/02 03:49:10 hal9
1522 Major changes to doc structure and layout. Sections are not automatically
1523 numbered now. TOC is on page by itself.
1525 Revision 1.37 2002/04/01 16:24:07 hal9
1526 -Rework of supported Q/A.
1527 -Set up entities to include boilerplate text.
1529 Revision 1.36 2002/03/31 23:18:47 hal9
1530 More on dealing with BLOCKED.
1532 Revision 1.35 2002/03/30 04:14:19 hal9
1533 Fix privoxy.org/config links.
1535 Revision 1.34 2002/03/29 04:35:56 hal9
1538 Revision 1.33 2002/03/29 01:31:48 hal9
1539 Several new Q/A's and other touch ups.
1541 Revision 1.32 2002/03/27 00:57:03 hal9
1542 Touch ups for name change.
1544 Revision 1.31 2002/03/26 22:29:55 swa
1545 we have a new homepage!
1547 Revision 1.30 2002/03/25 16:39:22 hal9
1548 A few new sections. Made all links relative to user-manual.
1550 Revision 1.29 2002/03/25 05:23:57 hal9
1551 Moved section, and touch ups.
1553 Revision 1.28 2002/03/25 04:27:33 hal9
1554 New section related to name change.
1556 Revision 1.25 2002/03/24 16:08:08 swa
1557 we are too lazy to make a block-built
1558 privoxy logo. hence removed the option.
1560 Revision 1.24 2002/03/24 15:46:20 swa
1561 name change related issue.
1563 Revision 1.23 2002/03/24 12:33:01 swa
1566 Revision 1.22 2002/03/24 11:51:00 swa
1567 name change. changed filenames.
1569 Revision 1.21 2002/03/24 11:01:06 swa
1572 Revision 1.20 2002/03/23 15:13:11 swa
1573 renamed every reference to the old name with foobar.
1574 fixed "application foobar application" tag, fixed
1575 "the foobar" with "foobar". left junkbustser in cvs
1576 comments and remarks to history untouched.
1578 Revision 1.19 2002/03/21 17:01:54 hal9
1581 Revision 1.18 2002/03/18 16:40:31 hal9
1584 Revision 1.17 2002/03/18 03:53:53 hal9
1587 Revision 1.16 2002/03/17 21:32:56 hal9
1588 A few more additions.
1590 Revision 1.15 2002/03/17 07:25:59 hal9
1591 Correcting some of my typos, and some additions.
1593 Revision 1.14 2002/03/17 02:39:13 hal9
1594 A little more added ...
1596 Revision 1.13 2002/03/17 00:22:20 hal9
1597 Adding new stuff, and trying to incorporate stuff from old faq.
1599 Revision 1.12 2002/03/11 20:13:21 swa
1602 Revision 1.11 2002/03/11 18:42:27 swa
1605 Revision 1.10 2002/03/11 13:13:27 swa
1606 correct feedback channels
1608 Revision 1.9 2002/03/10 23:34:04 swa
1609 more info on not hiding ip address
1611 Revision 1.8 2002/03/09 15:55:48 swa
1612 added default config section
1614 Revision 1.7 2002/03/07 18:16:55 swa
1617 Revision 1.6 2002/03/07 13:16:31 oes
1618 Committing changes by Stefan
1620 Revision 1.5 2002/03/02 15:50:04 swa
1621 2.9.11 version. more input for docs.
1623 Revision 1.4 2002/02/24 14:34:24 jongfoster
1624 Formatting changes. Now changing the doctype to DocBook XML 4.1
1625 will work - no other changes are needed.
1627 Revision 1.3 2001/09/23 10:13:48 swa
1628 upload process established. run make webserver and
1629 the documentation is moved to the webserver. documents
1630 are now linked correctly.
1632 Revision 1.2 2001/09/13 15:20:17 swa
1633 merged standards into developer manual
1635 Revision 1.1 2001/09/12 15:36:41 swa
1636 source files for junkbuster documentation
1638 Revision 1.3 2001/09/10 17:43:59 swa
1639 first proposal of a structure.
1641 Revision 1.2 2001/06/13 14:28:31 swa
1642 docs should have an author.
1644 Revision 1.1 2001/06/13 14:20:37 swa
1645 first import of project's documentation for the webserver.