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 1.62 2002/06/03 00:28:16 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.
54 ========================================================================
60 <article id="index" class="faq">
62 <title>Privoxy Frequently Asked Questions</title>
66 <!-- Completely the wrong markup, but very little is allowed -->
67 <!-- in this part of an article. FIXME -->
68 <link linkend="copyright">Copyright</link> &my-copy; 2001, 2002 by
69 <ulink url="http://www.privoxy.org">Privoxy Developers</ulink>
73 <pubdate>$Id: faq.sgml,v 1.62 2002/06/03 00:28:16 hal9 Exp $</pubdate>
77 Note: this should generate a separate page, and a live link to it.
78 But it doesn't for some mysterious reason. Please leave commented
79 unless it can be fixed proper. For the time being, the copyright
80 statement will be in copyright.smgl.
84 <legalnotice id="legalnotice">
86 text goes here ........
96 <orgname>By: Privoxy Developers</orgname>
105 This is here to keep vim syntax file from breaking :/
106 If I knew enough to fix it, I would.
107 PLEASE DO NOT REMOVE! HB: hal@foobox.net
112 This FAQ gives quick answers to frequently asked questions about
113 <ulink url="http://www.privoxy.org/">Privoxy</ulink>
114 <![%p-stable;[ v.&p-version]]>. It can't and doesn't replace the
115 <ulink url="../user-manual/index.html">user manual</ulink>.
118 <!-- Include privoxy.sgml boilerplate: -->
120 <!-- end boilerplate -->
123 You can find the latest version of the document at <ulink
124 url="http://www.privoxy.org/faq/">http://www.privoxy.org/faq/</ulink>.
125 Please see the Contact section if you want to contact the developers.
129 <!-- Feel free to send a note to the developers at <email>ijbswa-developers@lists.sourceforge.net</email>. -->
135 <!-- ~~~~~ New section ~~~~~ -->
137 <sect1 id="general"><title>General Information</title>
139 <sect2 renderas="sect3" id="newjb"><title>What is this new version of <application>Privoxy</application>?</title>
141 <!-- Include history.sgml -->
148 <sect2 renderas="sect3">
149 <title id="whyprivoxy">Why <quote>Privoxy</quote>? Why a name change at all?</title>
151 <application>Privoxy</application> is the
152 <quote><emphasis>Privacy Enhancing Proxy</emphasis></quote>. Also, its content
153 modification and junk suppression allow you to browse your
154 <quote><emphasis>private</emphasis> edition</quote> of the web.
157 <ulink url="http://junkbusters.com/">Junkbusters Corporation</ulink>
158 continues to offer their original version of the <application>Internet
159 Junkbuster</application>, so publishing our
160 <application> Junkbuster</application>-derived software under the same name
164 There are also potential legal complications from the continued use of the
165 <application>Junkbuster</application> name, which is a registered trademark of
166 <ulink url="http://junkbusters.com/">Junkbusters Corporation</ulink>.
167 There are, however, no objections from Junkbusters Corporation to the
168 <application>Privoxy</application> project itself, and they, in fact, still
169 share our ideals and goals.
172 The developers also believed that there are so many changes from the original
173 code, that it was time to make a clean break from the past and make
174 a name in their own right<![%p-not-stable;[, especially now with the pending
175 release of version 3.0]]>.
180 <sect2 renderas="sect3" id="differs"><title>How does <application>Privoxy</application> differ
181 from the old <application>Junkbuster?</application></title>
183 <application>Privoxy</application> picks up where
184 <application>Junkbuster</application> left off. All the old features remain.
185 The new <application>Privoxy</application> still blocks ads and banners,
186 still manages cookies, and still helps protect your privacy. But, these are
187 all enhanced, and many new features have been added, all in the same vein.
190 The configuration has changed significantly as well. This is something that
191 users will notice right off the bat if upgrading from
192 <application>Junkbuster</application> 2.0.x. The <quote>blocklist</quote>
193 <quote>cookielist</quote>, <quote>imagelist</quote> and much more has been
194 combined into the <quote>actions</quote> files, with a completely different
195 syntax. See the <ulink url="../user-manual/upgradersnote.html">note to
196 upgraders</ulink> for details.
199 <application>Privoxy</application>'s new features include:
202 <!-- Include newfeatures.sgml: -->
208 <sect2 renderas="sect3" id="proxymoron"><title>What is a <quote>proxy</quote>? How does
209 <application>Privoxy</application> work? </title>
211 A web proxy is a service, based on a software such as <application>Privoxy</application>,
212 that clients (i.e. browsers) can use instead of connecting directly to the web
213 servers on the Internet. The clients then ask the proxy to fetch the objects
214 they need (web pages, images, movies etc) on their behalf, and when the proxy
215 has done so, it hands the results back to the client.
218 There are many reasons to use web proxies, such as security (firewalling),
219 efficiency (caching) and others, and there are just as many different proxies
220 to accommodate those needs.
223 <application>Privoxy</application> is a proxy that is solely focused on privacy
224 protection and junk elimination. Sitting between your browser(s) and the Internet,
225 it is in a perfect position to filter outbound personal information that your
226 browser is leaking, as well as inbound junk. It uses a variety of techniques to do
227 this, all of which are under your control via the various configuration
233 <sect2 renderas="sect3" id="whatsanad">
234 <title id="knows">How does <application>Privoxy</application> know what is
235 an ad, and what is not?</title>
237 <application>Privoxy</application>'s approach to blocking ads is twofold:
240 First, there are certain patterns in the <emphasis>locations</emphasis> (URLs)
241 of banner images. This applies to both the path (you wouldn't guess how many
242 web sites serve their banners from a directory called <quote>banners</quote>!)
243 and the host (blocking the big banner hosting services like doublecklick.net
244 already helps a lot). <application>Privoxy</application> takes advantage of this
245 fact by using <ulink url="../user-manual/actions-file.html#AF-PATTERNS">URL
246 patterns</ulink> to sort out and block the requests for banners.
249 Second, banners tend to come in certain <emphasis>sizes</emphasis>. But you
250 can't tell the size of an image by its URL without downloading it, and if you
251 do, it's too late to save bandwidth. Therefore, <application>Privoxy</application>
252 also inspects the HTML sources of web pages while they are loaded, and replaces
253 references to images with standard banner sizes by dummy references, so that
254 your browser doesn't request them anymore in the first place.
257 Both of this involves a certain amount of guesswork and is, of course, freely
262 <sect2 renderas="sect3">
263 <title id="mistakes">Can <application>Privoxy</application> make mistakes?
264 This does not sound very scientific.</title>
266 Actually, it's a black art ;-) And yes, it is always possible to have a broad
267 rule accidentally block or change something by mistake. There is a good chance
268 you may run into such a situation at some point. It is tricky writing rules to
269 cover every conceivable possibility, and not occasionally get false positives.
273 But this should not be a big concern since the
274 <application>Privoxy</application> configuration is very flexible, and
275 includes tools to help identify these types of situations so they can be
276 addressed as needed, allowing you to customize your installation.
277 (<link linkend="badsite">See the Troubleshooting section below</link>.)
283 <sect2 renderas="sect3" id="browsers2"><title>My browser does the same things as
284 <application>Privoxy</application>. Why should I use
285 <application>Privoxy</application> at all?</title>
287 Modern browsers do indeed have <emphasis>some</emphasis> of the same
288 functionality as <application>Privoxy</application>. Maybe this is
289 adequate for you. But <application>Privoxy</application> is much more
290 versatile and powerful, and can do a number of things that browsers just can't.
293 In addition, a proxy is good choice if you use multiple browsers, or
294 have a LAN with multiple computers. This way all the configuration
295 is in one place, and you don't have to maintain a similar configuration
296 for possibly many browsers.
302 <sect2 renderas="sect3" id="license"><title>Is there is a license or fee? What about a
303 warranty? Registration?</title>
305 <application>Privoxy</application> is licensed under the <ulink
306 url="http://www.gnu.org/copyleft/gpl.html">GNU General Public License (GPL)</ulink>.
307 It is free to use, copy, modify or distribute as you wish under the terms of this
308 license. Please see the <link linkend="copyright">Copyright</link> section for more
309 information on the license and copyright. Or the <filename>LICENSE</filename> file
310 that should be included.
313 There is <emphasis>no warranty</emphasis> of any kind, expressed, implied or otherwise.
314 That is something that would cost real money ;-) There is no registration either.
315 <application>Privoxy</application> really is <emphasis>free</emphasis>
321 <sect2 renderas="sect3" id="jointeam"><title>I would like to help you, what do I do?</title>
323 <sect3 renderas="sect4" id="jointeam-money"><title>Money Money Money</title>
325 We, of course, welcome donations and could use money for domain registering,
326 buying software to test <application>Privoxy</application> with, and, of course,
327 for regular world-wide get-togethers (hahaha). If you enjoy the software and feel
328 like helping us with a donation, just <ulink
329 url="mailto:developers@privoxy.org">drop us a note</ulink>.
333 <sect3 renderas="sect4" id="jointeam-software"><title>Software</title>
335 If you are a vendor of a web-related software like a browser, web server
336 or proxy, and would like us to ensure that <application>Privoxy</application>
337 runs smoothly with your product, you might consider supplying us with a
338 copy or license. We can't, however, guarantee that we will fix all potential
339 compatibility issues as a result.
343 <sect3 renderas="sect4" id="jointeam-work"><title>You want to work with us?</title>
345 Well, helping the team is always a good idea. We welcome new developers,
346 packaging gurus or documentation writers. Simply <ulink
347 url="https://sourceforge.net/account/register.php">get an account on SourceForge.net</ulink>
348 and mail your id to the <ulink url="mailto:developers@privoxy.org">developers
349 mailing list</ulink>. Then read the <ulink
350 url="../developer-manual/index.html">Developer's Manual</ulink>.
353 Once we have added you to the team, you'll have write access to the <ulink
354 url="http://sourceforge.net/cvs/?group_id=11118">CVS repository</ulink>, and
355 together we'll find a suitable task for you.
364 <!-- ~~~~~ New section ~~~~~ -->
366 <sect1 id="installation"><title>Installation</title>
368 <sect2 renderas="sect3" id="whichbrowsers">
369 <title>Which browsers are supported by <application>Privoxy</application>?</title>
371 Any browser that can be configured to use a proxy, which
372 should be virtually all browsers. Direct browser support is not necessary
373 since <application>Privoxy</application> runs as a separate application and
374 talks to the browser in the standardized HTTP protocol, just like a web server
379 <sect2 renderas="sect3" id="whichos">
380 <title>Which operating systems are supported?</title>
382 Include supported.sgml here:
387 <sect2 renderas="sect3" id="newinstall"><title>Can I install
388 <application>Privoxy</application> over <application>Junkbuster</application>?</title>
390 We recommend you un-install <application>Junkbuster</application>
391 first to minimize conflicts and confusion. You may want to
392 save your old configuration files for future reference. The configuration
393 files and syntax have substantially changed, so you will need to manually
394 port your old patterns. See the <ulink url="../user-manual/upgradersnote.html">note
395 to upgraders</ulink> and <ulink url="../user-manual/installation.html">installation
396 chapter</ulink> in the <ulink url="../user-manual/index.html">user manual</ulink>
400 Note: Some installers may automatically un-install
401 <application>Junkbuster</application>, if present!
406 <sect2 renderas="sect3">
407 <title id="firststep">I just installed <application>Privoxy</application>. Is there anything
408 special I have to do now?</title>
411 All browsers must be told to use <application>Privoxy</application>
412 as a proxy by specifying the correct proxy address and port number
413 in the appropriate configuration area for the browser. See below.
414 You should also flush your browser's memory and disk cache to get rid of any
422 <sect2 renderas="sect3" id="localhost"><title>What is the proxy address of <application>Privoxy</application>?</title>
424 If you set up the <application>Privoxy</application> to run on
425 the computer you browse from (rather than your ISP's server or some
426 networked computer on a LAN), the proxy will be on <literal>127.0.0.1</literal>
427 (sometimes referred to as <quote>localhost</quote>,
428 which is the special name used by every computer on the Internet to refer
429 to itself) and the port will be 8118 (unless you have <application>Privoxy</application>
430 to run on a different port with the <ulink
431 url="../user-manual/config.html#LISTEN-ADDRESS">listen-address</ulink> config option).
434 When configuring your browser's proxy settings you typically enter
435 the word <quote>localhost</quote> or the IP address <quote>127.0.0.1</quote>
436 in the boxes next to <quote>HTTP</quote> and <quote>Secure</quote> (HTTPS) and
437 then the number <quote>8118</quote> for <quote>port</quote>.
438 This tells your browser to send all web requests to <application>Privoxy</application>
439 instead of directly to the Internet.
442 <application>Privoxy</application> can also be used to proxy for
443 a Local Area Network. In this case, your would enter either the IP
444 address of the LAN host where <application>Privoxy</application>
445 is running, or the equivalent hostname. Port assignment would be
446 same as above. Note that <application>Privoxy</application> doesn't
447 listen on any LAN interfaces by default.
450 <application>Privoxy</application> does not currently handle
451 protocols such as FTP, SMTP, IM, IRC, ICQ, or other Internet
456 <sect2 renderas="sect3">
457 <title id="nothing">I just installed <application>Privoxy</application>, and nothing is happening.
458 All the ads are there. What's wrong?</title>
461 Did you configure your browser to use <application>Privoxy</application>
462 as a proxy? It does not sound like it. See above. You might also try flushing
463 the browser's caches to force a full re-reading of pages. You can verify
464 that <application>Privoxy</application> is running, and your browser
465 is correctly configured by entering the special URL:
466 <ulink url="http:/config.privoxy.org/">http://config.privoxy.org/</ulink>.
467 This should take you to a page titled <quote>This is Privoxy..</quote> with
468 access to <application>Privoxy's</application> internal configuration.
469 If you see this, then you are good to go. If you receive a page saying
470 <quote>Privoxy is not running</quote>, then the browser is not set up to use
471 your <application>Privoxy</application> installation.
472 If you receive anything else (probably nothing at all), it could either
473 be that the browser is not set up correctly, or that
474 <application>Privoxy</application> is not running at all. Check the <ulink
475 url="../user-manual/config.html#LOGFILE">log file</ulink>.
485 <!-- ~~~~~ New section ~~~~~ -->
487 <sect1 id="configuration"><title>Configuration</title>
489 <sect2 renderas="sect3" id="newconfig"><title>Can I use my old config files?</title>
491 The syntax, number, and purpose of configuration files has substantially
492 changed from <application>Junkbuster</application> and earlier versions
493 of <application>Privoxy</application>. The old files, like <filename>blocklist</filename>
494 will not work at all. If you are upgrading from a 2.0.x version, you will
495 need to port your configuration data to the new format. Note that even the
496 pattern syntax has changed! Even configuration files from the 2.9.x versions
497 will need to be adapted, as configuration syntax has been very much in flow
502 <sect2 renderas="sect3">
503 <title id="actionsfile">What is an <quote>actions</quote> file?</title>
506 <ulink url="../user-manual/actions-file.html">Actions files</ulink>
507 are where various <ulink url="../user-manual/actions-file.html#ACTIONS">actions</ulink>
508 that <application>Privoxy</application> might take while processing a certain
509 request, are configured. Typically, you would define a set of default actions
510 that apply to all URLs, then add exceptions to these defaults where needed.
514 Actions can be defined on a <ulink
515 url="../user-manual/actions-file.html#AF-PATTERNS">URL pattern</ulink> basis, i.e.
516 for single URLs, whole web sites, groups or parts thereof etc. Actions can also be
517 grouped together and then applied to requests matching one or more patterns.
518 There are many possible actions that might apply to any given site. As an example,
519 if you are blocking cookies as one of your default actions, but need to accept
520 cookies from a given site, you would need to define an exception for this
521 site in one of your actions files, preferably in <filename>user.action</filename>
526 <sect2 renderas="sect3" id="actionss">
527 <title>The <quote>actions</quote> concept confuses me. Please list
528 some of these <quote>actions</quote>.</title>
530 For a comprehensive discussion of the actions concept, please refer
531 to the <ulink url="../user-manual/actions-file.html">actions file
532 chapter</ulink> in the <ulink url="../user-manual/index.html">user
533 manual</ulink>. It includes a <ulink
534 url="../user-manual/actions-file.html#ACTIONS">list of all actions</ulink>
535 and an <ulink url="../user-manual/actions-file.html#ACT-EXAMPLES">actions
536 file tutorial</ulink> to get you started.
541 <sect2 renderas="sect3">
542 <title id="actconfig">How are actions files configured? What is the easiest
543 way to do this?</title>
546 Actions files are just text files in a special syntax and can be edited
547 with a text editor. The probably easiest way is to access
548 <application>Privoxy</application>'s user interface with your web browser
549 at <ulink url="http://config.privoxy.org/">http://config.privoxy.org/</ulink>
550 (Shortcut: <ulink url="http://p.p/">http://p.p/</ulink>) and then select
551 <quote><ulink url="http://config.privoxy.org/show-status">View &
552 change the current configuration</ulink></quote> from the menu.
557 <!-- ~~~~~ New section ~~~~~ -->
558 <sect2 renderas="sect3">
559 <title>There are several different <quote>actions</quote> files. What are
560 the differences?</title>
562 As of <application>Privoxy</application> v2.9.15, three actions files
563 are being included, to be used for
564 different purposes: These are
565 <filename>default.action</filename>, the <quote>main</quote> actions file
566 which is actively maintained by the <application>Privoxy</application>
567 developers, <filename>user.action</filename>, where users are encouraged
568 to make their private customizations, and <filename>standard.action</filename>,
569 which is for internal <application>Privoxy</application> use only.
570 Please see <ulink url="../user-manual/actions-file.html">the actions chapter</ulink>
571 in the <ulink url="../user-manual/index.html">user manual</ulink> for a more
572 detailed explanation.
576 Earlier versions included three different versions of the
577 <filename>default.action</filename> file. The new scheme allows for
578 greater flexibility of local configuration, and for browser based
579 selection of pre-defined <quote>aggressiveness</quote> levels.
584 <sect2 renderas="sect3" id="yahoo"><title>How can I make my Yahoo/Hotmail/GMX account work?</title>
586 The default configuration shouldn't impact the usability of any of these services.
587 It will, however, make all cookies temporary, so that your browser will forget your
588 login credentials in between browser sessions. If you would like not to have to log
589 in manually each time you access those websites, simply turn off all cookie handling
590 for them in the <filename>user.action</filename> file. An example for yahoo might
594 <screen># Allow all cookies for Yahoo login:
596 { -<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> }
597 .login.yahoo.com</screen>
602 <sect2 renderas="sect3" id="configfiles"> <title>What's the difference between the
603 <quote>Cautious</quote>, <quote>Medium</quote> and <quote>Advenced</quote> defaults?</title>
605 Configuring <application>Privoxy</application> is not entirely trivial. To help you get
606 started, we provide you with three different default action <quote>packages</quote> in
607 the web based actions file editor at <ulink
608 url="http://config.privoxy.org/show-status">http://config.privoxy.org/show-status</ulink>.
609 The following table shows you, which of the most important features are enabled in each
613 <table frame=all><title>Default Configurations</title>
614 <tgroup cols=4 align=left colsep=1 rowsep=1>
621 <entry>Feature</entry>
622 <entry>Cautious</entry>
623 <entry>Intermadiate</entry>
624 <entry>Advanced</entry>
629 <!-- <entry>f1</entry> -->
630 <!-- <entry>f2</entry> -->
631 <!-- <entry>f3</entry> -->
632 <!-- <entry>f4</entry> -->
638 <entry>Ad-blocking by URL</entry>
645 <entry>Ad-filtering by size</entry>
652 <entry>GIF de-animation</entry>
659 <entry>Referer forging</entry>
666 <entry>Cookie handling</entry>
668 <entry>session-only</entry>
673 <entry>Pop-up killing</entry>
680 <entry>Fast redirects</entry>
687 <entry>HTML taming</entry>
694 <entry>JavaScript taming</entry>
701 <entry>Web-bug killing</entry>
708 <entry>Fun text replacements</entry>
719 Where the defaults are likely to break some sites, exceptions for
720 known popular <quote>problem</quote> sites are included, but in
721 general, the more aggressive your default settings are, the more
722 exceptions you will have to make later. See the <ulink
723 url="../user-manual/index.html">user manual</ulink> for a more
729 <sect2 renderas="sect3" id="browseconfig"> <title>Why can I change the configuration
730 with a browser? Does that not raise security issues?</title>
732 It may seem strange that regular users can edit the config files with their
733 browsers, although the whole <filename>/etc/privoxy</filename> hierarchy
734 belongs to the user <quote>privoxy</quote>, with only 644 permissions.
737 When you use the browser-based editor, <application>Privoxy</application>
738 itself is writing to the config files. Because
739 <application>Privoxy</application> is running as the user <quote>privoxy</quote>,
740 it can update the config files.
743 If you run <application>Privoxy</application> for multiple untrusted users (e.g. in
744 a LAN), you will probably want to turn the web-based editor and remote toggle
745 features off by setting <quote><literal><ulink
746 url="../user-manual/config.html#ENABLE-EDIT-ACTIONS">enable-edit-actions</ulink>
747 0</literal></quote> and <quote><literal><ulink
748 url="../user-manual/config.html#ENABLE-REMOTE-TOGGLE">enable-remote-toggle</ulink>
749 0</literal></quote> in the <ulink url="../user-manual/config.html">main configuration file</ulink>.
752 Note that in the default configuration, only local users (i.e. those on
753 <quote>localhost</quote>) can connect to <application>Privoxy</application>,
754 so this is not (normally) a security problem.
759 <sect2 renderas="sect3">
760 <title id="filterfile">What is the <filename>default.filter</filename> file?</title>
762 The <ulink url="../user-manual/filter-file.html"><filename>default.filter</filename></ulink>
763 file is where <emphasis>filters</emphasis> are defined, which can be used to modify or
764 remove, web page content on the fly. This applies to <emphasis>anything</emphasis>
765 in the page source, including HTML tags, and JavaScript. Regular expressions are used
766 to accomplish this. There are a number of pre-defined filters to deal with common
767 annoyances. The filters are only defined here, to invoke them, you need to use the
768 <ulink url="../user-manual/actions-file.html#FILTER"><literal>filter</literal> action</ulink>.
772 If you are familiar with regular expressions, and HTML, you can look at
773 the provided <filename>default.filter</filename> with a text editor and define
774 your own filters. This is potentially a very powerful feature, but
775 requires some expertise.
779 Presently, there is no GUI editor option for this part of the configuration,
780 but you can disable/enable the various pre-defined filters of the included
781 <filename>default.filter</filename> file with the <ulink
782 url="http://config.privoxy.org/show-status">web-based actions file editor</ulink>.
787 <sect2 renderas="sect3">
788 <title id="lanconfig">How can I set up <application>Privoxy</application> to act as a proxy for my
791 By default, <application>Privoxy</application> only responds to requests
792 from <literal>127.0.0.1</literal> (localhost). To have it act as a server for
793 a network, this needs to be changed in the <ulink
794 url="../user-manual/config.html">main configuration file</ulink>. Look for
796 url="../user-manual/config.html#LISTEN-ADDRESS">listen-address</ulink></literal>
797 option, which may be commented out with a <quote>#</quote> symbol. Make sure
798 it is uncommented, and assign it the address of the LAN gateway interface,
799 and port number to use. Assuming your LAN address is 192.168.1.1 and you
800 wish to run <application>Privoxy</application> on port 8118, this line
806 listen-address 192.168.1.1:8118</screen>
810 Save the file, and restart <application>Privoxy</application>. Configure
811 all browsers on the network then to use this address and port number.
815 If you run <application>Privoxy</application> on a LAN with untrusted users,
816 we recommend that you double-check the <ulink
817 url="../user-manual/config.html#ACCESS-CONTROL">access control and security</ulink>
824 <sect2 renderas="sect3">
825 <title id="noseeum">Instead of ads, now I get a checkerboard pattern. I don't want to see anything.</title>
827 The replacement for blocked images can be controlled with the <ulink
828 url="../user-manual/actions-file.html#SET-IMAGE-BLOCKER"><literal>set-image-blocker</literal>
829 action</ulink>. You have the choice of a checkerboard pattern, a transparent 1x1 GIF
830 image (aka <quote>blank</quote>), or a redirect to a custom image of your choice.
831 Note that this choice only has effect for images which are blocked as images, i.e.
832 whose URLs match both a <literal><ulink
833 url="../user-manual/actions-file.html#HANDLE-AS-IMAGE">handle-as-image</ulink></literal>
834 <emphasis>and</emphasis> <literal><ulink
835 url="../user-manual/actions-file.html#BLOCK">block</ulink></literal> action.
838 If you want to see nothing, then change the <ulink
839 url="../user-manual/actions-file.html#SET-IMAGE-BLOCKER"><literal>set-image-blocker</literal>
840 action</ulink> to <quote>blank</quote>. This can be done by editing the
841 <filename>default.action</filename> file, or trough the <ulink
842 url="http://config.privoxy.org/show-status">web-based actions file editor</ulink>.
847 <sect2 renderas="sect3">
848 <title id="whyseeum">Why would anybody want to see a checkerboard pattern?</title>
850 Remember that <link linkend="whatsanad">telling which image is an ad and which
851 isn't</link>, is mostly guesswork. While we hope that the standard configuration
852 is rather smart, it can and will make errors. The checkerboard image is visually
853 decent, but it shows you that and where images were blocked, which can be very
854 helpful in case some navigation aid or otherwise innocent image was
855 erraneously blocked. Some people might also enjoy seeing how many banners
856 they <emphasis>don't</emphasis> have to see..
861 <!-- This has changed with the adaptive "blocked" page
863 <sect2 renderas="sect3">
864 <title id="blockedisugly">I see large red banners on some pages that say
865 <quote>Blocked</quote>. Why and how do I get rid of this?</title>
867 These are URLs that match something in one of
868 <application>Privoxy's</application> block actions
870 url="../user-manual/actions-file.html#BLOCK"><quote>+block</quote></ulink>).
871 It is meant to be a warning so that you know something has been blocked and
872 an easy way for you to see why. These are handled differently than what has
873 been defined explicitly as <quote>images</quote> (e.g. ads that are GIF image
874 files). Depending on the URL itself, it is sometimes hard for
875 <application>Privoxy</application> to really know whether there is indeed an
876 ad image there or not. And there are limitations as to what
877 <application>Privoxy</application> can do to <quote>fool</quote> the
882 For instance, if the ad is in a frame, then it is embedded in the separate
883 HTML page used for the frame. In this case, you cannot just substitute an
884 aribitrary image (like we would for a <quote>blank</quote> image), for an HTML
885 page. The browser is expecting an HTML page, and that is what it must have
886 for frames. Such situations can be a little trickier to deal with, and
887 <application>Privoxy</application> may show the <quote>Blocked</quote> page,
888 despite your best efforts.
892 If you want these to be treated as if they were images, so that they can be
893 made invisible, you can try moving the offending URL from the
894 <quote>+block</quote> section to the <quote>+imageblock</quote> section of
895 your actions file. Just be forewarned, if any URL is made
896 <quote>invisible</quote>, you may not have any inkling that something has
897 been removed from that page, or why. If this approach does not work, then you are
898 probably dealing with a frame (or <quote>ilayer</quote>), and the only thing
899 that can go there is an HTML page of some sort.
902 To deal with this situation, you could modify the
903 <quote><filename>block</filename></quote> HTML template that is used by
904 <application>Privoxy</application> to display this, and make it something
905 more to your liking. Currently, there is no configuration option for this.
906 You will have to modify, or create your own page, and use this to replace
907 <filename>templates/blocked</filename>, which is what
908 <application>Privoxy</application> uses to display the <quote>Blocked</quote>
912 Another way to deal with this is find why and where
913 <application>Privoxy</application> is blocking the frame, and
914 diable this. Then let the <quote>+set-image-blocker</quote> action
915 handle the ad that is embedded in the frame's HTML page.
920 <sect2 renderas="sect3" id="alliseeisred">
921 <title>I cannot see all of the <quote>Blocked</quote> page banner. Help.</title>
923 There is not enough available space to fit the entire Blocked page. Try right
924 clicking on the visible portion, and select <quote>Show Frame</quote>,
925 or equivalent. This will usually allow you to see the entire Privoxy
926 <quote>Blocked</quote> page, and from there you can see just what is being
930 As of Privoxy 2.9.14, the Blocked banner page is re-sizeable, and tries
931 to adjust to the allotted space. There may be occassions where there
932 just isn't enough room to display much of anything useful though.
939 <sect2 renderas="sect3">
940 <title id="blockedbytext">I see some images being replaced by a text
941 instead of the checkerboard image. Why and how do I get rid of this?</title>
943 This happens when the banners are not embedded in the HTML code of the
944 page itself, but in separate HTML (sub)documents that are loaded into (i)frames
945 or (i)layers, and these external HTML documents are blocked. Being non-images
946 they get replaced by a substitute HTML page rather than a substitute image,
947 which wouldn't work out technically, since the browser expects and accepts
948 only HTML when it has requested an HTML document.
951 The substitute page adapts to the available space and shows itself as a
952 miniature two-liner if loaded into small frames, or full-blown with a
953 large red "BLOCKED" banner if space allows.
956 If you prefer the banners to be blocked by images, you must see to it that
957 the HTML documents in which they are embedded are not blocked. Clicking
958 the <quote>See why</quote> link offered in the substitute page will show
959 you which rule blocked the page. After changing the rule and un-blocking
960 the HTML documents, the browser will try to load the actual banner images
961 and the usual image blocking will (hopefully!) kick in.
966 <sect2 renderas="sect3" id="srvany">
967 <title>Can <application>Privoxy</application> run as a service
970 Yes, it can run as a system service using <command>srvany.exe</command>.
971 The only catch is that this will effectively disable the
972 <application>Privoxy</application> icon (and its menu!) in the taskbar. You can have
973 one or the other, but not both at this time :(
976 There is a pending feature request for this functionality. See the discussion
978 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>,
979 for details, and a sample configuration.
985 <sect2 renderas="sect3" id="otherproxy">
986 <title>How can I make <application>Privoxy</application> work with other
987 proxies like <application>Squid</application>?</title>
989 This can be done and is often useful to combine the benefits of
990 <application>Privoxy</application> with those of a caching proxy.
992 url="../user-manual/config.html#FORWARDING">forwarding chapter</ulink>
993 in the <ulink url="../user-manual/index.html">user manual</ulink> which
994 describes how to do this.
998 <sect2 renderas="sect3" id="transparent">
999 <title>Can <application>Privoxy</application> run as a <quote>transparent
1000 </quote> proxy?</title>
1002 No, <application>Privoxy</application> currently does not have this ability,
1003 though it is planned for a future release. Transparent proxies require
1004 special handling of the request headers beyond what
1005 <application>Privoxy</application> is now capable of.
1009 Chaining <application>Privoxy</application> behind another proxy that has
1010 this ability should work though.
1012 url="../user-manual/config.html#FORWARDING">forwarding chapter</ulink>
1013 in the <ulink url="../user-manual/index.html">user manual</ulink>. As
1014 a transparent proxy to be used for chaining we recommend Transproxy
1015 (<ulink url="http://www.transproxy.nlc.net.au/">http://www.transproxy.nlc.net.au/</ulink>).
1022 <!-- ~ End section ~ -->
1025 <!-- ~~~~~ New section ~~~~~ -->
1027 <sect1 id="misc"><title>Miscellaneous</title>
1029 <sect2 renderas="sect3">
1030 <title id="slowsme">How much does <application>Privoxy</application> slow my browsing down? This
1031 has to add extra time to browsing.</title>
1033 It should not slow you down any in real terms, and may actually help
1034 speed things up since ads, banners and other junk are not being displayed.
1035 The actual processing time required by <application>Privoxy</application>
1036 itself for each page, is relatively small in the overall scheme of things,
1037 and happens very quickly. This is typically more than offset by time saved
1038 not downloading and rendering ad images.
1042 <quote>Filtering</quote> content via the <literal><ulink
1043 url="../user-manual/actions-file.html#FILTER">filter</ulink></literal> or
1045 url="../user-manual/actions-file.html#DEANIMATE-GIFS">deanimate-gifs</ulink></literal>
1046 actions may cause a perceived slowdown, since the entire document needs to be buffered
1047 before displaying. See below.
1053 <sect2 renderas="sect3" id="loadingtimes"><title>I noticed considerable
1054 delays in page requests compared to the old Junkbuster. What's wrong?</title>
1056 If you use any <literal><ulink
1057 url="../user-manual/actions-file.html#FILTER">filter</ulink></literal> action,
1058 such as filtering banners by size, web-bugs etc, or the <literal><ulink
1059 url="../user-manual/actions-file.html#DEANIMATE-GIFS">deanimate-gifs</ulink></literal>
1060 action, the entire document must be loaded into memory in order for the filtering
1061 mechanism to work, and nothing is sent to the browser during this time.
1064 The loading time does not really change in real numbers, but the feeling is
1065 different, because most browsers are able to start rendering incomplete
1066 content, giving the user a feeling of "it works". This effect is especially
1067 noticeable on slow dialup connections.
1072 <sect2 renderas="sect3" id="configurl"><title>What are "http://config.privoxy.org/" and
1073 "http://p.p/"?</title>
1075 <ulink url="http://config.privoxy.org/">http://config.privoxy.org/</ulink> is the
1076 address of <application>Privoxy</application>'s built-in user interface, and
1077 <ulink url="http://p.p/">http://p.p/</ulink> is a shortcut for it.
1080 Since <application>Privoxy</application> sits between your web browser and the Internet,
1081 it can simply intercept requests for these addresses and answer them with its built-in
1082 <quote>web server</quote>.
1085 This also makes for a good test for your browser configuration: If entering the
1086 URL <ulink url="http://config.privoxy.org/">http://config.privoxy.org/</ulink>
1087 takes you to a page saying <quote>This is Privoxy..</quote>, everything is OK.
1088 If you get a page saying <quote>Privoxy is not working</quote> instead, then
1089 your browser didn't use <application>Privoxy</application> for the request,
1090 hence it could not be intercepted, and you have accessed the <emphasis>real</emphasis>
1091 web site at config.privoxy.org.
1094 With recent versions of <application>Privoxy</application> (version 2.9.x and
1095 later), the user interface features information on the run time status, the
1096 configuration, and even a built-in editor for the <ulink
1097 url="../user-manual/actions-file.html">actions files</ulink>.
1101 Note that the built-in URLs from earlier versions of <application>Junkbuster</application>
1102 / <application>Privoxy</application>, http://example.com/show-proxy-args and http://i.j.b/,
1103 are no longer supported. If you still use such an old version, you should really consider
1104 upgrading to &p-version;.
1109 FIXME: commented out until we have data. HB 03/18/02.
1111 <sect2 renderas="sect3" id="badfiledesc"><title>I get the message 'Bad File Descriptor', why?</title>
1119 <sect2 renderas="sect3" id="blocklist"><title>Do you still maintain the blocklists?</title>
1121 No. The patterns for blocking now reside (among other things) in the <ulink
1122 url="../user-manual/actions-file.html">actions files</ulink>, which are
1123 actively maintained instead. See next question ...
1127 <sect2 renderas="sect3" id="newads"><title>How can I submit new ads?</title>
1129 Yes, absolutely! Please see the <link linkend="contact">Contact section</link> for
1130 how to do that. Please note that you (technically) need the latest
1131 <application>Privoxy</application> version for this to work.
1136 <sect2 renderas="sect3" id="ip"><title>How can I hide my IP address?</title>
1138 If you run both the browser and the proxy locally, you cannot hide your IP
1139 address with <application>Privoxy</application> or any other software. The
1140 server needs to know your IP address to send the answers back to you.
1143 Fortunately there are many publicly usable anonymous proxies out there, which
1144 solve the problem by providing a further level of indirection between you and
1145 the web server, shared by many people, and thus letting your requests "drown"
1146 in white noise of unrelated requests as far as user tracking is concerned.
1149 Most of them will, however, log your IP address and make it available to the
1150 authorities in case you abuse that anonymity for criminal purposes. In fact
1151 you can't even rule out that some of them only exist to *collect* information
1152 on (those suspicious) people with a more than average preference for privacy.
1155 You can find a list of anonymous public proxies at <ulink
1156 url="http://www.multiproxy.org/anon_list.htm">multiproxy.org</ulink> and many
1157 more through Google. A particularly interesting project is the JAP service
1158 offered by the Technical University of Dresden (<ulink
1159 url="http://anon.inf.tu-dresden.de/index_en.html">http://anon.inf.tu-dresden.de/index_en.html</ulink>.
1162 There is, however, even in the single-machine case the possibility to make the
1163 server believe that your machine is in fact a shared proxy serving a whole big
1164 LAN, and we are looking into that.
1168 <sect2 renderas="sect3">
1169 <title id="anonforsure">Can <application>Privoxy</application> guarantee I am anonymous?</title>
1171 No. Your chances of remaining anonymous are greatly improved, but unless you
1172 are an expert on Internet security it would be safest to assume that
1173 everything you do on the Web can be traced back to you.
1176 <application>Privoxy</application> can remove various information about you,
1177 and allows <emphasis>you</emphasis> more freedom to decide which sites
1178 you can trust, and what details you want to reveal. But it's still possible
1179 that web sites can find out who you are. Here's one way this can happen.
1182 A few browsers disclose the user's email address in certain situations, such
1183 as when transferring a file by FTP. <application>Privoxy</application>
1184 does not filter FTP. If you need this feature, or are concerned about the
1185 mail handler of your browser disclosing your email address, you might
1186 consider products such as <application>NSClean</application>.
1189 Browsers available only as binaries could use non-standard headers to give
1190 out any information they can have access to: see the manufacturer's license
1191 agreement. It's impossible to anticipate and prevent every breach of privacy
1192 that might occur. The professionally paranoid prefer browsers available as
1193 source code, because anticipating their behavior is easier. Trust the source,
1199 <sect2 renderas="sect3">
1200 <title id="sitebreak">Might some things break because header information or
1201 content is being altered?</title>
1204 Definitely. More and more sites use HTTP header content to decide what to
1205 display and how to display it. There is many ways that this can be handled,
1206 so having hard and fast rules, is tricky.
1210 <quote>User-Agent</quote> in particular is often used in this way to identify
1211 the browser, and adjust content accordingly. Changing this now (at least not
1212 further than removing the OS information) is not recommended, since so many
1213 sites do look for it. You may get undesirable results by changing this.
1217 For instance, different browsers use different encodings of Russian and Czech
1218 characters, certain web servers convert pages on-the-fly according to the
1219 User Agent header. Giving a <quote>User Agent</quote> with the wrong
1220 operating system or browser manufacturer causes some sites in these languages
1221 to be garbled; Surfers to Eastern European sites should change it to
1222 something closer. And then some page access counters work by looking at the
1223 <quote>Referer</quote> header; they may fail or break if unavailable. The
1224 weather maps of Intellicast have been blocked by their server when no
1225 <quote>Referer</quote> or cookie is provided, is another example. (But you
1226 can forge both headers without giving information away). There are
1227 many other ways things can go wrong when trying to fool a web server.
1231 Similar thoughts apply to modifying JavaScript, and, to a lesser degree,
1236 If you have problems with a site, you will have to adjust your configuration
1237 accordingly. Cookies are probably the most likely adjustment that may
1238 be required, but by no means the only one.
1244 <sect2 renderas="sect3">
1245 <title id="caching">Can <application>Privoxy</application> act as a <quote>caching</quote> proxy to
1246 speed up web browsing?</title>
1248 No, it does not have this ability at all. You want something like
1249 <ulink url="http://www.squid-cache.org/">Squid</ulink> for this. And, yes,
1250 before you ask, <application>Privoxy</application> can co-exist
1251 with other kinds of proxies like <application>Squid</application>.
1252 See the <ulink url="../user-manual/config.html#FORWARDING">forwarding
1253 chapter</ulink> in the <ulink url="../user-manual/index.html">user
1254 manual</ulink> for details.
1258 <sect2 renderas="sect3">
1259 <title id="firewall">What about as a firewall? Can <application>Privoxy</application> protect me?</title>
1261 Not in the way you mean, or in the way a true firewall can.
1262 <application>Privoxy</application> can help protect your privacy, but not
1263 protect you from intrusion attempts. It is, of course, perfectly possible
1264 and recommended to use <emphasis>both</emphasis>.
1268 <!-- No longer needed
1269 <sect2 renderas="sect3">
1270 <title id="logo">The <application>Privoxy</application> logo that replaces ads is very blocky
1271 and ugly looking. Can't a better font be used?</title>
1274 This is not a font problem. The logo is an image that is created by
1275 <application>Privoxy</application> on the fly. So as to not waste
1276 memory, the image is rather small. The blockiness comes when the
1277 image is scaled to fill a largish area. There is not much to be done
1278 about this, other than to use one of the other
1279 <quote>imageblock</quote> directives: <emphasis>pattern</emphasis>,
1280 <emphasis>blank</emphasis>, or a URL of your choosing.
1283 Given the above problem, we have decided to remove the logo option entirely
1289 <sect2 renderas="sect3">
1290 <title id="wasted">I have large empty spaces / a checkerboard pattern now where
1291 ads used to be. Why?</title>
1293 It would be technically possible eliminate the banners in a way that frees
1294 their screen estate in many cases, by doing all banner blocking with filters,
1295 i.e. eliminating the whole image references from the HTML pages instead
1296 of letting them stay in, and blocking the resulting requests for the
1300 But this would consume considerable CPU resources, would likely destroy
1301 the layout of many web pages which rely on the banners consuming a certain
1302 amount of screen space, and would fail in other cases, where the screen space
1303 is reserved e.g. by tables anyway. Also, making the banners disappear without
1304 a visual trace complicates troubleshooting.
1307 So we won't support this in the default configuration, but you can of course
1308 define appropriate filters yourself.
1312 <sect2 renderas="sect3">
1313 <title id="ssl">How can <application>Privoxy</application> filter Secure (HTTPS) URLs?</title>
1315 Since secure HTTP connections are encrypted SSL sessions between your browser
1316 and the secure site, and are meant to be reliably <emphasis>secure</emphasis>,
1317 there is little that <application>Privoxy</application> can do but hand the raw
1318 gibberish data though from one end to the other unprocessed.
1321 The only exception to this is blocking by host patterns, as the client needs
1322 to tell <application>Privoxy</application> the name of the remote server,
1323 so that <application>Privoxy</application> can establish the connection.
1324 If that name matches a host-only pattern, the connection will be blocked.
1327 As far as ad blocking is concerned, this is less of a restriction than it may
1328 seem, since ad sources are often identifiable by the host name, and often
1329 the banners to be placed in an encrypted page come unencrypted nonetheless
1330 for efficiency reasons, which exposes them to the full power of
1331 <application>Privoxy</application>'s ad blocking.
1336 <sect2 renderas="sect3">
1337 <title id="secure"><application>Privoxy</application> runs as a <quote>server</quote>. How
1338 secure is it? Do I need to take any special precautions?</title>
1340 There are no known exploits that might affect
1341 <application>Privoxy</application>. On Unix-like systems,
1342 <application>Privoxy</application> can run as a non-privileged
1343 user, which is how we recommend it be run. Also, by default
1344 <application>Privoxy</application> only listens to requests
1345 from <quote>localhost</quote> only. The server aspect of
1346 <application>Privoxy</application> is not itself directly exposed to the
1347 Internet in this configuration. If you want to have
1348 <application>Privoxy</application> serve as a LAN proxy, this will have to
1349 be opened up to allow for LAN requests. In this case, we'd recommend
1350 you specify only the LAN gateway address, e.g. 192.168.1.1, in the main
1351 <application>Privoxy</application> configuration file and check all <ulink
1352 url="../user-manual/config.html#ACCESS-CONTROL">access control and security
1353 options</ulink>. All LAN hosts can then use this as their proxy address
1354 in the browser proxy configuration, but <application>Privoxy</application>
1355 will not listen on any external interfaces. ACLs can be defined in addition,
1356 and using a firewall is always good too. Better safe than sorry.
1361 <sect2 renderas="sect3" id="turnoff">
1362 <title>How can I temporarily disable <application>Privoxy</application>?</title>
1364 The easiest way is to access <application>Privoxy</application> with your
1365 browser by using the remote toggle URL: <ulink
1366 url="http://config.privoxy.org/toggle">http://config.privoxy.org/toggle</ulink>.
1370 <sect2 renderas="sect3" id="seealso">
1371 <title>Where can I find more information about <application>Privoxy</application>
1372 and related issues?</title>
1373 <!-- Include seealso.sgml boilerplate: -->
1375 <!-- end boilerplate -->
1380 <ulink url="../user-manual/seealso.html">user-manual</ulink> for
1389 <!-- ~~~~~ New section ~~~~~ -->
1391 <sect1 id="trouble">
1392 <title>Troubleshooting</title>
1394 <sect2 renderas="sect3">
1395 <title id="refused">I just upgraded and am getting <quote>connection refused</quote>
1396 with every web page?</title>
1398 Either <application>Privoxy</application> is not running, or your
1399 browser is configured for a different port than what
1400 <application>Privoxy</application> is using.
1404 The old <application>Privoxy</application> (and also
1405 <application>Junkbuster</application>) used port 8000 by
1406 default. This has been changed to port 8118 now, due to a conflict
1407 with NAS (Network Audio Service), which uses port 8000. If you haven't,
1408 you need to change your browser to the new port number, or alternately
1410 url="../user-manual/config.html#LISTEN-ADDRESS"><literal>listen-address</literal>
1411 option</ulink> in <application>Privoxy's</application> <ulink
1412 url="../user-manual/config.html">main configuration file</ulink>.
1417 <sect2 renderas="sect3">
1418 <title id="flushit">I just added a new rule, but the steenkin ad is
1419 still getting through. How?</title>
1421 If the ad had been displayed before you added its URL, it will probably be
1422 held in the browser's cache for some time, so it will be displayed without
1423 the need for any request to the server, and <application>Privoxy</application>
1424 will not be in the picture. The best thing to do is try flushing the browser's
1425 caches. And then try again.
1429 If this doesn't help, you probably have an error in the rule you
1430 applied. Try pasting the full URL of the offending ad into <ulink
1431 url="http://config.privoxy.org/show-url-info">http://config.privoxy.org/show-url-info</ulink>
1432 and see if it really matches your new rule.
1437 <sect2 renderas="sect3">
1438 <title id="badsite">One of my favorite sites does not work with <application>Privoxy</application>.
1439 What can I do?</title>
1442 First verify that it is indeed a <application>Privoxy</application> problem,
1443 by toggling off <application>Privoxy</application> through <ulink
1444 url="http://config.privoxy.org/toggle">http://config.privoxy.org/toggle</ulink>,
1445 and then shift-reloading the problem page (i.e. holding down the shift key
1446 while clicking reload. Alternatively, flush your browser's disk and memory
1451 If still a problem, go to <ulink
1452 url="http://config.privoxy.org/show-url-info">http://config.privoxy.org/show-url-info</ulink>
1453 and paste the full URL of the page in question into the prompt. See which actions
1454 are being applied to the URL, and which matches in which actions files are
1455 responsible for that. Now, armed with this information, go to <ulink
1456 url="http://config.privoxy.org/show-status">http://config.privoxy.org/show-status</ulink>
1457 and select the appropriate actions files for editing.
1460 You can now either look for a section which disables the actions that
1461 you suspect to cause the problem and add a pattern for your site there,
1462 or make up a completely new section for your site. In any case, the recommended
1463 way is to disable only the prime suspect, reload the problem page, and only
1464 if the problem persists, disable more and more actions until you have
1465 identified the culprit. You may or may not want to turn the other actions
1466 on again. Remember to flush your browser's caches in between any such changes!
1469 Alternately, if you are comfortable with a text editor, you can accomplish
1470 the same thing by editing the appropriate actions file. Probably the easiest
1471 way to deal with such problems when editing by hand is to add your
1472 site to a <literal>{ fragile }</literal> section in <filename>user.action</filename>,
1473 which is an alias that turns off most <quote>dangerous</quote>
1474 actions, but is also likely to turn off more actions then needed, and thus lower
1475 your privacy and protection more than necessary,
1478 Troubleshooting actions is discussed in more detail in the <ulink
1479 url="../user-manual/appendix.html#ACTIONSANAT">user-manual appendix</ulink>.
1480 There is also an <ulink
1481 url="../user-manual/actions-file.html#ACT-EXAMPLES">actions tutorial</ulink>.
1491 <!-- ~~~~~ New section ~~~~~ -->
1493 FIXME: Commented out until we have something to put here. HB 03/18/02.
1494 <sect1 id="knownissues"><title>Known Issues</title>
1501 <!-- ~~~~~ New section ~~~~~ -->
1502 <sect1 id="contact"><title>Contacting the developers, Bug Reporting and Feature Requests</title>
1503 <!-- Include contacting.sgml -->
1505 <!-- end contacting -->
1508 <!-- ~~~~~ New section ~~~~~ -->
1509 <sect1 id="copyright"><title>Privoxy Copyright, License and History</title>
1511 <!-- Include copyright.sgml -->
1516 Portions of this document are <quote>borrowed</quote> from the original
1517 <application>Junkbuster</application> (tm) FAQ, and modified as
1518 appropriate for <application>Privoxy</application>.
1521 <!-- ~~~~~ New section ~~~~~ -->
1522 <sect2><title>License</title>
1523 <!-- Include copyright.sgml: -->
1525 <!-- end copyright -->
1527 <!-- ~ End section ~ -->
1529 <!-- ~~~~~ New section ~~~~~ -->
1530 <sect2><title>History</title>
1531 <!-- Include history.sgml -->
1537 <!-- ~ End section ~ -->
1540 <!-- ~~~~~ New section ~~~~~ -->
1542 <sect1 id="seealso"><title>See also</title>
1544 <!-- Include seealso.sgml -->
1555 Tue 09/11/01 06:38:14 PM EST: Test SGML doc by Hal Burgiss.
1557 Last modified: Mon Sep 10 19:22:09 CEST 2001
1559 This program is free software; you can redistribute it
1560 and/or modify it under the terms of the GNU General
1561 Public License as published by the Free Software
1562 Foundation; either version 2 of the License, or (at
1563 your option) any later version.
1565 This program is distributed in the hope that it will
1566 be useful, but WITHOUT ANY WARRANTY; without even the
1567 implied warranty of MERCHANTABILITY or FITNESS FOR A
1568 PARTICULAR PURPOSE. See the GNU General Public
1569 License for more details.
1571 The GNU General Public License should be included with
1572 this file. If not, you can view it at
1573 http://www.gnu.org/copyleft/gpl.html
1574 or write to the Free Software Foundation, Inc., 59
1575 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
1578 Revision 1.62 2002/06/03 00:28:16 hal9
1579 Sync with various changes from 3.0 branch. Add two new files for config stuff.
1581 Revision 1.61 2002/05/25 12:37:25 hal9
1582 Various minor changes and edits.
1584 Revision 1.60 2002/05/22 17:17:48 oes
1585 Proofread & added more links into u-m
1587 Revision 1.59 2002/05/15 04:03:30 hal9
1588 Fix ulink -> link markup.
1590 Revision 1.58 2002/05/10 01:48:20 hal9
1591 This is mostly proposed copyright/licensing additions and changes. Docs
1592 are still GPL, but licensing and copyright are more visible. Also, copyright
1593 changed in doc header comments (eliminate references to JB except FAQ).
1595 Revision 1.57 2002/05/05 20:26:02 hal9
1596 Sorting out license vs copyright in these docs.
1598 Revision 1.56 2002/05/04 08:44:44 swa
1601 Revision 1.55 2002/05/04 00:41:56 hal9
1602 -Remove TOC/first page kludge in favor of proper handling via dsl file.
1604 Revision 1.54 2002/05/03 05:06:44 hal9
1605 Add brief Q/A on transparent proxies.
1607 Revision 1.53 2002/05/03 01:34:52 hal9
1608 Fix section numbering for new sections (due to TOC kludge).
1610 Revision 1.52 2002/04/29 03:08:43 hal9
1611 -Added new Q/A on new actions file set up (pointer to u-m)
1612 -Fixed a few broken links and converted old actions as a result of
1615 Revision 1.51 2002/04/26 17:24:31 swa
1616 bookmarks cleaned, changed structure of user manual, screen and programlisting cleanups, and numerous other changes that I forgot
1618 Revision 1.50 2002/04/26 05:25:23 hal9
1619 Mass commit to catch a few scattered fixes.
1621 Revision 1.49 2002/04/12 10:10:18 swa
1624 Revision 1.48 2002/04/10 18:45:15 swa
1627 Revision 1.47 2002/04/10 04:05:32 hal9
1630 Revision 1.45 2002/04/08 22:59:26 hal9
1631 Version update. Spell chkconfig correctly :)
1633 Revision 1.44 2002/04/07 21:24:29 hal9
1634 Touch up on name change.
1636 Revision 1.43 2002/04/04 21:59:53 hal9
1637 Added NT/W2K service/icon situation.
1639 Revision 1.42 2002/04/04 18:46:47 swa
1640 consistent look. reuse of copyright, history et. al.
1642 Revision 1.41 2002/04/04 06:48:37 hal9
1643 Structural changes to allow for conditional inclusion/exclusion of content
1644 based on entity toggles, e.g. 'entity % p-not-stable "INCLUDE"'. And
1645 definition of internal entities, e.g. 'entity p-version "2.9.13"' that will
1646 eventually be set by Makefile.
1647 More boilerplate text for use across multiple docs.
1649 Revision 1.40 2002/04/03 04:22:03 hal9
1650 Fixed several typos.
1652 Revision 1.39 2002/04/03 03:53:03 hal9
1653 Revert some changes, and then make some news, to layout, and appearance.
1655 Revision 1.38 2002/04/02 03:49:10 hal9
1656 Major changes to doc structure and layout. Sections are not automatically
1657 numbered now. TOC is on page by itself.
1659 Revision 1.37 2002/04/01 16:24:07 hal9
1660 -Rework of supported Q/A.
1661 -Set up entities to include boilerplate text.
1663 Revision 1.36 2002/03/31 23:18:47 hal9
1664 More on dealing with BLOCKED.
1666 Revision 1.35 2002/03/30 04:14:19 hal9
1667 Fix privoxy.org/config links.
1669 Revision 1.34 2002/03/29 04:35:56 hal9
1672 Revision 1.33 2002/03/29 01:31:48 hal9
1673 Several new Q/A's and other touch ups.
1675 Revision 1.32 2002/03/27 00:57:03 hal9
1676 Touch ups for name change.
1678 Revision 1.31 2002/03/26 22:29:55 swa
1679 we have a new homepage!
1681 Revision 1.30 2002/03/25 16:39:22 hal9
1682 A few new sections. Made all links relative to user-manual.
1684 Revision 1.29 2002/03/25 05:23:57 hal9
1685 Moved section, and touch ups.
1687 Revision 1.28 2002/03/25 04:27:33 hal9
1688 New section related to name change.
1690 Revision 1.25 2002/03/24 16:08:08 swa
1691 we are too lazy to make a block-built
1692 privoxy logo. hence removed the option.
1694 Revision 1.24 2002/03/24 15:46:20 swa
1695 name change related issue.
1697 Revision 1.23 2002/03/24 12:33:01 swa
1700 Revision 1.22 2002/03/24 11:51:00 swa
1701 name change. changed filenames.
1703 Revision 1.21 2002/03/24 11:01:06 swa
1706 Revision 1.20 2002/03/23 15:13:11 swa
1707 renamed every reference to the old name with foobar.
1708 fixed "application foobar application" tag, fixed
1709 "the foobar" with "foobar". left junkbustser in cvs
1710 comments and remarks to history untouched.
1712 Revision 1.19 2002/03/21 17:01:54 hal9
1715 Revision 1.18 2002/03/18 16:40:31 hal9
1718 Revision 1.17 2002/03/18 03:53:53 hal9
1721 Revision 1.16 2002/03/17 21:32:56 hal9
1722 A few more additions.
1724 Revision 1.15 2002/03/17 07:25:59 hal9
1725 Correcting some of my typos, and some additions.
1727 Revision 1.14 2002/03/17 02:39:13 hal9
1728 A little more added ...
1730 Revision 1.13 2002/03/17 00:22:20 hal9
1731 Adding new stuff, and trying to incorporate stuff from old faq.
1733 Revision 1.12 2002/03/11 20:13:21 swa
1736 Revision 1.11 2002/03/11 18:42:27 swa
1739 Revision 1.10 2002/03/11 13:13:27 swa
1740 correct feedback channels
1742 Revision 1.9 2002/03/10 23:34:04 swa
1743 more info on not hiding ip address
1745 Revision 1.8 2002/03/09 15:55:48 swa
1746 added default config section
1748 Revision 1.7 2002/03/07 18:16:55 swa
1751 Revision 1.6 2002/03/07 13:16:31 oes
1752 Committing changes by Stefan
1754 Revision 1.5 2002/03/02 15:50:04 swa
1755 2.9.11 version. more input for docs.
1757 Revision 1.4 2002/02/24 14:34:24 jongfoster
1758 Formatting changes. Now changing the doctype to DocBook XML 4.1
1759 will work - no other changes are needed.
1761 Revision 1.3 2001/09/23 10:13:48 swa
1762 upload process established. run make webserver and
1763 the documentation is moved to the webserver. documents
1764 are now linked correctly.
1766 Revision 1.2 2001/09/13 15:20:17 swa
1767 merged standards into developer manual
1769 Revision 1.1 2001/09/12 15:36:41 swa
1770 source files for junkbuster documentation
1772 Revision 1.3 2001/09/10 17:43:59 swa
1773 first proposal of a structure.
1775 Revision 1.2 2001/06/13 14:28:31 swa
1776 docs should have an author.
1778 Revision 1.1 2001/06/13 14:20:37 swa
1779 first import of project's documentation for the webserver.