1 <!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V3.1//EN"[
2 <!entity % dummy "IGNORE">
3 <!entity supported SYSTEM "supported.sgml">
4 <!entity newfeatures SYSTEM "newfeatures.sgml">
5 <!entity p-intro SYSTEM "privoxy.sgml">
6 <!entity seealso SYSTEM "seealso.sgml">
7 <!entity contacting SYSTEM "contacting.sgml">
8 <!entity history SYSTEM "history.sgml">
9 <!entity copyright SYSTEM "copyright.sgml">
10 <!entity license SYSTEM "license.sgml">
11 <!entity p-version "2.9.15">
12 <!entity p-status "beta">
13 <!entity % p-not-stable "INCLUDE">
14 <!entity % p-stable "IGNORE">
15 <!entity % p-text "IGNORE"> <!-- define we are not a text only doc -->
16 <!entity % p-doc "INCLUDE"> <!-- and we are a formal doc -->
17 <!entity % p-supp-userman "INCLUDE"> <!-- Include all from supported.sgml -->
18 <!entity my-copy "©"> <!-- kludge for docbook2man -->
21 File : $Source: /cvsroot/ijbswa/current/doc/source/faq.sgml,v $
24 This file belongs into
25 ijbswa.sourceforge.net:/home/groups/i/ij/ijbswa/htdocs/
27 $Id: faq.sgml,v 1.60 2002/05/22 17:17:48 oes Exp $
29 Copyright (C) 2001, 2002 Privoxy Developers <developers@privoxy.org>
32 Based partially on the Internet Junkbuster FAQ originally written by and
33 Copyright (C) 1997 Anonymous Coders and Junkbusters Corporation.
34 http://www.junkbusters.com/
36 <Qandaset defaultlabel='qanda'>
51 ========================================================================
52 NOTE: Please read developer-manual/documentation.html before touching
53 anything in this, or other Privoxy documentation. You have been warned!
54 Failure to abide by this rule will result in the revocation of your license
55 to live a peaceful existence!
56 ========================================================================
62 <article id="index" class="faq">
64 <title>Privoxy Frequently Asked Questions</title>
68 <!-- Completely the wrong markup, but very little is allowed -->
69 <!-- in this part of an article. FIXME -->
70 <link linkend="copyright">Copyright</link> &my-copy; 2001, 2002 by
71 <ulink url="http://www.privoxy.org">Privoxy Developers</ulink>
75 <pubdate>$Id: faq.sgml,v 1.60 2002/05/22 17:17:48 oes 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 <![%p-stable;[ v.&p-version]]>. It can't and doesn't replace the
117 <ulink url="../user-manual/index.html">user manual</ulink>.
120 <!-- Include privoxy.sgml boilerplate: -->
122 <!-- end boilerplate -->
125 You can find the latest version of the document at <ulink
126 url="http://www.privoxy.org/faq/">http://www.privoxy.org/faq/</ulink>.
127 Please see the Contact section if you want to contact the developers.
131 <!-- Feel free to send a note to the developers at <email>ijbswa-developers@lists.sourceforge.net</email>. -->
137 <!-- ~~~~~ New section ~~~~~ -->
139 <sect1 id="general"><title>General Information</title>
141 <sect2 renderas="sect3" id="newjb"><title>What is this new version of <application>Privoxy</application>?</title>
143 <!-- Include history.sgml -->
150 <sect2 renderas="sect3">
151 <title id="whyprivoxy">Why <quote>Privoxy</quote>? Why a name change at all?</title>
153 <application>Privoxy</application> is the
154 <quote><emphasis>Privacy Enhancing Proxy</emphasis></quote>. Also, its content
155 modification and junk suppression allow you to browse your
156 <quote><emphasis>private</emphasis> edition</quote> of the web.
159 <ulink url="http://junkbusters.com/">Junkbusters Corporation</ulink>
160 continues to offer their original version of the <application>Internet
161 Junkbuster</application>, so publishing our
162 <application> Junkbuster</application>-derived software under the same name
166 There are also potential legal complications from the continued use of the
167 <application>Junkbuster</application> name, which is a registered trademark of
168 <ulink url="http://junkbusters.com/">Junkbusters Corporation</ulink>.
169 There are, however, no objections from Junkbusters Corporation to the
170 <application>Privoxy</application> project itself, and they, in fact, still
171 share our ideals and goals.
174 The developers also believed that there are so many changes from the original
175 code, that it was time to make a clean break from the past and make
176 a name in their own right<![%p-not-stable;[, especially now with the pending
177 release of version 3.0]]>.
182 <sect2 renderas="sect3" id="differs"><title>How does <application>Privoxy</application> differ
183 from the old <application>Junkbuster?</application></title>
185 <application>Privoxy</application> picks up where
186 <application>Junkbuster</application> left off. All the old features remain.
187 The new <application>Privoxy</application> still blocks ads and banners,
188 still manages cookies, and still helps protect your privacy. But, these are
189 all enhanced, and many new features have been added, all in the same vein.
192 The configuration has changed significantly as well. This is something that
193 users will notice right off the bat if upgrading from
194 <application>Junkbuster</application> 2.0.x. The <quote>blocklist</quote>
195 <quote>cookielist</quote>, <quote>imagelist</quote> and much more has been
196 combined into the <quote>actions</quote> files, with a completely different
197 syntax. See the <ulink url="../user-manual/upgradersnote.html">note to
198 upgraders</ulink> for details.
201 <application>Privoxy</application>'s new features include:
204 <!-- Include newfeatures.sgml: -->
210 <sect2 renderas="sect3" id="proxymoron"><title>What is a <quote>proxy</quote>? How does
211 <application>Privoxy</application> work? </title>
213 A web proxy is a service, based on a software such as <application>Privoxy</application>,
214 that clients (i.e. browsers) can use instead of connecting directly to the web
215 servers on the Internet. The clients then ask the proxy to fetch the objects
216 they need (web pages, images, movies etc) on their behalf, and when the proxy
217 has done so, it hands the results back to the client.
220 There are many reasons to use web proxies, such as security (firewalling),
221 efficiency (caching) and others, and there are just as many different proxies
222 to accommodate those needs.
225 <application>Privoxy</application> is a proxy that is solely focused on privacy
226 protection and junk elimination. Sitting between your browser(s) and the Internet,
227 it is in a perfect position to filter outbound personal information that your
228 browser is leaking, as well as inbound junk. It uses a variety of techniques to do
229 this, all of which are under your control via the various configuration
235 <sect2 renderas="sect3" id="whatsanad">
236 <title id="knows">How does <application>Privoxy</application> know what is
237 an ad, and what is not?</title>
239 <application>Privoxy</application>'s approach to blocking ads is twofold:
242 First, there are certain patterns in the <emphasis>locations</emphasis> (URLs)
243 of banner images. This applies to both the path (you wouldn't guess how many
244 web sites serve their banners from a directory called <quote>banners</quote>!)
245 and the host (blocking the big banner hosting services like doublecklick.net
246 already helps a lot). <application>Privoxy</application> takes advantage of this
247 fact by using <ulink url="../user-manual/actions-file.html#AF-PATTERNS">URL
248 patterns</ulink> to sort out and block the requests for banners.
251 Second, banners tend to come in certain <emphasis>sizes</emphasis>. But you
252 can't tell the size of an image by its URL without downloading it, and if you
253 do, it's too late to save bandwidth. Therefore, <application>Privoxy</application>
254 also inspects the HTML sources of web pages while they are loaded, and replaces
255 references to images with standard banner sizes by dummy references, so that
256 your browser doesn't request them anymore in the first place.
259 Both of this involves a certain amount of guesswork and is, of course, freely
264 <sect2 renderas="sect3">
265 <title id="mistakes">Can <application>Privoxy</application> make mistakes?
266 This does not sound very scientific.</title>
268 Actually, it's a black art ;-) And yes, it is always possible to have a broad
269 rule accidentally block or change something by mistake. There is a good chance
270 you may run into such a situation at some point. It is tricky writing rules to
271 cover every conceivable possibility, and not occasionally get false positives.
275 But this should not be a big concern since the
276 <application>Privoxy</application> configuration is very flexible, and
277 includes tools to help identify these types of situations so they can be
278 addressed as needed, allowing you to customize your installation.
279 (<link linkend="badsite">See the Troubleshooting section below</link>.)
285 <sect2 renderas="sect3" id="browsers2"><title>My browser does the same things as
286 <application>Privoxy</application>. Why should I use
287 <application>Privoxy</application> at all?</title>
289 Modern browsers do indeed have <emphasis>some</emphasis> of the same
290 functionality as <application>Privoxy</application>. Maybe this is
291 adequate for you. But <application>Privoxy</application> is much more
292 versatile and powerful, and can do a number of things that browsers just can't.
295 In addition, a proxy is good choice if you use multiple browsers, or
296 have a LAN with multiple computers. This way all the configuration
297 is in one place, and you don't have to maintain a similar configuration
298 for possibly many browsers.
304 <sect2 renderas="sect3" id="license"><title>Is there is a license or fee? What about a
305 warranty? Registration?</title>
307 <application>Privoxy</application> is licensed under the <ulink
308 url="http://www.gnu.org/copyleft/gpl.html">GNU General Public License (GPL)</ulink>.
309 It is free to use, copy, modify or distribute as you wish under the terms of this
310 license. Please see the <link linkend="copyright">Copyright</link> section for more
311 information on the license and copyright. Or the <filename>LICENSE</filename> file
312 that should be included.
315 There is <emphasis>no warranty</emphasis> of any kind, expressed, implied or otherwise.
316 That is something that would cost real money ;-) There is no registration either.
317 <application>Privoxy</application> really is <emphasis>free</emphasis>
323 <sect2 renderas="sect3" id="jointeam"><title>I would like to help you, what do I do?</title>
325 <sect3 renderas="sect4" id="jointeam-money"><title>Money Money Money</title>
327 We, of course, welcome donations and could use money for domain registering,
328 buying software to test <application>Privoxy</application> with, and, of course,
329 for regular world-wide get-togethers (hahaha). If you enjoy the software and feel
330 like helping us with a donation, just <ulink
331 url="mailto:developers@privoxy.org">drop us a note</ulink>.
335 <sect3 renderas="sect4" id="jointeam-software"><title>Software</title>
337 If you are a vendor of a web-related software like a browser, web server
338 or proxy, and would like us to ensure that <application>Privoxy</application>
339 runs smoothly with your product, you might consider supplying us with a
340 copy or license. We can't, however, guarantee that we will fix all potential
341 compatibility issues as a result.
345 <sect3 renderas="sect4" id="jointeam-work"><title>You want to work with us?</title>
347 Well, helping the team is always a good idea. We welcome new developers,
348 packaging gurus or documentation writers. Simply <ulink
349 url="https://sourceforge.net/account/register.php">get an account on SourceForge.net</ulink>
350 and mail your id to the <ulink url="mailto:developers@privoxy.org">developers
351 mailing list</ulink>. Then read the <ulink
352 url="../developer-manual/index.html">Developer's Manual</ulink>.
355 Once we have added you to the team, you'll have write access to the <ulink
356 url="http://sourceforge.net/cvs/?group_id=11118">CVS repository</ulink>, and
357 together we'll find a suitable task for you.
366 <!-- ~~~~~ New section ~~~~~ -->
368 <sect1 id="installation"><title>Installation</title>
370 <sect2 renderas="sect3" id="whichbrowsers">
371 <title>Which browsers are supported by <application>Privoxy</application>?</title>
373 Any browser that can be configured to use a proxy, which
374 should be virtually all browsers. Direct browser support is not necessary
375 since <application>Privoxy</application> runs as a separate application and
376 talks to the browser in the standardized HTTP protocol, just like a web server
381 <sect2 renderas="sect3" id="whichos">
382 <title>Which operating systems are supported?</title>
384 Include supported.sgml here:
389 <sect2 renderas="sect3" id="newinstall"><title>Can I install
390 <application>Privoxy</application> over <application>Junkbuster</application>?</title>
392 We recommend you un-install <application>Junkbuster</application>
393 first to minimize conflicts and confusion. You may want to
394 save your old configuration files for future reference. The configuration
395 files and syntax have substantially changed, so you will need to manually
396 port your old patterns. See the <ulink url="../user-manual/upgradersnote.html">note
397 to upgraders</ulink> and <ulink url="../user-manual/installation.html">installation
398 chapter</ulink> in the <ulink url="../user-manual/index.html">user manual</ulink>
402 Note: Some installers may automatically un-install
403 <application>Junkbuster</application>, if present!
408 <sect2 renderas="sect3">
409 <title id="firststep">I just installed <application>Privoxy</application>. Is there anything
410 special I have to do now?</title>
413 All browsers must be told to use <application>Privoxy</application>
414 as a proxy by specifying the correct proxy address and port number
415 in the appropriate configuration area for the browser. See below.
416 You should also flush your browser's memory and disk cache to get rid of any
424 <sect2 renderas="sect3" id="localhost"><title>What is the proxy address of <application>Privoxy</application>?</title>
426 If you set up the <application>Privoxy</application> to run on
427 the computer you browse from (rather than your ISP's server or some
428 networked computer on a LAN), the proxy will be on <literal>127.0.0.1</literal>
429 (sometimes referred to as <quote>localhost</quote>,
430 which is the special name used by every computer on the Internet to refer
431 to itself) and the port will be 8118 (unless you have <application>Privoxy</application>
432 to run on a different port with the <ulink
433 url="../user-manual/config.html#LISTEN-ADDRESS">listen-address</ulink> config option).
436 When configuring your browser's proxy settings you typically enter
437 the word <quote>localhost</quote> or the IP address <quote>127.0.0.1</quote>
438 in the boxes next to <quote>HTTP</quote> and <quote>Secure</quote> (HTTPS) and
439 then the number <quote>8118</quote> for <quote>port</quote>.
440 This tells your browser to send all web requests to <application>Privoxy</application>
441 instead of directly to the Internet.
444 <application>Privoxy</application> can also be used to proxy for
445 a Local Area Network. In this case, your would enter either the IP
446 address of the LAN host where <application>Privoxy</application>
447 is running, or the equivalent hostname. Port assignment would be
448 same as above. Note that <application>Privoxy</application> doesn't
449 listen on any LAN interfaces by default.
452 <application>Privoxy</application> does not currently handle
453 protocols such as FTP, SMTP, IM, IRC, ICQ, or other Internet
458 <sect2 renderas="sect3">
459 <title id="nothing">I just installed <application>Privoxy</application>, and nothing is happening.
460 All the ads are there. What's wrong?</title>
463 Did you configure your browser to use <application>Privoxy</application>
464 as a proxy? It does not sound like it. See above. You might also try flushing
465 the browser's caches to force a full re-reading of pages. You can verify
466 that <application>Privoxy</application> is running, and your browser
467 is correctly configured by entering the special URL:
468 <ulink url="http:/config.privoxy.org/">http://config.privoxy.org/</ulink>.
469 This should take you to a page titled <quote>This is Privoxy..</quote> with
470 access to <application>Privoxy's</application> internal configuration.
471 If you see this, then you are good to go. If you receive a page saying
472 <quote>Privoxy is not running</quote>, then the browser is not set up to use
473 your <application>Privoxy</application> installation.
474 If you receive anything else (probably nothing at all), it could either
475 be that the browser is not set up correctly, or that
476 <application>Privoxy</application> is not running at all. Check the <ulink
477 url="../user-manual/config.html#LOGFILE">log file</ulink>.
487 <!-- ~~~~~ New section ~~~~~ -->
489 <sect1 id="configuration"><title>Configuration</title>
491 <sect2 renderas="sect3" id="newconfig"><title>Can I use my old config files?</title>
493 The syntax, number, and purpose of configuration files has substantially
494 changed from <application>Junkbuster</application> and earlier versions
495 of <application>Privoxy</application>. The old files, like <filename>blocklist</filename>
496 will not work at all. If you are upgrading from a 2.0.x version, you will
497 need to port your configuration data to the new format. Note that even the
498 pattern syntax has changed! Even configuration files from the 2.9.x versions
499 will need to be adapted, as configuration syntax has been very much in flow
504 <sect2 renderas="sect3">
505 <title id="actionsfile">What is an <quote>actions</quote> file?</title>
508 <ulink url="../user-manual/actions-file.html">Actions files</ulink>
509 are where various <ulink url="../user-manual/actions-file.html#ACTIONS">actions</ulink>
510 that <application>Privoxy</application> might take while processing a certain
511 request, are configured. Typically, you would define a set of default actions
512 that apply to all URLs, then add exceptions to these defaults where needed.
516 Actions can be defined on a <ulink
517 url="../user-manual/actions-file.html#AF-PATTERNS">URL pattern</ulink> basis, i.e.
518 for single URLs, whole web sites, groups or parts thereof etc. Actions can also be
519 grouped together and then applied to requests matching one or more patterns.
520 There are many possible actions that might apply to any given site. As an example,
521 if you are blocking cookies as one of your default actions, but need to accept
522 cookies from a given site, you would need to define an exception for this
523 site in one of your actions files, preferably in <filename>user.action</filename>
528 <sect2 renderas="sect3" id="actionss">
529 <title>The <quote>actions</quote> concept confuses me. Please list
530 some of these <quote>actions</quote>.</title>
532 For a comprehensive discussion of the actions concept, please refer
533 to the <ulink url="../user-manual/actions-file.html">actions file
534 chapter</ulink> in the <ulink url="../user-manual/index.html">user
535 manual</ulink>. It includes a <ulink
536 url="../user-manual/actions-file.html#ACTIONS">list of all actions</ulink>
537 and an <ulink url="../user-manual/actions-file.html#ACT-EXAMPLES">actions
538 file tutorial</ulink> to get you started.
543 <sect2 renderas="sect3">
544 <title id="actconfig">How are actions files configured? What is the easiest
545 way to do this?</title>
548 Actions files are just text files in a special syntax and can be edited
549 with a text editor. The probably easiest way is to access
550 <application>Privoxy</application>'s user interface with your web browser
551 at <ulink url="http://config.privoxy.org/">http://config.privoxy.org/</ulink>
552 (Shortcut: <ulink url="http://p.p/">http://p.p/</ulink>) and then select
553 <quote><ulink url="http://config.privoxy.org/show-status">View &
554 change the current configuration</ulink></quote> from the menu.
559 <!-- ~~~~~ New section ~~~~~ -->
560 <sect2 renderas="sect3">
561 <title>There are several different <quote>actions</quote> files. What are
562 the differences?</title>
564 As of <application>Privoxy</application> v2.9.15, three actions files
565 are being included, to be used for
566 different purposes: These are
567 <filename>default.action</filename>, the <quote>main</quote> actions file
568 which is actively maintained by the <application>Privoxy</application>
569 developers, <filename>user.action</filename>, where users are encouraged
570 to make their private customizations, and <filename>standard.action</filename>,
571 which is for internal <application>Privoxy</application> use only.
572 Please see <ulink url="../user-manual/actions-file.html">the actions chapter</ulink>
573 in the <ulink url="../user-manual/index.html">user manual</ulink> for a more
574 detailed explanation.
578 Earlier versions included three different versions of the
579 <filename>default.action</filename> file. The new scheme allows for
580 greater flexibility of local configuration, and for browser based
581 selection of pre-defined <quote>aggressiveness</quote> levels.
586 <sect2 renderas="sect3" id="yahoo"><title>How can I make my Yahoo/Hotmail/GMX account work?</title>
588 The default configuration shouldn't impact the usability of any of these services.
589 It will, however, make all cookies temporary, so that your browser will forget your
590 login credentials in between browser sessions. If you would like not to have to log
591 in manually each time you access those websites, simply turn off all cookie handling
592 for them in the <filename>user.action</filename> file. An example for yahoo might
596 <screen># Allow all cookies for Yahoo login:
598 { -<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> }
599 .login.yahoo.com</screen>
604 <sect2 renderas="sect3" id="configfiles"> <title>What's the difference between the
605 <quote>Cautious</quote>, <quote>Medium</quote> and <quote>Advenced</quote> defaults?</title>
607 Configuring <application>Privoxy</application> is not entirely trivial. To help you get
608 started, we provide you with three different default action <quote>packages</quote> in
609 the web based actions file editor at <ulink
610 url="http://config.privoxy.org/show-status">http://config.privoxy.org/show-status</ulink>.
611 The following table shows you, which of the most important features are enabled in each
615 <table frame=all><title>Default Configurations</title>
616 <tgroup cols=4 align=left colsep=1 rowsep=1>
623 <entry>Feature</entry>
624 <entry>Cautious</entry>
625 <entry>Intermadiate</entry>
626 <entry>Advanced</entry>
631 <!-- <entry>f1</entry> -->
632 <!-- <entry>f2</entry> -->
633 <!-- <entry>f3</entry> -->
634 <!-- <entry>f4</entry> -->
640 <entry>Ad-blocking by URL</entry>
647 <entry>Ad-filtering by size</entry>
654 <entry>GIF de-animation</entry>
661 <entry>Referer forging</entry>
668 <entry>Cookie handling</entry>
670 <entry>session-only</entry>
675 <entry>Pop-up killing</entry>
682 <entry>Fast redirects</entry>
689 <entry>HTML taming</entry>
696 <entry>JavaScript taming</entry>
703 <entry>Web-bug killing</entry>
710 <entry>Fun text replacements</entry>
721 Where the defaults are likely to break some sites, exceptions for
722 known popular <quote>problem</quote> sites are included, but in
723 general, the more aggressive your default settings are, the more
724 exceptions you will have to make later. See the <ulink
725 url="../user-manual/index.html">user manual</ulink> for a more
731 <sect2 renderas="sect3" id="browseconfig"> <title>Why can I change the configuration
732 with a browser? Does that not raise security issues?</title>
734 It may seem strange that regular users can edit the config files with their
735 browsers, although the whole <filename>/etc/privoxy</filename> hierarchy
736 belongs to the user <quote>privoxy</quote>, with only 644 permissions.
739 When you use the browser-based editor, <application>Privoxy</application>
740 itself is writing to the config files. Because
741 <application>Privoxy</application> is running as the user <quote>privoxy</quote>,
742 it can update the config files.
745 If you run <application>Privoxy</application> for multiple untrusted users (e.g. in
746 a LAN), you will probably want to turn the web-based editor and remote toggle
747 features off by setting <quote><literal><ulink
748 url="../user-manual/config.html#ENABLE-EDIT-ACTIONS">enable-edit-actions</ulink>
749 0</literal></quote> and <quote><literal><ulink
750 url="../user-manual/config.html#ENABLE-REMOTE-TOGGLE">enable-remote-toggle</ulink>
751 0</literal></quote> in the <ulink url="../user-manual/config.html">main configuration file</ulink>.
754 Note that in the default configuration, only local users (i.e. those on
755 <quote>localhost</quote>) can connect to <application>Privoxy</application>,
756 so this is not (normally) a security problem.
761 <sect2 renderas="sect3">
762 <title id="filterfile">What is the <filename>default.filter</filename> file?</title>
764 The <ulink url="../user-manual/filter-file.html"><filename>default.filter</filename></ulink>
765 file is where <emphasis>filters</emphasis> are defined, which can be used to modify or
766 remove, web page content on the fly. This applies to <emphasis>anything</emphasis>
767 in the page source, including HTML tags, and JavaScript. Regular expressions are used
768 to accomplish this. There are a number of pre-defined filters to deal with common
769 annoyances. The filters are only defined here, to invoke them, you need to use the
770 <ulink url="../user-manual/actions-file.html#FILTER"><literal>filter</literal> action</ulink>.
774 If you are familiar with regular expressions, and HTML, you can look at
775 the provided <filename>default.filter</filename> with a text editor and define
776 your own filters. This is potentially a very powerful feature, but
777 requires some expertise.
781 Presently, there is no GUI editor option for this part of the configuration,
782 but you can disable/enable the various pre-defined filters of the included
783 <filename>default.filter</filename> file with the <ulink
784 url="http://config.privoxy.org/show-status">web-based actions file editor</ulink>.
789 <sect2 renderas="sect3">
790 <title id="lanconfig">How can I set up <application>Privoxy</application> to act as a proxy for my
793 By default, <application>Privoxy</application> only responds to requests
794 from <literal>127.0.0.1</literal> (localhost). To have it act as a server for
795 a network, this needs to be changed in the <ulink
796 url="../user-manual/config.html">main configuration file</ulink>. Look for
798 url="../user-manual/config.html#LISTEN-ADDRESS">listen-address</ulink></literal>
799 option, which may be commented out with a <quote>#</quote> symbol. Make sure
800 it is uncommented, and assign it the address of the LAN gateway interface,
801 and port number to use. Assuming your LAN address is 192.168.1.1 and you
802 wish to run <application>Privoxy</application> on port 8118, this line
808 listen-address 192.168.1.1:8118</screen>
812 Save the file, and restart <application>Privoxy</application>. Configure
813 all browsers on the network then to use this address and port number.
817 If you run <application>Privoxy</application> on a LAN with untrusted users,
818 we recommend that you double-check the <ulink
819 url="../user-manual/config.html#ACCESS-CONTROL">access control and security</ulink>
826 <sect2 renderas="sect3">
827 <title id="noseeum">Instead of ads, now I get a checkerboard pattern. I don't want to see anything.</title>
829 The replacement for blocked images can be controlled with the <ulink
830 url="../user-manual/actions-file.html#SET-IMAGE-BLOCKER"><literal>set-image-blocker</literal>
831 action</ulink>. You have the choice of a checkerboard pattern, a transparent 1x1 GIF
832 image (aka <quote>blank</quote>), or a redirect to a custom image of your choice.
833 Note that this choice only has effect for images which are blocked as images, i.e.
834 whose URLs match both a <literal><ulink
835 url="../user-manual/actions-file.html#HANDLE-AS-IMAGE">handle-as-image</ulink></literal>
836 <emphasis>and</emphasis> <literal><ulink
837 url="../user-manual/actions-file.html#BLOCK">block</ulink></literal> action.
840 If you want to see nothing, then change the <ulink
841 url="../user-manual/actions-file.html#SET-IMAGE-BLOCKER"><literal>set-image-blocker</literal>
842 action</ulink> to <quote>blank</quote>. This can be done by editing the
843 <filename>default.action</filename> file, or trough the <ulink
844 url="http://config.privoxy.org/show-status">web-based actions file editor</ulink>.
849 <sect2 renderas="sect3">
850 <title id="whyseeum">Why would anybody want to see a checkerboard pattern?</title>
852 Remember that <link linkend="whatsanad">telling which image is an ad and which
853 isn't</link>, is mostly guesswork. While we hope that the standard configuration
854 is rather smart, it can and will make errors. The checkerboard image is visually
855 decent, but it shows you that and where images were blocked, which can be very
856 helpful in case some navigation aid or otherwise innocent image was
857 erraneously blocked. Some people might also enjoy seeing how many banners
858 they <emphasis>don't</emphasis> have to see..
863 <!-- This has changed with the adaptive "blocked" page
865 <sect2 renderas="sect3">
866 <title id="blockedisugly">I see large red banners on some pages that say
867 <quote>Blocked</quote>. Why and how do I get rid of this?</title>
869 These are URLs that match something in one of
870 <application>Privoxy's</application> block actions
872 url="../user-manual/actions-file.html#BLOCK"><quote>+block</quote></ulink>).
873 It is meant to be a warning so that you know something has been blocked and
874 an easy way for you to see why. These are handled differently than what has
875 been defined explicitly as <quote>images</quote> (e.g. ads that are GIF image
876 files). Depending on the URL itself, it is sometimes hard for
877 <application>Privoxy</application> to really know whether there is indeed an
878 ad image there or not. And there are limitations as to what
879 <application>Privoxy</application> can do to <quote>fool</quote> the
884 For instance, if the ad is in a frame, then it is embedded in the separate
885 HTML page used for the frame. In this case, you cannot just substitute an
886 aribitrary image (like we would for a <quote>blank</quote> image), for an HTML
887 page. The browser is expecting an HTML page, and that is what it must have
888 for frames. Such situations can be a little trickier to deal with, and
889 <application>Privoxy</application> may show the <quote>Blocked</quote> page,
890 despite your best efforts.
894 If you want these to be treated as if they were images, so that they can be
895 made invisible, you can try moving the offending URL from the
896 <quote>+block</quote> section to the <quote>+imageblock</quote> section of
897 your actions file. Just be forewarned, if any URL is made
898 <quote>invisible</quote>, you may not have any inkling that something has
899 been removed from that page, or why. If this approach does not work, then you are
900 probably dealing with a frame (or <quote>ilayer</quote>), and the only thing
901 that can go there is an HTML page of some sort.
904 To deal with this situation, you could modify the
905 <quote><filename>block</filename></quote> HTML template that is used by
906 <application>Privoxy</application> to display this, and make it something
907 more to your liking. Currently, there is no configuration option for this.
908 You will have to modify, or create your own page, and use this to replace
909 <filename>templates/blocked</filename>, which is what
910 <application>Privoxy</application> uses to display the <quote>Blocked</quote>
914 Another way to deal with this is find why and where
915 <application>Privoxy</application> is blocking the frame, and
916 diable this. Then let the <quote>+set-image-blocker</quote> action
917 handle the ad that is embedded in the frame's HTML page.
922 <sect2 renderas="sect3" id="alliseeisred">
923 <title>I cannot see all of the <quote>Blocked</quote> page banner. Help.</title>
925 There is not enough available space to fit the entire Blocked page. Try right
926 clicking on the visible portion, and select <quote>Show Frame</quote>,
927 or equivalent. This will usually allow you to see the entire Privoxy
928 <quote>Blocked</quote> page, and from there you can see just what is being
932 As of Privoxy 2.9.14, the Blocked banner page is re-sizeable, and tries
933 to adjust to the allotted space. There may be occassions where there
934 just isn't enough room to display much of anything useful though.
941 <sect2 renderas="sect3">
942 <title id="blockedbytext">I see some images being replaced by a text
943 instead of the checkerboard image. Why and how do I get rid of this?</title>
945 This happens when the banners are not embedded in the HTML code of the
946 page itself, but in separate HTML (sub)documents that are loaded into (i)frames
947 or (i)layers, and these external HTML documents are blocked. Being non-images
948 they get replaced by a substitute HTML page rather than a substitute image,
949 which wouldn't work out technically, since the browser expects and accepts
950 only HTML when it has requested an HTML document.
953 The substitute page adapts to the available space and shows itself as a
954 miniature two-liner if loaded into small frames, or full-blown with a
955 large red "BLOCKED" banner if space allows.
958 If you prefer the banners to be blocked by images, you must see to it that
959 the HTML documents in which they are embedded are not blocked. Clicking
960 the <quote>See why</quote> link offered in the substitute page will show
961 you which rule blocked the page. After changing the rule and un-blocking
962 the HTML documents, the browser will try to load the actual banner images
963 and the usual image blocking will (hopefully!) kick in.
968 <sect2 renderas="sect3" id="srvany">
969 <title>Can <application>Privoxy</application> run as a service
972 Yes, it can run as a system service using <command>srvany.exe</command>.
973 The only catch is that this will effectively disable the
974 <application>Privoxy</application> icon (and its menu!) in the taskbar. You can have
975 one or the other, but not both at this time :(
978 There is a pending feature request for this functionality. See the discussion
980 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>,
981 for details, and a sample configuration.
987 <sect2 renderas="sect3" id="otherproxy">
988 <title>How can I make <application>Privoxy</application> work with other
989 proxies like <application>Squid</application>?</title>
991 This can be done and is often useful to combine the benefits of
992 <application>Privoxy</application> with those of a caching proxy.
994 url="../user-manual/config.html#FORWARDING">forwarding chapter</ulink>
995 in the <ulink url="../user-manual/index.html">user manual</ulink> which
996 describes how to do this.
1000 <sect2 renderas="sect3" id="transparent">
1001 <title>Can <application>Privoxy</application> run as a <quote>transparent
1002 </quote> proxy?</title>
1004 No, <application>Privoxy</application> currently does not have this ability,
1005 though it is planned for a future release. Transparent proxies require
1006 special handling of the request headers beyond what
1007 <application>Privoxy</application> is now capable of.
1011 Chaining <application>Privoxy</application> behind another proxy that has
1012 this ability should work though.
1014 url="../user-manual/config.html#FORWARDING">forwarding chapter</ulink>
1015 in the <ulink url="../user-manual/index.html">user manual</ulink>. As
1016 a transparent proxy to be used for chaining we recommend Transproxy
1017 (<ulink url="http://www.transproxy.nlc.net.au/">http://www.transproxy.nlc.net.au/</ulink>).
1024 <!-- ~ End section ~ -->
1027 <!-- ~~~~~ New section ~~~~~ -->
1029 <sect1 id="misc"><title>Miscellaneous</title>
1031 <sect2 renderas="sect3">
1032 <title id="slowsme">How much does <application>Privoxy</application> slow my browsing down? This
1033 has to add extra time to browsing.</title>
1035 It should not slow you down any in real terms, and may actually help
1036 speed things up since ads, banners and other junk are not being displayed.
1037 The actual processing time required by <application>Privoxy</application>
1038 itself for each page, is relatively small in the overall scheme of things,
1039 and happens very quickly. This is typically more than offset by time saved
1040 not downloading and rendering ad images.
1044 <quote>Filtering</quote> content via the <literal><ulink
1045 url="../user-manual/actions-file.html#FILTER">filter</ulink></literal> or
1047 url="../user-manual/actions-file.html#DEANIMATE-GIFS">deanimate-gifs</ulink></literal>
1048 actions may cause a perceived slowdown, since the entire document needs to be buffered
1049 before displaying. See below.
1055 <sect2 renderas="sect3" id="loadingtimes"><title>I noticed considerable
1056 delays in page requests compared to the old Junkbuster. What's wrong?</title>
1058 If you use any <literal><ulink
1059 url="../user-manual/actions-file.html#FILTER">filter</ulink></literal> action,
1060 such as filtering banners by size, web-bugs etc, or the <literal><ulink
1061 url="../user-manual/actions-file.html#DEANIMATE-GIFS">deanimate-gifs</ulink></literal>
1062 action, the entire document must be loaded into memory in order for the filtering
1063 mechanism to work, and nothing is sent to the browser during this time.
1066 The loading time does not really change in real numbers, but the feeling is
1067 different, because most browsers are able to start rendering incomplete
1068 content, giving the user a feeling of "it works". This effect is especially
1069 noticeable on slow dialup connections.
1074 <sect2 renderas="sect3" id="configurl"><title>What are "http://config.privoxy.org/" and
1075 "http://p.p/"?</title>
1077 <ulink url="http://config.privoxy.org/">http://config.privoxy.org/</ulink> is the
1078 address of <application>Privoxy</application>'s built-in user interface, and
1079 <ulink url="http://p.p/">http://p.p/</ulink> is a shortcut for it.
1082 Since <application>Privoxy</application> sits between your web browser and the Internet,
1083 it can simply intercept requests for these addresses and answer them with its built-in
1084 <quote>web server</quote>.
1087 This also makes for a good test for your browser configuration: If entering the
1088 URL <ulink url="http://config.privoxy.org/">http://config.privoxy.org/</ulink>
1089 takes you to a page saying <quote>This is Privoxy..</quote>, everything is OK.
1090 If you get a page saying <quote>Privoxy is not working</quote> instead, then
1091 your browser didn't use <application>Privoxy</application> for the request,
1092 hence it could not be intercepted, and you have accessed the <emphasis>real</emphasis>
1093 web site at config.privoxy.org.
1096 With recent versions of <application>Privoxy</application> (version 2.9.x and
1097 later), the user interface features information on the run time status, the
1098 configuration, and even a built-in editor for the <ulink
1099 url="../user-manual/actions-file.html">actions files</ulink>.
1103 Note that the built-in URLs from earlier versions of <application>Junkbuster</application>
1104 / <application>Privoxy</application>, http://example.com/show-proxy-args and http://i.j.b/,
1105 are no longer supported. If you still use such an old version, you should really consider
1106 upgrading to &p-version;.
1111 FIXME: commented out until we have data. HB 03/18/02.
1113 <sect2 renderas="sect3" id="badfiledesc"><title>I get the message 'Bad File Descriptor', why?</title>
1121 <sect2 renderas="sect3" id="blocklist"><title>Do you still maintain the blocklists?</title>
1123 No. The patterns for blocking now reside (among other things) in the <ulink
1124 url="../user-manual/actions-file.html">actions files</ulink>, which are
1125 actively maintained instead. See next question ...
1129 <sect2 renderas="sect3" id="newads"><title>How can I submit new ads?</title>
1131 Yes, absolutely! Please see the <link linkend="contact">Contact section</link> for
1132 how to do that. Please note that you (technically) need the latest
1133 <application>Privoxy</application> version for this to work.
1138 <sect2 renderas="sect3" id="ip"><title>How can I hide my IP address?</title>
1140 If you run both the browser and the proxy locally, you cannot hide your IP
1141 address with <application>Privoxy</application> or any other software. The
1142 server needs to know your IP address to send the answers back to you.
1145 Fortunately there are many publicly usable anonymous proxies out there, which
1146 solve the problem by providing a further level of indirection between you and
1147 the web server, shared by many people, and thus letting your requests "drown"
1148 in white noise of unrelated requests as far as user tracking is concerned.
1151 Most of them will, however, log your IP address and make it available to the
1152 authorities in case you abuse that anonymity for criminal purposes. In fact
1153 you can't even rule out that some of them only exist to *collect* information
1154 on (those suspicious) people with a more than average preference for privacy.
1157 You can find a list of anonymous public proxies at <ulink
1158 url="http://www.multiproxy.org/anon_list.htm">multiproxy.org</ulink> and many
1159 more through Google. A particularly interesting project is the JAP service
1160 offered by the Technical University of Dresden (<ulink
1161 url="http://anon.inf.tu-dresden.de/index_en.html">http://anon.inf.tu-dresden.de/index_en.html</ulink>.
1164 There is, however, even in the single-machine case the possibility to make the
1165 server believe that your machine is in fact a shared proxy serving a whole big
1166 LAN, and we are looking into that.
1170 <sect2 renderas="sect3">
1171 <title id="anonforsure">Can <application>Privoxy</application> guarantee I am anonymous?</title>
1173 No. Your chances of remaining anonymous are greatly improved, but unless you
1174 are an expert on Internet security it would be safest to assume that
1175 everything you do on the Web can be traced back to you.
1178 <application>Privoxy</application> can remove various information about you,
1179 and allows <emphasis>you</emphasis> more freedom to decide which sites
1180 you can trust, and what details you want to reveal. But it's still possible
1181 that web sites can find out who you are. Here's one way this can happen.
1184 A few browsers disclose the user's email address in certain situations, such
1185 as when transferring a file by FTP. <application>Privoxy</application>
1186 does not filter FTP. If you need this feature, or are concerned about the
1187 mail handler of your browser disclosing your email address, you might
1188 consider products such as <application>NSClean</application>.
1191 Browsers available only as binaries could use non-standard headers to give
1192 out any information they can have access to: see the manufacturer's license
1193 agreement. It's impossible to anticipate and prevent every breach of privacy
1194 that might occur. The professionally paranoid prefer browsers available as
1195 source code, because anticipating their behavior is easier. Trust the source,
1201 <sect2 renderas="sect3">
1202 <title id="sitebreak">Might some things break because header information or
1203 content is being altered?</title>
1206 Definitely. More and more sites use HTTP header content to decide what to
1207 display and how to display it. There is many ways that this can be handled,
1208 so having hard and fast rules, is tricky.
1212 <quote>User-Agent</quote> in particular is often used in this way to identify
1213 the browser, and adjust content accordingly. Changing this now (at least not
1214 further than removing the OS information) is not recommended, since so many
1215 sites do look for it. You may get undesirable results by changing this.
1219 For instance, different browsers use different encodings of Russian and Czech
1220 characters, certain web servers convert pages on-the-fly according to the
1221 User Agent header. Giving a <quote>User Agent</quote> with the wrong
1222 operating system or browser manufacturer causes some sites in these languages
1223 to be garbled; Surfers to Eastern European sites should change it to
1224 something closer. And then some page access counters work by looking at the
1225 <quote>Referer</quote> header; they may fail or break if unavailable. The
1226 weather maps of Intellicast have been blocked by their server when no
1227 <quote>Referer</quote> or cookie is provided, is another example. (But you
1228 can forge both headers without giving information away). There are
1229 many other ways things can go wrong when trying to fool a web server.
1233 Similar thoughts apply to modifying JavaScript, and, to a lesser degree,
1238 If you have problems with a site, you will have to adjust your configuration
1239 accordingly. Cookies are probably the most likely adjustment that may
1240 be required, but by no means the only one.
1246 <sect2 renderas="sect3">
1247 <title id="caching">Can <application>Privoxy</application> act as a <quote>caching</quote> proxy to
1248 speed up web browsing?</title>
1250 No, it does not have this ability at all. You want something like
1251 <ulink url="http://www.squid-cache.org/">Squid</ulink> for this. And, yes,
1252 before you ask, <application>Privoxy</application> can co-exist
1253 with other kinds of proxies like <application>Squid</application>.
1254 See the <ulink url="../user-manual/config.html#FORWARDING">forwarding
1255 chapter</ulink> in the <ulink url="../user-manual/index.html">user
1256 manual</ulink> for details.
1260 <sect2 renderas="sect3">
1261 <title id="firewall">What about as a firewall? Can <application>Privoxy</application> protect me?</title>
1263 Not in the way you mean, or in the way a true firewall can.
1264 <application>Privoxy</application> can help protect your privacy, but not
1265 protect you from intrusion attempts. It is, of course, perfectly possible
1266 and recommended to use <emphasis>both</emphasis>.
1270 <!-- No longer needed
1271 <sect2 renderas="sect3">
1272 <title id="logo">The <application>Privoxy</application> logo that replaces ads is very blocky
1273 and ugly looking. Can't a better font be used?</title>
1276 This is not a font problem. The logo is an image that is created by
1277 <application>Privoxy</application> on the fly. So as to not waste
1278 memory, the image is rather small. The blockiness comes when the
1279 image is scaled to fill a largish area. There is not much to be done
1280 about this, other than to use one of the other
1281 <quote>imageblock</quote> directives: <emphasis>pattern</emphasis>,
1282 <emphasis>blank</emphasis>, or a URL of your choosing.
1285 Given the above problem, we have decided to remove the logo option entirely
1291 <sect2 renderas="sect3">
1292 <title id="wasted">I have large empty spaces / a checkerboard pattern now where
1293 ads used to be. Why?</title>
1295 It would be technically possible eliminate the banners in a way that frees
1296 their screen estate in many cases, by doing all banner blocking with filters,
1297 i.e. eliminating the whole image references from the HTML pages instead
1298 of letting them stay in, and blocking the resulting requests for the
1302 But this would consume considerable CPU resources, would likely destroy
1303 the layout of many web pages which rely on the banners consuming a certain
1304 amount of screen space, and would fail in other cases, where the screen space
1305 is reserved e.g. by tables anyway. Also, making the banners disappear without
1306 a visual trace complicates troubleshooting.
1309 So we won't support this in the default configuration, but you can of course
1310 define appropriate filters yourself.
1314 <sect2 renderas="sect3">
1315 <title id="ssl">How can <application>Privoxy</application> filter Secure (HTTPS) URLs?</title>
1317 Since secure HTTP connections are encrypted SSL sessions between your browser
1318 and the secure site, and are meant to be reliably <emphasis>secure</emphasis>,
1319 there is little that <application>Privoxy</application> can do but hand the raw
1320 gibberish data though from one end to the other unprocessed.
1323 The only exception to this is blocking by host patterns, as the client needs
1324 to tell <application>Privoxy</application> the name of the remote server,
1325 so that <application>Privoxy</application> can establish the connection.
1326 If that name matches a host-only pattern, the connection will be blocked.
1329 As far as ad blocking is concerned, this is less of a restriction than it may
1330 seem, since ad sources are often identifiable by the host name, and often
1331 the banners to be placed in an encrypted page come unencrypted nonetheless
1332 for efficiency reasons, which exposes them to the full power of
1333 <application>Privoxy</application>'s ad blocking.
1338 <sect2 renderas="sect3">
1339 <title id="secure"><application>Privoxy</application> runs as a <quote>server</quote>. How
1340 secure is it? Do I need to take any special precautions?</title>
1342 There are no known exploits that might affect
1343 <application>Privoxy</application>. On Unix-like systems,
1344 <application>Privoxy</application> can run as a non-privileged
1345 user, which is how we recommend it be run. Also, by default
1346 <application>Privoxy</application> only listens to requests
1347 from <quote>localhost</quote> only. The server aspect of
1348 <application>Privoxy</application> is not itself directly exposed to the
1349 Internet in this configuration. If you want to have
1350 <application>Privoxy</application> serve as a LAN proxy, this will have to
1351 be opened up to allow for LAN requests. In this case, we'd recommend
1352 you specify only the LAN gateway address, e.g. 192.168.1.1, in the main
1353 <application>Privoxy</application> configuration file and check all <ulink
1354 url="../user-manual/config.html#ACCESS-CONTROL">access control and security
1355 options</ulink>. All LAN hosts can then use this as their proxy address
1356 in the browser proxy configuration, but <application>Privoxy</application>
1357 will not listen on any external interfaces. ACLs can be defined in addition,
1358 and using a firewall is always good too. Better safe than sorry.
1363 <sect2 renderas="sect3" id="turnoff">
1364 <title>How can I temporarily disable <application>Privoxy</application>?</title>
1366 The easiest way is to access <application>Privoxy</application> with your
1367 browser by using the remote toggle URL: <ulink
1368 url="http://config.privoxy.org/toggle">http://config.privoxy.org/toggle</ulink>.
1372 <sect2 renderas="sect3" id="seealso">
1373 <title>Where can I find more information about <application>Privoxy</application>
1374 and related issues?</title>
1375 <!-- Include seealso.sgml boilerplate: -->
1377 <!-- end boilerplate -->
1382 <ulink url="../user-manual/seealso.html">user-manual</ulink> for
1391 <!-- ~~~~~ New section ~~~~~ -->
1393 <sect1 id="trouble">
1394 <title>Troubleshooting</title>
1396 <sect2 renderas="sect3">
1397 <title id="refused">I just upgraded and am getting <quote>connection refused</quote>
1398 with every web page?</title>
1400 Either <application>Privoxy</application> is not running, or your
1401 browser is configured for a different port than what
1402 <application>Privoxy</application> is using.
1406 The old <application>Privoxy</application> (and also
1407 <application>Junkbuster</application>) used port 8000 by
1408 default. This has been changed to port 8118 now, due to a conflict
1409 with NAS (Network Audio Service), which uses port 8000. If you haven't,
1410 you need to change your browser to the new port number, or alternately
1412 url="../user-manual/config.html#LISTEN-ADDRESS"><literal>listen-address</literal>
1413 option</ulink> in <application>Privoxy's</application> <ulink
1414 url="../user-manual/config.html">main configuration file</ulink>.
1419 <sect2 renderas="sect3">
1420 <title id="flushit">I just added a new rule, but the steenkin ad is
1421 still getting through. How?</title>
1423 If the ad had been displayed before you added its URL, it will probably be
1424 held in the browser's cache for some time, so it will be displayed without
1425 the need for any request to the server, and <application>Privoxy</application>
1426 will not be in the picture. The best thing to do is try flushing the browser's
1427 caches. And then try again.
1431 If this doesn't help, you probably have an error in the rule you
1432 applied. Try pasting the full URL of the offending ad into <ulink
1433 url="http://config.privoxy.org/show-url-info">http://config.privoxy.org/show-url-info</ulink>
1434 and see if it really matches your new rule.
1439 <sect2 renderas="sect3">
1440 <title id="badsite">One of my favorite sites does not work with <application>Privoxy</application>.
1441 What can I do?</title>
1444 First verify that it is indeed a <application>Privoxy</application> problem,
1445 by toggling off <application>Privoxy</application> through <ulink
1446 url="http://config.privoxy.org/toggle">http://config.privoxy.org/toggle</ulink>,
1447 and then shift-reloading the problem page (i.e. holding down the shift key
1448 while clicking reload. Alternatively, flush your browser's disk and memory
1453 If still a problem, go to <ulink
1454 url="http://config.privoxy.org/show-url-info">http://config.privoxy.org/show-url-info</ulink>
1455 and paste the full URL of the page in question into the prompt. See which actions
1456 are being applied to the URL, and which matches in which actions files are
1457 responsible for that. Now, armed with this information, go to <ulink
1458 url="http://config.privoxy.org/show-status">http://config.privoxy.org/show-status</ulink>
1459 and select the appropriate actions files for editing.
1462 You can now either look for a section which disables the actions that
1463 you suspect to cause the problem and add a pattern for your site there,
1464 or make up a completely new section for your site. In any case, the recommended
1465 way is to disable only the prime suspect, reload the problem page, and only
1466 if the problem persists, disable more and more actions until you have
1467 identified the culprit. You may or may not want to turn the other actions
1468 on again. Remember to flush your browser's caches in between any such changes!
1471 Alternately, if you are comfortable with a text editor, you can accomplish
1472 the same thing by editing the appropriate actions file. Probably the easiest
1473 way to deal with such problems when editing by hand is to add your
1474 site to a <literal>{ fragile }</literal> section in <filename>user.action</filename>,
1475 which is an alias that turns off most <quote>dangerous</quote>
1476 actions, but is also likely to turn off more actions then needed, and thus lower
1477 your privacy and protection more than necessary,
1480 Troubleshooting actions is discussed in more detail in the <ulink
1481 url="../user-manual/appendix.html#ACTIONSANAT">user-manual appendix</ulink>.
1482 There is also an <ulink
1483 url="../user-manual/actions-file.html#ACT-EXAMPLES">actions tutorial</ulink>.
1493 <!-- ~~~~~ New section ~~~~~ -->
1495 FIXME: Commented out until we have something to put here. HB 03/18/02.
1496 <sect1 id="knownissues"><title>Known Issues</title>
1503 <!-- ~~~~~ New section ~~~~~ -->
1504 <sect1 id="contact"><title>Contacting the developers, Bug Reporting and Feature Requests</title>
1505 <!-- Include contacting.sgml -->
1507 <!-- end contacting -->
1510 <!-- ~~~~~ New section ~~~~~ -->
1511 <sect1 id="copyright"><title>Privoxy Copyright, License and History</title>
1513 <!-- Include copyright.sgml -->
1518 Portions of this document are <quote>borrowed</quote> from the original
1519 <application>Junkbuster</application> (tm) FAQ, and modified as
1520 appropriate for <application>Privoxy</application>.
1523 <!-- ~~~~~ New section ~~~~~ -->
1524 <sect2><title>License</title>
1525 <!-- Include copyright.sgml: -->
1527 <!-- end copyright -->
1529 <!-- ~ End section ~ -->
1531 <!-- ~~~~~ New section ~~~~~ -->
1532 <sect2><title>History</title>
1533 <!-- Include history.sgml -->
1539 <!-- ~ End section ~ -->
1542 <!-- ~~~~~ New section ~~~~~ -->
1544 <sect1 id="seealso"><title>See also</title>
1546 <!-- Include seealso.sgml -->
1557 Tue 09/11/01 06:38:14 PM EST: Test SGML doc by Hal Burgiss.
1559 Last modified: Mon Sep 10 19:22:09 CEST 2001
1561 This program is free software; you can redistribute it
1562 and/or modify it under the terms of the GNU General
1563 Public License as published by the Free Software
1564 Foundation; either version 2 of the License, or (at
1565 your option) any later version.
1567 This program is distributed in the hope that it will
1568 be useful, but WITHOUT ANY WARRANTY; without even the
1569 implied warranty of MERCHANTABILITY or FITNESS FOR A
1570 PARTICULAR PURPOSE. See the GNU General Public
1571 License for more details.
1573 The GNU General Public License should be included with
1574 this file. If not, you can view it at
1575 http://www.gnu.org/copyleft/gpl.html
1576 or write to the Free Software Foundation, Inc., 59
1577 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
1580 Revision 1.60 2002/05/22 17:17:48 oes
1581 Proofread & added more links into u-m
1583 Revision 1.59 2002/05/15 04:03:30 hal9
1584 Fix ulink -> link markup.
1586 Revision 1.58 2002/05/10 01:48:20 hal9
1587 This is mostly proposed copyright/licensing additions and changes. Docs
1588 are still GPL, but licensing and copyright are more visible. Also, copyright
1589 changed in doc header comments (eliminate references to JB except FAQ).
1591 Revision 1.57 2002/05/05 20:26:02 hal9
1592 Sorting out license vs copyright in these docs.
1594 Revision 1.56 2002/05/04 08:44:44 swa
1597 Revision 1.55 2002/05/04 00:41:56 hal9
1598 -Remove TOC/first page kludge in favor of proper handling via dsl file.
1600 Revision 1.54 2002/05/03 05:06:44 hal9
1601 Add brief Q/A on transparent proxies.
1603 Revision 1.53 2002/05/03 01:34:52 hal9
1604 Fix section numbering for new sections (due to TOC kludge).
1606 Revision 1.52 2002/04/29 03:08:43 hal9
1607 -Added new Q/A on new actions file set up (pointer to u-m)
1608 -Fixed a few broken links and converted old actions as a result of
1611 Revision 1.51 2002/04/26 17:24:31 swa
1612 bookmarks cleaned, changed structure of user manual, screen and programlisting cleanups, and numerous other changes that I forgot
1614 Revision 1.50 2002/04/26 05:25:23 hal9
1615 Mass commit to catch a few scattered fixes.
1617 Revision 1.49 2002/04/12 10:10:18 swa
1620 Revision 1.48 2002/04/10 18:45:15 swa
1623 Revision 1.47 2002/04/10 04:05:32 hal9
1626 Revision 1.45 2002/04/08 22:59:26 hal9
1627 Version update. Spell chkconfig correctly :)
1629 Revision 1.44 2002/04/07 21:24:29 hal9
1630 Touch up on name change.
1632 Revision 1.43 2002/04/04 21:59:53 hal9
1633 Added NT/W2K service/icon situation.
1635 Revision 1.42 2002/04/04 18:46:47 swa
1636 consistent look. reuse of copyright, history et. al.
1638 Revision 1.41 2002/04/04 06:48:37 hal9
1639 Structural changes to allow for conditional inclusion/exclusion of content
1640 based on entity toggles, e.g. 'entity % p-not-stable "INCLUDE"'. And
1641 definition of internal entities, e.g. 'entity p-version "2.9.13"' that will
1642 eventually be set by Makefile.
1643 More boilerplate text for use across multiple docs.
1645 Revision 1.40 2002/04/03 04:22:03 hal9
1646 Fixed several typos.
1648 Revision 1.39 2002/04/03 03:53:03 hal9
1649 Revert some changes, and then make some news, to layout, and appearance.
1651 Revision 1.38 2002/04/02 03:49:10 hal9
1652 Major changes to doc structure and layout. Sections are not automatically
1653 numbered now. TOC is on page by itself.
1655 Revision 1.37 2002/04/01 16:24:07 hal9
1656 -Rework of supported Q/A.
1657 -Set up entities to include boilerplate text.
1659 Revision 1.36 2002/03/31 23:18:47 hal9
1660 More on dealing with BLOCKED.
1662 Revision 1.35 2002/03/30 04:14:19 hal9
1663 Fix privoxy.org/config links.
1665 Revision 1.34 2002/03/29 04:35:56 hal9
1668 Revision 1.33 2002/03/29 01:31:48 hal9
1669 Several new Q/A's and other touch ups.
1671 Revision 1.32 2002/03/27 00:57:03 hal9
1672 Touch ups for name change.
1674 Revision 1.31 2002/03/26 22:29:55 swa
1675 we have a new homepage!
1677 Revision 1.30 2002/03/25 16:39:22 hal9
1678 A few new sections. Made all links relative to user-manual.
1680 Revision 1.29 2002/03/25 05:23:57 hal9
1681 Moved section, and touch ups.
1683 Revision 1.28 2002/03/25 04:27:33 hal9
1684 New section related to name change.
1686 Revision 1.25 2002/03/24 16:08:08 swa
1687 we are too lazy to make a block-built
1688 privoxy logo. hence removed the option.
1690 Revision 1.24 2002/03/24 15:46:20 swa
1691 name change related issue.
1693 Revision 1.23 2002/03/24 12:33:01 swa
1696 Revision 1.22 2002/03/24 11:51:00 swa
1697 name change. changed filenames.
1699 Revision 1.21 2002/03/24 11:01:06 swa
1702 Revision 1.20 2002/03/23 15:13:11 swa
1703 renamed every reference to the old name with foobar.
1704 fixed "application foobar application" tag, fixed
1705 "the foobar" with "foobar". left junkbustser in cvs
1706 comments and remarks to history untouched.
1708 Revision 1.19 2002/03/21 17:01:54 hal9
1711 Revision 1.18 2002/03/18 16:40:31 hal9
1714 Revision 1.17 2002/03/18 03:53:53 hal9
1717 Revision 1.16 2002/03/17 21:32:56 hal9
1718 A few more additions.
1720 Revision 1.15 2002/03/17 07:25:59 hal9
1721 Correcting some of my typos, and some additions.
1723 Revision 1.14 2002/03/17 02:39:13 hal9
1724 A little more added ...
1726 Revision 1.13 2002/03/17 00:22:20 hal9
1727 Adding new stuff, and trying to incorporate stuff from old faq.
1729 Revision 1.12 2002/03/11 20:13:21 swa
1732 Revision 1.11 2002/03/11 18:42:27 swa
1735 Revision 1.10 2002/03/11 13:13:27 swa
1736 correct feedback channels
1738 Revision 1.9 2002/03/10 23:34:04 swa
1739 more info on not hiding ip address
1741 Revision 1.8 2002/03/09 15:55:48 swa
1742 added default config section
1744 Revision 1.7 2002/03/07 18:16:55 swa
1747 Revision 1.6 2002/03/07 13:16:31 oes
1748 Committing changes by Stefan
1750 Revision 1.5 2002/03/02 15:50:04 swa
1751 2.9.11 version. more input for docs.
1753 Revision 1.4 2002/02/24 14:34:24 jongfoster
1754 Formatting changes. Now changing the doctype to DocBook XML 4.1
1755 will work - no other changes are needed.
1757 Revision 1.3 2001/09/23 10:13:48 swa
1758 upload process established. run make webserver and
1759 the documentation is moved to the webserver. documents
1760 are now linked correctly.
1762 Revision 1.2 2001/09/13 15:20:17 swa
1763 merged standards into developer manual
1765 Revision 1.1 2001/09/12 15:36:41 swa
1766 source files for junkbuster documentation
1768 Revision 1.3 2001/09/10 17:43:59 swa
1769 first proposal of a structure.
1771 Revision 1.2 2001/06/13 14:28:31 swa
1772 docs should have an author.
1774 Revision 1.1 2001/06/13 14:20:37 swa
1775 first import of project's documentation for the webserver.