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 "3.0.22">
12 <!entity p-status "UNRELEASED">
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 -->
19 <!entity % p-newstuff "INCLUDE"> <!-- exclude stuff from devel versions -->
20 <!entity % seealso-extra "INCLUDE"> <!-- extra stuff from seealso.sgml -->
21 <!entity my-app "<application>Privoxy</application>">
24 File : $Source: /cvsroot/ijbswa/current/doc/source/faq.sgml,v $
27 This file belongs into
28 ijbswa.sourceforge.net:/home/groups/i/ij/ijbswa/htdocs/
30 $Id: faq.sgml,v 2.103 2014/10/21 12:02:16 fabiankeil Exp $
32 Copyright (C) 2001-2014 Privoxy Developers http://www.privoxy.org/
35 Based partially on the Internet Junkbuster FAQ originally written by and
36 Copyright (C) 1997 Anonymous Coders and Junkbusters Corporation.
37 http://www.junkbusters.com/
39 <Qandaset defaultlabel='qanda'>
54 ========================================================================
55 NOTE: Please read developer-manual/documentation.html before touching
58 Please we keep the info in this file as version independent as possible
59 so we only have to maintain one FAQ. Where significant changes are
60 made to Privoxy configuration, please note the change in such a way that
61 it makes sense to both users of older and newer versions.
62 ========================================================================
68 <article id="index" class="faq">
70 <title>Privoxy Frequently Asked Questions</title>
74 <!-- Completely the wrong markup, but very little is allowed -->
75 <!-- in this part of an article. FIXME -->
76 <link linkend="copyright">Copyright</link> &my-copy; 2001-2014 by
77 <ulink url="http://www.privoxy.org/">Privoxy Developers</ulink>
81 <pubdate>$Id: faq.sgml,v 2.103 2014/10/21 12:02:16 fabiankeil Exp $</pubdate>
85 Note: this should generate a separate page, and a live link to it.
86 But it doesn't for some mysterious reason. Please leave commented
87 unless it can be fixed proper. For the time being, the copyright
88 statement will be in copyright.smgl.
92 <legalnotice id="legalnotice">
94 text goes here ........
104 <orgname>By: Privoxy Developers</orgname>
113 This is here to keep vim syntax file from breaking :/
114 If I knew enough to fix it, I would.
115 PLEASE DO NOT REMOVE! HB: hal@foobox.net
120 This FAQ gives quick answers to frequently asked questions about
121 <ulink url="http://www.privoxy.org/">Privoxy</ulink>.
122 It is not a substitute for the
123 <ulink url="../user-manual/index.html"><citetitle>Privoxy User Manual</citetitle></ulink>.
125 This works, at least in some situtations:
126 Test: <ulink url="privoxy-user-manual.pdf"><citetitle>User Manual</citetitle></ulink>.
130 <!-- Include privoxy.sgml boilerplate: -->
131 <para>What is Privoxy?</para> &p-intro;
132 <!-- end boilerplate -->
135 Please note that this document is a work in progress. This copy represents
136 the state at the release of version &p-version;.
137 You can find the latest version of the document at <ulink
138 url="http://www.privoxy.org/faq/">http://www.privoxy.org/faq/</ulink>.
139 Please see the <link linkend="contact">Contact section</link> if you want to
140 contact the developers.
144 <!-- Feel free to send a note to the developers at <email>ijbswa-developers@lists.sourceforge.net</email>. -->
150 <!-- ~~~~~ New section ~~~~~ -->
152 <sect1 id="general"><title>General Information</title>
153 <sect2 renderas="sect3" id="who-uses"><title>Who should give &my-app; a try?</title>
155 Anyone who is interested in security, privacy, or in
156 finer-grained control over their web and Internet experience.
160 <sect2 renderas="sect3" id="bestchoice"><title>Is Privoxy the best choice for
163 &my-app; is certainly a good choice, especially for those who want more
164 control and security. Those with the willingness to read the documentation
165 and the ability to fine-tune their installation will benefit the most.
168 One of <application>Privoxy's</application>
169 strengths is that it is highly configurable giving you the ability to
170 completely personalize your installation. Being familiar with, or at least
171 having an interest in learning about <ulink
172 url="http://en.wikipedia.org/wiki/Http">HTTP</ulink> and other networking
173 protocols, <ulink url="http://en.wikipedia.org/wiki/Html">HTML</ulink>, and
174 <ulink url="http://en.wikipedia.org/wiki/Regular_expressions"><quote>Regular
175 Expressions</quote></ulink>
176 will be a big plus and will help you get the most out of &my-app;.
177 A new installation just includes a very basic configuration. The user
178 should take this as a starting point only, and enhance it as he or she
179 sees fit. In fact, the user is encouraged, and expected to, fine-tune the
183 Much of <application>Privoxy's</application> configuration can be done
184 with a <ulink url="http://en.wikipedia.org/wiki/Web_browser">Web browser</ulink>.
185 But there are areas where configuration is done using a
186 <ulink url="http://en.wikipedia.org/wiki/Text_editors">text editor</ulink>
187 to edit configuration files. Also note that the web-based action editor
188 doesn't use authentication and should only be enabled in environments
189 where all clients with access to &my-app; listening port can be trusted.
193 <sect2 renderas="sect3" id="proxymoron"><title>What is a <quote>proxy</quote>? How does
194 Privoxy work? </title>
196 A <ulink url="http://en.wikipedia.org/wiki/Proxy_server">web proxy</ulink>
197 is a service, based on a software such as &my-app;, that clients
198 (i.e. browsers) can use instead of connecting to web servers directly.
199 The clients then ask the proxy to request objects (web pages, images, movies etc)
200 on their behalf and to forward the data to the clients.
201 It is a <quote>go-between</quote>. For details, see
202 <ulink url="http://en.wikipedia.org/wiki/Proxy_server">Wikipedia's proxy definition</ulink>.
205 There are many reasons to use web proxies, such as security (firewalling),
206 efficiency (caching) and others, and there are any number of proxies
207 to accommodate those needs.
210 &my-app; is a proxy that is primarily focused on
211 privacy enhancement, ad and junk elimination and freeing the user from
212 restrictions placed on his activities. Sitting between your browser(s) and the Internet,
213 it is in a perfect position to filter outbound personal information that your
214 browser is leaking, as well as inbound junk. It uses a variety of techniques to do
215 this, all of which are under your complete control via the various configuration
216 files and options. Being a proxy also makes it easier to share
217 configurations among multiple browsers and/or users.
221 <sect2 renderas="sect3" id="otherstuff">
222 <title>Does Privoxy do anything more than ad blocking?</title>
224 Yes, ad blocking is but one possible use. There are many, many ways &my-app;
225 can be used to sanitize and customize web browsing.
229 <sect2 renderas="sect3" id="newjb"><title>What is this new version of
230 <quote><citetitle>Junkbuster</citetitle></quote>?</title>
232 <!-- Include history.sgml -->
239 <sect2 renderas="sect3">
240 <title id="whyprivoxy">Why <quote>Privoxy</quote>? Why change the name from
241 Junkbuster at all?</title>
243 Though outdated, Junkbusters Corporation continued to offer their original
244 version of the <application>Internet Junkbuster</application> for a while,
245 so publishing our <application> Junkbuster</application>-derived software
246 under the same name would have led to confusion.
249 There were also potential legal reasons not to use the
250 <application>Junkbuster</application> name, as it was (and maybe still is)
251 a registered trademark of Junkbusters Corporation.
252 There were, however, no objections from Junkbusters Corporation to the
253 <application>Privoxy</application> project itself, and they, in fact,
254 shared our ideals and goals.
257 The Privoxy developers also believed that there were so many improvements
258 over the original code, that it was time to make a clean break from the past
259 and make a name in their own right.
262 <application>Privoxy</application> is the
263 <quote><emphasis>Privacy Enhancing Proxy</emphasis></quote>. Also, its content
264 modification and junk suppression gives <emphasis>you</emphasis>, the user, more
265 control, more freedom, and allows you to browse your personal and
266 <quote><emphasis>private</emphasis> edition</quote> of the web.
270 <sect2 renderas="sect3" id="differs"><title>How does Privoxy differ
271 from the old Junkbuster?</title>
273 <application>Privoxy</application> picks up where
274 <application>Junkbuster</application> left off.
275 <application>Privoxy</application> still blocks ads and banners,
277 url="http://en.wikipedia.org/wiki/Browser_cookie">cookies</ulink>, and still
278 helps protect your privacy. But, most of these features have been enhanced,
279 and many new ones have been added, all in the same vein.
282 <application>Privoxy</application>'s new features include:
285 <!-- Include newfeatures.sgml: -->
291 <sect2 renderas="sect3" id="whatsanad">
292 <title id="knows">How does Privoxy know what is
293 an ad, and what is not?</title>
295 <application>Privoxy</application>'s approach to blocking ads is twofold:
298 First, there are certain patterns in the <emphasis>locations</emphasis> (URLs)
299 of banner images. This applies to both the path (you wouldn't guess how many
300 web sites serve their banners from a directory called <quote>banners</quote>!)
301 and the host (blocking the big banner hosting services like doublecklick.net
302 already helps a lot). <application>Privoxy</application> takes advantage of this
303 fact by using <ulink url="../user-manual/actions-file.html#AF-PATTERNS">URL
304 patterns</ulink> to sort out and block the requests for things that sound
305 like they would be ads or banners.
308 Second, banners tend to come in certain <emphasis>sizes</emphasis>. But you
309 can't tell the size of an image by its URL without downloading it, and if you
310 do, it's too late to save bandwidth. Therefore, <application>Privoxy</application>
311 also inspects the HTML sources of web pages while they are loaded, and replaces
312 references to images with standard banner sizes by dummy references, so that
313 your browser doesn't request them anymore in the first place.
316 Both of this involves a certain amount of guesswork and is, of course, freely
317 and readily configurable.
321 <sect2 renderas="sect3">
322 <title id="mistakes">Can Privoxy make mistakes?
323 This does not sound very scientific.</title>
325 Actually, it's a black art ;-) And yes, it is always possible to have a broad
326 rule accidentally block or change something by mistake. You will almost surely
327 run into such situations at some point. It is tricky writing rules to
328 cover every conceivable possibility, and not occasionally get false positives.
332 But this should not be a big concern since the
333 <application>Privoxy</application> configuration is very flexible, and
334 includes tools to help identify these types of situations so they can be
335 addressed as needed, allowing you to customize your installation.
336 (<link linkend="badsite">See the Troubleshooting section below</link>.)
341 <sect2 renderas="sect3">
342 <title id="configornot">Will I have to configure Privoxy
343 before I can use it?</title>
345 That depends on your expectations.
346 The default installation should give you a good starting
347 point, and block <emphasis>most</emphasis> ads and unwanted content,
348 but many of the more advanced features are off by default, and require
349 you to activate them.
352 You do have to set up your browser to use
353 <application>Privoxy</application> (see the <link
354 linkend="firststep">Installation section below</link>).
357 And you will certainly run into situations where there are false positives,
358 or ads not being blocked that you may not want to see. In these cases, you
359 would certainly benefit by customizing <application>Privoxy's</application>
360 configuration to more closely match your individual situation. And we
361 encourage you to do this. This is where the real power of
362 <application>Privoxy</application> lies!
367 <sect2 renderas="sect3" id="lan">
368 <title>Can Privoxy run as a server on a network?</title>
370 Yes, &my-app; runs as a server already, and can easily be configured to
371 <quote>serve</quote> more than one client. See <link linkend="lanconfig">
372 How can I set up Privoxy to act as a proxy for my LAN</link> below.
376 <sect2 renderas="sect3" id="browsers2"><title>My browser does the same things as
377 Privoxy. Why should I use Privoxy at all?</title>
379 Modern browsers do indeed have <emphasis>some</emphasis> of the same
380 functionality as <application>Privoxy</application>. Maybe this is
381 adequate for you. But <application>Privoxy</application> is very
382 versatile and powerful, and can probably do a number of things
383 your browser just can't.
386 In addition, a proxy is good choice if you use multiple browsers, or
387 have a LAN with multiple computers since &my-app; can run as a server
388 application. This way all the configuration is in one place, and you don't
389 have to maintain a similar configuration for possibly many browsers or
393 Note, however, that it's recommended to leverage both your browser's
394 and <application>Privoxy's</application> privacy enhancing features
395 at the same time. While your browser probably lacks some features
396 &my-app; offers, it should also be able to do some things more
397 reliably, for example restricting and suppressing JavaScript.
401 <sect2 renderas="sect3" id="whytrust"><title>Why should I trust Privoxy?</title>
403 The most important reason is because you have access to
404 <emphasis>everything</emphasis>, and you can control everything. You can
405 check every line of every configuration file yourself. You can check every
406 last bit of source code should you desire. And even if you can't read code,
407 there should be some comfort in knowing that <!-- thousands of -->other people can,
408 and do read it. You can build the software from scratch, if you want,
409 so that you know the executable is clean, and that it is
410 <emphasis>yours</emphasis>. In fact, we encourage this level of scrutiny. It
411 is one reason we use &my-app; ourselves.
415 <sect2 renderas="sect3" id="license"><title>Is there is a license or fee? What about a
416 warranty? Registration?</title>
418 <application>Privoxy</application> is free software and licensed under the <ulink
419 url="http://www.gnu.org/licenses/old-licenses/gpl-2.0.html">GNU General Public License (GPL) version 2</ulink>.
420 It is free to use, copy, modify or distribute as you wish under the terms of this
421 license. Please see the <link linkend="copyright">Copyright</link> section for more
422 information on the license and copyright. Or the <filename>LICENSE</filename> file
423 that should be included.
426 There is <emphasis>no warranty</emphasis> of any kind, expressed, implied or otherwise.
427 That is something that would cost real money ;-) There is no registration either.
432 <sect2 renderas="sect3" id="spyware">
433 <title>Can Privoxy remove spyware? Adware? Viruses?</title>
435 No, at least not reliably enough to trust it. &my-app; is not designed to be
436 a malware removal tool and the default configuration doesn't even try to
437 filter out any malware.
440 &my-app; could help prevent contact from (known) sites that use such
441 tactics with appropriate configuration rules, and thus could conceivably
442 prevent contamination from such sites. However, keeping such a configuration
443 up to date would require a lot of time and effort that would be better spend
444 on keeping your software itself up to date so it doesn't have known
450 <sect2 renderas="sect3" id="otherads">
451 <title>Can I use Privoxy with other ad-blocking software?</title>
453 &my-app; should work fine with other proxies and other software in general.
456 But it is probably not necessary to use &my-app; in conjunction with other
457 ad-blocking products, and this could conceivably cause undesirable results.
458 It might be better to choose one software or the other and work a little to
459 tweak its configuration to your liking.
462 Note that this is an advice specific to ad blocking.
466 <sect2 renderas="sect3" id="help-the-developers"><title id="jointeam">I would like to help you, what can I do?</title>
468 <sect3 renderas="sect4" id="participate"><title id="jointeam-work">Would you like to participate?</title>
470 Well, we <emphasis>always</emphasis> need help. There is something for
471 everybody who wants to help us. We welcome new developers, packagers,
472 testers, documentation writers or really anyone with a desire to help in
473 any way. You <emphasis>DO NOT</emphasis> need to be a
474 <quote>programmer</quote>. There are many other tasks available. In fact,
475 the programmers often can't spend as much time programming because of some
476 of the other, more mundane things that need to be done, like checking the
477 Tracker feedback sections or responding to user questions on the mailing
481 So first thing, subscribe to the <ulink
482 url="https://lists.sourceforge.net/lists/listinfo/ijbswa-users">Privoxy Users</ulink>
483 or the <ulink url="https://lists.sourceforge.net/lists/listinfo/ijbswa-developers">Privoxy
484 Developers</ulink> mailing list, join the discussion, help out other users, provide general
485 feedback or report problems you noticed.
488 If you intend to help out with the trackers, you also might want to <ulink
489 url="https://sourceforge.net/user/registration">get an account on SourceForge.net</ulink>
490 so we don't confuse you with the other name-less users.
493 We also have a <ulink
494 url="../developer-manual/index.html">Developer's Manual</ulink>.
495 While it is partly out of date, it's still worth reading.
498 Our <ulink url="http://ijbswa.cvs.sourceforge.net/viewvc/ijbswa/current/TODO?view=markup">TODO list</ulink>
499 may be of interest to you as well.
500 Please let us know if you want to work on one of the items listed.
504 <sect3 renderas="sect4" id="donate"><title>Would you like to donate?</title>
506 Donations are welcome. Our
507 <ulink url="http://ijbswa.cvs.sourceforge.net/viewvc/ijbswa/current/TODO">TODO list</ulink>
508 is rather long and being able to pay one (or more) developers to work on Privoxy
509 would make a huge difference, even if it was only for a couple of weeks. Donations may
510 also be used for Privoxy-related travel expenses (for example to attend conferences),
511 for hardware used for Privoxy development and for hosting expenses etc.
515 <application>Privoxy</application> is an associated
516 project of <ulink url="http://www.spi-inc.org/">Software
517 in the Public Interest (SPI)</ulink>, which allows us to receive
518 tax-deductible donations in the United States. If you want to donate through
519 SPI, please use <ulink url="http://www.spi-inc.org/donations">SPI's donation page</ulink>
520 to see what the options are.
524 You can also donate to Privoxy using a bank account managed by
525 <ulink url="https://www.zwiebelfreunde.de/">Zwiebelfreunde e.V.</ulink>:
528 Name on Account: Zwiebelfreunde e.V.
529 IBAN: DE95430609671126825604
534 Donations made through Zwiebelfreunde e.V. are tax-deductible in Germany
535 and other countries that recognize German charitable clubs. Feel free to
536 use the Subject field to provide a name to be credited and a list of TODO
537 list items you are interested in the most. For example: Max Mustermann: #16, #1, #14.
541 If you have any questions regarding donations please mail to either the
542 public user mailing list or, if it's a private matter, to
543 <ulink url="mailto:fk@fabiankeil.de">Fabian Keil</ulink> (Privoxy's SPI liason)
552 <!-- ~~~~~ New section ~~~~~ -->
554 <sect1 id="installation"><title>Installation</title>
556 <sect2 renderas="sect3" id="whichbrowsers">
557 <title>Which browsers are supported by Privoxy?</title>
559 Any browser that can be configured to use a proxy, which
560 should be virtually all browsers, including
561 <application>Firefox</application>, <application>Internet
562 Explorer</application>, <application>Opera</application>, and
563 <application>Safari</application> among others.
564 Direct browser support is not an absolute requirement since
565 <application>Privoxy</application> runs as a separate application and talks
566 to the browser in the standardized HTTP protocol, just like a web server
571 <sect2 renderas="sect3" id="whichos">
572 <title>Which operating systems are supported?</title>
574 Include supported.sgml here:
579 <sect2 renderas="sect3" id="email-client">
580 <title>Can I use Privoxy with my email client?</title>
582 As long as there is some way to set a HTTP proxy for the client, then yes,
583 any application can be used, whether it is strictly speaking a
584 <quote>browser</quote> or not. Though this may not be the best approach for
585 dealing with some of the common abuses of HTML in email. See <link
586 linkend="outlook">How can I configure <application>Privoxy</application>
587 with <application>Outlook</application>?</link> below for more on
591 Be aware that HTML email presents a number of unique security and privacy
592 related issues, that can require advanced skills to overcome. The developers
593 recommend using email clients that can be configured to convert HTML to plain
594 text for these reasons.
598 <!-- Nobody is going to still be doing this!
599 <sect2 renderas="sect3" id="newinstall"><title>Can I install
600 Privoxy over Junkbuster?</title>
602 We recommend you un-install <application>Junkbuster</application>
603 first to minimize conflicts and confusion. You may want to
604 save your old configuration files for future reference. The configuration
605 files and syntax have substantially changed, so you will need to manually
606 port your old patterns. See the <ulink url="../user-manual/upgradersnote.html">note
607 to upgraders</ulink> and <ulink url="../user-manual/installation.html">installation
608 chapter</ulink> in the <ulink url="../user-manual/index.html">User Manual</ulink>
612 Note: Some installers may automatically un-install
613 <application>Junkbuster</application>, if present!
619 <sect2 renderas="sect3" id="firststep">
620 <title>I just installed Privoxy. Is there anything
621 special I have to do now?</title>
624 All browsers should be told to use <application>Privoxy</application>
625 as a proxy by specifying the correct proxy address and port number
626 in the appropriate configuration area for the browser. It's possible
627 to combine &my-app; with a packet filter to intercept HTTP requests
628 even if the client isn't explicitly configured to use &my-app;,
629 but where possible, configuring the client is recommended. See
630 <ulink url="../user-manual/startup.html">the User Manual for more
631 details</ulink>. You should also flush your browser's memory and disk
632 cache to get rid of any cached junk items, and remove any stored
633 <ulink url="http://en.wikipedia.org/wiki/Browser_cookie">cookies</ulink>.
639 <sect2 renderas="sect3" id="localhost"><title>What is the proxy address of Privoxy?</title>
641 If you set up the <application>Privoxy</application> to run on
642 the computer you browse from (rather than your ISP's server or some
643 networked computer on a LAN), the proxy will be on <literal>127.0.0.1</literal>
644 (sometimes referred to as <quote>localhost</quote>,
645 which is the special name used by every computer on the Internet to refer
646 to itself) and the port will be 8118 (unless you used the <ulink
647 url="../user-manual/config.html#LISTEN-ADDRESS">listen-address</ulink>
648 config option to tell <application>Privoxy</application> to run on
652 When configuring your browser's proxy settings you typically enter
653 the word <quote>localhost</quote> or the IP address <quote>127.0.0.1</quote>
654 in the boxes next to <quote>HTTP</quote> and <quote>Secure</quote> (HTTPS) and
655 then the number <quote>8118</quote> for <quote>port</quote>.
656 This tells your browser to send all web requests to <application>Privoxy</application>
657 instead of directly to the Internet.
660 <application>Privoxy</application> can also be used to proxy for
661 a Local Area Network. In this case, your would enter either the IP
662 address of the LAN host where <application>Privoxy</application>
663 is running, or the equivalent hostname, e.g. <literal>192.168.1.1</literal>.
664 Port assignment would be same as above. Note that
665 <application>Privoxy</application> doesn't listen on any LAN interfaces by
669 <application>Privoxy</application> does not currently handle
670 any other protocols such as FTP, SMTP, IM, IRC, ICQ, etc.
674 <sect2 renderas="sect3" id="nothing">
675 <title>I just installed Privoxy, and nothing is happening.
676 All the ads are there. What's wrong?</title>
679 Did you configure your browser to use <application>Privoxy</application>
680 as a proxy? It does not sound like it. See above. You might also try flushing
681 the browser's caches to force a full re-reading of pages. You can verify
682 that <application>Privoxy</application> is running, and your browser
683 is correctly configured by entering the special URL:
684 <ulink url="http://p.p/">http://p.p/</ulink>.
685 <!-- Use http://p.p/ instead of http://config.privoxy.org/ here because
686 of potential redirect caching problem (see next Q). -->
687 This should take you to a page titled <quote>This is Privoxy..</quote> with
688 access to <application>Privoxy's</application> internal configuration.
689 If you see this, then you are good to go. If you receive a page saying
690 <quote>Privoxy is not running</quote>, then the browser is not set up to use
691 your <application>Privoxy</application> installation.
692 If you receive anything else (probably nothing at all), it could either
693 be that the browser is not set up correctly, or that
694 <application>Privoxy</application> is not running at all. Check the <ulink
695 url="../user-manual/config.html#LOGFILE">log file</ulink>. For instructions
696 on starting <application>Privoxy</application> and browser configuration,
697 see the <ulink url="http://www.privoxy.org/user-manual/startup.html">chapter
698 on starting <application>Privoxy</application></ulink> in the
699 <ulink url="http://www.privoxy.org/user-manual/">User Manual</ulink>.
704 <sect2 renderas="sect3" id="notused">
705 <title>I get a <quote>Privoxy is not being used</quote> dummy page although
706 Privoxy is running and being used.</title>
709 First, make sure that Privoxy is <emphasis>really</emphasis> running and
710 being used by visiting <ulink url="http://p.p/">http://p.p/</ulink>. You
711 should see the <application>Privoxy</application> main page. If not, see
712 the <ulink url="http://www.privoxy.org/user-manual/startup.html">chapter
713 on starting <application>Privoxy</application></ulink> in the
714 <ulink url="http://www.privoxy.org/user-manual/">User Manual</ulink>.
718 Now if <ulink url="http://p.p/">http://p.p/</ulink> works for you, but
719 other parts of <application>Privoxy</application>'s web interface show
720 the dummy page, your browser has cached a redirection it encountered before
721 <application>Privoxy</application> was being used. You need to clear your
722 browser's cache. Note that shift-reloading the dummy page won't help, since
723 that'll only refresh the dummy page, not the redirection that lead you there.
727 The procedure for clearing the cache varies from browser to browser. For
728 example, <application>Mozilla/Netscape</application> users would click
729 <guibutton>Edit</guibutton> --> <guibutton>Preferences</guibutton> -->
730 <guibutton>Advanced</guibutton> --> <guibutton>Cache</guibutton> and
731 then click both <quote><guibutton>Clear Memory Cache</guibutton></quote>
732 and <quote><guibutton>Clear Disk Cache</guibutton></quote>.
733 In some <application>Firefox</application> versions it's
734 <guibutton>Tools</guibutton> --> <guibutton>Options</guibutton> -->
735 <guibutton>Privacy</guibutton> --> <guibutton>Cache</guibutton> and
736 then click <quote><guibutton>Clear Cache Now</guibutton></quote>.
737 <!-- In my Firefox versions it's the Netscape way. fk 2007-11-19-->
744 <!-- ~~~~~ New section ~~~~~ -->
746 <sect1 id="configuration"><title>Configuration</title>
747 <sect2 renderas="sect3">
748 <title id="actionsfile">What exactly is an <quote>actions</quote> file?</title>
751 &my-app; utilizes the concept of <quote>
752 <ulink url="../user-manual/actions-file.html#ACTIONS">actions</ulink></quote>
753 that are used to manipulate and control web page data.
754 <ulink url="../user-manual/actions-file.html">Actions files</ulink>
755 are where these <ulink url="../user-manual/actions-file.html#ACTIONS">actions</ulink>
756 that <application>Privoxy</application> could take while processing a certain
757 request, are configured. Typically, you would define a set of default actions
758 that apply globally to all URLs, then add exceptions to these defaults where needed.
759 There is a wide array of actions available that give the user a high degree
760 of control and flexibility on how to process each and every web page.
764 Actions can be defined on a <ulink
765 url="../user-manual/actions-file.html#AF-PATTERNS">URL pattern</ulink> basis, i.e.
766 for single URLs, whole web sites, groups or parts thereof etc. Actions can also be
767 grouped together and then applied to requests matching one or more patterns.
768 There are many possible actions that might apply to any given site. As an example,
769 if you are blocking <ulink url="http://en.wikipedia.org/wiki/Browser_cookie">cookies</ulink>
770 as one of your default actions, but need to accept cookies from a given site,
771 you would need to define an exception for this site in one of your actions
772 files, preferably in <filename>user.action</filename>.
777 <sect2 renderas="sect3" id="actionss">
778 <title>The <quote>actions</quote> concept confuses me. Please list
779 some of these <quote>actions</quote>.</title>
781 For a comprehensive discussion of the actions concept, please refer
782 to the <ulink url="../user-manual/actions-file.html">actions file
783 chapter</ulink> in the <ulink url="../user-manual/index.html">User
784 Manual</ulink>. It includes a <ulink
785 url="../user-manual/actions-file.html#ACTIONS">list of all actions</ulink>
786 and an <ulink url="../user-manual/actions-file.html#ACT-EXAMPLES">actions
787 file tutorial</ulink> to get you started.
792 <sect2 renderas="sect3">
793 <title id="actconfig">How are actions files configured? What is the easiest
794 way to do this?</title>
797 Actions files are just text files in a special syntax and can be edited
798 with a text editor. But probably the easiest way is to access
799 <application>Privoxy</application>'s user interface with your web browser
800 at <ulink url="http://config.privoxy.org/">http://config.privoxy.org/</ulink>
801 (Shortcut: <ulink url="http://p.p/">http://p.p/</ulink>) and then select
802 <quote><ulink url="http://config.privoxy.org/show-status">View &
803 change the current configuration</ulink></quote> from the menu. Note
804 that this feature must be explicitly enabled in the main config file
806 url="../user-manual/config.html#ENABLE-EDIT-ACTIONS">enable-edit-actions</ulink>).
811 <sect2 renderas="sect3">
812 <title>There are several different <quote>actions</quote> files. What are
813 the differences?</title>
815 Please have a look at the <ulink url="../user-manual/actions-file.html">the actions chapter</ulink>
816 in the <ulink url="../user-manual/index.html">User Manual</ulink> for a detailed explanation.
821 <sect2 renderas="sect3" id="getupdates"><title>Where can I get updated Actions Files?</title>
823 Based on your feedback and the continuing development, updates of
824 <filename>default.action</filename> will be
825 made available from time to time on the <ulink
826 url="http://sourceforge.net/project/showfiles.php?group_id=11118">files section</ulink> of
827 our <ulink url="http://sf.net/projects/ijbswa/">project page</ulink>.
831 If you wish to receive an email notification whenever we release updates of
832 <application>Privoxy</application> or the actions file, <ulink
833 url="http://lists.sourceforge.net/lists/listinfo/ijbswa-announce/">subscribe
834 to our announce mailing list</ulink>, ijbswa-announce@lists.sourceforge.net.
839 <sect2 renderas="sect3" id="newconfig"><title>Can I use my old config files?</title>
841 The syntax and purpose of configuration files has remained roughly the
842 same throughout the 3.x series, but backwards compatibility is not guaranteed.
843 Also each release contains updated, <quote>improved</quote> versions and it is
844 therefore strongly recommended to install the newer configuration files
845 and merge back your modifications.
849 <sect2 renderas="sect3" id="difficult">
850 <title>Why is the configuration so complicated?</title>
852 <quote>Complicated</quote> is in the eye of the beholder.
855 Privoxy is currently mainly written by and for people who are already
856 familiar with the underlying concepts like regular expressions, HTTP and HTML,
857 or are willing to become familiar with them to be able to get the most
858 out of a powerful and flexible tool such as Privoxy.
861 While everybody is expected to be able to get a Privoxy default installation
862 up and running, fine-tuning requires a certain amount of background
863 information and Privoxy's documentation mainly concentrates on the
864 Privoxy-specific parts while only providing references to the rest.
867 If you or anyone you know has the skills, time and energy to
868 reduce the barrier of entry, please <link linkend="participate">get involved</link>.
872 <sect2 renderas="sect3" id="yahoo"><title>How can I make my Yahoo/Hotmail/Gmail account work?</title>
874 The default configuration shouldn't impact the usability of any of these services.
875 It may, however, make all <ulink
876 url="http://en.wikipedia.org/wiki/Browser_cookie">cookies</ulink>
877 temporary, so that your browser will forget your
878 login credentials in between browser sessions. If you would like not to have to log
879 in manually each time you access those websites, simply turn off all cookie handling
880 for them in the <filename>user.action</filename> file. An example for yahoo might
884 <screen># Allow all cookies for Yahoo login:
886 { -<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> }
887 .login.yahoo.com</screen>
890 These kinds of sites are often quite complex and heavy with
891 <ulink url="http://en.wikipedia.org/wiki/Javascript">Javascript</ulink> and
892 thus <quote>fragile</quote>. So if <emphasis>still</emphasis> a problem,
894 url="../user-manual/actions-file.html#ALIASES">alias</ulink> just for such
898 <screen># Gmail is a _fragile_ site:
900 { <literal>fragile</literal> }
902 mail.google.com</screen>
905 Be sure to flush your browser's caches whenever making these kinds of
906 changes, just to make sure the changes <quote>take</quote>.
909 Make sure the domain, host and path are appropriate as well. Your browser can
910 tell you where you are specifically and you should use that information for
911 your configuration settings. Note that above it is not referenced as
912 <literal>gmail.com</literal>, which is a valid domain name.
917 <sect2 renderas="sect3" id="configfiles"> <title>What's the difference between the
918 <quote>Cautious</quote>, <quote>Medium</quote> and <quote>Advanced</quote> defaults?</title>
920 Configuring <application>Privoxy</application> is not entirely trivial. To
921 help you get started, we provide you with three different default action
922 <quote>profiles</quote> in the web based actions file editor at <ulink
923 url="http://config.privoxy.org/show-status">http://config.privoxy.org/show-status</ulink>.
924 See the <ulink url="../user-manual/actions-file.html"><citetitle>User
925 Manual</citetitle></ulink> for a list of actions, and how the default
930 Where the defaults are likely to break some sites, exceptions for
931 known popular <quote>problem</quote> sites are included, but in
932 general, the more aggressive your default settings are, the more exceptions
933 you will have to make later. New users are best to start off in
934 <quote>Cautious</quote> setting. This is safest and will have the fewest
935 problems. See the <ulink
936 url="../user-manual/index.html"><citetitle>User Manual</citetitle></ulink>
937 for a more detailed discussion.
941 It should be noted that the <quote>Advanced</quote> profile (formerly known
942 as the <quote>Adventuresome</quote> profile) is more
943 aggressive, and will make use of some of
944 <application>Privoxy's</application> advanced features. Use at your own risk!
949 <sect2 renderas="sect3" id="browseconfig"> <title>Why can I change the configuration
950 with a browser? Does that not raise security issues?</title>
952 It may seem strange that regular users can edit the config files with their
953 browsers, although the whole <filename>/etc/privoxy</filename> hierarchy
954 belongs to the user <quote>privoxy</quote>, with only 644 permissions.
957 When you use the browser-based editor, <application>Privoxy</application>
958 itself is writing to the config files. Because
959 <application>Privoxy</application> is running as the user <quote>privoxy</quote>,
960 it can update its own config files.
963 If you run <application>Privoxy</application> for multiple untrusted users (e.g. in
964 a LAN) or aren't entirely in control of your own browser, you will probably want
965 to make sure that the web-based editor and remote toggle features are
966 <quote>off</quote> by setting <quote><literal><ulink
967 url="../user-manual/config.html#ENABLE-EDIT-ACTIONS">enable-edit-actions</ulink>
968 0</literal></quote> and <quote><literal><ulink
969 url="../user-manual/config.html#ENABLE-REMOTE-TOGGLE">enable-remote-toggle</ulink>
970 0</literal></quote> in the <ulink url="../user-manual/config.html">main configuration file</ulink>.
973 As of &my-app; 3.0.7 these options are disabled by default.
978 <sect2 renderas="sect3">
979 <title id="filterfile">What is the <filename>default.filter</filename> file? What is a <quote>filter</quote>?</title>
981 The <ulink url="../user-manual/filter-file.html"><filename>default.filter</filename></ulink>
982 file is where <emphasis>filters</emphasis> as supplied by the developers are defined.
983 Filters are a special subset of actions that can be used to modify or
984 remove web page content or headers on the fly. Content filters can
985 be applied to <emphasis>anything</emphasis> in the page source,
986 header filters can be applied to either server or client headers.
987 Regular expressions are used to accomplish this.
990 There are a number of pre-defined filters to deal with common annoyances. The
991 filters are only defined here, to invoke them, you need to use the
993 url="../user-manual/actions-file.html#FILTER"><literal>filter</literal>
994 action</ulink> in one of the actions files. Content filtering is automatically
995 disabled for inappropriate MIME types, but if you know better than Privoxy
996 what should or should not be filtered you can filter any content you like.
1000 <emphasis>not</emphasis> be confused with <ulink
1001 url="../user-manual/actions-file.html#BLOCK"><literal>blocks</literal></ulink>, which
1002 is a completely different action, and is more typically used to block ads and
1007 If you are familiar with regular expressions, and HTML, you can look at
1008 the provided <filename>default.filter</filename> with a text editor and define
1009 your own filters. This is potentially a very powerful feature, but
1010 requires some expertise in both regular expressions and HTML/HTTP.
1011 <![%p-newstuff;[ You should
1012 place any modifications to the default filters, or any new ones you create
1013 in a separate file, such as <filename>user.filter</filename>, so they won't
1014 be overwritten during upgrades.
1015 The ability to define multiple filter files
1016 in <filename>config</filename> is a new feature as of v. 3.0.5.]]>
1020 There is no GUI editor option for this part of the configuration,
1021 but you can disable/enable the various pre-defined filters of the included
1022 <filename>default.filter</filename> file with the <ulink
1023 url="http://config.privoxy.org/show-status">web-based actions file editor</ulink>.
1024 Note that the custom actions editor must be explicitly enabled in
1025 the main config file (see <ulink
1026 url="../user-manual/config.html#ENABLE-EDIT-ACTIONS">enable-edit-actions</ulink>).
1030 If you intend to develop your own filters, you might want to have a look at
1032 url="http://www.fabiankeil.de/sourcecode/pft/">Privoxy-Filter-Test</ulink>.
1037 <sect2 renderas="sect3" id="lanconfig">
1038 <title>How can I set up Privoxy to act as a proxy for my
1041 By default, <application>Privoxy</application> only responds to requests
1042 from <literal>127.0.0.1</literal> (localhost). To have it act as a server for
1043 a network, this needs to be changed in the <ulink
1044 url="../user-manual/config.html">main configuration file</ulink>. Look for
1046 url="../user-manual/config.html#LISTEN-ADDRESS">listen-address</ulink></literal>
1047 option, which may be commented out with a <quote>#</quote> symbol. Make sure
1048 it is uncommented, and assign it the address of the LAN gateway interface,
1049 and port number to use. Assuming your LAN address is 192.168.1.1 and you
1050 wish to run <application>Privoxy</application> on port 8118, this line
1056 listen-address 192.168.1.1:8118</screen>
1060 Save the file, and restart <application>Privoxy</application>. Configure
1061 all browsers on the network then to use this address and port number.
1065 Alternately, you can have <application>Privoxy</application> listen on
1066 all available interfaces:
1071 listen-address :8118</screen>
1075 And then use <application>Privoxy's</application>
1077 url="../user-manual/config.html#PERMIT-ACCESS">permit-access</ulink>
1078 feature to limit connections. A firewall in this situation is recommended
1083 The above steps should be the same for any TCP network, regardless of
1088 If you run <application>Privoxy</application> on a LAN with untrusted users,
1089 we recommend that you double-check the <ulink
1090 url="../user-manual/config.html#ACCESS-CONTROL">access control and security</ulink>
1097 <sect2 renderas="sect3">
1098 <title id="noseeum">Instead of ads, now I get a checkerboard pattern. I don't want to see anything.</title>
1100 The replacement for blocked images can be controlled with the <ulink
1101 url="../user-manual/actions-file.html#SET-IMAGE-BLOCKER"><literal>set-image-blocker</literal>
1102 action</ulink>. You have the choice of a checkerboard pattern, a transparent 1x1 GIF
1103 image (aka <quote>blank</quote>), or a redirect to a custom image of your choice.
1104 Note that this choice only has effect for images which are blocked as images, i.e.
1105 whose URLs match both a <literal><ulink
1106 url="../user-manual/actions-file.html#HANDLE-AS-IMAGE">handle-as-image</ulink></literal>
1107 <emphasis>and</emphasis> <literal><ulink
1108 url="../user-manual/actions-file.html#BLOCK">block</ulink></literal> action.
1111 If you want to see nothing, then change the <ulink
1112 url="../user-manual/actions-file.html#SET-IMAGE-BLOCKER"><literal>set-image-blocker</literal>
1113 action</ulink> to <quote>blank</quote>. This can be done by editing the
1114 <filename>user.action</filename> file, or through the <ulink
1115 url="http://config.privoxy.org/show-status">web-based actions file editor</ulink>.
1120 <sect2 renderas="sect3">
1121 <title id="whyseeum">Why would anybody want to see a checkerboard pattern?</title>
1123 Remember that <link linkend="whatsanad">telling which image is an ad and which
1124 isn't</link>, is an educated guess. While we hope that the standard configuration
1125 is rather smart, it will make occasional mistakes. The checkerboard image is visually
1126 decent, and it shows you where images have been blocked, which can be very
1127 helpful in case some navigation aid or otherwise innocent image was
1128 erroneously blocked. It is recommended for new users so they can
1129 <quote>see</quote> what is happening. Some people might also enjoy seeing how
1130 many banners they <emphasis>don't</emphasis> have to see.
1135 <sect2 renderas="sect3">
1136 <title id="blockedbytext">I see some images being replaced with text
1137 instead of the checkerboard image. Why and how do I get rid of this?</title>
1139 This happens when the banners are not embedded in the HTML code of the
1140 page itself, but in separate HTML (sub)documents that are loaded into (i)frames
1141 or (i)layers, and these external HTML documents are blocked. Being non-images
1142 they get replaced by a substitute HTML page rather than a substitute image,
1143 which wouldn't work out technically, since the browser expects and accepts
1144 only HTML when it has requested an HTML document.
1147 The substitute page adapts to the available space and shows itself as a
1148 miniature two-liner if loaded into small frames, or full-blown with a
1149 large red "BLOCKED" banner if space allows.
1152 If you prefer the banners to be blocked by images, you must see to it that
1153 the HTML documents in which they are embedded are not blocked. Clicking
1154 the <quote>See why</quote> link offered in the substitute page will show
1155 you which rule blocked the page. After changing the rule and un-blocking
1156 the HTML documents, the browser will try to load the actual banner images
1157 and the usual image blocking will (hopefully!) kick in.
1162 <sect2 renderas="sect3" id="srvany">
1163 <title>Can Privoxy run as a service
1164 on Win2K/NT/XP?</title>
1167 Yes. Version 3.0.5 introduces full <application>Windows</application> service
1168 functionality. See <ulink url="../user-manual/installation.html#installation-pack-win">
1169 the <citetitle>User Manual</citetitle></ulink> for details on how to install and configure
1170 <application>Privoxy</application> as a service.
1173 Earlier ]]>3.x versions could run as a system service using <command>srvany.exe</command>.
1174 See the discussion at <ulink
1175 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>,
1176 for details, and a sample configuration.
1181 <sect2 renderas="sect3" id="otherproxy">
1182 <title>How can I make Privoxy work with other proxies?</title>
1184 This can be done and is often useful to combine the benefits of
1185 <application>Privoxy</application> with those of a another proxy,
1186 for example to cache content.
1188 url="../user-manual/config.html#FORWARDING">forwarding chapter</ulink>
1189 in the <ulink url="../user-manual/index.html">User Manual</ulink> which
1190 describes how to do this. If you intend to use Privoxy with Tor,
1191 please also have a look at
1192 <link linkend="TOR">How do I use Privoxy together with Tor</link>.
1196 <sect2 renderas="sect3" id="port-80">
1197 <title>Can I just set Privoxy to use port 80
1198 and thus avoid individual browser configuration?</title>
1201 No, its more complicated than that. This only works with special kinds
1202 of proxies known as <quote>intercepting</quote> proxies
1203 (<link linkend="INTERCEPTING">see below</link>).
1208 <sect2 renderas="sect3" id="transparent">
1209 <title>Can Privoxy run as a <quote>transparent
1210 </quote> proxy?</title>
1212 The whole idea of Privoxy is to modify client requests
1213 and server responses in all sorts of ways and therefore
1214 it's not a transparent proxy as described in
1215 <ulink url="http://tools.ietf.org/html/rfc2616">RFC 2616</ulink>.
1218 However, some people say <quote>transparent proxy</quote> when they
1219 mean <quote>intercepting proxy</quote>. If you are one of them,
1220 please read the <link linkend="INTERCEPTING">next entry</link>.
1225 <sect2 renderas="sect3" id="intercepting">
1226 <title>Can Privoxy run as a <quote>intercepting</quote> proxy?</title>
1228 <application>Privoxy</application> can't intercept traffic itself,
1229 but it can handle requests that where intercepted and redirected
1230 with a packet filter (like <application>PF</application> or
1231 <application>iptables</application>), as long as the <literal>Host</literal>
1235 As the <literal>Host</literal> header is required by HTTP/1.1 and as most
1236 web sites rely on it anyway, this limitation shouldn't be a problem.
1239 Please refer to your packet filter's documentation to learn how to
1240 intercept and redirect traffic into <application>Privoxy</application>.
1241 Afterward you just have to configure <application>Privoxy</application> to
1242 <ulink url="../user-manual/config.html#ACCEPT-INTERCEPTED-REQUESTS">accept
1243 intercepted requests</ulink>.
1248 <sect2 renderas="sect3" id="outlook">
1249 <title>How can I configure Privoxy for use with Outlook?</title>
1251 Versions of <application>Outlook</application> prior to Office 2007, use
1252 <application>Internet Explorer</application> components to both render HTML,
1253 and fetch any HTTP requests that may be embedded in an HTML email. So however
1254 you have <application>Privoxy</application> configured to work with IE, this
1255 configuration should automatically be shared, at least with older version of
1259 Starting with Office 2007, Microsoft is instead using the MS-Word rendering
1260 engine with Outlook. It is unknown whether this can be configured to use a
1262 <!-- FIXME HB 2009-02-15 -->
1266 <sect2 renderas="sect3" id="outlook-more">
1267 <title>How can I have separate rules just for HTML mail?</title>
1269 The short answer is, you can't. <application>Privoxy</application> has no way
1270 of knowing which particular application makes a request, so there is no way to
1271 distinguish between web pages and HTML mail.
1272 <application>Privoxy</application> just blindly proxies all requests. In the
1273 case of <application>Outlook Express</application> (see above), OE uses
1274 IE anyway, and there is no way for <application>Privoxy</application> to ever
1275 be able to distinguish between them (nor could any other proxy type application for
1279 For a good discussion of some of the issues involved (including privacy and
1280 security issues), see
1281 <ulink url="http://sourceforge.net/tracker/?func=detail&atid=211118&aid=629518&group_id=11118">http://sourceforge.net/tracker/?func=detail&atid=211118&aid=629518&group_id=11118</ulink>.
1285 <sect2 renderas="sect3" id="sneaky-cookies">
1286 <title>I sometimes notice cookies sneaking through. How?</title>
1289 url="http://en.wikipedia.org/wiki/Browser_cookie">Cookies</ulink> can be
1290 set in several ways. The classic method is via the
1291 <literal>Set-Cookie</literal> HTTP header. This is straightforward, and an
1292 easy one to manipulate, such as the &my-app; concept of
1293 <ulink url="../user-manual/actions-file.html#SESSION-COOKIES-ONLY">session-cookies-only</ulink>.
1294 There is also the possibility of using
1295 <ulink url="http://en.wikipedia.org/wiki/Javascript">Javascript</ulink> to
1296 set cookies (&my-app; calls these <literal>content-cookies</literal>). This
1297 is trickier because the syntax can vary widely, and thus requires a certain
1298 amount of guesswork. It is not realistic to catch all of these short of
1299 disabling Javascript, which would break many sites. And lastly, if the
1300 cookies are embedded in a HTTPS/SSL secure session via Javascript, they are beyond
1301 <application>Privoxy's</application> reach.
1304 All in all, &my-app; can help manage cookies in general, can help minimize
1305 the loss of privacy posed by cookies, but can't realistically stop all
1310 <sect2 renderas="sect3" id="evil-cookies">
1311 <title>Are all cookies bad? Why?</title>
1313 No, in fact there are many beneficial uses of
1315 url="http://en.wikipedia.org/wiki/Browser_cookie">cookies</ulink>. Cookies are just a
1316 method that browsers can use to store data between pages, or between browser
1317 sessions. Sometimes there is a good reason for this, and the user's life is a
1318 bit easier as a result. But there is a long history of some websites taking
1319 advantage of this layer of trust, and using the data they glean from you and
1320 your browsing habits for their own purposes, and maybe to your potential
1321 detriment. Such sites are using you and storing their data on your system.
1322 That is why the privacy conscious watch from whom those cookies come, and why
1323 they really <emphasis>need</emphasis> to be there.
1327 <ulink url="http://en.wikipedia.org/wiki/Browser_cookie">Wikipedia cookie
1328 definition</ulink> for more.
1332 <sect2 renderas="sect3" id="allow-cookies">
1333 <title>How can I allow permanent cookies for my trusted sites?</title>
1336 There are several actions that relate to cookies. The default behavior is to
1337 allow only <quote>session cookies</quote>, which means the cookies only last
1338 for the current browser session. This eliminates most kinds of abuse related
1339 to cookies. But there may be cases where you want cookies to last.
1342 To disable all cookie actions, so that cookies are allowed unrestricted,
1343 both in and out, for <literal>example.com</literal>:
1347 { -crunch-incoming-cookies -crunch-outgoing-cookies -session-cookies-only -filter{content-cookies} }
1348 .example.com</screen>
1351 Place the above in <filename>user.action</filename>. Note that some of these may
1352 be off by default anyway, so this might be redundant, but there is no harm
1353 being explicit in what you want to happen. <filename>user.action</filename>
1354 includes an alias for this situation, called
1355 <literal>allow-all-cookies</literal>.
1359 <sect2 renderas="sect3" id="multiples">
1360 <title>Can I have separate configurations for different users?</title>
1362 Each instance of <application>Privoxy</application> has its own
1363 configuration, including such attributes as the TCP port that it listens on.
1364 What you can do is run multiple instances of <application>Privoxy</application>, each with
1366 <ulink url="../user-manual/config.html#LISTEN-ADDRESS">listen-address</ulink>
1367 configuration setting, and configuration path, and then
1368 each of these can have their own configurations. Think of it as per-port
1372 Simple enough for a few users, but for large installations, consider having
1373 groups of users that might share like configurations.
1377 <sect2 renderas="sect3" id="whitelists">
1378 <title>Can I set-up Privoxy as a whitelist of
1379 <quote>good</quote> sites?</title>
1381 Sure. There are a couple of things you can do for simple white-listing.
1382 Here's one real easy one:
1385 ############################################################
1387 ############################################################
1388 { <ulink url="../user-manual/actions-file.html#BLOCK">+block</ulink> }
1389 / # Block *all* URLs
1391 ############################################################
1393 ############################################################
1394 { <ulink url="../user-manual/actions-file.html#BLOCK">-block</ulink> }
1397 games.example.com</screen>
1399 This allows access to only those three sites by first blocking all URLs, and
1400 then subsequently allowing three specific exceptions.
1403 Another approach is <application>Privoxy's</application>
1404 <literal>trustfile</literal> concept, which incorporates the notion of
1405 <quote>trusted referrers</quote>. See the <ulink
1406 url="../user-manual/config.html#TRUSTFILE">Trust documentation</ulink>
1410 These are fairly simple approaches and are not completely foolproof. There
1411 are various other configuration options that should be disabled (described
1412 elsewhere here and in <ulink url="../user-manual/">the User Manual</ulink>)
1413 so that users can't modify their own configuration and easily circumvent the
1418 <sect2 renderas="sect3" id="no-adblock">
1419 <title>How can I turn off ad-blocking?</title>
1421 Ad blocking is achieved through a complex application of various &my-app;
1422 <ulink url="../user-manual/actions-file.html">actions</ulink>. These
1423 actions are deployed against simple images, banners, flash animations,
1424 text pages, JavaScript, pop-ups and pop-unders, etc., so its not as simple as
1425 just turning one or two actions off. The various actions that make up
1426 &my-app; ad blocking are hard-coded into the default configuration files. It
1427 has been assumed that everyone using &my-app; is interested in this
1431 If you want to do without this, there are several approaches you can take:
1432 You can manually undo the many block rules in
1433 <filename>default.action</filename>. Or even easier, just create your own
1434 <filename>default.action</filename> file from scratch without the many ad
1435 blocking rules, and corresponding exceptions. Or lastly, if you are not
1436 concerned about the additional blocks that are done for privacy reasons, you
1437 can very easily over-ride <emphasis>all</emphasis> blocking with the
1438 following very simple rule in your <filename>user.action</filename>:
1442 # Unblock everybody, everywhere
1443 { <ulink url="../user-manual/actions-file.html#BLOCK">-block</ulink> }
1444 / # UN-Block *all* URLs</screen>
1447 Or even a more comprehensive reversing of various ad related actions:
1451 # Unblock everybody, everywhere, and turn off appropriate filtering, etc
1452 { <ulink url="../user-manual/actions-file.html#BLOCK">-block</ulink> \
1453 <ulink url="../user-manual/actions-file.html#FILTER-BANNERS-BY-SIZE">-filter{banners-by-size}</ulink> \
1454 <ulink url="../user-manual/actions-file.html#FILTER-BANNERS-BY-LINK">-filter{banners-by-link}</ulink> \
1455 <literal>allow-popups</literal> \
1457 / # UN-Block *all* URLs and allow ads</screen>
1460 This last <quote>action</quote> in this compound statement,
1461 <literal>allow-popups</literal>, is an <ulink
1462 url="../user-manual/actions-file.html#ALIASES">alias</ulink> that disables
1463 various pop-up blocking features.
1467 <sect2 renderas="sect3" id="templates">
1468 <title>How can I have custom template pages, like the
1469 <emphasis>BLOCKED</emphasis> page?</title>
1471 &my-app; <quote>templates</quote> are specialized text files utilized by
1472 &my-app; for various purposes and can easily be modified using any text
1473 editor. All the template pages are installed in a sub-directory appropriately
1474 named: <filename>templates</filename>. Knowing something about HTML syntax
1475 will of course be helpful.
1478 Be forewarned that the default templates are subject to being overwritten
1479 during upgrades. You can, however, create completely new templates,
1480 place them in another directory and specify the alternate path in the main
1481 <filename>config</filename>. For details, have a look at the <ulink
1482 url="../user-manual/config.html#templdir">templdir</ulink> option.
1486 <sect2 renderas="sect3" id="blockall">
1487 <title>How can I remove the <quote>Go There Anyway</quote> link from
1488 the <emphasis>BLOCKED</emphasis> page?</title>
1490 There is more than one way to do it (although Perl is not involved).
1493 Editing the BLOCKED template page (see above) may dissuade some users, but
1494 this method is easily circumvented. Where you need this level of control, you
1495 might want to build &my-app; from source, and disable various features that are
1496 available as compile-time options. You should
1497 <command>configure</command> the sources as follows:
1501 ./configure --disable-toggle --disable-editor --disable-force</screen>
1504 This will create an executable with hard-coded security features so that
1505 &my-app; does not allow easy bypassing of blocked sites, or changing the
1506 current configuration via any connected user's web browser.
1509 Finally, all of these features can also be toggled on/off via options in
1510 <application>Privoxy's</application> main <ulink
1511 url="../user-manual/config.html#ACCESS-CONTROL">config</ulink> file which
1512 means you don't have to recompile anything.
1518 <!-- ~ End section ~ -->
1521 <!-- ~~~~~ New section ~~~~~ -->
1523 <sect1 id="misc"><title>Miscellaneous</title>
1525 <sect2 renderas="sect3">
1526 <title id="slowsme">How much does Privoxy slow my browsing down? This
1527 has to add extra time to browsing.</title>
1529 How much of an impact depends on many things, including the CPU of the host
1530 system, how aggressive the configuration is, which specific actions are being triggered,
1531 the size of the page, the bandwidth of the connection, etc.
1534 Overall, it should not slow you down any in real terms, and may actually help
1535 speed things up since ads, banners and other junk are not typically being
1536 retrieved and displayed. The actual processing time required by
1537 <application>Privoxy</application> itself for each page, is relatively small
1538 in the overall scheme of things, and happens very quickly. This is typically
1539 more than offset by time saved not downloading and rendering ad images and
1540 other junk content (if ad blocking is being used).
1544 <quote>Filtering</quote> content via the <literal><ulink
1545 url="../user-manual/actions-file.html#FILTER">filter</ulink></literal> or
1547 url="../user-manual/actions-file.html#DEANIMATE-GIFS">deanimate-gifs</ulink></literal>
1548 actions may cause a perceived slowdown, since the entire document
1549 needs to be buffered before displaying. And on very large documents,
1550 filtering may have some measurable impact. How much depends on the page size,
1551 the actual definition of the filter(s), etc. See below. Most other actions
1552 have little to no impact on speed.
1555 Also, when filtering is enabled but zlib support isn't available, compression
1556 is often disabled (see <ulink
1557 url="../user-manual/actions-file.html#PREVENT-COMPRESSION">prevent-compression</ulink>).
1558 This can have an impact on speed as well, although it's probably smaller than
1559 you might think. Again, the page size, etc. will determine how much of an impact.
1565 <sect2 renderas="sect3" id="loadingtimes"><title>I notice considerable
1566 delays in page requests. What's wrong?</title>
1568 If you use any <literal><ulink
1569 url="../user-manual/actions-file.html#FILTER">filter</ulink></literal> action,
1570 such as filtering banners by size, web-bugs etc, or the <literal><ulink
1571 url="../user-manual/actions-file.html#DEANIMATE-GIFS">deanimate-gifs</ulink></literal>
1572 action, the entire document must be loaded into memory in order for the filtering
1573 mechanism to work, and nothing is sent to the browser during this time.
1576 The loading time typically does not really change much in real numbers, but
1577 the feeling is different, because most browsers are able to start rendering
1578 incomplete content, giving the user a feeling of "it works". This effect is
1579 more noticeable on slower dialup connections. Extremely large documents
1580 may have some impact on the time to load the page where there is filtering
1581 being done. But overall, the difference should be very minimal. If there is a
1582 big impact, then probably some other situation is contributing (like
1583 anti-virus software).
1586 Filtering is automatically disabled for inappropriate MIME types. But note
1587 that if the web server mis-reports the MIME type, then content that should
1588 not be filtered, could be. <application>Privoxy</application> only knows how
1589 to differentiate filterable content because of the MIME type as reported by
1590 the server, or because of some configuration setting that enables/disables
1595 <sect2 renderas="sect3" id="configurl"><title>What are "http://config.privoxy.org/" and
1596 "http://p.p/"?</title>
1598 <ulink url="http://config.privoxy.org/">http://config.privoxy.org/</ulink> is the
1599 address of <application>Privoxy</application>'s built-in user interface, and
1600 <ulink url="http://p.p/">http://p.p/</ulink> is a shortcut for it.
1603 Since <application>Privoxy</application> sits between your web browser and the Internet,
1604 it can simply intercept requests for these addresses and answer them with its built-in
1605 <quote>web server</quote>.
1608 This also makes for a good test for your browser configuration: If entering the
1609 URL <ulink url="http://config.privoxy.org/">http://config.privoxy.org/</ulink>
1610 takes you to a page saying <quote>This is Privoxy ...</quote>, everything is OK.
1611 If you get a page saying <quote>Privoxy is not working</quote> instead, then
1612 your browser didn't use <application>Privoxy</application> for the request,
1613 hence it could not be intercepted, and you have accessed the <emphasis>real</emphasis>
1614 web site at config.privoxy.org.
1620 out of date 09/02/06 HB
1621 <sect2 renderas="sect3" id="blocklist"><title>Do you still maintain the blocklists?</title>
1623 No. The patterns for blocking now reside (among other things) in the <ulink
1624 url="../user-manual/actions-file.html">actions files</ulink>, which are
1625 actively maintained instead. See next question ...
1629 <sect2 renderas="sect3" id="newads"><title>How can I submit new ads, or report
1632 Please see the <link linkend="contact">Contact section</link> for
1633 various ways to interact with the developers.
1638 <sect2 renderas="sect3" id="newads2"><title>If I do submit missed ads, will
1639 they be included in future updates?</title>
1641 Whether such submissions are eventually included in the
1642 <filename>default.action</filename> configuration file depends on how
1643 significant the issue is. We of course want to address any potential
1644 problem with major, high-profile sites such as <citetitle>Google</citetitle>,
1645 <citetitle>Yahoo</citetitle>, etc. Any site with global or regional reach,
1646 has a good chance of being a candidate. But at the other end of the spectrum
1647 are any number of smaller, low-profile sites such as for local clubs or
1648 schools. Since their reach and impact are much less, they are best handled by
1649 inclusion in the user's <filename>user.action</filename>, and thus would be
1650 unlikely to be included.
1656 <sect2 renderas="sect3" id="noonecares"><title>Why doesn't anyone answer my support
1659 Rest assured that it has been read and considered. Why it is not answered,
1660 could be for various reasons, including no one has a good answer for it, no
1661 one has had time to yet investigate it thoroughly, it has been reported
1662 numerous times already, or because not enough information was provided to help
1663 us help you. Your efforts are not wasted, and we do appreciate them.
1669 <sect2 renderas="sect3" id="ip"><title>How can I hide my IP address?</title>
1671 If you run both the browser and &my-app; locally, you cannot hide your IP
1672 address with <application>Privoxy</application> or ultimately any other
1673 software alone. The server needs to know your IP address so that it knows
1674 where to send the responses back.
1677 There are many publicly usable "anonymous" proxies out there, which
1678 provide a further level of indirection between you and the web server.
1681 However, these proxies are called "anonymous" because you don't need
1682 to authenticate, not because they would offer any real anonymity.
1683 Most of them will log your IP address and make it available to the
1684 authorities in case you violate the law of the country they run in. In fact
1685 you can't even rule out that some of them only exist to *collect* information
1686 on (those suspicious) people with a more than average preference for privacy.
1689 If you want to hide your IP address from most adversaries,
1690 you should consider chaining <application>Privoxy</application>
1691 with <ulink url="https://www.torproject.org/">Tor</ulink>.
1692 The configuration details can be found in
1693 <ulink url="#TOR">How do I use <application>Privoxy</application> together
1694 with <application>Tor</application> section</ulink>
1699 <sect2 renderas="sect3">
1700 <title id="anonforsure">Can Privoxy guarantee I am anonymous?</title>
1702 No. Your chances of remaining anonymous are improved, but unless you
1703 <ulink url="#TOR">chain <application>Privoxy</application> with <application>Tor</application></ulink>
1704 or a similar proxy and know what you're doing when it comes to configuring
1705 the rest of your system, you should assume that everything you do
1706 on the Web can be traced back to you.
1709 <application>Privoxy</application> can remove various information about you,
1710 and allows <emphasis>you</emphasis> more freedom to decide which sites
1711 you can trust, and what details you want to reveal. But it neither
1712 hides your IP address, nor can it guarantee that the rest of the system
1713 behaves correctly. There are several possibilities how a web sites can find
1714 out who you are, even if you are using a strict <application>Privoxy</application>
1715 configuration and chained it with <application>Tor</application>.
1718 Most of <application>Privoxy's</application> privacy-enhancing features can be easily subverted
1719 by an insecure browser configuration, therefore you should use a browser that can
1720 be configured to only execute code from trusted sites, and be careful which sites you trust.
1721 For example there is no point in having <application>Privoxy</application>
1722 modify the User-Agent header, if websites can get all the information they want
1723 through JavaScript, ActiveX, Flash, Java etc.
1726 A few browsers disclose the user's email address in certain situations, such
1727 as when transferring a file by FTP. <application>Privoxy</application>
1728 does not filter FTP. If you need this feature, or are concerned about the
1729 mail handler of your browser disclosing your email address, you might
1730 consider products such as <application>NSClean</application>.
1733 Browsers available only as binaries could use non-standard headers to give
1734 out any information they can have access to: see the manufacturer's license
1735 agreement. It's impossible to anticipate and prevent every breach of privacy
1736 that might occur. The professionally paranoid prefer browsers available as
1737 source code, because anticipating their behavior is easier. Trust the source,
1743 <sect2 renderas="sect3">
1744 <title id="proxytest">A test site says I am not using a Proxy.</title>
1746 Good! Actually, they are probably testing for some other kinds of proxies.
1747 Hiding yourself completely would require additional steps.
1751 <sect2 renderas="sect3" id="tor"><title>How do I use Privoxy
1752 together with Tor?</title>
1754 Before you configure <application>Privoxy</application> to use
1755 <ulink url="https://www.torproject.org/">Tor</ulink>,
1756 please follow the <citetitle>User Manual</citetitle> chapters
1757 <ulink url="../user-manual/installation.html">2. Installation</ulink> and
1758 <ulink url="../user-manual/startup.html">5. Startup</ulink> to make sure
1759 <application>Privoxy</application> itself is setup correctly.
1762 If it is, refer to <ulink url="https://www.torproject.org/documentation.html">Tor's
1763 extensive documentation</ulink> to learn how to install <application>Tor</application>,
1764 and make sure <application>Tor</application>'s logfile says that
1765 <quote>Tor has successfully opened a circuit</quote> and it
1766 <quote>looks like client functionality is working</quote>.
1769 If either <application>Tor</application> or <application>Privoxy</application>
1770 isn't working, their combination most likely will neither. Testing them on their
1771 own will also help you to direct problem reports to the right audience.
1772 If <application>Privoxy</application> isn't working, don't bother the
1773 <application>Tor</application> developers. If <application>Tor</application>
1774 isn't working, don't send bug reports to the <application>Privoxy</application> Team.
1777 If you verified that <application>Privoxy</application> and <application>Tor</application>
1778 are working, it is time to connect them. As far as <application>Privoxy</application>
1779 is concerned, <application>Tor</application> is just another proxy that can be reached
1780 by socks4, socks4a and socks5. Most likely you are interested in <application>Tor</application>
1781 to increase your anonymity level, therefore you should use socks5, to make sure DNS
1782 requests are done through <application>Tor</application> and thus invisible to your
1783 local network. Using socks4a would work too, but with socks5 you get more precise error
1788 <application>Privoxy's</application>
1789 <ulink url="../user-manual/config.html">main configuration file</ulink>
1790 is already prepared for <application>Tor</application>, if you are using a
1791 default <application>Tor</application> configuration and run it on the same
1792 system as &my-app;, you just have to edit the
1793 <ulink url="../user-manual/config.html#FORWARDING">forwarding section</ulink>
1794 and uncomment the line:
1798 # forward-socks5t / 127.0.0.1:9050 .
1802 This is enough to reach the Internet, but additionally you might want to
1803 uncomment the following forward rules, to make sure your local network is still
1804 reachable through Privoxy:
1808 # forward 192.168.*.*/ .
1809 # forward 10.*.*.*/ .
1810 # forward 127.*.*.*/ .
1814 Unencrypted connections to systems in these address ranges will
1815 be as (un)secure as the local network is, but the alternative is
1816 that your browser can't reach the network at all. Then again,
1817 that may actually be desired and if you don't know for sure
1818 that your browser has to be able to reach the local network,
1819 there's no reason to allow it.
1822 If you want your browser to be able to reach servers in your local
1823 network by using their names, you will need additional exceptions
1824 that look like this:
1828 # forward localhost/ .
1832 Save the modified configuration file and open
1833 <ulink url="http://config.privoxy.org/show-status">http://config.privoxy.org/show-status</ulink>
1834 in your browser, confirm that <application>Privoxy</application> has reloaded its configuration
1835 and that there are no other forward lines, unless you know that you need them. If everything looks good,
1837 <ulink url="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#IsMyConnectionPrivate">Tor
1838 Faq 4.2</ulink> to learn how to verify that you are really using <application>Tor</application>.
1841 Afterward, please take the time to at least skim through the rest
1842 of <application>Tor's</application> documentation. Make sure you understand
1843 what <application>Tor</application> does, why it is no replacement for
1844 application level security, and why you probably don't want to
1845 use it for unencrypted logins.
1849 <sect2 renderas="sect3">
1850 <title id="sitebreak">Might some things break because header information or
1851 content is being altered?</title>
1854 Definitely. It is common for sites to use browser type, browser version,
1855 HTTP header content, and various other techniques in order to dynamically
1856 decide what to display and how to display it. What you see, and what I see,
1857 might be very different. There are many, many ways that this can be handled,
1858 so having hard and fast rules, is tricky.
1862 The <quote>User-Agent</quote> is sometimes used in this way to identify
1863 the browser, and adjust content accordingly.
1867 Also, different browsers use different encodings of non-English
1868 characters, certain web servers convert pages on-the-fly according to the
1869 User Agent header. Giving a <quote>User Agent</quote> with the wrong
1870 operating system or browser manufacturer causes some sites in these languages
1871 to be garbled; Surfers to Eastern European sites should change it to
1872 something closer. And then some page access counters work by looking at the
1873 <quote>Referer</quote> header; they may fail or break if unavailable. The
1874 weather maps of Intellicast have been blocked by their server when no
1875 <quote>Referer</quote> or cookie is provided, is another example. (But you
1876 can forge both headers without giving information away). There are
1877 many other ways things can go wrong when trying to fool a web server. The
1878 results of which could inadvertently cause pages to load incorrectly,
1879 partially, or even not at all. And there may be no obvious clues as to just
1880 what went wrong, or why. Nowhere will there be a message that says
1881 <quote><emphasis>Turn off <literal>fast-redirects</literal> or else!</emphasis>
1886 Similar thoughts apply to modifying JavaScript, and, to a lesser degree,
1891 If you have problems with a site, you will have to adjust your configuration
1892 accordingly. Cookies are probably the most likely adjustment that may
1893 be required, but by no means the only one.
1899 <sect2 renderas="sect3">
1900 <title id="caching">Can Privoxy act as a <quote>caching</quote> proxy to
1901 speed up web browsing?</title>
1903 No, it does not have this ability at all. You want something like
1904 <ulink url="http://www.squid-cache.org/">Squid</ulink> or
1905 <ulink url="http://www.pps.jussieu.fr/~jch/software/polipo/">Polipo</ulink> for this.
1906 And, yes, before you ask, <application>Privoxy</application> can co-exist
1907 with other kinds of proxies like <application>Squid</application>.
1908 See the <ulink url="../user-manual/config.html#FORWARDING">forwarding
1909 chapter</ulink> in the <ulink url="../user-manual/index.html">user
1910 manual</ulink> for details.
1914 <sect2 renderas="sect3">
1915 <title id="firewall">What about as a firewall? Can Privoxy protect me?</title>
1917 Not in the way you mean, or in the way some firewall vendors claim they can.
1918 <application>Privoxy</application> can help protect your privacy, but can't
1919 protect your system from intrusion attempts. It is, of course, perfectly possible
1920 to use <emphasis>both</emphasis>.
1924 <sect2 renderas="sect3">
1925 <title id="wasted">I have large empty spaces / a checkerboard pattern now where
1926 ads used to be. Why?</title>
1928 It is technically possible to eliminate banners and ads in a way that frees
1929 their allocated page space. This could easily be done by blocking with
1930 <application>Privoxy's</application> filters,
1931 and eliminating the <emphasis>entire</emphasis> image references from the
1935 But, this would consume considerably more CPU resources (IOW, slow things
1936 down), would likely destroy the layout of some web pages which rely on the
1937 banners utilizing a certain amount of page space, and might fail in other
1938 cases, where the screen space is reserved (e.g. by HTML tables for instance).
1939 Also, making ads and banners disappear without any trace complicates
1940 troubleshooting, and would sooner or later be problematic.
1943 The better alternative is to instead let them stay, and block the resulting
1944 requests for the banners themselves as is now the case. This leaves either
1945 empty space, or the familiar checkerboard pattern.
1948 So the developers won't support this in the default configuration, but you
1949 can of course define appropriate filters yourself to achieve this.
1953 <sect2 renderas="sect3">
1954 <title id="ssl">How can Privoxy filter Secure (HTTPS) URLs?</title>
1956 Since secure HTTP connections are encrypted SSL sessions between your browser
1957 and the secure site, and are meant to be reliably <emphasis>secure</emphasis>,
1958 there is little that <application>Privoxy</application> can do but hand the raw
1959 gibberish data though from one end to the other unprocessed.
1962 The only exception to this is blocking by host patterns, as the client needs
1963 to tell <application>Privoxy</application> the name of the remote server,
1964 so that <application>Privoxy</application> can establish the connection.
1965 If that name matches a host-only pattern, the connection will be blocked.
1968 As far as ad blocking is concerned, this is less of a restriction than it may
1969 seem, since ad sources are often identifiable by the host name, and often
1970 the banners to be placed in an encrypted page come unencrypted nonetheless
1971 for efficiency reasons, which exposes them to the full power of
1972 <application>Privoxy</application>'s ad blocking.
1975 <quote>Content cookies</quote> (those that are embedded in the actual HTML or
1976 JS page content, see <literal><ulink
1977 url="../user-manual/actions-file.html#FILTER-CONTENT-COOKIES">filter{content-cookies}</ulink></literal>),
1978 in an SSL transaction will be impossible to block under these conditions.
1979 Fortunately, this does not seem to be a very common scenario since most
1980 cookies come by traditional means.
1985 <sect2 renderas="sect3">
1986 <title id="secure">Privoxy runs as a <quote>server</quote>. How
1987 secure is it? Do I need to take any special precautions?</title>
1989 On Unix-like systems, <application>Privoxy</application> can run as a non-privileged
1990 user, which is how we recommend it be run. Also, by default
1991 <application>Privoxy</application> listens to requests from <quote>localhost</quote>
1995 The server aspect of <application>Privoxy</application> is not itself directly
1996 exposed to the Internet in this configuration. If you want to have
1997 <application>Privoxy</application> serve as a LAN proxy, this will have to
1998 be opened up to allow for LAN requests. In this case, we'd recommend
1999 you specify only the LAN gateway address, e.g. 192.168.1.1, in the main
2000 <application>Privoxy</application> configuration file and check all <ulink
2001 url="../user-manual/config.html#ACCESS-CONTROL">access control and security
2002 options</ulink>. All LAN hosts can then use this as their proxy address
2003 in the browser proxy configuration, but <application>Privoxy</application>
2004 will not listen on any external interfaces. ACLs can be defined in addition,
2005 and using a firewall is always good too. Better safe than sorry.
2010 <sect2 renderas="sect3" id="turnoff">
2011 <title>Can I temporarily disable Privoxy?</title>
2013 &my-app; doesn't have a transparent proxy mode,
2014 but you can toggle off blocking and content filtering.
2017 The easiest way to do that is to point your browser
2018 to the remote toggle URL: <ulink
2019 url="http://config.privoxy.org/toggle">http://config.privoxy.org/toggle</ulink>.
2022 See the <ulink url="../user-manual/appendix.html#BOOKMARKLETS">Bookmarklets section</ulink>
2023 of the <citetitle>User Manual</citetitle> for an easy way to access this
2024 feature. Note that this is a feature that may need to be enabled in the main
2025 <filename>config</filename> file.
2030 <sect2 renderas="sect3" id="reallyoff">
2031 <title>When <quote>disabled</quote> is Privoxy totally
2032 out of the picture?</title>
2034 No, this just means all optional filtering and actions are disabled.
2035 <application>Privoxy</application> is still acting as a proxy, but just
2036 doing less of the things that <application>Privoxy</application> would
2037 normally be expected to do. It is still a <quote>middle-man</quote> in
2038 the interaction between your browser and web sites. See below to bypass
2043 <sect2 renderas="sect3" id="turnoff2">
2044 <title>How can I tell Privoxy to totally ignore certain sites?</title>
2046 Bypassing a proxy, or proxying based on arbitrary criteria, is purely a browser
2047 configuration issue, not a &my-app; issue. Modern browsers typically do have
2048 settings for not proxying certain sites. Check your browser's help files.
2053 <sect2 renderas="sect3" id="crunch">
2054 <title>My logs show Privoxy <quote>crunches</quote>
2055 ads, but also its own internal CGI pages. What is a <quote>crunch</quote>?</title>
2057 A <quote>crunch</quote> simply means <application>Privoxy</application> intercepted
2058 <emphasis>something</emphasis>, nothing more. Often this is indeed ads or
2059 banners, but <application>Privoxy</application> uses the same mechanism for
2060 trapping requests for its own internal pages. For instance, a request for
2061 <application>Privoxy's</application> configuration page at: <ulink
2062 url="http://config.privoxy.org">http://config.privoxy.org</ulink>, is
2063 intercepted (i.e. it does not go out to the 'net), and the familiar CGI
2064 configuration is returned to the browser, and the log consequently will show
2065 a <quote>crunch</quote>.
2068 Since version 3.0.7, Privoxy will also log the crunch reason.
2069 If you are using an older version you might want to upgrade.
2073 <sect2 renderas="sect3" id="downloads">
2074 <title>Can Privoxy effect files that I download
2075 from a webserver? FTP server?</title>
2077 From the webserver's perspective, there is no difference between
2078 viewing a document (i.e. a page), and downloading a file. The same is true of
2079 <application>Privoxy</application>. If there is a match for a <literal><ulink
2080 url="../user-manual/actions-file.html#BLOCK">block</ulink></literal> pattern,
2081 it will still be blocked, and of course this is obvious.
2084 Filtering is potentially more of a concern since the results are not always
2085 so obvious, and the effects of filtering are there whether the file is simply
2086 viewed, or downloaded. And potentially whether the content is some obnoxious
2087 advertisement, or Mr. Jimmy's latest/greatest source code jewel. Of course,
2088 one of these presumably is <quote>bad</quote> content that we don't want, and
2089 the other is <quote>good</quote> content that we do want.
2090 <application>Privoxy</application> is blind to the differences, and can only
2091 distinguish <quote>good from bad</quote> by the configuration parameters
2092 <emphasis>we</emphasis> give it.
2095 <application>Privoxy</application> knows the differences in files according
2096 to the <quote>Content Type</quote> as reported by the webserver. If this is
2097 reported accurately (e.g. <quote>application/zip</quote> for a zip archive),
2098 then <application>Privoxy</application> knows to ignore these where
2099 appropriate. <application>Privoxy</application> potentially can filter HTML
2100 as well as plain text documents, subject to configuration parameters of
2101 course. Also, documents that are of an unknown type (generally assumed to be
2102 <quote>text/plain</quote>) can be filtered, as will those that might be
2103 incorrectly reported by the webserver. If such a file is a downloaded file
2104 that is intended to be saved to disk, then any content that might have been
2105 altered by filtering, will be saved too, for these (probably rare) cases.
2108 Note that versions later than 3.0.2 do NOT filter document types reported as
2109 <quote>text/plain</quote>. Prior to this, <application>Privoxy</application>
2110 did filter this document type.
2113 In short, filtering is <quote>ON</quote> if a) the content type as reported
2114 by the webserver is appropriate <emphasis>and</emphasis> b) the configuration
2115 allows it (or at least does not disallow it). That's it. There is no magic
2116 cookie anywhere to say this is <quote>good</quote> and this is
2117 <quote>bad</quote>. It's the configuration that lets it all happen or not.
2120 If you download text files, you probably do not want these to be filtered,
2121 particularly if the content is source code, or other critical content. Source
2122 code sometimes might be mistaken for Javascript (i.e. the kind that might
2123 open a pop-up window). It is recommended to turn off filtering for download
2124 sites (particularly if the content may be plain text files and you are using
2125 version 3.0.2 or earlier) in your <filename>user.action</filename> file. And
2126 also, for any site or page where making <emphasis>any</emphasis> changes at
2127 all to the content is to be avoided.
2130 <application>Privoxy</application> does not do FTP at all, only HTTP
2131 and HTTPS (SSL) protocols.
2135 <sect2 renderas="sect3" id="downloads2">
2136 <title>I just downloaded a Perl script, and Privoxy
2137 altered it! Yikes, what is wrong!</title>
2143 <sect2 renderas="sect3" id="hostsfile">
2144 <title>Should I continue to use a <quote>HOSTS</quote> file for ad-blocking?</title>
2146 One time-tested technique to defeat common ads is to trick the local DNS
2147 system by giving a phony IP address for the ad generator in the local
2148 <filename>HOSTS</filename> file, typically using <literal>127.0.0.1</literal>, aka
2149 <literal>localhost</literal>. This effectively blocks the ad.
2152 There is no reason to use this technique in conjunction with
2153 <application>Privoxy</application>. <application>Privoxy</application>
2154 does essentially the same thing, much more elegantly and with much more
2155 flexibility. A large <filename>HOSTS</filename> file, in fact, not only
2156 duplicates effort, but may get in the way and seriously slow down your system.
2157 It is recommended to remove such entries from your <filename>HOSTS</filename> file. If you think
2158 your hosts list is neglected by <application>Privoxy's </application>
2159 configuration, consider adding your list to your <filename>user.action</filename> file:
2166 ads.galore.example.com
2167 etc.example.com</screen>
2171 <sect2 renderas="sect3" id="seealso">
2172 <title>Where can I find more information about Privoxy
2173 and related issues?</title>
2174 <!-- Include seealso.sgml boilerplate: -->
2176 <!-- end boilerplate -->
2181 <ulink url="../user-manual/seealso.html">user-manual</ulink> for
2187 <sect2 renderas="sect3" id="microsuck">
2188 <title>I've noticed that Privoxy changes <quote>Microsoft</quote> to
2189 <quote>MicroSuck</quote>! Why are you manipulating my browsing?</title>
2192 We're not. The text substitutions that you are seeing are disabled
2193 in the default configuration as shipped. You have either manually
2194 activated the <quote><literal>fun</literal></quote> filter which
2195 is clearly labeled <quote>Text replacements for subversive browsing
2196 fun!</quote> or you are using an older Privoxy version and have implicitly
2197 activated it by choosing the <quote>Advanced</quote> profile in the
2198 web-based editor. Please upgrade.
2202 <sect2 renderas="sect3" id="valid">
2203 <title>Does Privoxy produce <quote>valid</quote> HTML (or XHTML)?</title>
2206 Privoxy generates HTML in both its own <quote>templates</quote>, and possibly
2207 whenever there are text substitutions via a &my-app; filter. While this
2208 should always conform to the HTML 4.01 specifications, it has not been
2209 validated against this or any other standard.
2213 <sect2 renderas="sect3" id="surprise-privoxy">
2214 <title>How did you manage to get Privoxy on my computer without my consent?</title>
2217 We didn't. We make Privoxy available for download, but we don't go
2218 around installing it on other people's systems behind their back.
2219 If you discover Privoxy running on your system and are sure you didn't
2220 install it yourself, somebody else did. You may not even be running
2221 the real Privoxy, but maybe something else that only pretends to be
2222 Privoxy, or maybe something that is based on the real Privoxy,
2223 but has been modified.
2226 Lately there have been reports of problems with some kind of
2227 Privoxy versions that come preinstalled on some Netbooks.
2228 Some of the problems described are inconsistent with the behaviour
2229 of official Privoxy versions, which suggests that the preinstalled
2230 software may contain vendor modifications that we don't know about
2231 and thus can't debug.
2234 Privoxy's <link linkend="copyright">license</link> allows vendor
2235 modifications, but the vendor has to comply with the license,
2236 which involves informing the user about the changes and to make
2237 the changes available under the same license as Privoxy itself.
2240 If you are having trouble with a modified Privoxy version,
2241 please try to talk to whoever made the modifications before
2242 reporting the problem to us. Please also try to convince
2243 whoever made the modifications to talk to us. If you think
2244 somebody gave you a modified Privoxy version without complying
2245 to the license, please let us know.
2253 <!-- ~~~~~ New section ~~~~~ -->
2255 <sect1 id="trouble">
2256 <title>Troubleshooting</title>
2258 <sect2 renderas="sect3">
2259 <title id="refused">I cannot connect to any websites. Or, I am getting
2260 <quote>connection refused</quote> message with every web page. Why?</title>
2262 There are several possibilities:
2267 <application>Privoxy</application> is not running. Solution: verify
2268 that &my-app; is installed correctly, has not crashed, and is indeed running.
2269 Turn on <application>Privoxy's</application> logging, and look at the logs to see what they say.
2271 <listitem><para>Or your browser is configured for a different port than what
2272 <application>Privoxy</application> is using. Solution: verify that &my-app;
2273 and your browser are set to the same port (<literal>listen-address</literal>).
2275 <listitem><para>Or if using a forwarding rule, you have a configuration problem or a
2276 problem with a host in the forwarding chain. Solution: temporarily alter your
2277 configuration and take the forwarders out of the equation.
2280 Or you have a firewall that is interfering and blocking you. Solution:
2281 try disabling or removing the firewall as a simple test.
2288 <!-- ~~~~~ New section ~~~~~ -->
2289 <sect2 renderas="sect3" id="error503">
2290 <title>Why am I getting a 503 Error (WSAECONNREFUSED) on every page?</title>
2292 More than likely this is a problem with your TCP/IP networking. ZoneAlarm has
2293 been reported to cause this symptom -- even if not running! The solution is
2294 to either fight the ZA configuration, or uninstall ZoneAlarm, and then find
2295 something better behaved in its place. Other personal firewall type products
2296 may cause similar type problems if not configured correctly.
2300 <sect2 renderas="sect3">
2301 <title id="flushit">I just added a new rule, but the steenkin ad is
2302 still getting through. How?</title>
2304 If the ad had been displayed before you added its URL, it will probably be
2305 held in the browser's cache for some time, so it will be displayed without
2306 the need for any request to the server, and <application>Privoxy</application>
2307 will not be involved. Flush the browser's caches, and then try again.
2311 If this doesn't help, you probably have an error in the rule you
2312 applied. Try pasting the full URL of the offending ad into <ulink
2313 url="http://config.privoxy.org/show-url-info">http://config.privoxy.org/show-url-info</ulink>
2314 and see if it really matches your new rule. Blocking ads is like blocking
2315 spam: a lot of tinkering is required to stay ahead of the game. And
2316 remember you need to block the URL of the ad in question, which may be
2317 entirely different from the site URL itself. Most ads are hosted on different
2318 servers than the main site itself. If you right-click on the ad, you should
2319 be able to get all the relevant information you need. Alternately, you can
2320 find the correct URL by looking at <application>Privoxy's</application> logs
2321 (you may need to enable logging in the main config file if its disabled).
2324 Below is a slightly modified real-life log snippet that originates with one
2325 requested URL: <literal>www.example.com</literal> (name of site was changed
2326 for this example, the number of requests is real). You can see in this the
2327 complexity of what goes into making up this one <quote>page</quote>. There
2328 are eight different domains involved here, with thirty two separate URLs
2329 requested in all, making up all manner of images, Shockwave Flash,
2330 JavaScript, CSS stylesheets, scripts, and other related content. Some of this
2331 content is obviously <quote>good</quote> or <quote>bad</quote>, but not all.
2332 Many of the more questionable looking requests, are going to outside domains
2333 that seem to be identifying themselves with suspicious looking names, making
2334 our job a little easier. &my-app; has <quote>crunched</quote> (meaning caught
2335 and BLOCKED) quite a few items in this example, but perhaps missed a few as well.
2340 Request: www.example.com/
2341 Request: www.example.com/favicon.ico
2342 Request: img.example.com/main.css
2343 Request: img.example.com/sr.js
2344 Request: example.betamarker.com/example.html
2345 Request: www.lik-sang.com/Banners/bestsellers/skyscraper.php?likref=BSellers
2346 Request: img.example.com/pb.png
2347 Request: www.google-analytics.com/urchin.js crunch! (Blocked)
2348 Request: www.advertising-department.com/ats/switch.ps.php?26856 crunch! (Blocked)
2349 Request: img.example.com/p.gif
2350 Request: www.popuptraffic.com/assign.php?l=example&mode=behind crunch! (Blocked)
2351 Request: www.popuptraffic.com/scripts/popup.php?hid=5c3cf&tmpl=PBa.tmpl crunch! (Blocked)
2352 Request: www.popuptraffic.com/assign.php?l=example crunch! (Blocked)
2353 Request: www.lik-sang.com/Banners/best_sellers/best_sellers.css
2354 Request: www.adtrak.net/adx.js crunch! (Blocked)
2355 Request: img.example.com/hbg.gif
2356 Request: img.example.com/example.jpg
2357 Request: img.example.com/mt.png
2358 Request: img.example.com/mm.png
2359 Request: img.example.com/mb.png
2360 Request: www.popuptraffic.com/scripts/popup.php?hid=a71b91fa5&tmpl=Ua.tmp crunch! (Blocked)
2361 Request: www.example.com/tracker.js
2362 Request: www.lik-sang.com/Banners/best_sellers/lsi_head.gif
2363 Request: www.adtrak.net/adjs.php?n=020548130&what=zone:61 crunch! (Blocked)
2364 Request: www.adtrak.net/adjs.php?n=463594413&what=zone:58&source=Ua crunch! (Blocked)
2365 Request: www.lik-sang.com/Banners/best_sellers/bottomani.swf
2366 Request: mmm.elitemediagroup.net/install.php?allowpop=no&popupmincook=0&allowsp2=1 crunch! (Blocked)
2367 Request: www.example.com/tracker.js?screen=1400x1050&win=962x693
2368 Request: www.adtrak.net/adlog.php?bannerid=1309&clientid=439&zoneid=61 crunch! (Blocked)
2369 Request: 66.70.21.80/scripts/click.php?hid=5c3cf599a9efd0320d26&si
2370 Request: 66.70.21.80/img/pixel.gif
2371 Request: www.adtrak.net/adlog.php?bannerid=1309&clientid=439&zoneid=58&source=Ua&block=86400 crunch! (Blocked)
2372 Request: 66.70.21.80/scripts/click.php?hid=a71b9f6504b0c5681fa5&si=Ua
2377 Despite 12 out of 32 requests being blocked, the page looked, and seemed to
2378 behave perfectly <quote>normal</quote> (minus some ads, of course).
2383 <sect2 id="badsite" renderas="sect3">
2384 <title >One of my favorite sites does not work with Privoxy.
2385 What can I do?</title>
2388 First verify that it is indeed a <application>Privoxy</application> problem,
2389 by toggling off <application>Privoxy</application> through <ulink
2390 url="http://config.privoxy.org/toggle">http://config.privoxy.org/toggle</ulink>
2391 (the toggle feature may need to be enabled in the main
2392 <filename>config</filename>),
2393 and then shift-reloading the problem page (i.e. holding down the shift key
2394 while clicking reload. Alternatively, flush your browser's disk and memory
2399 If the problem went away, we know we have a configuration related problem.
2401 url="http://config.privoxy.org/show-url-info">http://config.privoxy.org/show-url-info</ulink>
2402 and paste the full URL of the page in question into the prompt. See which
2403 actions are being applied to the URL, and which matches in which actions
2404 files are responsible for that. It might be helpful also to look at your logs
2405 for this site too, to see what else might be happening (note: logging may need
2406 to be enabled in the main config file). Many sites are
2407 complex and require a number of related pages to help present their content.
2408 Look at what else might be used by the page in question, and what of that
2409 might be <emphasis>required</emphasis>.
2410 Now, armed with this information, go to
2412 url="http://config.privoxy.org/show-status">http://config.privoxy.org/show-status</ulink>
2413 and select the appropriate actions files for editing. </para>
2415 You can now either look for a section which disables the actions that
2416 you suspect to cause the problem and add a pattern for your site there,
2417 or make up a completely new section for your site. In any case, the recommended
2418 way is to disable only the prime suspect, reload the problem page, and only
2419 if the problem persists, disable more and more actions until you have
2420 identified the culprit. You may or may not want to turn the other actions
2421 on again. Remember to flush your browser's caches in between any such changes!
2424 Alternately, if you are comfortable with a text editor, you can accomplish
2425 the same thing by editing the appropriate actions file. Probably the easiest
2426 way to deal with such problems when editing by hand is to add your
2427 site to a <literal>{ fragile }</literal> section in <filename>user.action</filename>,
2428 which is an alias that turns off most <quote>dangerous</quote>
2429 actions, but is also likely to turn off more actions then needed, and thus lower
2430 your privacy and protection more than necessary,
2433 Troubleshooting actions is discussed in more detail in the <ulink
2434 url="../user-manual/appendix.html#ACTIONSANAT">User Manual appendix,
2435 Troubleshooting: the Anatomy of an Action</ulink>.
2436 There is also an <ulink
2437 url="../user-manual/actions-file.html#ACT-EXAMPLES">actions tutorial</ulink>
2438 with general configuration information and examples.
2441 As a last resort, you can always see if your browser has a setting that will
2442 bypass the proxy setting for selective sites. Modern browsers can do this.
2448 <!-- ~~~~~ New section ~~~~~ -->
2449 <sect2 id="dun" renderas="sect3">
2450 <title>After installing Privoxy, I have to log in
2451 every time I start IE. What gives?</title>
2454 This is a quirk that effects the installation of
2455 <application>Privoxy</application>, in conjunction with Internet Explorer and
2456 Internet Connection Sharing on Windows 2000 and Windows XP. The symptoms may
2457 appear to be corrupted or invalid DUN settings, or passwords.
2461 When setting up an NT based Windows system with
2462 <application>Privoxy</application> you may find that things do not seem to be
2463 doing what you expect. When you set your system up you will probably have set
2464 up Internet Connection Sharing (ICS) with Dial up Networking (DUN) when
2465 logged in with administrator privileges. You will probably have made this DUN
2466 connection available to other accounts that you may have set-up on your
2467 system. E.g. Mum or Dad sets up the system and makes accounts suitably
2468 configured for the kids.
2472 When setting up <application>Privoxy</application> in this environment you
2473 will have to alter the proxy set-up of Internet Explorer (IE) for the
2474 specific DUN connection on which you wish to use
2475 <application>Privoxy</application>. When you do this the ICS DUN set-up
2476 becomes user specific. In this instance you will see no difference if you
2477 change the DUN connection under the account used to set-up the connection.
2478 However when you do this from another user you will notice that the DUN
2479 connection changes to make available to "Me only". You will also find that
2480 you have to store the password under each different user!
2484 The reason for this is that each user's set-up for IE is user specific. Each
2485 set-up DUN connection and each LAN connection in IE store the settings for
2486 each user individually. As such this enforces individual configurations
2487 rather than common ones. Hence the first time you use a DUN connection after
2488 re-booting your system it may not perform as you expect, and prompt you for
2489 the password. Just set and save the password again and all should be OK.
2493 [Thanks to Ray Griffith for this submission.]
2498 <!-- ~~~~~ New section ~~~~~ -->
2499 <sect2 id="ftp" renderas="sect3">
2500 <title>I cannot connect to any FTP sites. Privoxy
2501 is blocking me.</title>
2503 <application>Privoxy</application> cannot act as a proxy for FTP traffic,
2504 so do not configure your browser to use <application>Privoxy</application>
2505 as an FTP proxy. The same is true for <emphasis>any protocol other than HTTP
2506 or HTTPS (SSL)</emphasis>.
2509 Most browsers understand FTP as well as HTTP. If you connect to a site, with
2510 a URL like <literal>ftp://ftp.example.com</literal>, your browser is making
2511 an FTP connection, and not a HTTP connection. So while your browser may
2512 speak FTP, <application>Privoxy</application> does not, and cannot proxy
2516 To complicate matters, some systems may have a generic <quote>proxy</quote>
2517 setting, which will enable various protocols, including
2518 <emphasis>both</emphasis> HTTP and FTP proxying! So it is possible to
2519 accidentally enable FTP proxying in these cases. And of course, if this
2520 happens, <application>Privoxy</application> will indeed cause problems since
2521 it does not know FTP. <![%p-newstuff;[Newer version will give a sane error
2522 message if a FTP connection is attempted.]]> Just disable the FTP setting
2523 and all will be well again.
2526 Will <application>Privoxy</application> ever proxy FTP traffic? Unlikely.
2527 There just is not much reason, and the work to make this happen is more than
2532 <!-- ~~~~~ New section ~~~~~ -->
2533 <sect2 id="macosxie" renderas="sect3">
2534 <title>In Mac OS X, I can't configure Microsoft Internet Explorer to use
2535 Privoxy as the HTTP proxy.</title>
2537 Microsoft Internet Explorer (in versions like 5.1) respects system-wide
2538 network settings. In order to change the HTTP proxy, open System
2539 Preferences, and click on the Network icon. In the settings pane that
2540 comes up, click on the Proxies tab. Ensure the "Web Proxy (HTTP)" checkbox
2541 is checked and enter <literal>127.0.0.1</literal> in the entry field.
2542 Enter <literal>8118</literal> in the Port field. The next time you start
2543 IE, it should reflect these values.
2547 <!-- ~~~~~ New section ~~~~~ -->
2548 <sect2 renderas="sect3" id="macosxuninstall">
2549 <title>In Mac OS X, I dragged the Privoxy folder to the trash in order to
2550 uninstall it. Now the finder tells me I don't have sufficient privileges to
2551 empty the trash.</title>
2553 Note: This ONLY applies to privoxy 3.0.6 and earlier.
2556 Just dragging the <application>Privoxy</application> folder to the trash is
2557 not enough to delete it. <application>Privoxy</application> supplies an
2558 <application>uninstall.command</application> file that takes care of
2559 these details. Open the trash, drag the <application>uninstall.command</application>
2560 file out of the trash and double-click on it. You will be prompted for
2561 confirmation and the administration password.
2564 The trash may still appear full after this command; emptying the trash
2565 from the desktop should make it appear empty again.
2569 <!-- ~~~~~ New section ~~~~~ -->
2570 <sect2 renderas="sect3" id="macosximages">
2571 <title>In Mac OS X Panther (10.3), images often fail to load and/or I
2572 experience random delays in page loading. I'm using
2573 <literal>localhost</literal> as my browser's proxy setting.</title>
2575 We believe this is due to an IPv6-related bug in Mac OS X, but don't fully
2576 understand the issue yet. In any case, changing the proxy setting to
2577 <literal>127.0.0.1</literal> instead of <literal>localhost</literal>
2578 works around the problem.
2582 <!-- ~~~~~ New section ~~~~~ -->
2583 <sect2 renderas="sect3" id="macosxaccountdeletion">
2584 <title>I just upgraded to Mac OS X 10.9 (Mavericks) and now &my-app; has stopped
2587 The upgrade process to Mac OS X Mavericks (10.9) from an earlier version of OS
2588 X deletes all user accounts that are either not part of OS X itself or are
2589 not interactive user accounts (ones you log in with). Since, for the sake of
2590 security, &my-app; runs as a non-privileged user that is created by its
2591 installer (_privoxy), it can no longer start up once that account gets deleted.
2592 The solution is to perform a complete uninstall using the supplied
2593 <application>uninstall.command</application> script (either back up your
2594 configuration files or select to not have the uninstaller remove them when it
2595 prompts you) and then reinstall &my-app; using the installer package and merge
2596 in your configuration.
2600 <!-- ~~~~~ New section ~~~~~ -->
2601 <!-- XXX: Is this still relevant now that we have gzip support? -->
2602 <sect2 renderas="sect3" id="blankpage">
2603 <title>I get a completely blank page at one site. <quote>View Source</quote>
2604 shows only: <markup><![CDATA[<html><body></body></html>]]></markup>. Without
2605 Privoxy the page loads fine.</title>
2607 Chances are that the site suffers from a bug in
2608 <ulink url="http://www.php.net/"><application>PHP</application></ulink>,
2609 which results in empty pages being sent if the client explicitly requests
2610 an uncompressed page, like <application>Privoxy</application> does.
2611 This bug has been fixed in PHP 4.2.3.
2614 To find out if this is in fact the source of the problem, try adding
2615 the site to a <literal>-prevent-compression</literal> section in
2616 <filename>user.action</filename>:
2619 # Make exceptions for ill-behaved sites:
2621 {-prevent-compression}
2622 .example.com</screen>
2624 If that works, you may also want to report the problem to the
2625 site's webmasters, telling them to use zlib.output_compression
2626 instead of ob_gzhandler in their PHP applications (workaround)
2627 or upgrade to PHP 4.2.3 or later (fix).
2631 <sect2 renderas="sect3" id="nohostname">
2632 <title>My logs show many <quote>Unable to get my own hostname</quote> lines.
2635 <application>Privoxy</application> tries to get the hostname of the system
2636 its running on from the IP address of the system interface it is bound to
2637 (from the <filename>config</filename> file
2638 <emphasis>listen-address</emphasis> setting). If the system cannot supply
2639 this information, <application>Privoxy</application> logs this condition.
2642 Typically, this would be considered a minor system configuration error. It is
2643 not a fatal error to <application>Privoxy</application> however, but may
2644 result in a much slower response from <application>Privoxy</application> on
2645 some platforms due to DNS timeouts.
2648 This can be caused by a problem with the local <filename>hosts</filename>
2649 file. If this file has been changed from the original, try reverting it to
2650 see if that helps. Make sure whatever name(s) are used for the local system,
2651 that they resolve both ways.
2654 You should also be able to work around the problem with the
2655 <ulink url="../user-manual/config.html#HOSTNAME">hostname option</ulink>.
2659 <sect2 renderas="sect3" id="inuse">
2660 <title>When I try to launch Privoxy, I get an
2661 error message <quote>port 8118 is already in use</quote> (or similar wording).
2664 Port 8118 is <application>Privoxy's</application> default TCP
2665 <quote>listening</quote> port. Typically this message would mean that there
2666 is already one instance of <application>Privoxy</application> running, and
2667 your system is actually trying to start a second
2668 <application>Privoxy</application> on the same port, which will not work.
2669 (You can have multiple instances but they must be assigned different ports.)
2670 How and why this might happen varies from platform to platform, but you need
2671 to check your installation and start-up procedures.
2675 <sect2 renderas="sect3" id="demoronizer">
2677 Pages with UTF-8 fonts are garbled.
2680 This may be the result of an overly aggressive filter. The filters that
2681 are enabled in the default configuration aren't expected to cause problems
2682 like this. If you enabled the <quote>demoronizer</quote> filter, please
2683 try temporarily disabling it.
2686 If that doesn't help, temporarily disable all filters to see if another
2687 filter could be the culprit. If the problem disappears, enable the filters
2688 one by one, until the problem reappears and the offending filter is found.
2691 Once the problem-causing filter is known, it can be fixed or disabled.
2694 Upgrading <application>Privoxy</application>, or going to the most recent
2695 <filename>default.action</filename> file available from <ulink
2696 url="http://sourceforge.net/project/showfiles.php?group_id=11118">SourceForge</ulink>
2697 might be worth a try, too.
2701 <sect2 renderas="sect3" id="demoronizer2">
2703 Why are binary files (such as images) corrupted when Privoxy
2707 This may also be caused by an (<link linkend="DEMORONIZER">overly aggressive
2708 filter</link> in conjunction with a web server that is misreporting the content
2709 type. By default binary files are exempted from
2710 <application>Privoxy's</application> filtering
2711 (unless the web server by mistake says the file is something else).
2715 <sect2 renderas="sect3" id="demoronizer3">
2717 What is the <quote>demoronizer</quote> and why is it there?
2720 The original demoronizer was a Perl script that cleaned up HTML pages which
2721 were created with certain Microsoft products. MS has used proprietary extensions
2722 to standardized font encodings (ISO 8859-1), which has caused problems for pages
2723 that are viewed with non-Microsoft products (and are expecting to see a
2724 standard set of fonts). The demoronizer corrected these errors so the pages
2725 displayed correctly. <application>Privoxy</application> borrowed from this
2726 script, introducing a filter based on the original demoronizer, which in turn could
2727 correct these errors on the fly.
2730 But this is only needed in some situations, and will cause serious problems in some
2734 If you are using Microsoft products, you do not need it. If you need to view
2735 pages with UTF-8 characters (such as Cyrillic or Chinese), then it will
2736 cause corruption of the fonts, and thus <emphasis>should not be on</emphasis>.
2739 On the other hand, if you use non-Microsoft products, and you occasionally
2740 notice weird characters on pages, you might want to try it.
2744 <sect2 renderas="sect3" id="windowopen">
2746 Why do I keep seeing <quote>PrivoxyWindowOpen()</quote> in raw source code?
2749 <application>Privoxy</application> is attempting to disable malicious
2750 <ulink url="http://en.wikipedia.org/wiki/Javascript">Javascript</ulink>
2751 in this case, with the <literal>unsolicited-popups</literal>
2752 filter. <application>Privoxy</application> cannot tell very well
2753 <quote>good</quote> code snippets from <quote>bad</quote> code snippets.
2756 If you see this in HTML source, and the page displays without problems, then
2757 this is good, and likely some pop-up window was disabled. If you see this
2758 where it is causing a problem, such as a downloaded program source code file,
2759 then you should set an exception for this site or page such that the
2760 integrity of the page stays in tact by disabling all filtering.
2764 <sect2 renderas="sect3" id="dnserrors">
2766 I am getting too many DNS errors like <quote>404 No Such Domain</quote>. Why
2767 can't Privoxy do this better?
2770 There are potentially several factors here. First of all, the DNS resolution
2771 is done by the underlying operating system -- not
2772 <application>Privoxy</application> itself. <application>Privoxy</application>
2773 merely initiates the process and hands it off, and then later reports
2774 whatever the outcome was and tries to give a coherent message if there seems
2775 to be a problem. In some cases, this might otherwise be mitigated by the
2776 browser itself which might try some work-arounds and alternate approaches (e.g
2777 adding <quote>www.</quote> to the URL).
2780 In other cases, if <application>Privoxy</application> is being chained
2781 with another proxy, this could complicate the issue, and cause undue
2782 delays and timeouts. In the case of a <quote>socks4a</quote> proxy, the socks
2783 server handles all the DNS. <application>Privoxy</application> would just be
2784 the <quote>messenger</quote> which is reporting whatever problem occurred
2785 downstream, and not the root cause of the error.
2789 In any case, versions newer than 3.0.3 include various improvements to help
2790 <application>Privoxy</application> better handle these cases.
2794 <sect2 renderas="sect3" id="allcpu">
2796 At one site Privoxy just hangs, and starts taking
2797 all CPU. Why is this?
2800 This is probably a manifestation of the <quote>100% cpu</quote> problem that
2801 occurs on pages containing many (thousands upon thousands) of blank lines. The blank lines
2802 are in the raw HTML source of the page, and the browser just ignores them. But the
2803 pattern matching in <application>Privoxy's</application> page filtering
2804 mechanism is trying to match against absurdly long strings and this becomes
2805 very CPU-intensive, taking a long, long time to complete.
2808 Until a better solution comes along, disable filtering on these pages,
2809 particularly the <literal>js-annoyances</literal> and
2810 <literal>unsolicited-popups</literal> filters. If you run into this problem
2811 with a recent &my-app; version, please send a problem report.
2815 <sect2 renderas="sect3" id="slowcrawl">
2816 <title>I just installed Privoxy, and all my
2817 browsing has slowed to a crawl. What gives? </title>
2819 This should not happen, and for the overwhelming number of users world-wide,
2820 it does not happen. I would suspect some inadvertent interaction of software
2821 components such as anti-virus software, spyware protectors, personal
2822 firewalls or similar components. Try disabling (or uninstalling) these one
2823 at a time and see if that helps. Either way, if you are using a
2824 recent &my-app; version, please report the problem.
2828 <sect2 renderas="sect3" id="preventcomp">
2829 <title>Why do my filters work on some sites but not on others? </title>
2831 It's probably due to compression. It is a common practice for web servers to
2832 send their content <quote>compressed</quote> in order to speed things up, and
2833 then let the browser <quote>uncompress</quote> them. When compiled with zlib support
2834 &my-app; can decompress content before filtering, otherwise you may want to enable
2836 url="../user-manual/actions-file.html#PREVENT-COMPRESSION">prevent-compression</ulink>.
2839 As of &my-app; 3.0.9, zlib support is enabled in the default builds.
2844 <sect2 renderas="sect3" id="ssl-warnings">
2845 <title>On some HTTPS sites my browser warns me about unauthenticated content,
2846 the URL bar doesn't get highlighted and the lock symbol appears to be broken.
2847 What's going on?</title>
2849 Probably the browser is requesting ads through HTTPS and &my-app;
2850 is blocking the requests. Privoxy's error messages are delivered
2851 unencrypted and while it's obvious for the browser that the HTTPS
2852 request is already blocked by the proxy, some warn about unauthenticated
2856 To work around the problem you can redirect those requests to an invalid
2857 local address instead of blocking them. While the redirects aren't
2858 encrypted either, many browsers don't care. They simply follow the
2859 redirect, fail to reach a server and display an error message instead
2863 To do that, enable logging to figure out which requests get blocked by
2864 &my-app; and add the hosts (no path patterns) to a section like this:
2869 {+redirect{http://127.0.0.1:0/} -block -limit-connect}
2875 Additionally you have to configure your browser to contact
2876 <quote>127.0.0.1:0</quote> directly (instead of through &my-app;).
2879 To add a proxy exception in <application>Mozilla Firefox</application>
2880 open the <quote>Preferences</quote>, click the <quote>Settings</quote>
2881 button located on the <quote>Network</quote> tab in the <quote>Advanced</quote>
2882 section, and add <quote>127.0.0.1:0</quote> in the <quote>No Proxy for:</quote>
2888 <sect2 renderas="sect3" id="se-linux">
2889 <title>I get selinux error messages. How can I fix this?</title>
2891 Please report the problem to the creator of your selinux policies.
2894 The problem is that some selinux policy writers aren't familiar
2895 with the application they are trying to <quote>secure</quote> and
2896 thus create policies that make no sense.
2899 In <application>Privoxy's</application> case the problem usually
2900 is that the policy only allows outgoing connections for certain
2901 destination ports (e.g. 80 and 443). While this may cover the
2902 standard ports, websites occasionally use other ports as well.
2903 This isn't a security problem and therefore <application>Privoxy's</application>
2904 default configuration doesn't block these requests.
2907 If you really want to block these ports (and don't be able
2908 to load websites that don't use standard ports), you should
2909 configure Privoxy to block these ports as well, so it doesn't
2910 trigger the selinux warnings.
2915 <sect2 renderas="sect3" id="gentoo-ricers">
2916 <title>I compiled &my-app; with Gentoo's portage and it appears to be very slow. Why?</title>
2918 Probably you unintentionally compiled &my-app; without threading support
2919 in which case requests have to be serialized and only one can be served
2923 Check your <quote>USE</quote> flags and make sure they include
2924 <quote>threads</quote>. If they don't, add the flag and rebuild &my-app;.
2927 If you compiled &my-app; with threading support (on POSIX-based systems),
2928 the <quote>Conditional #defines</quote> section on <ulink
2929 url="http://config.privoxy.org/show-status">http://config.privoxy.org/show-status</ulink>
2930 will list <quote>FEATURE_PTHREAD</quote> as <quote>enabled</quote>.
2937 <!-- ~~~~~ New section ~~~~~ -->
2938 <sect1 id="contact"><title>Contacting the developers, Bug Reporting and Feature Requests</title>
2939 <!-- Include contacting.sgml -->
2941 <!-- end contacting -->
2944 <!-- ~~~~~ New section ~~~~~ -->
2945 <sect1 id="copyright"><title>Privoxy Copyright, License and History</title>
2947 <!-- Include copyright.sgml -->
2953 Portions of this document are <quote>borrowed</quote> from the original
2954 <application>Junkbuster</application> (tm) FAQ, and modified as
2955 appropriate for <application>Privoxy</application>.
2958 <!-- ~~~~~ New section ~~~~~ -->
2959 <sect2><title>License</title>
2960 <!-- Include copyright.sgml: -->
2962 <!-- end copyright -->
2964 <!-- ~ End section ~ -->
2966 <!-- ~~~~~ New section ~~~~~ -->
2967 <sect2><title>History</title>
2968 <!-- Include history.sgml -->
2974 <!-- ~ End section ~ -->
2977 <!-- ~~~~~ New section ~~~~~ -->
2979 <sect1 id="seealso"><title>See also</title>
2981 <!-- Include seealso.sgml -->
2992 Tue 09/11/01 06:38:14 PM EST: Test SGML doc by Hal Burgiss.
2994 This program is free software; you can redistribute it
2995 and/or modify it under the terms of the GNU General
2996 Public License as published by the Free Software
2997 Foundation; either version 2 of the License, or (at
2998 your option) any later version.
3000 This program is distributed in the hope that it will
3001 be useful, but WITHOUT ANY WARRANTY; without even the
3002 implied warranty of MERCHANTABILITY or FITNESS FOR A
3003 PARTICULAR PURPOSE. See the GNU General Public
3004 License for more details.
3006 The GNU General Public License should be included with
3007 this file. If not, you can view it at
3008 http://www.gnu.org/copyleft/gpl.html
3009 or write to the Free Software Foundation, Inc.,
3010 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA
3013 Revision 2.103 2014/10/21 12:02:16 fabiankeil
3016 Revision 2.102 2014/10/06 10:20:09 fabiankeil
3017 Update the 'Would you like to donate?' section
3019 Mention that donations will be used to get TODO list
3020 items done and add the Zwiebelfreunde e.V. bank
3023 Revision 2.101 2014/05/26 10:48:39 fabiankeil
3024 Bump entities for 3.0.22 UNRELEASED
3026 Revision 2.100 2014/05/05 09:59:30 fabiankeil
3027 Recommend forward-socks5t when using Tor
3029 It seems to work fine and modifying the Tor configuration
3030 to profit from it hasn't been necessary for a while now.
3032 Revision 2.99 2014/02/10 14:43:46 fabiankeil
3033 Make 'demoronizer' FAQ entries more generic
3035 Revision 2.98 2013/12/16 11:20:14 fabiankeil
3036 Spell 'more reliably' more correctly
3038 Reported by Reuben Thomas in #3615276.
3040 Revision 2.97 2013/11/07 14:42:02 fabiankeil
3041 White-space adjustments for the previous commit
3043 Revision 2.96 2013/11/06 19:24:18 diem
3044 Added an entry for the _privoxy user account deletion issue when upgrading to OS X 10.9
3046 Revision 2.95 2013/11/06 16:28:58 fabiankeil
3047 Rephrase the 'Why is the configuration so complicated?' answer
3049 .. to be slightly less condescending.
3051 Anonymously suggested in #3615122.
3053 Revision 2.94 2013/06/21 14:46:46 fabiankeil
3054 Link to the SPI homepage instead of the "About SPI" page which no longer exists
3056 Reported by Mark Nelson in #3614557.
3058 Revision 2.93 2013/06/21 14:46:09 fabiankeil
3059 Update link to the SF registration form
3061 Reported by Mark Nelson in #3614557.
3063 Revision 2.92 2013/03/01 17:44:24 fabiankeil
3064 Bump entities for 3.0.21 stable
3066 Revision 2.91 2013/02/26 15:09:35 fabiankeil
3067 Bump entities for 3.0.21 UNRELEASED
3069 Revision 2.90 2013/01/06 11:25:52 fabiankeil
3070 Set entities to 3.0.20 beta
3072 Revision 2.89 2012/06/19 12:49:48 fabiankeil
3073 Update Junkbuster-related FAQ sections
3075 Remove the dead links and use the past tense as
3076 the fork happened years ago.
3078 Revision 2.88 2012/04/22 12:16:24 fabiankeil
3079 Remove an obsolete newstuff marker
3081 Revision 2.87 2012/04/22 12:16:09 fabiankeil
3082 Fix an URL in the "Privoxy with Tor" FAQ
3084 Revision 2.86 2012/03/18 15:41:49 fabiankeil
3085 Bump entities to 3.0.20 UNRELEASED
3087 Revision 2.85 2011/12/26 17:05:40 fabiankeil
3088 Bump entities for 3.0.19
3090 Revision 2.84 2011/11/13 17:03:54 fabiankeil
3091 Bump entities for 3.0.18 stable
3093 Revision 2.83 2011/11/13 16:53:24 fabiankeil
3094 Rephrase the donations section some more
3096 Mention that the domain is now sponsored by Mythic Beasts Ltd
3097 and make it clear that asking questions about donations is
3100 Revision 2.82 2011/11/13 16:50:34 fabiankeil
3101 Note that donations for Privoxy are currently only tax-deductible in the US
3103 As it turns out tax-deductible donations in a few other western
3104 countries are theoretically possible through partner organizations
3105 but aren't available out of the box.
3107 Revision 2.81 2011/09/04 11:10:12 fabiankeil
3108 Ditch trailing whitespace
3110 Revision 2.80 2011/08/18 11:42:50 fabiankeil
3111 Bump some more documentation copyright ranges.
3113 Revision 2.79 2011/08/17 10:40:07 fabiankeil
3114 Update the entities.
3116 This commit is chronological out of order.
3118 Revision 2.78 2011/04/19 13:14:10 fabiankeil
3119 Fix spelling errors in the documentation. Found with codespell.
3121 Revision 2.77 2011/03/03 14:22:12 fabiankeil
3122 Remove duplicated 'the'
3124 Revision 2.76 2010/11/22 10:35:02 fabiankeil
3125 Mention socks5 in another part of the Tor section.
3127 Revision 2.75 2010/11/13 10:08:00 fabiankeil
3128 Fix a link to the 'intercepting' entry and add another one
3130 Revision 2.74 2010/11/13 10:07:46 fabiankeil
3131 Remove the product names in the 'otherproxy' entry's title.
3133 I'm tired of getting the 'otherproxy' entry as first hit
3134 when searching the index for the Tor FAQ.
3136 Revision 2.73 2010/11/06 12:55:48 fabiankeil
3137 Set p-version to 3.0.17
3139 Revision 2.72 2010/02/27 12:13:17 fabiankeil
3142 Revision 2.71 2010/02/27 12:12:13 fabiankeil
3143 Consistently recommending socks5 in the Tor entry and mention its advantage compared to socks4a.
3144 Reported by David in #2960129.
3146 Revision 2.70 2010/02/20 18:08:31 ler762
3149 Revision 2.69 2010/02/13 17:38:27 fabiankeil
3150 Update entities for 3.0.16 stable.
3152 Revision 2.68 2010/01/30 19:51:28 fabiankeil
3153 New FAQ entry: How did you manage to get Privoxy on my computer without my consent?
3155 Also bump copyright.
3157 Revision 2.67 2009/11/15 14:24:12 fabiankeil
3158 Prepare to generate docs for 3.0.16 UNRELEASED.
3160 Revision 2.66 2009/10/10 05:48:55 fabiankeil
3161 Prepare for 3.0.15 beta.
3163 Revision 2.65 2009/07/18 16:24:39 fabiankeil
3164 Bump entities for 3.0.14 beta.
3166 Revision 2.64 2009/07/18 12:18:52 fabiankeil
3167 Don't describe the action files in the FAQ when we can simply link to the description in the User Manual.
3169 Revision 2.63 2009/06/15 15:08:03 fabiankeil
3170 Patch #2806626 from Frédéric Crozat to fix a closing tag.
3172 Revision 2.62 2009/06/12 14:30:58 fabiankeil
3173 Update entities for 3.0.13 beta.
3175 Revision 2.61 2009/06/12 11:52:33 fabiankeil
3176 Mention the TODO list in the participate entry.
3178 Revision 2.60 2009/04/07 12:25:05 fabiankeil
3179 In the "I would like to help ..." entry:
3180 - Change the ids to more general ones as helping out doesn't require
3181 joining the team (and joining the team requires significantly helping
3183 - Add links to the subscription pages for the main mailing lists.
3185 Revision 2.59 2009/03/28 15:33:41 fabiankeil
3186 Recommend the use of forward-socks5 when forwarding to Tor.
3187 The error messages are more detailed than with forward-socks4a.
3189 Revision 2.58 2009/03/21 12:27:44 fabiankeil
3190 Turn the donation entry title into a question,
3191 also rephrase the content a bit.
3193 Revision 2.57 2009/03/19 19:07:49 fabiankeil
3194 First draft of a "Donating" entry. To be polished tomorrow.
3196 Revision 2.56 2009/02/19 17:05:05 fabiankeil
3197 Explain slowness when build with Gentoo's portage.
3199 Revision 2.55 2009/02/19 02:20:21 hal9
3200 Make some links in seealso conditional. Man page is now privoxy only links.
3202 Revision 2.54 2009/02/15 20:47:12 hal9
3205 Revision 2.53 2009/02/15 20:46:13 hal9
3206 Update Outlook HTML rendering engine comments re: Office 2007.
3208 Revision 2.52 2009/02/14 10:27:52 fabiankeil
3209 Finish last paragraph in the selinux entry which
3210 I unintentionally committed with the last commit.
3212 Revision 2.51 2009/02/12 16:08:26 fabiankeil
3213 Declare the code stable.
3215 Revision 2.50 2009/02/11 18:13:36 fabiankeil
3218 Revision 2.49 2009/02/10 16:30:20 fabiankeil
3219 Add a workaround for "unauthenticated content" warnings on HTTPS sites.
3221 Revision 2.48 2009/01/13 16:50:35 fabiankeil
3222 The standard.action file is gone.
3224 Revision 2.47 2008/11/24 18:29:39 fabiankeil
3225 Two changes suggested by Roger Dingledine:
3226 - Use https://www.torproject.org/ in section 4.7, too.
3227 - Replace the Tor wiki URL in section 4.10 with one
3228 with a more useful anchor name.
3230 Revision 2.46 2008/08/30 15:37:35 fabiankeil
3233 Revision 2.45 2008/08/16 08:51:28 fabiankeil
3234 Update version-related entities.
3236 Revision 2.44 2008/06/19 01:41:36 hal9
3237 Add short note about zlib being enabled in 3.0.9
3239 Revision 2.43 2008/06/14 13:21:25 fabiankeil
3240 Prepare for the upcoming 3.0.9 beta release.
3242 Revision 2.42 2008/06/07 13:11:15 fabiankeil
3243 - Note that the "100% cpu problem" is worth
3244 reporting if it happens with a recent release.
3245 - Mention the hostname option as a workaround for
3246 the "can't get my own hostname" issue.
3247 - The profile formerly known as "Adventuresome"
3248 is called "Advanced" now.
3249 - Some white-space fixes.
3251 Revision 2.41 2008/06/06 15:32:09 fabiankeil
3253 - Don't claim that all the old Junkbuster features remain.
3254 Some of them have been removed or replaced with better ones.
3256 Revision 2.40 2008/02/22 05:54:27 markm68k
3257 updates for mac os x
3259 Revision 2.39 2008/02/03 21:37:41 hal9
3260 Apply patch from Mark: s/OSX/OS X/
3262 Revision 2.38 2008/01/19 17:52:39 hal9
3263 Re-commit to fix various minor issues for new release.
3265 Revision 2.37 2008/01/19 15:03:05 hal9
3266 Doc sources tagged for 3.0.8 release.
3268 Revision 2.36 2008/01/17 01:49:51 hal9
3269 Change copyright notice for docs s/2007/2008/. All these will be rebuilt soon
3272 Revision 2.35 2007/11/19 17:57:59 fabiankeil
3273 A bunch of rewordings, minor updates and fixes.
3275 Revision 2.34 2007/11/19 02:38:11 hal9
3276 Minor revisions and rebuild
3278 Revision 2.33 2007/11/15 03:30:20 hal9
3279 Results of spell check.
3281 Revision 2.32 2007/11/13 03:03:42 hal9
3282 Various changes to reflect new features and revised configuration for the
3285 Revision 2.31 2007/11/05 02:34:53 hal9
3286 Various changes in preparation for the upcoming release. Much yet to be done.
3288 Revision 2.30 2007/11/04 15:16:40 hal9
3291 Revision 2.29 2007/11/04 15:12:47 hal9
3292 Various minor adjustments.
3294 Revision 2.28 2007/10/27 15:14:16 fabiankeil
3295 Change Tor links to use the new domain torproject.org.
3297 Revision 2.27 2007/10/22 19:47:05 fabiankeil
3298 - Bump version and copyright.
3299 - Adjust Tor section to make it clear that forward exceptions
3300 aren't required and may not even be desired.
3301 - A bunch of other minor rewordings.
3302 - Fix markup problems Roland noticed (hopefully without adding new ones).
3304 Revision 2.26 2007/08/05 15:37:55 fabiankeil
3305 - Don't claim that thousands of people read our code.
3306 - Specify the GPL version and link to GPLv2 instead of v3.
3307 - Note that configuration syntax may change between releases.
3308 - Mention zlib support.
3309 - Answer the "transparent proxy" question properly.
3310 - Add "intercepting proxy" entry.
3312 - Rephrase some other sentences for various reasons.
3314 Revision 2.25 2007/07/18 11:00:34 hal9
3315 Add misc note about valid mark-up in Privoxy.
3317 Revision 2.24 2006/11/14 01:57:46 hal9
3318 Dump all docs prior to 3.0.6 release. Various minor changes to faq and user
3321 Revision 2.23 2006/10/21 22:19:52 hal9
3322 Two new FAQs, a rewrite or two, and some touch ups.
3324 Revision 2.22 2006/10/14 20:33:10 hal9
3325 Three new FAQ's re: templates and blocking, and various minor touch-ups/improvements.
3327 Revision 2.21 2006/10/03 14:40:51 fabiankeil
3328 Added links from the Tor faq to the
3329 configuration chapter in the User Manual.
3331 Revision 2.20 2006/09/26 10:12:37 fabiankeil
3334 Revision 2.19 2006/09/22 10:54:32 hal9
3335 Change references to 3.0.4 to 3.0.5 and minor adjustments.
3337 Revision 2.18 2006/09/22 01:27:55 hal9
3338 Final commit of probably various minor changes here and there. Unless
3339 something changes this should be ready for pending release.
3341 Revision 2.17 2006/09/17 14:56:32 hal9
3342 This includes yet several more new FAQs, some improved wording, enhanced
3343 mark-up, various hyper links to wikipedia to explain key terminology to the
3344 uninitiated, etc. This is ready for release IMO pending final tagging of cvs
3345 and Privoxy version stamping.
3347 Revision 2.16 2006/09/10 15:30:46 hal9
3350 Revision 2.15 2006/09/08 23:05:07 hal9
3351 Fix broken links. Add faq on hosts files. Move most of new windows service
3352 feature to user manual and reference in faq. Various other small changes.
3354 Revision 2.14 2006/09/05 13:25:12 david__schmidt
3355 Add Windows service invocation stuff (duplicated) in FAQ and in user manual under Windows startup. One probably ought to reference the other.
3357 Revision 2.13 2006/09/04 19:20:33 fabiankeil
3358 Adjusted anonymity related sections to match reality.
3359 Added a section about using Privoxy with Tor.
3361 Revision 2.12 2006/09/03 14:15:30 hal9
3362 Various updates, including 7 or 8 new FAQs, and updates/changes to various
3363 other ones to better reflect improvements, additions and changes for the
3364 upcoming release. This is close to final form for 3.0.4 IMHO.
3366 Revision 2.11 2006/07/18 14:48:50 david__schmidt
3367 Reorganizing the repository: swapping out what was HEAD (the old 3.1 branch)
3368 with what was really the latest development (the v_3_0_branch branch)
3370 Revision 1.61.2.41 2004/04/05 13:44:05 oes
3371 Fixed allow-all-cookies alias name; closes SR #929746
3373 Revision 1.61.2.40 2004/01/30 17:00:33 oes
3374 Added Mac OS X Panther problem
3376 Revision 1.61.2.39 2004/01/29 22:53:08 hal9
3377 Minor changes for exempting docs of text/plain. Change copyright date.
3379 Revision 1.61.2.38 2003/12/10 03:39:45 hal9
3380 Added FAQs for: demoronizer, related problems and why its included. Also,
3381 port 8118 already in use questions, and PrivoxyWindowOpen() questions. All in
3382 troubleshooting section.
3384 Revision 1.61.2.37 2003/10/17 11:01:50 oes
3385 Added Q&A for "not being used" page problem
3387 Revision 1.61.2.36 2003/06/26 23:49:20 hal9
3388 More on the filter/source code problem.
3390 Revision 1.61.2.35 2003/06/26 13:38:08 hal9
3391 Add FAQ on whether configuring Privoxy is necessary or not.
3393 Revision 1.61.2.34 2003/06/26 03:00:03 hal9
3394 Sorry, found another copyright date.
3396 Revision 1.61.2.33 2003/06/26 02:57:05 hal9
3397 Fix typo (finally!) and very minor modifications.
3399 Revision 1.61.2.32 2003/06/26 02:52:04 hal9
3402 Revision 1.61.2.31 2003/06/25 01:27:51 hal9
3403 Fix copyright, and a few nits.
3405 Revision 1.61.2.30 2003/06/25 01:13:52 hal9
3408 - FAQ on "Unable to get my own hostname"
3409 - Another one on filtering effects on text files.
3411 Revision 1.61.2.29 2003/06/15 21:32:58 hal9
3412 Add to the 4.17 (filtering effects on downloaded files).
3414 Revision 1.61.2.28 2003/03/18 19:37:21 oes
3415 s/Advanced|Radical/Adventuresome/g to avoid complaints re fun filter
3417 Revision 1.61.2.27 2002/12/01 06:31:58 hal9
3418 Add faq on win32 error 503 due to ZoneAlarm.
3420 Revision 1.61.2.26 2002/11/17 06:41:06 hal9
3421 Move default profiles table from FAQ to U-M, and other minor related changes.
3424 Revision 1.61.2.25 2002/10/29 03:21:50 hal9
3425 Add 3 Q/A's relating to HTML in email. Other minor touchups.
3427 Revision 1.61.2.24 2002/10/15 12:50:22 oes
3428 s/Advanced/Radical/ (stupid me)
3430 Revision 1.61.2.23 2002/10/15 12:38:56 oes
3431 Added Microsuck faq; more detail for PHP problem
3433 Revision 1.61.2.22 2002/10/12 01:13:13 hal9
3434 Updates for demoronizer, more commentary on Radical profile, and update on
3435 the srvany.exe/icon fix.
3437 Revision 1.61.2.21 2002/10/10 04:09:35 hal9
3438 s/Advanced/Radical/ and added very brief note.
3440 Revision 1.61.2.20 2002/09/26 01:22:45 hal9
3441 Small additions for LAN setup, content-cookies/SSL, and FTP non-support.
3443 Revision 1.61.2.19 2002/08/25 23:31:56 hal9
3444 Fix one grammatical error. Add brief FAQ relating to tranparent proxies (ie
3445 port 80 setting). Add FAQ on effects of Privoxy on downloaded files
3446 (especially filtering).
3448 Revision 1.61.2.18 2002/08/14 16:39:37 hal9
3449 Fix wrong tag on FAQ addition.
3451 Revision 1.61.2.17 2002/08/14 00:01:18 hal9
3454 Revision 1.61.2.16 2002/08/13 00:10:38 hal9
3455 Add faq to troubleshooting re: blank page syndrome, ie {-prevent-compression}.
3457 Revision 1.61.2.15 2002/08/10 11:34:22 oes
3458 Add disclaimer about probably being out-of-date
3460 Revision 1.61.2.14 2002/08/07 02:53:43 hal9
3461 Fix some minor markup errors, and move one Mac OS X Q/A to troubleshooting section.
3463 Revision 1.61.2.13 2002/08/06 11:55:32 oes
3464 Added missing close tag
3466 Revision 1.61.2.12 2002/08/06 11:43:46 david__schmidt
3467 Updated Mac OS X uninstall FAQ... we have an uninstall script now.
3469 Revision 1.61.2.11 2002/08/06 08:54:03 oes
3470 Style police: Fixed formatting details
3472 Revision 1.61.2.10 2002/08/02 14:00:25 david__schmidt
3473 Made the Mac OS X removal commands far less dangerous
3475 Revision 1.61.2.9 2002/08/02 13:14:45 oes
3476 Added warning about sudo rm -r for Mac OS X deinstallation; moved this item to install section
3478 Revision 1.61.2.8 2002/08/02 02:01:42 david__schmidt
3479 Add FAQ item for MSIE on Mac OS X HTTP proxy confusion
3481 Revision 1.61.2.7 2002/08/02 01:46:01 david__schmidt
3482 Added FAQ item for Mac OS X uninstall woes
3484 Revision 1.61.2.6 2002/07/30 20:04:56 hal9
3485 Fix typo: 'schould'.
3487 Revision 1.61.2.5 2002/07/26 15:22:58 oes
3488 - Updated to reflect changes in standard.action
3489 - Added info on where to get updated actions files
3491 Revision 1.61.2.4 2002/07/25 21:42:29 hal9
3492 Add brief notes on not proxying non-HTTP protocols.
3494 Revision 1.61.2.3 2002/06/09 16:36:33 hal9
3495 Clarifications on filtering and MIME. Hardcode 'latest release' in index.html.
3497 Revision 1.61.2.2 2002/06/06 02:51:34 hal9
3498 Fix typo in URL http:/config.privoxy.org
3500 Revision 1.61.2.1 2002/06/05 23:10:43 hal9
3501 Add new FAQ re: DUN/IE. Change release date from May to June :)
3503 Revision 1.61 2002/05/25 12:37:25 hal9
3504 Various minor changes and edits.
3506 Revision 1.60 2002/05/22 17:17:48 oes
3507 Proofread & added more links into u-m
3509 Revision 1.59 2002/05/15 04:03:30 hal9
3510 Fix ulink -> link markup.
3512 Revision 1.58 2002/05/10 01:48:20 hal9
3513 This is mostly proposed copyright/licensing additions and changes. Docs
3514 are still GPL, but licensing and copyright are more visible. Also, copyright
3515 changed in doc header comments (eliminate references to JB except FAQ).
3517 Revision 1.57 2002/05/05 20:26:02 hal9
3518 Sorting out license vs copyright in these docs.
3520 Revision 1.56 2002/05/04 08:44:44 swa
3523 Revision 1.55 2002/05/04 00:41:56 hal9
3524 -Remove TOC/first page kludge in favor of proper handling via dsl file.
3526 Revision 1.54 2002/05/03 05:06:44 hal9
3527 Add brief Q/A on transparent proxies.
3529 Revision 1.53 2002/05/03 01:34:52 hal9
3530 Fix section numbering for new sections (due to TOC kludge).
3532 Revision 1.52 2002/04/29 03:08:43 hal9
3533 -Added new Q/A on new actions file set up (pointer to u-m)
3534 -Fixed a few broken links and converted old actions as a result of
3537 Revision 1.51 2002/04/26 17:24:31 swa
3538 bookmarks cleaned, changed structure of user manual, screen and programlisting cleanups, and numerous other changes that I forgot
3540 Revision 1.50 2002/04/26 05:25:23 hal9
3541 Mass commit to catch a few scattered fixes.
3543 Revision 1.49 2002/04/12 10:10:18 swa
3546 Revision 1.48 2002/04/10 18:45:15 swa
3549 Revision 1.47 2002/04/10 04:05:32 hal9
3552 Revision 1.45 2002/04/08 22:59:26 hal9
3553 Version update. Spell chkconfig correctly :)
3555 Revision 1.44 2002/04/07 21:24:29 hal9
3556 Touch up on name change.
3558 Revision 1.43 2002/04/04 21:59:53 hal9
3559 Added NT/W2K service/icon situation.
3561 Revision 1.42 2002/04/04 18:46:47 swa
3562 consistent look. reuse of copyright, history et. al.
3564 Revision 1.41 2002/04/04 06:48:37 hal9
3565 Structural changes to allow for conditional inclusion/exclusion of content
3566 based on entity toggles, e.g. 'entity % p-not-stable "INCLUDE"'. And
3567 definition of internal entities, e.g. 'entity p-version "2.9.13"' that will
3568 eventually be set by Makefile.
3569 More boilerplate text for use across multiple docs.
3571 Revision 1.40 2002/04/03 04:22:03 hal9
3572 Fixed several typos.
3574 Revision 1.39 2002/04/03 03:53:03 hal9
3575 Revert some changes, and then make some news, to layout, and appearance.
3577 Revision 1.38 2002/04/02 03:49:10 hal9
3578 Major changes to doc structure and layout. Sections are not automatically
3579 numbered now. TOC is on page by itself.
3581 Revision 1.37 2002/04/01 16:24:07 hal9
3582 -Rework of supported Q/A.
3583 -Set up entities to include boilerplate text.
3585 Revision 1.36 2002/03/31 23:18:47 hal9
3586 More on dealing with BLOCKED.
3588 Revision 1.35 2002/03/30 04:14:19 hal9
3589 Fix privoxy.org/config links.
3591 Revision 1.34 2002/03/29 04:35:56 hal9
3594 Revision 1.33 2002/03/29 01:31:48 hal9
3595 Several new Q/A's and other touch ups.
3597 Revision 1.32 2002/03/27 00:57:03 hal9
3598 Touch ups for name change.
3600 Revision 1.31 2002/03/26 22:29:55 swa
3601 we have a new homepage!
3603 Revision 1.30 2002/03/25 16:39:22 hal9
3604 A few new sections. Made all links relative to user-manual.
3606 Revision 1.29 2002/03/25 05:23:57 hal9
3607 Moved section, and touch ups.
3609 Revision 1.28 2002/03/25 04:27:33 hal9
3610 New section related to name change.
3612 Revision 1.25 2002/03/24 16:08:08 swa
3613 we are too lazy to make a block-built
3614 privoxy logo. hence removed the option.
3616 Revision 1.24 2002/03/24 15:46:20 swa
3617 name change related issue.
3619 Revision 1.23 2002/03/24 12:33:01 swa
3622 Revision 1.22 2002/03/24 11:51:00 swa
3623 name change. changed filenames.
3625 Revision 1.21 2002/03/24 11:01:06 swa
3628 Revision 1.20 2002/03/23 15:13:11 swa
3629 renamed every reference to the old name with foobar.
3630 fixed "application foobar application" tag, fixed
3631 "the foobar" with "foobar". left junkbustser in cvs
3632 comments and remarks to history untouched.
3634 Revision 1.19 2002/03/21 17:01:54 hal9
3637 Revision 1.18 2002/03/18 16:40:31 hal9
3640 Revision 1.17 2002/03/18 03:53:53 hal9
3643 Revision 1.16 2002/03/17 21:32:56 hal9
3644 A few more additions.
3646 Revision 1.15 2002/03/17 07:25:59 hal9
3647 Correcting some of my typos, and some additions.
3649 Revision 1.14 2002/03/17 02:39:13 hal9
3650 A little more added ...
3652 Revision 1.13 2002/03/17 00:22:20 hal9
3653 Adding new stuff, and trying to incorporate stuff from old faq.
3655 Revision 1.12 2002/03/11 20:13:21 swa
3658 Revision 1.11 2002/03/11 18:42:27 swa
3661 Revision 1.10 2002/03/11 13:13:27 swa
3662 correct feedback channels
3664 Revision 1.9 2002/03/10 23:34:04 swa
3665 more info on not hiding ip address
3667 Revision 1.8 2002/03/09 15:55:48 swa
3668 added default config section
3670 Revision 1.7 2002/03/07 18:16:55 swa
3673 Revision 1.6 2002/03/07 13:16:31 oes
3674 Committing changes by Stefan
3676 Revision 1.5 2002/03/02 15:50:04 swa
3677 2.9.11 version. more input for docs.
3679 Revision 1.4 2002/02/24 14:34:24 jongfoster
3680 Formatting changes. Now changing the doctype to DocBook XML 4.1
3681 will work - no other changes are needed.
3683 Revision 1.3 2001/09/23 10:13:48 swa
3684 upload process established. run make webserver and
3685 the documentation is moved to the webserver. documents
3686 are now linked correctly.
3688 Revision 1.2 2001/09/13 15:20:17 swa
3689 merged standards into developer manual
3691 Revision 1.1 2001/09/12 15:36:41 swa
3692 source files for junkbuster documentation
3694 Revision 1.3 2001/09/10 17:43:59 swa
3695 first proposal of a structure.
3697 Revision 1.2 2001/06/13 14:28:31 swa
3698 docs should have an author.
3700 Revision 1.1 2001/06/13 14:20:37 swa
3701 first import of project's documentation for the webserver.