1 <!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V3.1//EN"[
2 <!entity % dummy "IGNORE">
3 <!entity supported SYSTEM "supported.sgml">
4 <!entity newfeatures SYSTEM "newfeatures.sgml">
5 <!entity p-intro SYSTEM "privoxy.sgml">
6 <!entity seealso SYSTEM "seealso.sgml">
7 <!entity contacting SYSTEM "contacting.sgml">
8 <!entity history SYSTEM "history.sgml">
9 <!entity copyright SYSTEM "copyright.sgml">
10 <!entity license SYSTEM "license.sgml">
11 <!entity p-version SYSTEM "doc_version.tmp">
12 <!entity p-status SYSTEM "doc_status.tmp">
13 <!entity % p-not-stable "IGNORE">
14 <!entity % p-stable "IGNORE">
15 <!entity % p-text "IGNORE"> <!-- define we are not a text only doc -->
16 <!entity % p-doc "INCLUDE"> <!-- and we are a formal doc -->
17 <!entity % p-supp-userman "INCLUDE"> <!-- Include all from supported.sgml -->
18 <!entity my-copy "©"> <!-- kludge for docbook2man -->
21 File : $Source: /cvsroot/ijbswa/current/doc/source/faq.sgml,v $
24 This file belongs into
25 ijbswa.sourceforge.net:/home/groups/i/ij/ijbswa/htdocs/
27 $Id: faq.sgml,v 2.9 2002/10/29 03:22:22 hal9 Exp $
29 Copyright (C) 2001, 2002 Privoxy Developers <developers@privoxy.org>
32 Based partially on the Internet Junkbuster FAQ originally written by and
33 Copyright (C) 1997 Anonymous Coders and Junkbusters Corporation.
34 http://www.junkbusters.com/
36 <Qandaset defaultlabel='qanda'>
51 ========================================================================
52 NOTE: Please read developer-manual/documentation.html before touching
53 anything in this, or other Privoxy documentation. You have been warned!
54 Failure to abide by this rule will result in the revocation of your license
55 to live a peaceful existence!
56 ========================================================================
62 <article id="index" class="faq">
64 <title>Privoxy Frequently Asked Questions</title>
68 <!-- Completely the wrong markup, but very little is allowed -->
69 <!-- in this part of an article. FIXME -->
70 <link linkend="copyright">Copyright</link> &my-copy; 2001, 2002 by
71 <ulink url="http://www.privoxy.org">Privoxy Developers</ulink>
75 <pubdate>$Id: faq.sgml,v 2.9 2002/10/29 03:22:22 hal9 Exp $</pubdate>
79 Note: this should generate a separate page, and a live link to it.
80 But it doesn't for some mysterious reason. Please leave commented
81 unless it can be fixed proper. For the time being, the copyright
82 statement will be in copyright.smgl.
86 <legalnotice id="legalnotice">
88 text goes here ........
98 <orgname>By: Privoxy Developers</orgname>
107 This is here to keep vim syntax file from breaking :/
108 If I knew enough to fix it, I would.
109 PLEASE DO NOT REMOVE! HB: hal@foobox.net
114 This FAQ gives quick answers to frequently asked questions about
115 <ulink url="http://www.privoxy.org/">Privoxy</ulink>.
116 It can't and doesn't replace the
117 <ulink url="../user-manual/index.html"><citetitle>User Manual</citetitle></ulink>.
119 This works, at least in some situtations:
120 Test: <ulink url="privoxy-user-manual.pdf"><citetitle>User Manual</citetitle></ulink>.
124 <!-- Include privoxy.sgml boilerplate: -->
126 <!-- end boilerplate -->
130 Please note that this document is constantly evolving. This copy represents
131 the state at the release of version &p-version;. ]]>
132 You can find the latest version of the document at <ulink
133 url="http://www.privoxy.org/faq/">http://www.privoxy.org/faq/</ulink>.
134 Please see the <link linkend="contact">Contact section</link> if you want to
135 contact the developers.
139 <!-- Feel free to send a note to the developers at <email>ijbswa-developers@lists.sourceforge.net</email>. -->
145 <!-- ~~~~~ New section ~~~~~ -->
147 <sect1 id="general"><title>General Information</title>
149 <sect2 renderas="sect3" id="newjb"><title>What is this new version of <application>Privoxy</application>?</title>
151 <!-- Include history.sgml -->
158 <sect2 renderas="sect3">
159 <title id="whyprivoxy">Why <quote>Privoxy</quote>? Why a name change at all?</title>
161 <application>Privoxy</application> is the
162 <quote><emphasis>Privacy Enhancing Proxy</emphasis></quote>. Also, its content
163 modification and junk suppression allow you to browse your
164 <quote><emphasis>private</emphasis> edition</quote> of the web.
167 <ulink url="http://junkbusters.com/">Junkbusters Corporation</ulink>
168 continues to offer their original version of the <application>Internet
169 Junkbuster</application>, so publishing our
170 <application> Junkbuster</application>-derived software under the same name
174 There are also potential legal complications from the continued use of the
175 <application>Junkbuster</application> name, which is a registered trademark of
176 <ulink url="http://junkbusters.com/">Junkbusters Corporation</ulink>.
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.
182 The developers also believed that there are so many changes from the original
183 code, that it was time to make a clean break from the past and make
184 a name in their own right<![%p-not-stable;[, especially now with the pending
185 release of version 3.0]]>.
190 <sect2 renderas="sect3" id="differs"><title>How does <application>Privoxy</application> differ
191 from the old <application>Junkbuster?</application></title>
193 <application>Privoxy</application> picks up where
194 <application>Junkbuster</application> left off. All the old features remain.
195 The new <application>Privoxy</application> still blocks ads and banners,
196 still manages cookies, and still helps protect your privacy. But, these are
197 all enhanced, and many new features have been added, all in the same vein.
200 The configuration has changed significantly as well. This is something that
201 users will notice right off the bat if upgrading from
202 <application>Junkbuster</application> 2.0.x. The <quote>blocklist</quote>
203 <quote>cookielist</quote>, <quote>imagelist</quote> and much more has been
204 combined into the <quote>actions</quote> files, with a completely different
205 syntax. See the <ulink url="../user-manual/upgradersnote.html">note to
206 upgraders</ulink> for details.
209 <application>Privoxy</application>'s new features include:
212 <!-- Include newfeatures.sgml: -->
218 <sect2 renderas="sect3" id="proxymoron"><title>What is a <quote>proxy</quote>? How does
219 <application>Privoxy</application> work? </title>
221 A web proxy is a service, based on a software such as <application>Privoxy</application>,
222 that clients (i.e. browsers) can use instead of connecting directly to the web
223 servers on the Internet. The clients then ask the proxy to fetch the objects
224 they need (web pages, images, movies etc) on their behalf, and when the proxy
225 has done so, it hands the results back to the client.
228 There are many reasons to use web proxies, such as security (firewalling),
229 efficiency (caching) and others, and there are just as many different proxies
230 to accommodate those needs.
233 <application>Privoxy</application> is a proxy that is solely focused on privacy
234 protection and junk elimination. Sitting between your browser(s) and the Internet,
235 it is in a perfect position to filter outbound personal information that your
236 browser is leaking, as well as inbound junk. It uses a variety of techniques to do
237 this, all of which are under your control via the various configuration
243 <sect2 renderas="sect3" id="whatsanad">
244 <title id="knows">How does <application>Privoxy</application> know what is
245 an ad, and what is not?</title>
247 <application>Privoxy</application>'s approach to blocking ads is twofold:
250 First, there are certain patterns in the <emphasis>locations</emphasis> (URLs)
251 of banner images. This applies to both the path (you wouldn't guess how many
252 web sites serve their banners from a directory called <quote>banners</quote>!)
253 and the host (blocking the big banner hosting services like doublecklick.net
254 already helps a lot). <application>Privoxy</application> takes advantage of this
255 fact by using <ulink url="../user-manual/actions-file.html#AF-PATTERNS">URL
256 patterns</ulink> to sort out and block the requests for banners.
259 Second, banners tend to come in certain <emphasis>sizes</emphasis>. But you
260 can't tell the size of an image by its URL without downloading it, and if you
261 do, it's too late to save bandwidth. Therefore, <application>Privoxy</application>
262 also inspects the HTML sources of web pages while they are loaded, and replaces
263 references to images with standard banner sizes by dummy references, so that
264 your browser doesn't request them anymore in the first place.
267 Both of this involves a certain amount of guesswork and is, of course, freely
272 <sect2 renderas="sect3">
273 <title id="mistakes">Can <application>Privoxy</application> make mistakes?
274 This does not sound very scientific.</title>
276 Actually, it's a black art ;-) And yes, it is always possible to have a broad
277 rule accidentally block or change something by mistake. There is a good chance
278 you may run into such a situation at some point. It is tricky writing rules to
279 cover every conceivable possibility, and not occasionally get false positives.
283 But this should not be a big concern since the
284 <application>Privoxy</application> configuration is very flexible, and
285 includes tools to help identify these types of situations so they can be
286 addressed as needed, allowing you to customize your installation.
287 (<link linkend="badsite">See the Troubleshooting section below</link>.)
293 <sect2 renderas="sect3" id="browsers2"><title>My browser does the same things as
294 <application>Privoxy</application>. Why should I use
295 <application>Privoxy</application> at all?</title>
297 Modern browsers do indeed have <emphasis>some</emphasis> of the same
298 functionality as <application>Privoxy</application>. Maybe this is
299 adequate for you. But <application>Privoxy</application> is much more
300 versatile and powerful, and can do a number of things that browsers just can't.
303 In addition, a proxy is good choice if you use multiple browsers, or
304 have a LAN with multiple computers. This way all the configuration
305 is in one place, and you don't have to maintain a similar configuration
306 for possibly many browsers.
312 <sect2 renderas="sect3" id="license"><title>Is there is a license or fee? What about a
313 warranty? Registration?</title>
315 <application>Privoxy</application> is licensed under the <ulink
316 url="http://www.gnu.org/copyleft/gpl.html">GNU General Public License (GPL)</ulink>.
317 It is free to use, copy, modify or distribute as you wish under the terms of this
318 license. Please see the <link linkend="copyright">Copyright</link> section for more
319 information on the license and copyright. Or the <filename>LICENSE</filename> file
320 that should be included.
323 There is <emphasis>no warranty</emphasis> of any kind, expressed, implied or otherwise.
324 That is something that would cost real money ;-) There is no registration either.
325 <application>Privoxy</application> really is <emphasis>free</emphasis>
331 <sect2 renderas="sect3" id="jointeam"><title>I would like to help you, what do I do?</title>
333 <sect3 renderas="sect4" id="jointeam-money"><title>Money Money Money</title>
335 We, of course, welcome donations and could use money for domain registering,
336 buying software to test <application>Privoxy</application> with, and, of course,
337 for regular world-wide get-togethers (hahaha). If you enjoy the software and feel
338 like helping us with a donation, just <ulink
339 url="mailto:developers@privoxy.org">drop us a note</ulink>.
343 <sect3 renderas="sect4" id="jointeam-software"><title>Software</title>
345 If you are a vendor of a web-related software like a browser, web server
346 or proxy, and would like us to ensure that <application>Privoxy</application>
347 runs smoothly with your product, you might consider supplying us with a
348 copy or license. We can't, however, guarantee that we will fix all potential
349 compatibility issues as a result.
353 <sect3 renderas="sect4" id="jointeam-work"><title>You want to work with us?</title>
355 Well, helping the team is always a good idea. We welcome new developers,
356 packaging gurus or documentation writers. Simply <ulink
357 url="https://sourceforge.net/account/register.php">get an account on SourceForge.net</ulink>
358 and mail your id to the <ulink url="mailto:developers@privoxy.org">developers
359 mailing list</ulink>. Then read the <ulink
360 url="../developer-manual/index.html">Developer's Manual</ulink>.
363 Once we have added you to the team, you'll have write access to the <ulink
364 url="http://sourceforge.net/cvs/?group_id=11118">CVS repository</ulink>, and
365 together we'll find a suitable task for you.
374 <!-- ~~~~~ New section ~~~~~ -->
376 <sect1 id="installation"><title>Installation</title>
378 <sect2 renderas="sect3" id="whichbrowsers">
379 <title>Which browsers are supported by <application>Privoxy</application>?</title>
381 Any browser that can be configured to use a proxy, which
382 should be virtually all browsers. Direct browser support is not necessary
383 since <application>Privoxy</application> runs as a separate application and
384 talks to the browser in the standardized HTTP protocol, just like a web server
389 <sect2 renderas="sect3" id="whichos">
390 <title>Which operating systems are supported?</title>
392 Include supported.sgml here:
397 <sect2 renderas="sect3" id="email-client">
398 <title>Can I use <application>Privoxy</application> with my email client?</title>
400 As long as there is some way to set a HTTP proxy for the client, then yes,
401 any application can be used, whether it is strictly speaking a
402 <quote>browser</quote> or not. Though this may not be the best approach for
403 dealing with some of the common abuses of HTML in email. See <link
404 linkend="outlook">How can I configure <application>Privoxy</application> with
405 <application>Outlook Express</application>?</link> below for more on this.
408 Be aware that HTML email presents a number of unique security and privacy
409 related issues, that can require advanced skills to overcome. The developers
410 recommend using email clients that can be configured to convert HTML to plain
411 text for these reasons.
415 <sect2 renderas="sect3" id="newinstall"><title>Can I install
416 <application>Privoxy</application> over <application>Junkbuster</application>?</title>
418 We recommend you un-install <application>Junkbuster</application>
419 first to minimize conflicts and confusion. You may want to
420 save your old configuration files for future reference. The configuration
421 files and syntax have substantially changed, so you will need to manually
422 port your old patterns. See the <ulink url="../user-manual/upgradersnote.html">note
423 to upgraders</ulink> and <ulink url="../user-manual/installation.html">installation
424 chapter</ulink> in the <ulink url="../user-manual/index.html">user manual</ulink>
428 Note: Some installers may automatically un-install
429 <application>Junkbuster</application>, if present!
434 <sect2 renderas="sect3">
435 <title id="firststep">I just installed <application>Privoxy</application>. Is there anything
436 special I have to do now?</title>
439 All browsers must be told to use <application>Privoxy</application>
440 as a proxy by specifying the correct proxy address and port number
441 in the appropriate configuration area for the browser. See below.
442 You should also flush your browser's memory and disk cache to get rid of any
443 cached junk items, and any stored cookies.
450 <sect2 renderas="sect3" id="localhost"><title>What is the proxy address of <application>Privoxy</application>?</title>
452 If you set up the <application>Privoxy</application> to run on
453 the computer you browse from (rather than your ISP's server or some
454 networked computer on a LAN), the proxy will be on <literal>127.0.0.1</literal>
455 (sometimes referred to as <quote>localhost</quote>,
456 which is the special name used by every computer on the Internet to refer
457 to itself) and the port will be 8118 (unless you have <application>Privoxy</application>
458 to run on a different port with the <ulink
459 url="../user-manual/config.html#LISTEN-ADDRESS">listen-address</ulink> config option).
462 When configuring your browser's proxy settings you typically enter
463 the word <quote>localhost</quote> or the IP address <quote>127.0.0.1</quote>
464 in the boxes next to <quote>HTTP</quote> and <quote>Secure</quote> (HTTPS) and
465 then the number <quote>8118</quote> for <quote>port</quote>.
466 This tells your browser to send all web requests to <application>Privoxy</application>
467 instead of directly to the Internet.
470 <application>Privoxy</application> can also be used to proxy for
471 a Local Area Network. In this case, your would enter either the IP
472 address of the LAN host where <application>Privoxy</application>
473 is running, or the equivalent hostname. Port assignment would be
474 same as above. Note that <application>Privoxy</application> doesn't
475 listen on any LAN interfaces by default.
478 <application>Privoxy</application> does not currently handle
479 protocols such as FTP, SMTP, IM, IRC, ICQ, or other Internet
484 <sect2 renderas="sect3" id="nothing">
485 <title>I just installed <application>Privoxy</application>, and nothing is happening.
486 All the ads are there. What's wrong?</title>
489 Did you configure your browser to use <application>Privoxy</application>
490 as a proxy? It does not sound like it. See above. You might also try flushing
491 the browser's caches to force a full re-reading of pages. You can verify
492 that <application>Privoxy</application> is running, and your browser
493 is correctly configured by entering the special URL:
494 <ulink url="http://config.privoxy.org/">http://config.privoxy.org/</ulink>.
495 This should take you to a page titled <quote>This is Privoxy..</quote> with
496 access to <application>Privoxy's</application> internal configuration.
497 If you see this, then you are good to go. If you receive a page saying
498 <quote>Privoxy is not running</quote>, then the browser is not set up to use
499 your <application>Privoxy</application> installation.
500 If you receive anything else (probably nothing at all), it could either
501 be that the browser is not set up correctly, or that
502 <application>Privoxy</application> is not running at all. Check the <ulink
503 url="../user-manual/config.html#LOGFILE">log file</ulink>.
511 <!-- ~~~~~ New section ~~~~~ -->
513 <sect1 id="configuration"><title>Configuration</title>
515 <sect2 renderas="sect3" id="getupdates"><title>Where can I get updated Actions Files?</title>
517 Based on your feedback and the continuing development, updated actions files will be
518 made available on the <ulink
519 url="http://sourceforge.net/project/showfiles.php?group_id=11118">files section</ulink> of
520 our <ulink url="http://sf.net/projects/ijbswa/">project page</ulink>.
524 If you wish to receive an email notification whenever we release updates of
525 <application>Privoxy</application> or the actions file, <ulink
526 url="http://lists.sourceforge.net/lists/listinfo/ijbswa-announce/">subscribe
527 to our announce mailing list</ulink>, ijbswa-announce@lists.sourceforge.net.
532 <sect2 renderas="sect3" id="newconfig"><title>Can I use my old config files?</title>
534 The syntax, number, and purpose of configuration files has substantially
535 changed from <application>Junkbuster</application> and earlier versions
536 of <application>Privoxy</application>. The old files, like <filename>blocklist</filename>
537 will not work at all. If you are upgrading from a 2.0.x version, you will
538 need to port your configuration data to the new format. Note that even the
539 pattern syntax has changed! Even configuration files from the 2.9.x versions
540 will need to be adapted, as configuration syntax has been very much in flow
545 <sect2 renderas="sect3">
546 <title id="actionsfile">What is an <quote>actions</quote> file?</title>
549 <ulink url="../user-manual/actions-file.html">Actions files</ulink>
550 are where various <ulink url="../user-manual/actions-file.html#ACTIONS">actions</ulink>
551 that <application>Privoxy</application> might take while processing a certain
552 request, are configured. Typically, you would define a set of default actions
553 that apply to all URLs, then add exceptions to these defaults where needed.
557 Actions can be defined on a <ulink
558 url="../user-manual/actions-file.html#AF-PATTERNS">URL pattern</ulink> basis, i.e.
559 for single URLs, whole web sites, groups or parts thereof etc. Actions can also be
560 grouped together and then applied to requests matching one or more patterns.
561 There are many possible actions that might apply to any given site. As an example,
562 if you are blocking cookies as one of your default actions, but need to accept
563 cookies from a given site, you would need to define an exception for this
564 site in one of your actions files, preferably in <filename>user.action</filename>.
569 <sect2 renderas="sect3" id="actionss">
570 <title>The <quote>actions</quote> concept confuses me. Please list
571 some of these <quote>actions</quote>.</title>
573 For a comprehensive discussion of the actions concept, please refer
574 to the <ulink url="../user-manual/actions-file.html">actions file
575 chapter</ulink> in the <ulink url="../user-manual/index.html">user
576 manual</ulink>. It includes a <ulink
577 url="../user-manual/actions-file.html#ACTIONS">list of all actions</ulink>
578 and an <ulink url="../user-manual/actions-file.html#ACT-EXAMPLES">actions
579 file tutorial</ulink> to get you started.
584 <sect2 renderas="sect3">
585 <title id="actconfig">How are actions files configured? What is the easiest
586 way to do this?</title>
589 Actions files are just text files in a special syntax and can be edited
590 with a text editor. But probably the easiest way is to access
591 <application>Privoxy</application>'s user interface with your web browser
592 at <ulink url="http://config.privoxy.org/">http://config.privoxy.org/</ulink>
593 (Shortcut: <ulink url="http://p.p/">http://p.p/</ulink>) and then select
594 <quote><ulink url="http://config.privoxy.org/show-status">View &
595 change the current configuration</ulink></quote> from the menu.
600 <!-- ~~~~~ New section ~~~~~ -->
601 <sect2 renderas="sect3">
602 <title>There are several different <quote>actions</quote> files. What are
603 the differences?</title>
605 As of <application>Privoxy</application> v2.9.15, three actions files
606 are being included, to be used for
607 different purposes: These are
608 <filename>default.action</filename>, the <quote>main</quote> actions file
609 which is actively maintained by the <application>Privoxy</application>
610 developers, <filename>user.action</filename>, where users are encouraged
611 to make their private customizations, and <filename>standard.action</filename>,
612 which is for internal <application>Privoxy</application> use only.
613 Please see <ulink url="../user-manual/actions-file.html">the actions chapter</ulink>
614 in the <ulink url="../user-manual/index.html">user manual</ulink> for a more
615 detailed explanation.
619 Earlier versions included three different versions of the
620 <filename>default.action</filename> file. The new scheme allows for
621 greater flexibility of local configuration, and for browser based
622 selection of pre-defined <quote>aggressiveness</quote> levels.
627 <sect2 renderas="sect3" id="yahoo"><title>How can I make my Yahoo/Hotmail/GMX account work?</title>
629 The default configuration shouldn't impact the usability of any of these services.
630 It will, however, make all cookies temporary, so that your browser will forget your
631 login credentials in between browser sessions. If you would like not to have to log
632 in manually each time you access those websites, simply turn off all cookie handling
633 for them in the <filename>user.action</filename> file. An example for yahoo might
637 <screen># Allow all cookies for Yahoo login:
639 { -<ulink url="../user-manual/actions-file.html#CRUNCH-INCOMING-COOKIES">crunch-incoming-cookies</ulink> -<ulink url="../user-manual/actions-file.html#CRUNCH-OUTGOING-COOKIES">crunch-outgoing-cookies</ulink> -<ulink url="../user-manual/actions-file.html#SESSION-COOKIES-ONLY">session-cookies-only</ulink> }
640 .login.yahoo.com</screen>
645 <sect2 renderas="sect3" id="configfiles"> <title>What's the difference between the
646 <quote>Cautious</quote>, <quote>Medium</quote> and <quote>Radical</quote> defaults?</title>
648 Configuring <application>Privoxy</application> is not entirely trivial. To
649 help you get started, we provide you with three different default action
650 <quote>profiles</quote> in the web based actions file editor at <ulink
651 url="http://config.privoxy.org/show-status">http://config.privoxy.org/show-status</ulink>.
652 The following table shows you, which of the most important features are
653 enabled in each configuration:
656 <table frame=all><title>Default Configurations</title>
657 <tgroup cols=4 align=left colsep=1 rowsep=1>
664 <entry>Feature</entry>
665 <entry>Cautious</entry>
666 <entry>Intermadiate</entry>
667 <entry>Radical</entry>
672 <!-- <entry>f1</entry> -->
673 <!-- <entry>f2</entry> -->
674 <!-- <entry>f3</entry> -->
675 <!-- <entry>f4</entry> -->
681 <entry>Ad-blocking by URL</entry>
688 <entry>Ad-filtering by size</entry>
695 <entry>GIF de-animation</entry>
702 <entry>Referer forging</entry>
709 <entry>Cookie handling</entry>
711 <entry>session-only</entry>
716 <entry>Pop-up killing</entry>
723 <entry>Fast redirects</entry>
730 <entry>HTML taming</entry>
737 <entry>JavaScript taming</entry>
744 <entry>Web-bug killing</entry>
751 <entry>Fun text replacements</entry>
758 <entry>Image tag reordering</entry>
765 <entry>Ad-filtering by link</entry>
772 <entry>Demoronizer</entry>
783 Where the defaults are likely to break some sites, exceptions for
784 known popular <quote>problem</quote> sites are included, but in
785 general, the more aggressive your default settings are, the more
786 exceptions you will have to make later. See the <ulink
787 url="../user-manual/index.html">user manual</ulink> for a more
791 It should be noted that the <quote>Radical</quote> profile is not only more
792 aggressive, but also includes fun and, extreme usage of most of
793 <application>Privoxy's</application> features. Use at your own risk!
798 <sect2 renderas="sect3" id="browseconfig"> <title>Why can I change the configuration
799 with a browser? Does that not raise security issues?</title>
801 It may seem strange that regular users can edit the config files with their
802 browsers, although the whole <filename>/etc/privoxy</filename> hierarchy
803 belongs to the user <quote>privoxy</quote>, with only 644 permissions.
806 When you use the browser-based editor, <application>Privoxy</application>
807 itself is writing to the config files. Because
808 <application>Privoxy</application> is running as the user <quote>privoxy</quote>,
809 it can update the config files.
812 If you run <application>Privoxy</application> for multiple untrusted users (e.g. in
813 a LAN), you will probably want to turn the web-based editor and remote toggle
814 features off by setting <quote><literal><ulink
815 url="../user-manual/config.html#ENABLE-EDIT-ACTIONS">enable-edit-actions</ulink>
816 0</literal></quote> and <quote><literal><ulink
817 url="../user-manual/config.html#ENABLE-REMOTE-TOGGLE">enable-remote-toggle</ulink>
818 0</literal></quote> in the <ulink url="../user-manual/config.html">main configuration file</ulink>.
821 Note that in the default configuration, only local users (i.e. those on
822 <quote>localhost</quote>) can connect to <application>Privoxy</application>,
823 so this is not (normally) a security problem.
828 <sect2 renderas="sect3">
829 <title id="filterfile">What is the <filename>default.filter</filename> file? What is a <quote>filter</quote>?</title>
831 The <ulink url="../user-manual/filter-file.html"><filename>default.filter</filename></ulink>
832 file is where <emphasis>filters</emphasis> are defined, which can be used to modify or
833 remove, web page content on the fly. Filters apply to <emphasis>anything</emphasis>
834 in the page source, including HTML tags, and JavaScript. Regular expressions are used
835 to accomplish this. There are a number of pre-defined filters to deal with common
836 annoyances. The filters are only defined here, to invoke them, you need to use the
838 url="../user-manual/actions-file.html#FILTER"><literal>filter</literal>
839 action</ulink> in one of the actions files. Filtering is automatically
840 disabled for inappropriate MIME types.
844 If you are familiar with regular expressions, and HTML, you can look at
845 the provided <filename>default.filter</filename> with a text editor and define
846 your own filters. This is potentially a very powerful feature, but
847 requires some expertise in both regular expressions and HTML/HTTP.
851 Presently, there is no GUI editor option for this part of the configuration,
852 but you can disable/enable the various pre-defined filters of the included
853 <filename>default.filter</filename> file with the <ulink
854 url="http://config.privoxy.org/show-status">web-based actions file editor</ulink>.
859 <sect2 renderas="sect3">
860 <title id="lanconfig">How can I set up <application>Privoxy</application> to act as a proxy for my
863 By default, <application>Privoxy</application> only responds to requests
864 from <literal>127.0.0.1</literal> (localhost). To have it act as a server for
865 a network, this needs to be changed in the <ulink
866 url="../user-manual/config.html">main configuration file</ulink>. Look for
868 url="../user-manual/config.html#LISTEN-ADDRESS">listen-address</ulink></literal>
869 option, which may be commented out with a <quote>#</quote> symbol. Make sure
870 it is uncommented, and assign it the address of the LAN gateway interface,
871 and port number to use. Assuming your server's LAN address is 192.168.1.1 and you
872 wish to run <application>Privoxy</application> on port 8118, this line
878 listen-address 192.168.1.1:8118</screen>
882 Save the file, and restart <application>Privoxy</application>. Configure
883 all browsers on the network then to use this address and port number.
887 Alternately, you can have <application>Privoxy</application> listen on
888 all available interfaces:
893 listen-address :8118</screen>
897 And then use <application>Privoxy's</application>
899 url="../user-manual/config.html#PERMIT-ACCESS">permit-access</ulink>
900 feature to limit connections. A firewall in this situation is recommended
905 The above steps should be the same for any TCP network, regardless of
910 If you run <application>Privoxy</application> on a LAN with untrusted users,
911 we recommend that you double-check all <ulink
912 url="../user-manual/config.html#ACCESS-CONTROL">access control and security</ulink>
919 <sect2 renderas="sect3">
920 <title id="noseeum">Instead of ads, now I get a checkerboard pattern. I don't want to see anything.</title>
922 The replacement for blocked images can be controlled with the <ulink
923 url="../user-manual/actions-file.html#SET-IMAGE-BLOCKER"><literal>set-image-blocker</literal>
924 action</ulink>. You have the choice of a checkerboard pattern, a transparent 1x1 GIF
925 image (aka <quote>blank</quote>), or a redirect to a custom image of your choice.
926 Note that this choice only has effect for images which are blocked as images, i.e.
927 whose URLs match both a <literal><ulink
928 url="../user-manual/actions-file.html#HANDLE-AS-IMAGE">handle-as-image</ulink></literal>
929 <emphasis>and</emphasis> <literal><ulink
930 url="../user-manual/actions-file.html#BLOCK">block</ulink></literal> action.
933 If you want to see nothing, then change the <ulink
934 url="../user-manual/actions-file.html#SET-IMAGE-BLOCKER"><literal>set-image-blocker</literal>
935 action</ulink> to <quote>blank</quote>. This can be done by editing the
936 <filename>default.action</filename> file, or trough the <ulink
937 url="http://config.privoxy.org/show-status">web-based actions file editor</ulink>.
942 <sect2 renderas="sect3">
943 <title id="whyseeum">Why would anybody want to see a checkerboard pattern?</title>
945 Remember that <link linkend="whatsanad">telling which image is an ad and which
946 isn't</link>, is mostly guesswork. While we hope that the standard configuration
947 is rather smart, it can and will make errors. The checkerboard image is visually
948 decent, but it shows you that and where images were blocked, which can be very
949 helpful in case some navigation aid or otherwise innocent image was
950 erraneously blocked. Some people might also enjoy seeing how many banners
951 they <emphasis>don't</emphasis> have to see..
956 <!-- This has changed with the adaptive "blocked" page
958 <sect2 renderas="sect3">
959 <title id="blockedisugly">I see large red banners on some pages that say
960 <quote>Blocked</quote>. Why and how do I get rid of this?</title>
962 These are URLs that match something in one of
963 <application>Privoxy's</application> block actions
965 url="../user-manual/actions-file.html#BLOCK"><quote>+block</quote></ulink>).
966 It is meant to be a warning so that you know something has been blocked and
967 an easy way for you to see why. These are handled differently than what has
968 been defined explicitly as <quote>images</quote> (e.g. ads that are GIF image
969 files). Depending on the URL itself, it is sometimes hard for
970 <application>Privoxy</application> to really know whether there is indeed an
971 ad image there or not. And there are limitations as to what
972 <application>Privoxy</application> can do to <quote>fool</quote> the
977 For instance, if the ad is in a frame, then it is embedded in the separate
978 HTML page used for the frame. In this case, you cannot just substitute an
979 aribitrary image (like we would for a <quote>blank</quote> image), for an HTML
980 page. The browser is expecting an HTML page, and that is what it must have
981 for frames. Such situations can be a little trickier to deal with, and
982 <application>Privoxy</application> may show the <quote>Blocked</quote> page,
983 despite your best efforts.
987 If you want these to be treated as if they were images, so that they can be
988 made invisible, you can try moving the offending URL from the
989 <quote>+block</quote> section to the <quote>+imageblock</quote> section of
990 your actions file. Just be forewarned, if any URL is made
991 <quote>invisible</quote>, you may not have any inkling that something has
992 been removed from that page, or why. If this approach does not work, then you are
993 probably dealing with a frame (or <quote>ilayer</quote>), and the only thing
994 that can go there is an HTML page of some sort.
997 To deal with this situation, you could modify the
998 <quote><filename>block</filename></quote> HTML template that is used by
999 <application>Privoxy</application> to display this, and make it something
1000 more to your liking. Currently, there is no configuration option for this.
1001 You will have to modify, or create your own page, and use this to replace
1002 <filename>templates/blocked</filename>, which is what
1003 <application>Privoxy</application> uses to display the <quote>Blocked</quote>
1007 Another way to deal with this is find why and where
1008 <application>Privoxy</application> is blocking the frame, and
1009 diable this. Then let the <quote>+set-image-blocker</quote> action
1010 handle the ad that is embedded in the frame's HTML page.
1015 <sect2 renderas="sect3" id="alliseeisred">
1016 <title>I cannot see all of the <quote>Blocked</quote> page banner. Help.</title>
1018 There is not enough available space to fit the entire Blocked page. Try right
1019 clicking on the visible portion, and select <quote>Show Frame</quote>,
1020 or equivalent. This will usually allow you to see the entire Privoxy
1021 <quote>Blocked</quote> page, and from there you can see just what is being
1025 As of Privoxy 2.9.14, the Blocked banner page is re-sizeable, and tries
1026 to adjust to the allotted space. There may be occassions where there
1027 just isn't enough room to display much of anything useful though.
1034 <sect2 renderas="sect3">
1035 <title id="blockedbytext">I see some images being replaced by a text
1036 instead of the checkerboard image. Why and how do I get rid of this?</title>
1038 This happens when the banners are not embedded in the HTML code of the
1039 page itself, but in separate HTML (sub)documents that are loaded into (i)frames
1040 or (i)layers, and these external HTML documents are blocked. Being non-images
1041 they get replaced by a substitute HTML page rather than a substitute image,
1042 which wouldn't work out technically, since the browser expects and accepts
1043 only HTML when it has requested an HTML document.
1046 The substitute page adapts to the available space and shows itself as a
1047 miniature two-liner if loaded into small frames, or full-blown with a
1048 large red "BLOCKED" banner if space allows.
1051 If you prefer the banners to be blocked by images, you must see to it that
1052 the HTML documents in which they are embedded are not blocked. Clicking
1053 the <quote>See why</quote> link offered in the substitute page will show
1054 you which rule blocked the page. After changing the rule and un-blocking
1055 the HTML documents, the browser will try to load the actual banner images
1056 and the usual image blocking will (hopefully!) kick in.
1061 <sect2 renderas="sect3" id="srvany">
1062 <title>Can <application>Privoxy</application> run as a service
1063 on Win2K/NT?</title>
1065 Yes, it can run as a system service using <command>srvany.exe</command>.
1066 See the discussion at <ulink
1067 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>,
1068 for details, and a sample configuration.
1071 Version 3.0.1 fixes the problem where the icon and menu where not available
1072 in the taskbar for this usage.
1076 <sect2 renderas="sect3" id="otherproxy">
1077 <title>How can I make <application>Privoxy</application> work with other
1078 proxies like <application>Squid</application>?</title>
1080 This can be done and is often useful to combine the benefits of
1081 <application>Privoxy</application> with those of a caching proxy.
1083 url="../user-manual/config.html#FORWARDING">forwarding chapter</ulink>
1084 in the <ulink url="../user-manual/index.html">user manual</ulink> which
1085 describes how to do this.
1089 <sect2 renderas="sect3" id="port-80">
1090 <title>Can I just set <application>Privoxy</application> to use port 80
1091 and thus avoid individual browser configuration?</title>
1094 No, its more complicated than that. This only works with special kinds
1095 of proxies known as <quote>transparent</quote> proxies (see below).
1100 <sect2 renderas="sect3" id="transparent">
1101 <title>Can <application>Privoxy</application> run as a <quote>transparent
1102 </quote> proxy?</title>
1104 No, <application>Privoxy</application> currently does not have this ability,
1105 though it is planned for a future release. Transparent proxies require
1106 special handling of the request headers beyond what
1107 <application>Privoxy</application> is now capable of.
1111 Chaining <application>Privoxy</application> behind another proxy that has
1112 this ability should work though.
1114 url="../user-manual/config.html#FORWARDING">forwarding chapter</ulink>
1115 in the <ulink url="../user-manual/index.html">user manual</ulink>. As
1116 a transparent proxy to be used for chaining we recommend Transproxy
1117 (<ulink url="http://www.transproxy.nlc.net.au/">http://www.transproxy.nlc.net.au/</ulink>).
1122 <sect2 renderas="sect3" id="outlook">
1123 <title>How can I configure <application>Privoxy</application> for use with <application>Outlook
1124 Express</application>?</title>
1126 <application>Outlook Express</application> uses <application>Internet Explorer</application>
1127 components to both render HTML, and fetch any HTTP requests that may be embedded in an HTML email.
1128 So however you have <application>Privoxy</application> configured to work
1129 with IE, this configuration should automatically be shared.
1133 <sect2 renderas="sect3" id="outlook-more">
1134 <title>How can I have separate rules just for HTML mail?</title>
1136 The short answer is, you can't. <application>Privoxy</application> has no way
1137 of knowing which particular application makes a request, so there is no way to
1138 distinguish between web pages and HTML mail.
1139 <application>Privoxy</application> just blindly proxies all requests. In the
1140 case of <application>Outlook Express</application> (see above), OE uses
1141 IE anyway, and there is no way for <application>Privoxy</application> to ever
1142 be able to distinguish between them (nor could any other proxy type
1143 application for that matter).
1146 For a good discussion of some of the issues involved (including privacy and
1147 security issues), see
1148 <ulink url="http://sourceforge.net/tracker/?func=detail&atid=211118&aid=629518&group_id=11118">http://sourceforge.net/tracker/?func=detail&atid=211118&aid=629518&group_id=11118</ulink>.
1152 <sect2 renderas="sect3" id="allow-cookies">
1153 <title>How can I allow permanent cookies for my trusted sites?</title>
1156 There are several actions that relate to cookies. The default behavior is to
1157 allow only <quote>session cookies</quote>, which means the cookies only last
1158 for the current browser session. This eliminates most kinds of abuse related
1159 to cookies. But there may be cases where we want cookies to last.
1162 To disable all cookie actions, so that cookies are allowed unrestricted,
1163 both in and out, for <literal>example.com</literal>:
1167 { -crunch-incoming-cookies -crunch-outgoing-cookies -session-cookies-only -filter{content-cookies} }
1168 .example.com</screen>
1171 Place the above in <filename>user.action</filename>. Note some of these may
1172 be off by default anyway, so this might be redundant, but there is no harm
1173 being explicit in what you want to happen. <filename>user.action</filename>
1174 includes an alias for this situation, called
1175 <literal>allow-cookies</literal>.
1181 <!-- ~ End section ~ -->
1184 <!-- ~~~~~ New section ~~~~~ -->
1186 <sect1 id="misc"><title>Miscellaneous</title>
1188 <sect2 renderas="sect3">
1189 <title id="slowsme">How much does <application>Privoxy</application> slow my browsing down? This
1190 has to add extra time to browsing.</title>
1192 It should not slow you down any in real terms, and may actually help
1193 speed things up since ads, banners and other junk are not being displayed.
1194 The actual processing time required by <application>Privoxy</application>
1195 itself for each page, is relatively small in the overall scheme of things,
1196 and happens very quickly. This is typically more than offset by time saved
1197 not downloading and rendering ad images.
1201 <quote>Filtering</quote> content via the <literal><ulink
1202 url="../user-manual/actions-file.html#FILTER">filter</ulink></literal> or
1204 url="../user-manual/actions-file.html#DEANIMATE-GIFS">deanimate-gifs</ulink></literal>
1205 actions may cause a perceived slowdown, since the entire document needs to be buffered
1206 before displaying. See below.
1212 <sect2 renderas="sect3" id="loadingtimes"><title>I noticed considerable
1213 delays in page requests compared to the old Junkbuster. What's wrong?</title>
1215 If you use any <literal><ulink
1216 url="../user-manual/actions-file.html#FILTER">filter</ulink></literal> action,
1217 such as filtering banners by size, web-bugs etc, or the <literal><ulink
1218 url="../user-manual/actions-file.html#DEANIMATE-GIFS">deanimate-gifs</ulink></literal>
1219 action, the entire document must be loaded into memory in order for the filtering
1220 mechanism to work, and nothing is sent to the browser during this time.
1223 The loading time does not really change in real numbers, but the feeling is
1224 different, because most browsers are able to start rendering incomplete
1225 content, giving the user a feeling of "it works". This effect is especially
1226 noticeable on slow dialup connections.
1229 Filtering is automatically disabled for inappropriate MIME types.
1235 <sect2 renderas="sect3" id="configurl"><title>What are "http://config.privoxy.org/" and
1236 "http://p.p/"?</title>
1238 <ulink url="http://config.privoxy.org/">http://config.privoxy.org/</ulink> is the
1239 address of <application>Privoxy</application>'s built-in user interface, and
1240 <ulink url="http://p.p/">http://p.p/</ulink> is a shortcut for it.
1243 Since <application>Privoxy</application> sits between your web browser and the Internet,
1244 it can simply intercept requests for these addresses and answer them with its built-in
1245 <quote>web server</quote>.
1248 This also makes for a good test for your browser configuration: If entering the
1249 URL <ulink url="http://config.privoxy.org/">http://config.privoxy.org/</ulink>
1250 takes you to a page saying <quote>This is Privoxy ...</quote>, everything is OK.
1251 If you get a page saying <quote>Privoxy is not working</quote> instead, then
1252 your browser didn't use <application>Privoxy</application> for the request,
1253 hence it could not be intercepted, and you have accessed the <emphasis>real</emphasis>
1254 web site at config.privoxy.org.
1257 With recent versions of <application>Privoxy</application> (version 2.9.x and
1258 later), the user interface features information on the run time status, the
1259 configuration, and even a built-in editor for the <ulink
1260 url="../user-manual/actions-file.html">actions files</ulink>.
1264 Note that the built-in URLs from earlier versions of <application>Junkbuster</application>
1265 / <application>Privoxy</application>, http://example.com/show-proxy-args and http://i.j.b/,
1266 are no longer supported. If you still use such an old version, you should really consider
1267 upgrading to &p-version;.
1272 FIXME: commented out until we have data. HB 03/18/02.
1274 <sect2 renderas="sect3" id="badfiledesc"><title>I get the message 'Bad File Descriptor', why?</title>
1282 <sect2 renderas="sect3" id="blocklist"><title>Do you still maintain the blocklists?</title>
1284 No. The patterns for blocking now reside (among other things) in the <ulink
1285 url="../user-manual/actions-file.html">actions files</ulink>, which are
1286 actively maintained instead. See next question ...
1290 <sect2 renderas="sect3" id="newads"><title>How can I submit new ads?</title>
1292 Yes, absolutely! Please see the <link linkend="contact">Contact section</link> for
1293 how to do that. Please note that you (technically) need the latest
1294 <application>Privoxy</application> version for this to work.
1299 <sect2 renderas="sect3" id="ip"><title>How can I hide my IP address?</title>
1301 If you run both the browser and the proxy locally, you cannot hide your IP
1302 address with <application>Privoxy</application> or any other software. The
1303 server needs to know your IP address to send the answers back to you.
1306 Fortunately there are many publicly usable anonymous proxies out there, which
1307 solve the problem by providing a further level of indirection between you and
1308 the web server, shared by many people, and thus letting your requests "drown"
1309 in white noise of unrelated requests as far as user tracking is concerned.
1312 Most of them will, however, log your IP address and make it available to the
1313 authorities in case you abuse that anonymity for criminal purposes. In fact
1314 you can't even rule out that some of them only exist to *collect* information
1315 on (those suspicious) people with a more than average preference for privacy.
1318 You can find a list of anonymous public proxies at <ulink
1319 url="http://www.multiproxy.org/anon_list.htm">multiproxy.org</ulink> and many
1320 more through Google. A particularly interesting project is the JAP service
1321 offered by the Technical University of Dresden (<ulink
1322 url="http://anon.inf.tu-dresden.de/index_en.html">http://anon.inf.tu-dresden.de/index_en.html</ulink>).
1325 There is, however, even in the single-machine case the possibility to make the
1326 server believe that your machine is in fact a shared proxy serving a whole big
1327 LAN, and we are looking into that.
1331 <sect2 renderas="sect3">
1332 <title id="anonforsure">Can <application>Privoxy</application> guarantee I am anonymous?</title>
1334 No. Your chances of remaining anonymous are greatly improved, but unless you
1335 are an expert on Internet security it would be safest to assume that
1336 everything you do on the Web can be traced back to you.
1339 <application>Privoxy</application> can remove various information about you,
1340 and allows <emphasis>you</emphasis> more freedom to decide which sites
1341 you can trust, and what details you want to reveal. But it's still possible
1342 that web sites can find out who you are. Here's one way this can happen.
1345 A few browsers disclose the user's email address in certain situations, such
1346 as when transferring a file by FTP. <application>Privoxy</application>
1347 does not filter FTP. If you need this feature, or are concerned about the
1348 mail handler of your browser disclosing your email address, you might
1349 consider products such as <application>NSClean</application>.
1352 Browsers available only as binaries could use non-standard headers to give
1353 out any information they can have access to: see the manufacturer's license
1354 agreement. It's impossible to anticipate and prevent every breach of privacy
1355 that might occur. The professionally paranoid prefer browsers available as
1356 source code, because anticipating their behavior is easier. Trust the source,
1362 <sect2 renderas="sect3">
1363 <title id="sitebreak">Might some things break because header information or
1364 content is being altered?</title>
1367 Definitely. More and more sites use HTTP header content to decide what to
1368 display and how to display it. There is many ways that this can be handled,
1369 so having hard and fast rules, is tricky.
1373 <quote>User-Agent</quote> in particular is often used in this way to identify
1374 the browser, and adjust content accordingly. Changing this now (at least not
1375 further than removing the OS information) is not recommended, since so many
1376 sites do look for it. You may get undesirable results by changing this.
1380 For instance, different browsers use different encodings of Russian and Czech
1381 characters, certain web servers convert pages on-the-fly according to the
1382 User Agent header. Giving a <quote>User Agent</quote> with the wrong
1383 operating system or browser manufacturer causes some sites in these languages
1384 to be garbled; Surfers to Eastern European sites should change it to
1385 something closer. And then some page access counters work by looking at the
1386 <quote>Referer</quote> header; they may fail or break if unavailable. The
1387 weather maps of Intellicast have been blocked by their server when no
1388 <quote>Referer</quote> or cookie is provided, is another example. (But you
1389 can forge both headers without giving information away). There are
1390 many other ways things can go wrong when trying to fool a web server.
1394 Similar thoughts apply to modifying JavaScript, and, to a lesser degree,
1399 If you have problems with a site, you will have to adjust your configuration
1400 accordingly. Cookies are probably the most likely adjustment that may
1401 be required, but by no means the only one.
1407 <sect2 renderas="sect3">
1408 <title id="caching">Can <application>Privoxy</application> act as a <quote>caching</quote> proxy to
1409 speed up web browsing?</title>
1411 No, it does not have this ability at all. You want something like
1412 <ulink url="http://www.squid-cache.org/">Squid</ulink> for this. And, yes,
1413 before you ask, <application>Privoxy</application> can co-exist
1414 with other kinds of proxies like <application>Squid</application>.
1415 See the <ulink url="../user-manual/config.html#FORWARDING">forwarding
1416 chapter</ulink> in the <ulink url="../user-manual/index.html">user
1417 manual</ulink> for details.
1421 <sect2 renderas="sect3">
1422 <title id="firewall">What about as a firewall? Can <application>Privoxy</application> protect me?</title>
1424 Not in the way you mean, or in the way a true firewall can.
1425 <application>Privoxy</application> can help protect your privacy, but not
1426 protect you from intrusion attempts. It is, of course, perfectly possible
1427 and recommended to use <emphasis>both</emphasis>.
1431 <!-- No longer needed
1432 <sect2 renderas="sect3">
1433 <title id="logo">The <application>Privoxy</application> logo that replaces ads is very blocky
1434 and ugly looking. Can't a better font be used?</title>
1437 This is not a font problem. The logo is an image that is created by
1438 <application>Privoxy</application> on the fly. So as to not waste
1439 memory, the image is rather small. The blockiness comes when the
1440 image is scaled to fill a largish area. There is not much to be done
1441 about this, other than to use one of the other
1442 <quote>imageblock</quote> directives: <emphasis>pattern</emphasis>,
1443 <emphasis>blank</emphasis>, or a URL of your choosing.
1446 Given the above problem, we have decided to remove the logo option entirely
1452 <sect2 renderas="sect3">
1453 <title id="wasted">I have large empty spaces / a checkerboard pattern now where
1454 ads used to be. Why?</title>
1456 It would be technically possible eliminate the banners in a way that frees
1457 their screen estate in many cases, by doing all banner blocking with filters,
1458 i.e. eliminating the whole image references from the HTML pages instead
1459 of letting them stay in, and blocking the resulting requests for the
1463 But this would consume considerable CPU resources, would likely destroy
1464 the layout of many web pages which rely on the banners consuming a certain
1465 amount of screen space, and would fail in other cases, where the screen space
1466 is reserved e.g. by tables anyway. Also, making the banners disappear without
1467 a visual trace complicates troubleshooting.
1470 So we won't support this in the default configuration, but you can of course
1471 define appropriate filters yourself.
1475 <sect2 renderas="sect3">
1476 <title id="ssl">How can <application>Privoxy</application> filter Secure (HTTPS) URLs?</title>
1478 Since secure HTTP connections are encrypted SSL sessions between your browser
1479 and the secure site, and are meant to be reliably <emphasis>secure</emphasis>,
1480 there is little that <application>Privoxy</application> can do but hand the raw
1481 gibberish data though from one end to the other unprocessed.
1484 The only exception to this is blocking by host patterns, as the client needs
1485 to tell <application>Privoxy</application> the name of the remote server,
1486 so that <application>Privoxy</application> can establish the connection.
1487 If that name matches a host-only pattern, the connection will be blocked.
1490 As far as ad blocking is concerned, this is less of a restriction than it may
1491 seem, since ad sources are often identifiable by the host name, and often
1492 the banners to be placed in an encrypted page come unencrypted nonetheless
1493 for efficiency reasons, which exposes them to the full power of
1494 <application>Privoxy</application>'s ad blocking.
1497 <quote>Content cookies</quote> (those that are embedded in the actual HTML or
1498 JS page content, see <literal><ulink
1499 url="../user-manual/actions-file.html#FILTER-CONTENT-COOKIES">filter{content-cookies}</ulink></literal>),
1500 in an SSL transaction will be impossible to block under these conditions.
1501 Fortunately, this does not seem to be a very common scenario since most
1502 cookies come by traditional means.
1507 <sect2 renderas="sect3">
1508 <title id="secure"><application>Privoxy</application> runs as a <quote>server</quote>. How
1509 secure is it? Do I need to take any special precautions?</title>
1511 There are no known exploits that might affect
1512 <application>Privoxy</application>. On Unix-like systems,
1513 <application>Privoxy</application> can run as a non-privileged
1514 user, which is how we recommend it be run. Also, by default
1515 <application>Privoxy</application> only listens to requests
1516 from <quote>localhost</quote> only. The server aspect of
1517 <application>Privoxy</application> is not itself directly exposed to the
1518 Internet in this configuration. If you want to have
1519 <application>Privoxy</application> serve as a LAN proxy, this will have to
1520 be opened up to allow for LAN requests. In this case, we'd recommend
1521 you specify only the LAN gateway address, e.g. 192.168.1.1, in the main
1522 <application>Privoxy</application> configuration file and check all <ulink
1523 url="../user-manual/config.html#ACCESS-CONTROL">access control and security
1524 options</ulink>. All LAN hosts can then use this as their proxy address
1525 in the browser proxy configuration, but <application>Privoxy</application>
1526 will not listen on any external interfaces. ACLs can be defined in addition,
1527 and using a firewall is always good too. Better safe than sorry.
1532 <sect2 renderas="sect3" id="turnoff">
1533 <title>How can I temporarily disable <application>Privoxy</application>?</title>
1535 The easiest way is to access <application>Privoxy</application> with your
1536 browser by using the remote toggle URL: <ulink
1537 url="http://config.privoxy.org/toggle">http://config.privoxy.org/toggle</ulink>.
1538 See the <ulink url="../user-manual/appendix.html#BOOKMARKLETS">Bookmarklets section</ulink>
1539 of the <citetitle>User Manual</citetitle> for an easy way to access this
1544 <sect2 renderas="sect3" id="reallyoff">
1545 <title>When <quote>disabled</quote> is <application>Privoxy</application> totally
1546 out of the picture?</title>
1548 No, this just means all filtering and actions are disabled.
1549 <application>Privoxy</application> is still acting as a proxy, but just not
1550 doing any of the things that <application>Privoxy</application> would
1551 normally be expected to do. It is still a <quote>middle-man</quote> in
1552 the interaction between your browser and web sites.
1556 <sect2 renderas="sect3" id="crunch">
1557 <title>My logs show <application>Privoxy</application> <quote>crunches</quote>
1558 ads, but also its own CGI pages. What is a <quote>crunch</quote>?</title>
1560 A <quote>crunch</quote> simply means <application>Privoxy</application> intercepted
1561 <emphasis>something</emphasis>, nothing more. Often this is indeed ads or
1562 banners, but <application>Privoxy</application> uses the same mechanism for
1563 trapping requests for its own internal pages. For instance, a request for
1564 <application>Privoxy's</application> configuration page at: <ulink
1565 url="http://config.privoxy.org">http://config.privoxy.org</ulink>, is
1566 intercepted (i.e. it does not go out to the 'net), and the familiar CGI
1567 configuration is returned to the browser, and the log consequently will show
1568 a <quote>crunch</quote>.
1572 <sect2 renderas="sect3" id="downloads">
1573 <title>Can <application>Privoxy</application> effect files that I download
1574 from a webserver? FTP server?</title>
1576 From the webserver's perspective, there is no difference between
1577 viewing a document (i.e. a page), and downloading a file. The same is true of
1578 <application>Privoxy</application>. If there is a match for a <literal><ulink
1579 url="../user-manual/actions-file.html#BLOCK">block</ulink></literal> pattern,
1580 it will still be blocked, and of course this is obvious. Filtering is
1581 potentially more of a concern since the results are not always so obvious.
1584 <application>Privoxy</application> knows the differences in files according
1585 to the <quote>Document Type</quote> as reported by the webserver. If this is
1586 reported accurately (e.g. <quote>application/zip</quote> for a zip archive),
1587 then <application>Privoxy</application> knows to ignore these where
1588 appropriate. It is possible, however, that documents that are of an unknown
1589 type (generally assumed to be <quote>text/plain</quote>) will be filtered, as
1590 will those that might be incorrectly reported by the webserver. If such a
1591 file is a downloaded file that is intended to be saved to disk, then any
1592 content that might have been altered by filtering, will be saved too, for
1593 these (probably very rare) cases.
1596 <application>Privoxy</application> does not do FTP at all, only HTTP
1602 <sect2 renderas="sect3" id="seealso">
1603 <title>Where can I find more information about <application>Privoxy</application>
1604 and related issues?</title>
1605 <!-- Include seealso.sgml boilerplate: -->
1607 <!-- end boilerplate -->
1612 <ulink url="../user-manual/seealso.html">user-manual</ulink> for
1618 <sect2 renderas="sect3" id="microsuck">
1619 <title>I've noticed that Privoxy changes <quote>Microsoft</quote> to
1620 <quote>MicroSuck</quote>! Why are you manipulating my browsing?</title>
1623 We're not. The text substitutions that you are seeing are disabled
1624 in the default configuration as shipped. You have either manually
1625 activated the <quote><literal>fun</literal></quote> filter which
1626 is clearly labeled <quote>Text replacements for subversive browsing
1627 fun!</quote> or you have implicitly activated it by choosing the
1628 <quote>Radical</quote> profile in the web-based editor.
1635 <!-- ~~~~~ New section ~~~~~ -->
1637 <sect1 id="trouble">
1638 <title>Troubleshooting</title>
1640 <sect2 renderas="sect3">
1641 <title id="refused">I just upgraded and am getting <quote>connection refused</quote>
1642 with every web page?</title>
1644 Either <application>Privoxy</application> is not running, or your
1645 browser is configured for a different port than what
1646 <application>Privoxy</application> is using.
1650 The old <application>Privoxy</application> (and also
1651 <application>Junkbuster</application>) used port 8000 by
1652 default. This has been changed to port 8118 now, due to a conflict
1653 with NAS (Network Audio Service), which uses port 8000. If you haven't,
1654 you need to change your browser to the new port number, or alternately
1656 url="../user-manual/config.html#LISTEN-ADDRESS"><literal>listen-address</literal>
1657 option</ulink> in <application>Privoxy's</application> <ulink
1658 url="../user-manual/config.html">main configuration file</ulink>.
1663 <sect2 renderas="sect3">
1664 <title id="flushit">I just added a new rule, but the steenkin ad is
1665 still getting through. How?</title>
1667 If the ad had been displayed before you added its URL, it will probably be
1668 held in the browser's cache for some time, so it will be displayed without
1669 the need for any request to the server, and <application>Privoxy</application>
1670 will not be in the picture. The best thing to do is try flushing the browser's
1671 caches. And then try again.
1675 If this doesn't help, you probably have an error in the rule you
1676 applied. Try pasting the full URL of the offending ad into <ulink
1677 url="http://config.privoxy.org/show-url-info">http://config.privoxy.org/show-url-info</ulink>
1678 and see if it really matches your new rule.
1683 <sect2 id="badsite" renderas="sect3">
1684 <title >One of my favorite sites does not work with <application>Privoxy</application>.
1685 What can I do?</title>
1688 First verify that it is indeed a <application>Privoxy</application> problem,
1689 by toggling off <application>Privoxy</application> through <ulink
1690 url="http://config.privoxy.org/toggle">http://config.privoxy.org/toggle</ulink>,
1691 and then shift-reloading the problem page (i.e. holding down the shift key
1692 while clicking reload. Alternatively, flush your browser's disk and memory
1697 If still a problem, go to <ulink
1698 url="http://config.privoxy.org/show-url-info">http://config.privoxy.org/show-url-info</ulink>
1699 and paste the full URL of the page in question into the prompt. See which actions
1700 are being applied to the URL, and which matches in which actions files are
1701 responsible for that. Now, armed with this information, go to <ulink
1702 url="http://config.privoxy.org/show-status">http://config.privoxy.org/show-status</ulink>
1703 and select the appropriate actions files for editing.
1706 You can now either look for a section which disables the actions that
1707 you suspect to cause the problem and add a pattern for your site there,
1708 or make up a completely new section for your site. In any case, the recommended
1709 way is to disable only the prime suspect, reload the problem page, and only
1710 if the problem persists, disable more and more actions until you have
1711 identified the culprit. You may or may not want to turn the other actions
1712 on again. Remember to flush your browser's caches in between any such changes!
1715 Alternately, if you are comfortable with a text editor, you can accomplish
1716 the same thing by editing the appropriate actions file. Probably the easiest
1717 way to deal with such problems when editing by hand is to add your
1718 site to a <literal>{ fragile }</literal> section in <filename>user.action</filename>,
1719 which is an alias that turns off most <quote>dangerous</quote>
1720 actions, but is also likely to turn off more actions then needed, and thus lower
1721 your privacy and protection more than necessary,
1724 Troubleshooting actions is discussed in more detail in the <ulink
1725 url="../user-manual/appendix.html#ACTIONSANAT">user-manual appendix</ulink>.
1726 There is also an <ulink
1727 url="../user-manual/actions-file.html#ACT-EXAMPLES">actions tutorial</ulink>.
1733 <!-- ~~~~~ New section ~~~~~ -->
1734 <sect2 id="dun" renderas="sect3">
1735 <title>After installing <application>Privoxy</application>, I have to log in
1736 every time I start IE. What gives?</title>
1739 This is a quirk that effects the installation of
1740 <application>Privoxy</application>, in conjunction with Internet Explorer and
1741 Internet Connection Sharing on Windows 2000 and Windows XP. The symptoms may
1742 appear to be corrupted or invalid DUN settings, or passwords.
1746 When setting up an NT based Windows system with
1747 <application>Privoxy</application> you may find that things do not seem to be
1748 doing what you expect. When you set your system up you will probably have set
1749 up Internet Connection Sharing (ICS) with Dial up Networking (DUN) when
1750 logged in with administrator privileges. You will probably have made this DUN
1751 connection available to other accounts that you may have set-up on your
1752 system. E.g. Mum or Dad sets up the system and makes accounts suitably
1753 configured for the kids.
1757 When setting up <application>Privoxy</application> in this environment you
1758 will have to alter the proxy set-up of Internet Explorer (IE) for the
1759 specific DUN connection on which you wish to use
1760 <application>Privoxy</application>. When you do this the ICS DUN set-up
1761 becomes user specific. In this instance you will see no difference if you
1762 change the DUN connection under the account used to set-up the connection.
1763 However when you do this from another user you will notice that the DUN
1764 connection changes to make available to "Me only". You will also find that
1765 you have to store the password under each different user!
1769 The reason for this is that each user's set-up for IE is user specific. Each
1770 set-up DUN connection and each LAN connection in IE store the settings for
1771 each user individually. As such this enforces individual configurations
1772 rather than common ones. Hence the first time you use a DUN connection after
1773 re-booting your system it may not perform as you expect, and prompt you for
1774 the password. Just set and save the password again and all should be OK.
1778 [Thanks to Ray Griffith for this submission.]
1783 <!-- ~~~~~ New section ~~~~~ -->
1784 <sect2 id="ftp" renderas="sect3">
1785 <title>I cannot connect to any FTP sites. <application>Privoxy</application>
1786 seems to be blocking me.</title>
1788 <application>Privoxy</application> cannot act as a proxy for FTP traffic,
1789 so do not configure your browser to use <application>Privoxy</application>
1790 as an FTP proxy. The same is true for any protocol other than HTTP or HTTPS.
1793 Most browsers understand FTP as well as HTTP. If you connect to a site, with
1794 a URL like <literal>ftp://ftp.example.com</literal>, your browser is making
1795 an FTP connection, and not a HTTP connection. So while your browser may
1796 speak FTP, <application>Privoxy</application> does not, and cannot proxy
1801 <!-- ~~~~~ New section ~~~~~ -->
1802 <sect2 id="osxie" renderas="sect3">
1803 <title>In Mac OSX, I can't configure Microsoft Internet Explorer to use
1804 <application>Privoxy</application> as the HTTP proxy.</title>
1806 Microsoft Internet Explorer (in versions like 5.1) respects system-wide
1807 network settings. In order to change the HTTP proxy, open System
1808 Preferences, and click on the Network icon. In the settings pane that
1809 comes up, click on the Proxies tab. Ensure the "Web Proxy (HTTP)" checkbox
1810 is checked and enter <literal>127.0.0.1</literal> in the entry field.
1811 Enter <literal>8118</literal> in the Port field. The next time you start
1812 IE, it should reflect these values.
1816 <!-- ~~~~~ New section ~~~~~ -->
1817 <sect2 renderas="sect3" id="osxuninstall">
1818 <title>In Mac OSX, I dragged the Privoxy folder to the trash in order to
1819 uninstall it. Now the finder tells me I don't have sufficient privileges to
1820 empty the trash.</title>
1822 Just dragging the <application>Privoxy</application> folder to the trash is
1823 not enough to delete it. <application>Privoxy</application> supplies an
1824 <application>uninstall.command</application> file that takes care of
1825 these details. Open the trash, drag the <application>uninstall.command</application>
1826 file out of the trash and double-click on it. You will be prompted for
1827 confirmation and the administration password.
1830 The trash may still appear full after this command; emptying the trash
1831 from the desktop should make it appear empty again.
1836 <!-- ~~~~~ New section ~~~~~ -->
1837 <sect2 renderas="sect3" id="blankpage">
1838 <title>I get a completely blank page at one site. <quote>View Source</quote>
1839 shows only: <markup><![CDATA[<html><body></body></html>]]></markup>. Without
1840 <application>Privoxy</application> the page loads fine.</title>
1842 Chances are that the site suffers from a bug in
1843 <ulink url="http://www.php.net/"><application>PHP</application></ulink>,
1844 which results in empty pages being sent if the client explicitly requests
1845 an uncompressed page, like <application>Privoxy</application> does.
1846 This bug has been fixed in PHP 4.2.3.
1849 To find out if this is in fact the source of the problem, try adding
1850 the site to a <literal>-prevent-compression</literal> section in
1851 <filename>user.action</filename>:
1854 # Make exceptions for ill-behaved sites:
1856 {-prevent-compression}
1857 .example.com</screen>
1859 If that works, you may also want to report the problem to the
1860 site's webmasters, telling them to use zlib.output_compression
1861 instead of ob_gzhandler in their PHP applications (workaround)
1862 or upgrade to PHP 4.2.3 or later (fix).
1866 <!-- ~~~~~ New section ~~~~~ -->
1867 <sect2 renderas="sect3" id="error503">
1868 <title>Why am I getting a 503 Error (WSAECONNREFUSED) on every page?</title>
1870 More than likely this is a problem with the network stack. ZoneAlarm has
1871 been reported to cause this symptom -- even if not running. The solution is
1872 to either fight the ZA configuration, or uninstall ZoneAlarm, and then find
1873 something better behaved in its place. Other firewall type products may
1874 cause similar type problems if not configured correctly.
1883 <!-- ~~~~~ New section ~~~~~ -->
1885 FIXME: Commented out until we have something to put here. HB 03/18/02.
1886 <sect1 id="knownissues"><title>Known Issues</title>
1893 <!-- ~~~~~ New section ~~~~~ -->
1894 <sect1 id="contact"><title>Contacting the developers, Bug Reporting and Feature Requests</title>
1895 <!-- Include contacting.sgml -->
1897 <!-- end contacting -->
1900 <!-- ~~~~~ New section ~~~~~ -->
1901 <sect1 id="copyright"><title>Privoxy Copyright, License and History</title>
1903 <!-- Include copyright.sgml -->
1908 Portions of this document are <quote>borrowed</quote> from the original
1909 <application>Junkbuster</application> (tm) FAQ, and modified as
1910 appropriate for <application>Privoxy</application>.
1913 <!-- ~~~~~ New section ~~~~~ -->
1914 <sect2><title>License</title>
1915 <!-- Include copyright.sgml: -->
1917 <!-- end copyright -->
1919 <!-- ~ End section ~ -->
1921 <!-- ~~~~~ New section ~~~~~ -->
1922 <sect2><title>History</title>
1923 <!-- Include history.sgml -->
1929 <!-- ~ End section ~ -->
1932 <!-- ~~~~~ New section ~~~~~ -->
1934 <sect1 id="seealso"><title>See also</title>
1936 <!-- Include seealso.sgml -->
1947 Tue 09/11/01 06:38:14 PM EST: Test SGML doc by Hal Burgiss.
1949 Last modified: Mon Sep 10 19:22:09 CEST 2001
1951 This program is free software; you can redistribute it
1952 and/or modify it under the terms of the GNU General
1953 Public License as published by the Free Software
1954 Foundation; either version 2 of the License, or (at
1955 your option) any later version.
1957 This program is distributed in the hope that it will
1958 be useful, but WITHOUT ANY WARRANTY; without even the
1959 implied warranty of MERCHANTABILITY or FITNESS FOR A
1960 PARTICULAR PURPOSE. See the GNU General Public
1961 License for more details.
1963 The GNU General Public License should be included with
1964 this file. If not, you can view it at
1965 http://www.gnu.org/copyleft/gpl.html
1966 or write to the Free Software Foundation, Inc., 59
1967 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
1970 Revision 2.9 2002/10/29 03:22:22 hal9
1971 Add 3 FAQs relating to HTML in email. Other minor touch ups.
1973 Revision 2.8 2002/10/15 12:47:23 oes
1974 Added Microsuck faq; more detail for PHP problem
1976 Revision 2.7 2002/10/12 01:14:42 hal9
1977 Updates for demoronizer filter, Radical profile, and the srvany.exe/icon
1980 Revision 2.6 2002/10/10 04:10:38 hal9
1981 s/Advanced/Radical/ for standard.action change.
1983 Revision 2.5 2002/09/26 05:57:14 hal9
1984 Conditionally exclude 'this doc is evolving' comment in intro for non release
1987 Revision 2.4 2002/09/26 00:14:42 hal9
1988 Small additions for content-cookies/SSL, LAN configuration, and FTP (non)
1991 Revision 2.3 2002/09/13 11:50:55 oes
1992 Added MicroSuck topic; Updated PHP bug topic
1994 Revision 2.2 2002/09/05 04:25:05 hal9
1995 Sync with 3.0 branch. No new content.
1997 Revision 1.61.2.19 2002/08/25 23:31:56 hal9
1998 Fix one grammatical error. Add brief FAQ relating to tranparent proxies (ie
1999 port 80 setting). Add FAQ on effects of Privoxy on downloaded files
2000 (especially filtering).
2002 Revision 1.61.2.18 2002/08/14 16:39:37 hal9
2003 Fix wrong tag on FAQ addition.
2005 Revision 1.61.2.17 2002/08/14 00:01:18 hal9
2008 Revision 1.61.2.16 2002/08/13 00:10:38 hal9
2009 Add faq to troubleshooting re: blank page syndrome, ie {-prevent-compression}.
2011 Revision 1.61.2.15 2002/08/10 11:34:22 oes
2012 Add disclaimer about probably being out-of-date
2014 Revision 1.61.2.14 2002/08/07 02:53:43 hal9
2015 Fix some minor markup errors, and move one OSX Q/A to troubleshooting section.
2017 Revision 1.61.2.13 2002/08/06 11:55:32 oes
2018 Added missing close tag
2020 Revision 1.61.2.12 2002/08/06 11:43:46 david__schmidt
2021 Updated OSX uninstall FAQ... we have an uninstall script now.
2023 Revision 1.61.2.11 2002/08/06 08:54:03 oes
2024 Style police: Fixed formatting details
2026 Revision 1.61.2.10 2002/08/02 14:00:25 david__schmidt
2027 Made the OSX removal commands far less dangerous
2029 Revision 1.61.2.9 2002/08/02 13:14:45 oes
2030 Added warning about sudo rm -r for Mac OSX deinstallation; moved this item to install section
2032 Revision 1.61.2.8 2002/08/02 02:01:42 david__schmidt
2033 Add FAQ item for MSIE on OSX HTTP proxy confusion
2035 Revision 1.61.2.7 2002/08/02 01:46:01 david__schmidt
2036 Added FAQ item for Mac OSX uninstall woes
2038 Revision 1.61.2.6 2002/07/30 20:04:56 hal9
2039 Fix typo: 'schould'.
2041 Revision 1.61.2.5 2002/07/26 15:22:58 oes
2042 - Updated to reflect changes in standard.action
2043 - Added info on where to get updated actions files
2045 Revision 1.61.2.4 2002/07/25 21:42:29 hal9
2046 Add brief notes on not proxying non-HTTP protocols.
2048 Revision 1.61.2.3 2002/06/09 16:36:33 hal9
2049 Clarifications on filtering and MIME. Hardcode 'latest release' in index.html.
2051 Revision 1.61.2.2 2002/06/06 02:51:34 hal9
2052 Fix typo in URL http:/config.privoxy.org
2054 Revision 1.61.2.1 2002/06/05 23:10:43 hal9
2055 Add new FAQ re: DUN/IE. Change release date from May to June :)
2057 Revision 1.61 2002/05/25 12:37:25 hal9
2058 Various minor changes and edits.
2060 Revision 1.60 2002/05/22 17:17:48 oes
2061 Proofread & added more links into u-m
2063 Revision 1.59 2002/05/15 04:03:30 hal9
2064 Fix ulink -> link markup.
2066 Revision 1.58 2002/05/10 01:48:20 hal9
2067 This is mostly proposed copyright/licensing additions and changes. Docs
2068 are still GPL, but licensing and copyright are more visible. Also, copyright
2069 changed in doc header comments (eliminate references to JB except FAQ).
2071 Revision 1.57 2002/05/05 20:26:02 hal9
2072 Sorting out license vs copyright in these docs.
2074 Revision 1.56 2002/05/04 08:44:44 swa
2077 Revision 1.55 2002/05/04 00:41:56 hal9
2078 -Remove TOC/first page kludge in favor of proper handling via dsl file.
2080 Revision 1.54 2002/05/03 05:06:44 hal9
2081 Add brief Q/A on transparent proxies.
2083 Revision 1.53 2002/05/03 01:34:52 hal9
2084 Fix section numbering for new sections (due to TOC kludge).
2086 Revision 1.52 2002/04/29 03:08:43 hal9
2087 -Added new Q/A on new actions file set up (pointer to u-m)
2088 -Fixed a few broken links and converted old actions as a result of
2091 Revision 1.51 2002/04/26 17:24:31 swa
2092 bookmarks cleaned, changed structure of user manual, screen and programlisting cleanups, and numerous other changes that I forgot
2094 Revision 1.50 2002/04/26 05:25:23 hal9
2095 Mass commit to catch a few scattered fixes.
2097 Revision 1.49 2002/04/12 10:10:18 swa
2100 Revision 1.48 2002/04/10 18:45:15 swa
2103 Revision 1.47 2002/04/10 04:05:32 hal9
2106 Revision 1.45 2002/04/08 22:59:26 hal9
2107 Version update. Spell chkconfig correctly :)
2109 Revision 1.44 2002/04/07 21:24:29 hal9
2110 Touch up on name change.
2112 Revision 1.43 2002/04/04 21:59:53 hal9
2113 Added NT/W2K service/icon situation.
2115 Revision 1.42 2002/04/04 18:46:47 swa
2116 consistent look. reuse of copyright, history et. al.
2118 Revision 1.41 2002/04/04 06:48:37 hal9
2119 Structural changes to allow for conditional inclusion/exclusion of content
2120 based on entity toggles, e.g. 'entity % p-not-stable "INCLUDE"'. And
2121 definition of internal entities, e.g. 'entity p-version "2.9.13"' that will
2122 eventually be set by Makefile.
2123 More boilerplate text for use across multiple docs.
2125 Revision 1.40 2002/04/03 04:22:03 hal9
2126 Fixed several typos.
2128 Revision 1.39 2002/04/03 03:53:03 hal9
2129 Revert some changes, and then make some news, to layout, and appearance.
2131 Revision 1.38 2002/04/02 03:49:10 hal9
2132 Major changes to doc structure and layout. Sections are not automatically
2133 numbered now. TOC is on page by itself.
2135 Revision 1.37 2002/04/01 16:24:07 hal9
2136 -Rework of supported Q/A.
2137 -Set up entities to include boilerplate text.
2139 Revision 1.36 2002/03/31 23:18:47 hal9
2140 More on dealing with BLOCKED.
2142 Revision 1.35 2002/03/30 04:14:19 hal9
2143 Fix privoxy.org/config links.
2145 Revision 1.34 2002/03/29 04:35:56 hal9
2148 Revision 1.33 2002/03/29 01:31:48 hal9
2149 Several new Q/A's and other touch ups.
2151 Revision 1.32 2002/03/27 00:57:03 hal9
2152 Touch ups for name change.
2154 Revision 1.31 2002/03/26 22:29:55 swa
2155 we have a new homepage!
2157 Revision 1.30 2002/03/25 16:39:22 hal9
2158 A few new sections. Made all links relative to user-manual.
2160 Revision 1.29 2002/03/25 05:23:57 hal9
2161 Moved section, and touch ups.
2163 Revision 1.28 2002/03/25 04:27:33 hal9
2164 New section related to name change.
2166 Revision 1.25 2002/03/24 16:08:08 swa
2167 we are too lazy to make a block-built
2168 privoxy logo. hence removed the option.
2170 Revision 1.24 2002/03/24 15:46:20 swa
2171 name change related issue.
2173 Revision 1.23 2002/03/24 12:33:01 swa
2176 Revision 1.22 2002/03/24 11:51:00 swa
2177 name change. changed filenames.
2179 Revision 1.21 2002/03/24 11:01:06 swa
2182 Revision 1.20 2002/03/23 15:13:11 swa
2183 renamed every reference to the old name with foobar.
2184 fixed "application foobar application" tag, fixed
2185 "the foobar" with "foobar". left junkbustser in cvs
2186 comments and remarks to history untouched.
2188 Revision 1.19 2002/03/21 17:01:54 hal9
2191 Revision 1.18 2002/03/18 16:40:31 hal9
2194 Revision 1.17 2002/03/18 03:53:53 hal9
2197 Revision 1.16 2002/03/17 21:32:56 hal9
2198 A few more additions.
2200 Revision 1.15 2002/03/17 07:25:59 hal9
2201 Correcting some of my typos, and some additions.
2203 Revision 1.14 2002/03/17 02:39:13 hal9
2204 A little more added ...
2206 Revision 1.13 2002/03/17 00:22:20 hal9
2207 Adding new stuff, and trying to incorporate stuff from old faq.
2209 Revision 1.12 2002/03/11 20:13:21 swa
2212 Revision 1.11 2002/03/11 18:42:27 swa
2215 Revision 1.10 2002/03/11 13:13:27 swa
2216 correct feedback channels
2218 Revision 1.9 2002/03/10 23:34:04 swa
2219 more info on not hiding ip address
2221 Revision 1.8 2002/03/09 15:55:48 swa
2222 added default config section
2224 Revision 1.7 2002/03/07 18:16:55 swa
2227 Revision 1.6 2002/03/07 13:16:31 oes
2228 Committing changes by Stefan
2230 Revision 1.5 2002/03/02 15:50:04 swa
2231 2.9.11 version. more input for docs.
2233 Revision 1.4 2002/02/24 14:34:24 jongfoster
2234 Formatting changes. Now changing the doctype to DocBook XML 4.1
2235 will work - no other changes are needed.
2237 Revision 1.3 2001/09/23 10:13:48 swa
2238 upload process established. run make webserver and
2239 the documentation is moved to the webserver. documents
2240 are now linked correctly.
2242 Revision 1.2 2001/09/13 15:20:17 swa
2243 merged standards into developer manual
2245 Revision 1.1 2001/09/12 15:36:41 swa
2246 source files for junkbuster documentation
2248 Revision 1.3 2001/09/10 17:43:59 swa
2249 first proposal of a structure.
2251 Revision 1.2 2001/06/13 14:28:31 swa
2252 docs should have an author.
2254 Revision 1.1 2001/06/13 14:20:37 swa
2255 first import of project's documentation for the webserver.