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.25">
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.119 2016/03/17 10:18:57 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.119 2016/03/17 10:18:57 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" id="whyprivoxy">
240 <title>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>How does Privoxy know what is an ad, and what is not?</title>
294 <application>Privoxy</application>'s approach to blocking ads is twofold:
297 First, there are certain patterns in the <emphasis>locations</emphasis> (URLs)
298 of banner images. This applies to both the path (you wouldn't guess how many
299 web sites serve their banners from a directory called <quote>banners</quote>!)
300 and the host (blocking the big banner hosting services like doublecklick.net
301 already helps a lot). <application>Privoxy</application> takes advantage of this
302 fact by using <ulink url="../user-manual/actions-file.html#AF-PATTERNS">URL
303 patterns</ulink> to sort out and block the requests for things that sound
304 like they would be ads or banners.
307 Second, banners tend to come in certain <emphasis>sizes</emphasis>. But you
308 can't tell the size of an image by its URL without downloading it, and if you
309 do, it's too late to save bandwidth. Therefore, <application>Privoxy</application>
310 also inspects the HTML sources of web pages while they are loaded, and replaces
311 references to images with standard banner sizes by dummy references, so that
312 your browser doesn't request them anymore in the first place.
315 Both of this involves a certain amount of guesswork and is, of course, freely
316 and readily configurable.
320 <sect2 renderas="sect3" id="mistakes">
321 <title>Can Privoxy make mistakes?
322 This does not sound very scientific.</title>
324 Actually, it's a black art ;-) And yes, it is always possible to have a broad
325 rule accidentally block or change something by mistake. You will almost surely
326 run into such situations at some point. It is tricky writing rules to
327 cover every conceivable possibility, and not occasionally get false positives.
331 But this should not be a big concern since the
332 <application>Privoxy</application> configuration is very flexible, and
333 includes tools to help identify these types of situations so they can be
334 addressed as needed, allowing you to customize your installation.
335 (<link linkend="badsite">See the Troubleshooting section below</link>.)
340 <sect2 renderas="sect3" id="configornot">
341 <title>Will I have to configure Privoxy
342 before I can use it?</title>
344 That depends on your expectations.
345 The default installation should give you a good starting
346 point, and block <emphasis>most</emphasis> ads and unwanted content,
347 but many of the more advanced features are off by default, and require
348 you to activate them.
351 You do have to set up your browser to use
352 <application>Privoxy</application> (see the <link
353 linkend="firststep">Installation section below</link>).
356 And you will certainly run into situations where there are false positives,
357 or ads not being blocked that you may not want to see. In these cases, you
358 would certainly benefit by customizing <application>Privoxy's</application>
359 configuration to more closely match your individual situation. And we
360 encourage you to do this. This is where the real power of
361 <application>Privoxy</application> lies!
366 <sect2 renderas="sect3" id="lan">
367 <title>Can Privoxy run as a server on a network?</title>
369 Yes, &my-app; runs as a server already, and can easily be configured to
370 <quote>serve</quote> more than one client. See <link linkend="lanconfig">
371 How can I set up Privoxy to act as a proxy for my LAN</link> below.
375 <sect2 renderas="sect3" id="browsers2"><title>My browser does the same things as
376 Privoxy. Why should I use Privoxy at all?</title>
378 Modern browsers do indeed have <emphasis>some</emphasis> of the same
379 functionality as <application>Privoxy</application>. Maybe this is
380 adequate for you. But <application>Privoxy</application> is very
381 versatile and powerful, and can probably do a number of things
382 your browser just can't.
385 In addition, a proxy is good choice if you use multiple browsers, or
386 have a LAN with multiple computers since &my-app; can run as a server
387 application. This way all the configuration is in one place, and you don't
388 have to maintain a similar configuration for possibly many browsers or
392 Note, however, that it's recommended to leverage both your browser's
393 and <application>Privoxy's</application> privacy enhancing features
394 at the same time. While your browser probably lacks some features
395 &my-app; offers, it should also be able to do some things more
396 reliably, for example restricting and suppressing JavaScript.
400 <sect2 renderas="sect3" id="whytrust"><title>Why should I trust Privoxy?</title>
402 The most important reason is because you have access to
403 <emphasis>everything</emphasis>, and you can control everything. You can
404 check every line of every configuration file yourself. You can check every
405 last bit of source code should you desire. And even if you can't read code,
406 there should be some comfort in knowing that <!-- thousands of -->other people can,
407 and do read it. You can build the software from scratch, if you want,
408 so that you know the executable is clean, and that it is
409 <emphasis>yours</emphasis>. In fact, we encourage this level of scrutiny. It
410 is one reason we use &my-app; ourselves.
414 <sect2 renderas="sect3" id="license"><title>Is there is a license or fee? What about a
415 warranty? Registration?</title>
417 <application>Privoxy</application> is free software and licensed under the <ulink
418 url="http://www.gnu.org/licenses/old-licenses/gpl-2.0.html">GNU General Public License (GPL) version 2</ulink>.
419 It is free to use, copy, modify or distribute as you wish under the terms of this
420 license. Please see the <link linkend="copyright">Copyright</link> section for more
421 information on the license and copyright. Or the <filename>LICENSE</filename> file
422 that should be included.
425 There is <emphasis>no warranty</emphasis> of any kind, expressed, implied or otherwise.
426 That is something that would cost real money ;-) There is no registration either.
431 <sect2 renderas="sect3" id="spyware">
432 <title>Can Privoxy remove spyware? Adware? Viruses?</title>
434 No, at least not reliably enough to trust it. &my-app; is not designed to be
435 a malware removal tool and the default configuration doesn't even try to
436 filter out any malware.
439 &my-app; could help prevent contact from (known) sites that use such
440 tactics with appropriate configuration rules, and thus could conceivably
441 prevent contamination from such sites. However, keeping such a configuration
442 up to date would require a lot of time and effort that would be better spend
443 on keeping your software itself up to date so it doesn't have known
449 <sect2 renderas="sect3" id="otherads">
450 <title>Can I use Privoxy with other ad-blocking software?</title>
452 &my-app; should work fine with other proxies and other software in general.
455 But it is probably not necessary to use &my-app; in conjunction with other
456 ad-blocking products, and this could conceivably cause undesirable results.
457 It might be better to choose one software or the other and work a little to
458 tweak its configuration to your liking.
461 Note that this is an advice specific to ad blocking.
465 <sect2 renderas="sect3" id="help-the-developers"><title>I would like to help you, what can I do?</title>
467 <sect3 renderas="sect4" id="participate"><title>Would you like to participate?</title>
469 Well, we <emphasis>always</emphasis> need help. There is something for
470 everybody who wants to help us. We welcome new developers, packagers,
471 testers, documentation writers or really anyone with a desire to help in
472 any way. You <emphasis>DO NOT</emphasis> need to be a
473 <quote>programmer</quote>. There are many other tasks available. In fact,
474 the programmers often can't spend as much time programming because of some
475 of the other, more mundane things that need to be done, like checking the
476 Tracker feedback sections or responding to user questions on the mailing
480 So first thing, subscribe to the <ulink
481 url="https://lists.sourceforge.net/lists/listinfo/ijbswa-users">Privoxy Users</ulink>
482 or the <ulink url="https://lists.sourceforge.net/lists/listinfo/ijbswa-developers">Privoxy
483 Developers</ulink> mailing list, join the discussion, help out other users, provide general
484 feedback or report problems you noticed.
487 If you intend to help out with the trackers, you also might want to <ulink
488 url="https://sourceforge.net/user/registration">get an account on SourceForge.net</ulink>
489 so we don't confuse you with the other name-less users.
492 We also have a <ulink
493 url="../developer-manual/index.html">Developer's Manual</ulink>.
494 While it is partly out of date, it's still worth reading.
497 Our <ulink url="http://ijbswa.cvs.sourceforge.net/viewvc/ijbswa/current/TODO?view=markup">TODO list</ulink>
498 may be of interest to you as well.
499 Please let us know if you want to work on one of the items listed.
503 <sect3 renderas="sect4" id="donate"><title>Would you like to donate?</title>
505 Donations are welcome. Our
506 <ulink url="http://ijbswa.cvs.sourceforge.net/viewvc/ijbswa/current/TODO?view=markup">TODO list</ulink>
507 is rather long and being able to pay one (or more) developers to work on Privoxy
508 would make a huge difference, even if it was only for a couple of weeks. Donations may
509 also be used for Privoxy-related travel expenses (for example to attend conferences),
510 for hardware used for Privoxy development and for hosting expenses etc.
514 <application>Privoxy</application> is an associated
515 project of <ulink url="http://www.spi-inc.org/">Software
516 in the Public Interest (SPI)</ulink>, which allows us to receive
517 tax-deductible donations in the United States. If you want to donate through
518 SPI, please use <ulink url="http://www.spi-inc.org/donations">SPI's donation page</ulink>
519 to see what the options are.
523 You can also donate to Privoxy using a bank account or a "Paypal" address:
526 Name on account: <ulink url="https://www.zwiebelfreunde.de/">Zwiebelfreunde e.V.</ulink>
527 IBAN: DE95430609671126825604
532 "Paypal" address: privoxy@zwiebelfreunde.de
535 Donations made through Zwiebelfreunde e.V. are tax-deductible in Germany
536 and other countries that recognize German charitable clubs. Feel free to
537 use the Subject field to provide a name to be credited and a list of TODO
538 list items you are interested in the most. For example: Max Mustermann: #16, #1, #14.
542 Note that donations made through Zwiebelfreunde e.V. currently can't be checked
543 automatically so you may not get credited right away. The credits currently
544 reflect donations received before 2016-01-14.
548 If you have any questions regarding donations please mail to either the
549 public user mailing list or, if it's a private matter, to
550 <ulink url="mailto:fk@fabiankeil.de">Fabian Keil</ulink> (Privoxy's SPI liaison)
559 <!-- ~~~~~ New section ~~~~~ -->
561 <sect1 id="installation"><title>Installation</title>
563 <sect2 renderas="sect3" id="whichbrowsers">
564 <title>Which browsers are supported by Privoxy?</title>
566 Any browser that can be configured to use a proxy, which
567 should be virtually all browsers, including
568 <application>Firefox</application>, <application>Internet
569 Explorer</application>, <application>Opera</application>, and
570 <application>Safari</application> among others.
571 Direct browser support is not an absolute requirement since
572 <application>Privoxy</application> runs as a separate application and talks
573 to the browser in the standardized HTTP protocol, just like a web server
578 <sect2 renderas="sect3" id="whichos">
579 <title>Which operating systems are supported?</title>
581 Include supported.sgml here:
586 <sect2 renderas="sect3" id="email-client">
587 <title>Can I use Privoxy with my email client?</title>
589 As long as there is some way to set a HTTP proxy for the client, then yes,
590 any application can be used, whether it is strictly speaking a
591 <quote>browser</quote> or not. Though this may not be the best approach for
592 dealing with some of the common abuses of HTML in email. See <link
593 linkend="outlook">How can I configure <application>Privoxy</application>
594 with <application>Outlook</application>?</link> below for more on
598 Be aware that HTML email presents a number of unique security and privacy
599 related issues, that can require advanced skills to overcome. The developers
600 recommend using email clients that can be configured to convert HTML to plain
601 text for these reasons.
605 <!-- Nobody is going to still be doing this!
606 <sect2 renderas="sect3" id="newinstall"><title>Can I install
607 Privoxy over Junkbuster?</title>
609 We recommend you un-install <application>Junkbuster</application>
610 first to minimize conflicts and confusion. You may want to
611 save your old configuration files for future reference. The configuration
612 files and syntax have substantially changed, so you will need to manually
613 port your old patterns. See the <ulink url="../user-manual/upgradersnote.html">note
614 to upgraders</ulink> and <ulink url="../user-manual/installation.html">installation
615 chapter</ulink> in the <ulink url="../user-manual/index.html">User Manual</ulink>
619 Note: Some installers may automatically un-install
620 <application>Junkbuster</application>, if present!
626 <sect2 renderas="sect3" id="firststep">
627 <title>I just installed Privoxy. Is there anything
628 special I have to do now?</title>
631 All browsers should be told to use <application>Privoxy</application>
632 as a proxy by specifying the correct proxy address and port number
633 in the appropriate configuration area for the browser. It's possible
634 to combine &my-app; with a packet filter to intercept HTTP requests
635 even if the client isn't explicitly configured to use &my-app;,
636 but where possible, configuring the client is recommended. See
637 <ulink url="../user-manual/startup.html">the User Manual for more
638 details</ulink>. You should also flush your browser's memory and disk
639 cache to get rid of any cached junk items, and remove any stored
640 <ulink url="http://en.wikipedia.org/wiki/Browser_cookie">cookies</ulink>.
646 <sect2 renderas="sect3" id="localhost"><title>What is the proxy address of Privoxy?</title>
648 If you set up the <application>Privoxy</application> to run on
649 the computer you browse from (rather than your ISP's server or some
650 networked computer on a LAN), the proxy will be on <literal>127.0.0.1</literal>
651 (sometimes referred to as <quote>localhost</quote>,
652 which is the special name used by every computer on the Internet to refer
653 to itself) and the port will be 8118 (unless you used the <ulink
654 url="../user-manual/config.html#LISTEN-ADDRESS">listen-address</ulink>
655 config option to tell <application>Privoxy</application> to run on
659 When configuring your browser's proxy settings you typically enter
660 the word <quote>localhost</quote> or the IP address <quote>127.0.0.1</quote>
661 in the boxes next to <quote>HTTP</quote> and <quote>Secure</quote> (HTTPS) and
662 then the number <quote>8118</quote> for <quote>port</quote>.
663 This tells your browser to send all web requests to <application>Privoxy</application>
664 instead of directly to the Internet.
667 <application>Privoxy</application> can also be used to proxy for
668 a Local Area Network. In this case, your would enter either the IP
669 address of the LAN host where <application>Privoxy</application>
670 is running, or the equivalent hostname, e.g. <literal>192.168.1.1</literal>.
671 Port assignment would be same as above. Note that
672 <application>Privoxy</application> doesn't listen on any LAN interfaces by
676 <application>Privoxy</application> does not currently handle
677 any other protocols such as FTP, SMTP, IM, IRC, ICQ, etc.
681 <sect2 renderas="sect3" id="nothing">
682 <title>I just installed Privoxy, and nothing is happening.
683 All the ads are there. What's wrong?</title>
686 Did you configure your browser to use <application>Privoxy</application>
687 as a proxy? It does not sound like it. See above. You might also try flushing
688 the browser's caches to force a full re-reading of pages. You can verify
689 that <application>Privoxy</application> is running, and your browser
690 is correctly configured by entering the special URL:
691 <ulink url="http://p.p/">http://p.p/</ulink>.
692 <!-- Use http://p.p/ instead of http://config.privoxy.org/ here because
693 of potential redirect caching problem (see next Q). -->
694 This should take you to a page titled <quote>This is Privoxy..</quote> with
695 access to <application>Privoxy's</application> internal configuration.
696 If you see this, then you are good to go. If you receive a page saying
697 <quote>Privoxy is not running</quote>, then the browser is not set up to use
698 your <application>Privoxy</application> installation.
699 If you receive anything else (probably nothing at all), it could either
700 be that the browser is not set up correctly, or that
701 <application>Privoxy</application> is not running at all. Check the <ulink
702 url="../user-manual/config.html#LOGFILE">log file</ulink>. For instructions
703 on starting <application>Privoxy</application> and browser configuration,
704 see the <ulink url="http://www.privoxy.org/user-manual/startup.html">chapter
705 on starting <application>Privoxy</application></ulink> in the
706 <ulink url="http://www.privoxy.org/user-manual/">User Manual</ulink>.
711 <sect2 renderas="sect3" id="notused">
712 <title>I get a <quote>Privoxy is not being used</quote> dummy page although
713 Privoxy is running and being used.</title>
716 First, make sure that Privoxy is <emphasis>really</emphasis> running and
717 being used by visiting <ulink url="http://p.p/">http://p.p/</ulink>. You
718 should see the <application>Privoxy</application> main page. If not, see
719 the <ulink url="http://www.privoxy.org/user-manual/startup.html">chapter
720 on starting <application>Privoxy</application></ulink> in the
721 <ulink url="http://www.privoxy.org/user-manual/">User Manual</ulink>.
725 Now if <ulink url="http://p.p/">http://p.p/</ulink> works for you, but
726 other parts of <application>Privoxy</application>'s web interface show
727 the dummy page, your browser has cached a redirection it encountered before
728 <application>Privoxy</application> was being used. You need to clear your
729 browser's cache. Note that shift-reloading the dummy page won't help, since
730 that'll only refresh the dummy page, not the redirection that lead you there.
734 The procedure for clearing the cache varies from browser to browser. For
735 example, <application>Mozilla/Netscape</application> users would click
736 <guibutton>Edit</guibutton> --> <guibutton>Preferences</guibutton> -->
737 <guibutton>Advanced</guibutton> --> <guibutton>Cache</guibutton> and
738 then click both <quote><guibutton>Clear Memory Cache</guibutton></quote>
739 and <quote><guibutton>Clear Disk Cache</guibutton></quote>.
740 In some <application>Firefox</application> versions it's
741 <guibutton>Tools</guibutton> --> <guibutton>Options</guibutton> -->
742 <guibutton>Privacy</guibutton> --> <guibutton>Cache</guibutton> and
743 then click <quote><guibutton>Clear Cache Now</guibutton></quote>.
744 <!-- In my Firefox versions it's the Netscape way. fk 2007-11-19-->
751 <!-- ~~~~~ New section ~~~~~ -->
753 <sect1 id="configuration"><title>Configuration</title>
754 <sect2 renderas="sect3" id="actionsfile">
755 <title>What exactly is an <quote>actions</quote> file?</title>
758 &my-app; utilizes the concept of <quote>
759 <ulink url="../user-manual/actions-file.html#ACTIONS">actions</ulink></quote>
760 that are used to manipulate and control web page data.
761 <ulink url="../user-manual/actions-file.html">Actions files</ulink>
762 are where these <ulink url="../user-manual/actions-file.html#ACTIONS">actions</ulink>
763 that <application>Privoxy</application> could take while processing a certain
764 request, are configured. Typically, you would define a set of default actions
765 that apply globally to all URLs, then add exceptions to these defaults where needed.
766 There is a wide array of actions available that give the user a high degree
767 of control and flexibility on how to process each and every web page.
771 Actions can be defined on a <ulink
772 url="../user-manual/actions-file.html#AF-PATTERNS">URL pattern</ulink> basis, i.e.
773 for single URLs, whole web sites, groups or parts thereof etc. Actions can also be
774 grouped together and then applied to requests matching one or more patterns.
775 There are many possible actions that might apply to any given site. As an example,
776 if you are blocking <ulink url="http://en.wikipedia.org/wiki/Browser_cookie">cookies</ulink>
777 as one of your default actions, but need to accept cookies from a given site,
778 you would need to define an exception for this site in one of your actions
779 files, preferably in <filename>user.action</filename>.
784 <sect2 renderas="sect3" id="actionss">
785 <title>The <quote>actions</quote> concept confuses me. Please list
786 some of these <quote>actions</quote>.</title>
788 For a comprehensive discussion of the actions concept, please refer
789 to the <ulink url="../user-manual/actions-file.html">actions file
790 chapter</ulink> in the <ulink url="../user-manual/index.html">User
791 Manual</ulink>. It includes a <ulink
792 url="../user-manual/actions-file.html#ACTIONS">list of all actions</ulink>
793 and an <ulink url="../user-manual/actions-file.html#ACT-EXAMPLES">actions
794 file tutorial</ulink> to get you started.
799 <sect2 renderas="sect3" id="actconfig">
800 <title>How are actions files configured? What is the easiest
801 way to do this?</title>
804 Actions files are just text files in a special syntax and can be edited
805 with a text editor. But probably the easiest way is to access
806 <application>Privoxy</application>'s user interface with your web browser
807 at <ulink url="http://config.privoxy.org/">http://config.privoxy.org/</ulink>
808 (Shortcut: <ulink url="http://p.p/">http://p.p/</ulink>) and then select
809 <quote><ulink url="http://config.privoxy.org/show-status">View &
810 change the current configuration</ulink></quote> from the menu. Note
811 that this feature must be explicitly enabled in the main config file
813 url="../user-manual/config.html#ENABLE-EDIT-ACTIONS">enable-edit-actions</ulink>).
818 <sect2 renderas="sect3">
819 <title>There are several different <quote>actions</quote> files. What are
820 the differences?</title>
822 Please have a look at the <ulink url="../user-manual/actions-file.html">the actions chapter</ulink>
823 in the <ulink url="../user-manual/index.html">User Manual</ulink> for a detailed explanation.
828 <sect2 renderas="sect3" id="getupdates"><title>Where can I get updated Actions Files?</title>
830 Based on your feedback and the continuing development, updates of
831 <filename>default.action</filename> will be
832 made available from time to time on the <ulink
833 url="https://sourceforge.net/project/showfiles.php?group_id=11118">files section</ulink> of
834 our <ulink url="https://sourceforge.net/projects/ijbswa/">project page</ulink>.
838 If you wish to receive an email notification whenever we release updates of
839 <application>Privoxy</application> or the actions file, <ulink
840 url="https://lists.sourceforge.net/lists/listinfo/ijbswa-announce/">subscribe
841 to our announce mailing list</ulink>, ijbswa-announce@lists.sourceforge.net.
846 <sect2 renderas="sect3" id="newconfig"><title>Can I use my old config files?</title>
848 The syntax and purpose of configuration files has remained roughly the
849 same throughout the 3.x series, but backwards compatibility is not guaranteed.
850 Also each release contains updated, <quote>improved</quote> versions and it is
851 therefore strongly recommended to install the newer configuration files
852 and merge back your modifications.
856 <sect2 renderas="sect3" id="difficult">
857 <title>Why is the configuration so complicated?</title>
859 <quote>Complicated</quote> is in the eye of the beholder.
862 Privoxy is currently mainly written by and for people who are already
863 familiar with the underlying concepts like regular expressions, HTTP and HTML,
864 or are willing to become familiar with them to be able to get the most
865 out of a powerful and flexible tool such as Privoxy.
868 While everybody is expected to be able to get a Privoxy default installation
869 up and running, fine-tuning requires a certain amount of background
870 information and Privoxy's documentation mainly concentrates on the
871 Privoxy-specific parts while only providing references to the rest.
874 If you or anyone you know has the skills, time and energy to
875 reduce the barrier of entry, please <link linkend="participate">get involved</link>.
879 <sect2 renderas="sect3" id="yahoo"><title>How can I make my Yahoo/Hotmail/Gmail account work?</title>
881 The default configuration shouldn't impact the usability of any of these services.
882 It may, however, make all <ulink
883 url="http://en.wikipedia.org/wiki/Browser_cookie">cookies</ulink>
884 temporary, so that your browser will forget your
885 login credentials in between browser sessions. If you would like not to have to log
886 in manually each time you access those websites, simply turn off all cookie handling
887 for them in the <filename>user.action</filename> file. An example for yahoo might
891 <screen># Allow all cookies for Yahoo login:
893 { -<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> }
894 .login.yahoo.com</screen>
897 These kinds of sites are often quite complex and heavy with
898 <ulink url="http://en.wikipedia.org/wiki/Javascript">Javascript</ulink> and
899 thus <quote>fragile</quote>. So if <emphasis>still</emphasis> a problem,
901 url="../user-manual/actions-file.html#ALIASES">alias</ulink> just for such
905 <screen># Gmail is a _fragile_ site:
907 { <literal>fragile</literal> }
909 mail.google.com</screen>
912 Be sure to flush your browser's caches whenever making these kinds of
913 changes, just to make sure the changes <quote>take</quote>.
916 Make sure the domain, host and path are appropriate as well. Your browser can
917 tell you where you are specifically and you should use that information for
918 your configuration settings. Note that above it is not referenced as
919 <literal>gmail.com</literal>, which is a valid domain name.
924 <sect2 renderas="sect3" id="configfiles"> <title>What's the difference between the
925 <quote>Cautious</quote>, <quote>Medium</quote> and <quote>Advanced</quote> defaults?</title>
927 Configuring <application>Privoxy</application> is not entirely trivial. To
928 help you get started, we provide you with three different default action
929 <quote>profiles</quote> in the web based actions file editor at <ulink
930 url="http://config.privoxy.org/show-status">http://config.privoxy.org/show-status</ulink>.
931 See the <ulink url="../user-manual/actions-file.html"><citetitle>User
932 Manual</citetitle></ulink> for a list of actions, and how the default
937 Where the defaults are likely to break some sites, exceptions for
938 known popular <quote>problem</quote> sites are included, but in
939 general, the more aggressive your default settings are, the more exceptions
940 you will have to make later. New users are best to start off in
941 <quote>Cautious</quote> setting. This is safest and will have the fewest
942 problems. See the <ulink
943 url="../user-manual/index.html"><citetitle>User Manual</citetitle></ulink>
944 for a more detailed discussion.
948 It should be noted that the <quote>Advanced</quote> profile (formerly known
949 as the <quote>Adventuresome</quote> profile) is more
950 aggressive, and will make use of some of
951 <application>Privoxy's</application> advanced features. Use at your own risk!
956 <sect2 renderas="sect3" id="browseconfig"> <title>Why can I change the configuration
957 with a browser? Does that not raise security issues?</title>
959 It may seem strange that regular users can edit the config files with their
960 browsers, although the whole <filename>/etc/privoxy</filename> hierarchy
961 belongs to the user <quote>privoxy</quote>, with only 644 permissions.
964 When you use the browser-based editor, <application>Privoxy</application>
965 itself is writing to the config files. Because
966 <application>Privoxy</application> is running as the user <quote>privoxy</quote>,
967 it can update its own config files.
970 If you run <application>Privoxy</application> for multiple untrusted users (e.g. in
971 a LAN) or aren't entirely in control of your own browser, you will probably want
972 to make sure that the web-based editor and remote toggle features are
973 <quote>off</quote> by setting <quote><literal><ulink
974 url="../user-manual/config.html#ENABLE-EDIT-ACTIONS">enable-edit-actions</ulink>
975 0</literal></quote> and <quote><literal><ulink
976 url="../user-manual/config.html#ENABLE-REMOTE-TOGGLE">enable-remote-toggle</ulink>
977 0</literal></quote> in the <ulink url="../user-manual/config.html">main configuration file</ulink>.
980 As of &my-app; 3.0.7 these options are disabled by default.
985 <sect2 renderas="sect3" id="filterfile">
986 <title>What is the <filename>default.filter</filename> file? What is a <quote>filter</quote>?</title>
988 The <ulink url="../user-manual/filter-file.html"><filename>default.filter</filename></ulink>
989 file is where <emphasis>filters</emphasis> as supplied by the developers are defined.
990 Filters are a special subset of actions that can be used to modify or
991 remove web page content or headers on the fly. Content filters can
992 be applied to <emphasis>anything</emphasis> in the page source,
993 header filters can be applied to either server or client headers.
994 Regular expressions are used to accomplish this.
997 There are a number of pre-defined filters to deal with common annoyances. The
998 filters are only defined here, to invoke them, you need to use the
1000 url="../user-manual/actions-file.html#FILTER"><literal>filter</literal>
1001 action</ulink> in one of the actions files. Content filtering is automatically
1002 disabled for inappropriate MIME types, but if you know better than Privoxy
1003 what should or should not be filtered you can filter any content you like.
1007 <emphasis>not</emphasis> be confused with <ulink
1008 url="../user-manual/actions-file.html#BLOCK"><literal>blocks</literal></ulink>, which
1009 is a completely different action, and is more typically used to block ads and
1014 If you are familiar with regular expressions, and HTML, you can look at
1015 the provided <filename>default.filter</filename> with a text editor and define
1016 your own filters. This is potentially a very powerful feature, but
1017 requires some expertise in both regular expressions and HTML/HTTP.
1018 <![%p-newstuff;[ You should
1019 place any modifications to the default filters, or any new ones you create
1020 in a separate file, such as <filename>user.filter</filename>, so they won't
1021 be overwritten during upgrades.
1022 The ability to define multiple filter files
1023 in <filename>config</filename> is a new feature as of v. 3.0.5.]]>
1027 There is no GUI editor option for this part of the configuration,
1028 but you can disable/enable the various pre-defined filters of the included
1029 <filename>default.filter</filename> file with the <ulink
1030 url="http://config.privoxy.org/show-status">web-based actions file editor</ulink>.
1031 Note that the custom actions editor must be explicitly enabled in
1032 the main config file (see <ulink
1033 url="../user-manual/config.html#ENABLE-EDIT-ACTIONS">enable-edit-actions</ulink>).
1037 If you intend to develop your own filters, you might want to have a look at
1039 url="http://www.fabiankeil.de/sourcecode/pft/">Privoxy-Filter-Test</ulink>.
1044 <sect2 renderas="sect3" id="lanconfig">
1045 <title>How can I set up Privoxy to act as a proxy for my
1048 By default, <application>Privoxy</application> only responds to requests
1049 from <literal>127.0.0.1</literal> (localhost). To have it act as a server for
1050 a network, this needs to be changed in the <ulink
1051 url="../user-manual/config.html">main configuration file</ulink>. Look for
1053 url="../user-manual/config.html#LISTEN-ADDRESS">listen-address</ulink></literal>
1054 option, which may be commented out with a <quote>#</quote> symbol. Make sure
1055 it is uncommented, and assign it the address of the LAN gateway interface,
1056 and port number to use. Assuming your LAN address is 192.168.1.1 and you
1057 wish to run <application>Privoxy</application> on port 8118, this line
1063 listen-address 192.168.1.1:8118</screen>
1067 Save the file, and restart <application>Privoxy</application>. Configure
1068 all browsers on the network then to use this address and port number.
1072 Alternately, you can have <application>Privoxy</application> listen on
1073 all available interfaces:
1078 listen-address :8118</screen>
1082 And then use <application>Privoxy's</application>
1084 url="../user-manual/config.html#PERMIT-ACCESS">permit-access</ulink>
1085 feature to limit connections. A firewall in this situation is recommended
1090 The above steps should be the same for any TCP network, regardless of
1095 If you run <application>Privoxy</application> on a LAN with untrusted users,
1096 we recommend that you double-check the <ulink
1097 url="../user-manual/config.html#ACCESS-CONTROL">access control and security</ulink>
1104 <sect2 renderas="sect3" id="noseeum">
1105 <title>Instead of ads, now I get a checkerboard pattern. I don't want to see anything.</title>
1107 The replacement for blocked images can be controlled with the <ulink
1108 url="../user-manual/actions-file.html#SET-IMAGE-BLOCKER"><literal>set-image-blocker</literal>
1109 action</ulink>. You have the choice of a checkerboard pattern, a transparent 1x1 GIF
1110 image (aka <quote>blank</quote>), or a redirect to a custom image of your choice.
1111 Note that this choice only has effect for images which are blocked as images, i.e.
1112 whose URLs match both a <literal><ulink
1113 url="../user-manual/actions-file.html#HANDLE-AS-IMAGE">handle-as-image</ulink></literal>
1114 <emphasis>and</emphasis> <literal><ulink
1115 url="../user-manual/actions-file.html#BLOCK">block</ulink></literal> action.
1118 If you want to see nothing, then change the <ulink
1119 url="../user-manual/actions-file.html#SET-IMAGE-BLOCKER"><literal>set-image-blocker</literal>
1120 action</ulink> to <quote>blank</quote>. This can be done by editing the
1121 <filename>user.action</filename> file, or through the <ulink
1122 url="http://config.privoxy.org/show-status">web-based actions file editor</ulink>.
1127 <sect2 renderas="sect3" id="whyseeum">
1128 <title>Why would anybody want to see a checkerboard pattern?</title>
1130 Remember that <link linkend="whatsanad">telling which image is an ad and which
1131 isn't</link>, is an educated guess. While we hope that the standard configuration
1132 is rather smart, it will make occasional mistakes. The checkerboard image is visually
1133 decent, and it shows you where images have been blocked, which can be very
1134 helpful in case some navigation aid or otherwise innocent image was
1135 erroneously blocked. It is recommended for new users so they can
1136 <quote>see</quote> what is happening. Some people might also enjoy seeing how
1137 many banners they <emphasis>don't</emphasis> have to see.
1142 <sect2 renderas="sect3" id="blockedbytext">
1143 <title>I see some images being replaced with text
1144 instead of the checkerboard image. Why and how do I get rid of this?</title>
1146 This happens when the banners are not embedded in the HTML code of the
1147 page itself, but in separate HTML (sub)documents that are loaded into (i)frames
1148 or (i)layers, and these external HTML documents are blocked. Being non-images
1149 they get replaced by a substitute HTML page rather than a substitute image,
1150 which wouldn't work out technically, since the browser expects and accepts
1151 only HTML when it has requested an HTML document.
1154 The substitute page adapts to the available space and shows itself as a
1155 miniature two-liner if loaded into small frames, or full-blown with a
1156 large red "BLOCKED" banner if space allows.
1159 If you prefer the banners to be blocked by images, you must see to it that
1160 the HTML documents in which they are embedded are not blocked. Clicking
1161 the <quote>See why</quote> link offered in the substitute page will show
1162 you which rule blocked the page. After changing the rule and un-blocking
1163 the HTML documents, the browser will try to load the actual banner images
1164 and the usual image blocking will (hopefully!) kick in.
1169 <sect2 renderas="sect3" id="srvany">
1170 <title>Can Privoxy run as a service
1171 on Win2K/NT/XP?</title>
1174 Yes. Version 3.0.5 introduces full <application>Windows</application> service
1175 functionality. See <ulink url="../user-manual/installation.html#installation-pack-win">
1176 the <citetitle>User Manual</citetitle></ulink> for details on how to install and configure
1177 <application>Privoxy</application> as a service.
1180 Earlier ]]>3.x versions could run as a system service using <command>srvany.exe</command>.
1181 See the discussion at <ulink
1182 url="https://sourceforge.net/tracker/?func=detail&atid=361118&aid=485617&group_id=11118">https://sourceforge.net/tracker/?func=detail&atid=361118&aid=485617&group_id=11118</ulink>,
1183 for details, and a sample configuration.
1188 <sect2 renderas="sect3" id="otherproxy">
1189 <title>How can I make Privoxy work with other proxies?</title>
1191 This can be done and is often useful to combine the benefits of
1192 <application>Privoxy</application> with those of a another proxy,
1193 for example to cache content.
1195 url="../user-manual/config.html#FORWARDING">forwarding chapter</ulink>
1196 in the <ulink url="../user-manual/index.html">User Manual</ulink> which
1197 describes how to do this. If you intend to use Privoxy with Tor,
1198 please also have a look at
1199 <link linkend="TOR">How do I use Privoxy together with Tor</link>.
1203 <sect2 renderas="sect3" id="port-80">
1204 <title>Can I just set Privoxy to use port 80
1205 and thus avoid individual browser configuration?</title>
1208 No, its more complicated than that. This only works with special kinds
1209 of proxies known as <quote>intercepting</quote> proxies
1210 (<link linkend="INTERCEPTING">see below</link>).
1215 <sect2 renderas="sect3" id="transparent">
1216 <title>Can Privoxy run as a <quote>transparent
1217 </quote> proxy?</title>
1219 The whole idea of Privoxy is to modify client requests
1220 and server responses in all sorts of ways and therefore
1221 it's not a transparent proxy as described in
1222 <ulink url="http://tools.ietf.org/html/rfc2616">RFC 2616</ulink>.
1225 However, some people say <quote>transparent proxy</quote> when they
1226 mean <quote>intercepting proxy</quote>. If you are one of them,
1227 please read the <link linkend="INTERCEPTING">next entry</link>.
1232 <sect2 renderas="sect3" id="intercepting">
1233 <title>Can Privoxy run as a <quote>intercepting</quote> proxy?</title>
1235 <application>Privoxy</application> can't intercept traffic itself,
1236 but it can handle requests that where intercepted and redirected
1237 with a packet filter (like <application>PF</application> or
1238 <application>iptables</application>), as long as the <literal>Host</literal>
1242 As the <literal>Host</literal> header is required by HTTP/1.1 and as most
1243 web sites rely on it anyway, this limitation shouldn't be a problem.
1246 Please refer to your packet filter's documentation to learn how to
1247 intercept and redirect traffic into <application>Privoxy</application>.
1248 Afterward you just have to configure <application>Privoxy</application> to
1249 <ulink url="../user-manual/config.html#ACCEPT-INTERCEPTED-REQUESTS">accept
1250 intercepted requests</ulink>.
1255 <sect2 renderas="sect3" id="outlook">
1256 <title>How can I configure Privoxy for use with Outlook?</title>
1258 Versions of <application>Outlook</application> prior to Office 2007, use
1259 <application>Internet Explorer</application> components to both render HTML,
1260 and fetch any HTTP requests that may be embedded in an HTML email. So however
1261 you have <application>Privoxy</application> configured to work with IE, this
1262 configuration should automatically be shared, at least with older version of
1266 Starting with Office 2007, Microsoft is instead using the MS-Word rendering
1267 engine with Outlook. It is unknown whether this can be configured to use a
1269 <!-- FIXME HB 2009-02-15 -->
1273 <sect2 renderas="sect3" id="outlook-more">
1274 <title>How can I have separate rules just for HTML mail?</title>
1276 The short answer is, you can't. <application>Privoxy</application> has no way
1277 of knowing which particular application makes a request, so there is no way to
1278 distinguish between web pages and HTML mail.
1279 <application>Privoxy</application> just blindly proxies all requests. In the
1280 case of <application>Outlook Express</application> (see above), OE uses
1281 IE anyway, and there is no way for <application>Privoxy</application> to ever
1282 be able to distinguish between them (nor could any other proxy type application for
1286 For a good discussion of some of the issues involved (including privacy and
1287 security issues), see
1288 <ulink url="https://sourceforge.net/tracker/?func=detail&atid=211118&aid=629518&group_id=11118">https://sourceforge.net/tracker/?func=detail&atid=211118&aid=629518&group_id=11118</ulink>.
1292 <sect2 renderas="sect3" id="sneaky-cookies">
1293 <title>I sometimes notice cookies sneaking through. How?</title>
1296 url="http://en.wikipedia.org/wiki/Browser_cookie">Cookies</ulink> can be
1297 set in several ways. The classic method is via the
1298 <literal>Set-Cookie</literal> HTTP header. This is straightforward, and an
1299 easy one to manipulate, such as the &my-app; concept of
1300 <ulink url="../user-manual/actions-file.html#SESSION-COOKIES-ONLY">session-cookies-only</ulink>.
1301 There is also the possibility of using
1302 <ulink url="http://en.wikipedia.org/wiki/Javascript">Javascript</ulink> to
1303 set cookies (&my-app; calls these <literal>content-cookies</literal>). This
1304 is trickier because the syntax can vary widely, and thus requires a certain
1305 amount of guesswork. It is not realistic to catch all of these short of
1306 disabling Javascript, which would break many sites. And lastly, if the
1307 cookies are embedded in a HTTPS/SSL secure session via Javascript, they are beyond
1308 <application>Privoxy's</application> reach.
1311 All in all, &my-app; can help manage cookies in general, can help minimize
1312 the loss of privacy posed by cookies, but can't realistically stop all
1317 <sect2 renderas="sect3" id="evil-cookies">
1318 <title>Are all cookies bad? Why?</title>
1320 No, in fact there are many beneficial uses of
1322 url="http://en.wikipedia.org/wiki/Browser_cookie">cookies</ulink>. Cookies are just a
1323 method that browsers can use to store data between pages, or between browser
1324 sessions. Sometimes there is a good reason for this, and the user's life is a
1325 bit easier as a result. But there is a long history of some websites taking
1326 advantage of this layer of trust, and using the data they glean from you and
1327 your browsing habits for their own purposes, and maybe to your potential
1328 detriment. Such sites are using you and storing their data on your system.
1329 That is why the privacy conscious watch from whom those cookies come, and why
1330 they really <emphasis>need</emphasis> to be there.
1334 <ulink url="http://en.wikipedia.org/wiki/Browser_cookie">Wikipedia cookie
1335 definition</ulink> for more.
1339 <sect2 renderas="sect3" id="allow-cookies">
1340 <title>How can I allow permanent cookies for my trusted sites?</title>
1343 There are several actions that relate to cookies. The default behavior is to
1344 allow only <quote>session cookies</quote>, which means the cookies only last
1345 for the current browser session. This eliminates most kinds of abuse related
1346 to cookies. But there may be cases where you want cookies to last.
1349 To disable all cookie actions, so that cookies are allowed unrestricted,
1350 both in and out, for <literal>example.com</literal>:
1354 { -crunch-incoming-cookies -crunch-outgoing-cookies -session-cookies-only -filter{content-cookies} }
1355 .example.com</screen>
1358 Place the above in <filename>user.action</filename>. Note that some of these may
1359 be off by default anyway, so this might be redundant, but there is no harm
1360 being explicit in what you want to happen. <filename>user.action</filename>
1361 includes an alias for this situation, called
1362 <literal>allow-all-cookies</literal>.
1366 <sect2 renderas="sect3" id="multiples">
1367 <title>Can I have separate configurations for different users?</title>
1369 Each instance of <application>Privoxy</application> has its own
1370 configuration, including such attributes as the TCP port that it listens on.
1371 What you can do is run multiple instances of <application>Privoxy</application>, each with
1373 <ulink url="../user-manual/config.html#LISTEN-ADDRESS">listen-address</ulink>
1374 configuration setting, and configuration path, and then
1375 each of these can have their own configurations. Think of it as per-port
1379 Simple enough for a few users, but for large installations, consider having
1380 groups of users that might share like configurations.
1384 <sect2 renderas="sect3" id="whitelists">
1385 <title>Can I set-up Privoxy as a whitelist of
1386 <quote>good</quote> sites?</title>
1388 Sure. There are a couple of things you can do for simple white-listing.
1389 Here's one real easy one:
1392 ############################################################
1394 ############################################################
1395 { <ulink url="../user-manual/actions-file.html#BLOCK">+block</ulink> }
1396 / # Block *all* URLs
1398 ############################################################
1400 ############################################################
1401 { <ulink url="../user-manual/actions-file.html#BLOCK">-block</ulink> }
1404 games.example.com</screen>
1406 This allows access to only those three sites by first blocking all URLs, and
1407 then subsequently allowing three specific exceptions.
1410 Another approach is <application>Privoxy's</application>
1411 <literal>trustfile</literal> concept, which incorporates the notion of
1412 <quote>trusted referrers</quote>. See the <ulink
1413 url="../user-manual/config.html#TRUSTFILE">Trust documentation</ulink>
1417 These are fairly simple approaches and are not completely foolproof. There
1418 are various other configuration options that should be disabled (described
1419 elsewhere here and in <ulink url="../user-manual/">the User Manual</ulink>)
1420 so that users can't modify their own configuration and easily circumvent the
1425 <sect2 renderas="sect3" id="no-adblock">
1426 <title>How can I turn off ad-blocking?</title>
1428 Ad blocking is achieved through a complex application of various &my-app;
1429 <ulink url="../user-manual/actions-file.html">actions</ulink>. These
1430 actions are deployed against simple images, banners, flash animations,
1431 text pages, JavaScript, pop-ups and pop-unders, etc., so its not as simple as
1432 just turning one or two actions off. The various actions that make up
1433 &my-app; ad blocking are hard-coded into the default configuration files. It
1434 has been assumed that everyone using &my-app; is interested in this
1438 If you want to do without this, there are several approaches you can take:
1439 You can manually undo the many block rules in
1440 <filename>default.action</filename>. Or even easier, just create your own
1441 <filename>default.action</filename> file from scratch without the many ad
1442 blocking rules, and corresponding exceptions. Or lastly, if you are not
1443 concerned about the additional blocks that are done for privacy reasons, you
1444 can very easily over-ride <emphasis>all</emphasis> blocking with the
1445 following very simple rule in your <filename>user.action</filename>:
1449 # Unblock everybody, everywhere
1450 { <ulink url="../user-manual/actions-file.html#BLOCK">-block</ulink> }
1451 / # UN-Block *all* URLs</screen>
1454 Or even a more comprehensive reversing of various ad related actions:
1458 # Unblock everybody, everywhere, and turn off appropriate filtering, etc
1459 { <ulink url="../user-manual/actions-file.html#BLOCK">-block</ulink> \
1460 <ulink url="../user-manual/actions-file.html#FILTER-BANNERS-BY-SIZE">-filter{banners-by-size}</ulink> \
1461 <ulink url="../user-manual/actions-file.html#FILTER-BANNERS-BY-LINK">-filter{banners-by-link}</ulink> \
1462 <literal>allow-popups</literal> \
1464 / # UN-Block *all* URLs and allow ads</screen>
1467 This last <quote>action</quote> in this compound statement,
1468 <literal>allow-popups</literal>, is an <ulink
1469 url="../user-manual/actions-file.html#ALIASES">alias</ulink> that disables
1470 various pop-up blocking features.
1474 <sect2 renderas="sect3" id="templates">
1475 <title>How can I have custom template pages, like the
1476 <emphasis>BLOCKED</emphasis> page?</title>
1478 &my-app; <quote>templates</quote> are specialized text files utilized by
1479 &my-app; for various purposes and can easily be modified using any text
1480 editor. All the template pages are installed in a sub-directory appropriately
1481 named: <filename>templates</filename>. Knowing something about HTML syntax
1482 will of course be helpful.
1485 Be forewarned that the default templates are subject to being overwritten
1486 during upgrades. You can, however, create completely new templates,
1487 place them in another directory and specify the alternate path in the main
1488 <filename>config</filename>. For details, have a look at the <ulink
1489 url="../user-manual/config.html#templdir">templdir</ulink> option.
1493 <sect2 renderas="sect3" id="blockall">
1494 <title>How can I remove the <quote>Go There Anyway</quote> link from
1495 the <emphasis>BLOCKED</emphasis> page?</title>
1497 There is more than one way to do it (although Perl is not involved).
1500 Editing the BLOCKED template page (see above) may dissuade some users, but
1501 this method is easily circumvented. Where you need this level of control, you
1502 might want to build &my-app; from source, and disable various features that are
1503 available as compile-time options. You should
1504 <command>configure</command> the sources as follows:
1508 ./configure --disable-toggle --disable-editor --disable-force</screen>
1511 This will create an executable with hard-coded security features so that
1512 &my-app; does not allow easy bypassing of blocked sites, or changing the
1513 current configuration via any connected user's web browser.
1516 Finally, all of these features can also be toggled on/off via options in
1517 <application>Privoxy's</application> main <ulink
1518 url="../user-manual/config.html#ACCESS-CONTROL">config</ulink> file which
1519 means you don't have to recompile anything.
1525 <!-- ~ End section ~ -->
1528 <!-- ~~~~~ New section ~~~~~ -->
1530 <sect1 id="misc"><title>Miscellaneous</title>
1532 <sect2 renderas="sect3" id="slowsme">
1533 <title>How much does Privoxy slow my browsing down? This
1534 has to add extra time to browsing.</title>
1536 How much of an impact depends on many things, including the CPU of the host
1537 system, how aggressive the configuration is, which specific actions are being triggered,
1538 the size of the page, the bandwidth of the connection, etc.
1541 Overall, it should not slow you down any in real terms, and may actually help
1542 speed things up since ads, banners and other junk are not typically being
1543 retrieved and displayed. The actual processing time required by
1544 <application>Privoxy</application> itself for each page, is relatively small
1545 in the overall scheme of things, and happens very quickly. This is typically
1546 more than offset by time saved not downloading and rendering ad images and
1547 other junk content (if ad blocking is being used).
1551 <quote>Filtering</quote> content via the <literal><ulink
1552 url="../user-manual/actions-file.html#FILTER">filter</ulink></literal> or
1554 url="../user-manual/actions-file.html#DEANIMATE-GIFS">deanimate-gifs</ulink></literal>
1555 actions may cause a perceived slowdown, since the entire document
1556 needs to be buffered before displaying. And on very large documents,
1557 filtering may have some measurable impact. How much depends on the page size,
1558 the actual definition of the filter(s), etc. See below. Most other actions
1559 have little to no impact on speed.
1562 Also, when filtering is enabled but zlib support isn't available, compression
1563 is often disabled (see <ulink
1564 url="../user-manual/actions-file.html#PREVENT-COMPRESSION">prevent-compression</ulink>).
1565 This can have an impact on speed as well, although it's probably smaller than
1566 you might think. Again, the page size, etc. will determine how much of an impact.
1572 <sect2 renderas="sect3" id="loadingtimes"><title>I notice considerable
1573 delays in page requests. What's wrong?</title>
1575 If you use any <literal><ulink
1576 url="../user-manual/actions-file.html#FILTER">filter</ulink></literal> action,
1577 such as filtering banners by size, web-bugs etc, or the <literal><ulink
1578 url="../user-manual/actions-file.html#DEANIMATE-GIFS">deanimate-gifs</ulink></literal>
1579 action, the entire document must be loaded into memory in order for the filtering
1580 mechanism to work, and nothing is sent to the browser during this time.
1583 The loading time typically does not really change much in real numbers, but
1584 the feeling is different, because most browsers are able to start rendering
1585 incomplete content, giving the user a feeling of "it works". This effect is
1586 more noticeable on slower dialup connections. Extremely large documents
1587 may have some impact on the time to load the page where there is filtering
1588 being done. But overall, the difference should be very minimal. If there is a
1589 big impact, then probably some other situation is contributing (like
1590 anti-virus software).
1593 Filtering is automatically disabled for inappropriate MIME types. But note
1594 that if the web server mis-reports the MIME type, then content that should
1595 not be filtered, could be. <application>Privoxy</application> only knows how
1596 to differentiate filterable content because of the MIME type as reported by
1597 the server, or because of some configuration setting that enables/disables
1602 <sect2 renderas="sect3" id="configurl"><title>What are "http://config.privoxy.org/" and
1603 "http://p.p/"?</title>
1605 <ulink url="http://config.privoxy.org/">http://config.privoxy.org/</ulink> is the
1606 address of <application>Privoxy</application>'s built-in user interface, and
1607 <ulink url="http://p.p/">http://p.p/</ulink> is a shortcut for it.
1610 Since <application>Privoxy</application> sits between your web browser and the Internet,
1611 it can simply intercept requests for these addresses and answer them with its built-in
1612 <quote>web server</quote>.
1615 This also makes for a good test for your browser configuration: If entering the
1616 URL <ulink url="http://config.privoxy.org/">http://config.privoxy.org/</ulink>
1617 takes you to a page saying <quote>This is Privoxy ...</quote>, everything is OK.
1618 If you get a page saying <quote>Privoxy is not working</quote> instead, then
1619 your browser didn't use <application>Privoxy</application> for the request,
1620 hence it could not be intercepted, and you have accessed the <emphasis>real</emphasis>
1621 web site at config.privoxy.org.
1624 Note that config.privoxy.org resolves to a public IP address.
1625 If you use config.privoxy.org as ping or traceroute target you will
1626 reach the system on the Internet (Privoxy can't intercept ICMP requests).
1627 If you want to ping the system Privoxy runs on,
1628 you should use its IP address or local DNS name (if it has got one).
1634 out of date 09/02/06 HB
1635 <sect2 renderas="sect3" id="blocklist"><title>Do you still maintain the blocklists?</title>
1637 No. The patterns for blocking now reside (among other things) in the <ulink
1638 url="../user-manual/actions-file.html">actions files</ulink>, which are
1639 actively maintained instead. See next question ...
1643 <sect2 renderas="sect3" id="newads"><title>How can I submit new ads, or report
1646 Please see the <link linkend="contact">Contact section</link> for
1647 various ways to interact with the developers.
1652 <sect2 renderas="sect3" id="newads2"><title>If I do submit missed ads, will
1653 they be included in future updates?</title>
1655 Whether such submissions are eventually included in the
1656 <filename>default.action</filename> configuration file depends on how
1657 significant the issue is. We of course want to address any potential
1658 problem with major, high-profile sites such as <citetitle>Google</citetitle>,
1659 <citetitle>Yahoo</citetitle>, etc. Any site with global or regional reach,
1660 has a good chance of being a candidate. But at the other end of the spectrum
1661 are any number of smaller, low-profile sites such as for local clubs or
1662 schools. Since their reach and impact are much less, they are best handled by
1663 inclusion in the user's <filename>user.action</filename>, and thus would be
1664 unlikely to be included.
1670 <sect2 renderas="sect3" id="noonecares"><title>Why doesn't anyone answer my support
1673 Rest assured that it has been read and considered. Why it is not answered,
1674 could be for various reasons, including no one has a good answer for it, no
1675 one has had time to yet investigate it thoroughly, it has been reported
1676 numerous times already, or because not enough information was provided to help
1677 us help you. Your efforts are not wasted, and we do appreciate them.
1683 <sect2 renderas="sect3" id="ip"><title>How can I hide my IP address?</title>
1685 If you run both the browser and &my-app; locally, you cannot hide your IP
1686 address with <application>Privoxy</application> or ultimately any other
1687 software alone. The server needs to know your IP address so that it knows
1688 where to send the responses back.
1691 There are many publicly usable "anonymous" proxies out there, which
1692 provide a further level of indirection between you and the web server.
1695 However, these proxies are called "anonymous" because you don't need
1696 to authenticate, not because they would offer any real anonymity.
1697 Most of them will log your IP address and make it available to the
1698 authorities in case you violate the law of the country they run in. In fact
1699 you can't even rule out that some of them only exist to *collect* information
1700 on (those suspicious) people with a more than average preference for privacy.
1703 If you want to hide your IP address from most adversaries,
1704 you should consider chaining <application>Privoxy</application>
1705 with <ulink url="https://www.torproject.org/">Tor</ulink>.
1706 The configuration details can be found in
1707 <ulink url="#TOR">How do I use <application>Privoxy</application> together
1708 with <application>Tor</application> section</ulink>
1713 <sect2 renderas="sect3" id="anonforsure">
1714 <title>Can Privoxy guarantee I am anonymous?</title>
1716 No. Your chances of remaining anonymous are improved, but unless you
1717 <ulink url="#TOR">chain <application>Privoxy</application> with <application>Tor</application></ulink>
1718 or a similar proxy and know what you're doing when it comes to configuring
1719 the rest of your system, you should assume that everything you do
1720 on the Web can be traced back to you.
1723 <application>Privoxy</application> can remove various information about you,
1724 and allows <emphasis>you</emphasis> more freedom to decide which sites
1725 you can trust, and what details you want to reveal. But it neither
1726 hides your IP address, nor can it guarantee that the rest of the system
1727 behaves correctly. There are several possibilities how a web sites can find
1728 out who you are, even if you are using a strict <application>Privoxy</application>
1729 configuration and chained it with <application>Tor</application>.
1732 Most of <application>Privoxy's</application> privacy-enhancing features can be easily subverted
1733 by an insecure browser configuration, therefore you should use a browser that can
1734 be configured to only execute code from trusted sites, and be careful which sites you trust.
1735 For example there is no point in having <application>Privoxy</application>
1736 modify the User-Agent header, if websites can get all the information they want
1737 through JavaScript, ActiveX, Flash, Java etc.
1740 A few browsers disclose the user's email address in certain situations, such
1741 as when transferring a file by FTP. <application>Privoxy</application>
1742 does not filter FTP. If you need this feature, or are concerned about the
1743 mail handler of your browser disclosing your email address, you might
1744 consider products such as <application>NSClean</application>.
1747 Browsers available only as binaries could use non-standard headers to give
1748 out any information they can have access to: see the manufacturer's license
1749 agreement. It's impossible to anticipate and prevent every breach of privacy
1750 that might occur. The professionally paranoid prefer browsers available as
1751 source code, because anticipating their behavior is easier. Trust the source,
1757 <sect2 renderas="sect3" id="proxytest">
1758 <title>A test site says I am not using a Proxy.</title>
1760 Good! Actually, they are probably testing for some other kinds of proxies.
1761 Hiding yourself completely would require additional steps.
1765 <sect2 renderas="sect3" id="tor"><title>How do I use Privoxy
1766 together with Tor?</title>
1768 Before you configure <application>Privoxy</application> to use
1769 <ulink url="https://www.torproject.org/">Tor</ulink>,
1770 please follow the <citetitle>User Manual</citetitle> chapters
1771 <ulink url="../user-manual/installation.html">2. Installation</ulink> and
1772 <ulink url="../user-manual/startup.html">5. Startup</ulink> to make sure
1773 <application>Privoxy</application> itself is setup correctly.
1776 If it is, refer to <ulink url="https://www.torproject.org/documentation.html">Tor's
1777 extensive documentation</ulink> to learn how to install <application>Tor</application>,
1778 and make sure <application>Tor</application>'s logfile says that
1779 <quote>Tor has successfully opened a circuit</quote> and it
1780 <quote>looks like client functionality is working</quote>.
1783 If either <application>Tor</application> or <application>Privoxy</application>
1784 isn't working, their combination most likely will neither. Testing them on their
1785 own will also help you to direct problem reports to the right audience.
1786 If <application>Privoxy</application> isn't working, don't bother the
1787 <application>Tor</application> developers. If <application>Tor</application>
1788 isn't working, don't send bug reports to the <application>Privoxy</application> Team.
1791 If you verified that <application>Privoxy</application> and <application>Tor</application>
1792 are working, it is time to connect them. As far as <application>Privoxy</application>
1793 is concerned, <application>Tor</application> is just another proxy that can be reached
1794 by socks4, socks4a and socks5. Most likely you are interested in <application>Tor</application>
1795 to increase your anonymity level, therefore you should use socks5, to make sure DNS
1796 requests are done through <application>Tor</application> and thus invisible to your
1797 local network. Using socks4a would work too, but with socks5 you get more precise error
1802 <application>Privoxy's</application>
1803 <ulink url="../user-manual/config.html">main configuration file</ulink>
1804 is already prepared for <application>Tor</application>, if you are using a
1805 default <application>Tor</application> configuration and run it on the same
1806 system as &my-app;, you just have to edit the
1807 <ulink url="../user-manual/config.html#FORWARDING">forwarding section</ulink>
1808 and uncomment the line:
1812 # forward-socks5t / 127.0.0.1:9050 .
1816 Note that if you got Tor through one of the bundles, you may
1817 have to change the port from 9050 to 9150 (or even another one).
1818 For details, please check the documentation on the
1819 <ulink url="https://torproject.org/">Tor website</ulink>.
1823 This is enough to reach the Internet, but additionally you might want to
1824 uncomment the following forward rules, to make sure your local network is still
1825 reachable through Privoxy:
1829 # forward 192.168.*.*/ .
1830 # forward 10.*.*.*/ .
1831 # forward 127.*.*.*/ .
1835 Unencrypted connections to systems in these address ranges will
1836 be as (un)secure as the local network is, but the alternative is
1837 that your browser can't reach the network at all. Then again,
1838 that may actually be desired and if you don't know for sure
1839 that your browser has to be able to reach the local network,
1840 there's no reason to allow it.
1843 If you want your browser to be able to reach servers in your local
1844 network by using their names, you will need additional exceptions
1845 that look like this:
1849 # forward localhost/ .
1853 Save the modified configuration file and open
1854 <ulink url="http://config.privoxy.org/show-status">http://config.privoxy.org/show-status</ulink>
1855 in your browser, confirm that <application>Privoxy</application> has reloaded its configuration
1856 and that there are no other forward lines, unless you know that you need them. If everything looks good,
1858 <ulink url="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#IsMyConnectionPrivate">Tor
1859 Faq 4.2</ulink> to learn how to verify that you are really using <application>Tor</application>.
1862 Afterward, please take the time to at least skim through the rest
1863 of <application>Tor's</application> documentation. Make sure you understand
1864 what <application>Tor</application> does, why it is no replacement for
1865 application level security, and why you probably don't want to
1866 use it for unencrypted logins.
1870 <sect2 renderas="sect3" id="sitebreak">
1871 <title>Might some things break because header information or
1872 content is being altered?</title>
1875 Definitely. It is common for sites to use browser type, browser version,
1876 HTTP header content, and various other techniques in order to dynamically
1877 decide what to display and how to display it. What you see, and what I see,
1878 might be very different. There are many, many ways that this can be handled,
1879 so having hard and fast rules, is tricky.
1883 The <quote>User-Agent</quote> is sometimes used in this way to identify
1884 the browser, and adjust content accordingly.
1888 Also, different browsers use different encodings of non-English
1889 characters, certain web servers convert pages on-the-fly according to the
1890 User Agent header. Giving a <quote>User Agent</quote> with the wrong
1891 operating system or browser manufacturer causes some sites in these languages
1892 to be garbled; Surfers to Eastern European sites should change it to
1893 something closer. And then some page access counters work by looking at the
1894 <quote>Referer</quote> header; they may fail or break if unavailable. The
1895 weather maps of Intellicast have been blocked by their server when no
1896 <quote>Referer</quote> or cookie is provided, is another example. (But you
1897 can forge both headers without giving information away). There are
1898 many other ways things can go wrong when trying to fool a web server. The
1899 results of which could inadvertently cause pages to load incorrectly,
1900 partially, or even not at all. And there may be no obvious clues as to just
1901 what went wrong, or why. Nowhere will there be a message that says
1902 <quote><emphasis>Turn off <literal>fast-redirects</literal> or else!</emphasis>
1907 Similar thoughts apply to modifying JavaScript, and, to a lesser degree,
1912 If you have problems with a site, you will have to adjust your configuration
1913 accordingly. Cookies are probably the most likely adjustment that may
1914 be required, but by no means the only one.
1920 <sect2 renderas="sect3" id="caching">
1921 <title>Can Privoxy act as a <quote>caching</quote> proxy to
1922 speed up web browsing?</title>
1924 No, it does not have this ability at all. You want something like
1925 <ulink url="http://www.squid-cache.org/">Squid</ulink> or
1926 <ulink url="http://www.pps.jussieu.fr/~jch/software/polipo/">Polipo</ulink> for this.
1927 And, yes, before you ask, <application>Privoxy</application> can co-exist
1928 with other kinds of proxies like <application>Squid</application>.
1929 See the <ulink url="../user-manual/config.html#FORWARDING">forwarding
1930 chapter</ulink> in the <ulink url="../user-manual/index.html">user
1931 manual</ulink> for details.
1935 <sect2 renderas="sect3" id="firewall">
1936 <title>What about as a firewall? Can Privoxy protect me?</title>
1938 Not in the way you mean, or in the way some firewall vendors claim they can.
1939 <application>Privoxy</application> can help protect your privacy, but can't
1940 protect your system from intrusion attempts. It is, of course, perfectly possible
1941 to use <emphasis>both</emphasis>.
1945 <sect2 renderas="sect3" id="wasted">
1946 <title>I have large empty spaces / a checkerboard pattern now where
1947 ads used to be. Why?</title>
1949 It is technically possible to eliminate banners and ads in a way that frees
1950 their allocated page space. This could easily be done by blocking with
1951 <application>Privoxy's</application> filters,
1952 and eliminating the <emphasis>entire</emphasis> image references from the
1956 But, this would consume considerably more CPU resources (IOW, slow things
1957 down), would likely destroy the layout of some web pages which rely on the
1958 banners utilizing a certain amount of page space, and might fail in other
1959 cases, where the screen space is reserved (e.g. by HTML tables for instance).
1960 Also, making ads and banners disappear without any trace complicates
1961 troubleshooting, and would sooner or later be problematic.
1964 The better alternative is to instead let them stay, and block the resulting
1965 requests for the banners themselves as is now the case. This leaves either
1966 empty space, or the familiar checkerboard pattern.
1969 So the developers won't support this in the default configuration, but you
1970 can of course define appropriate filters yourself to achieve this.
1974 <sect2 renderas="sect3" id="ssl">
1975 <title>How can Privoxy filter Secure (HTTPS) URLs?</title>
1977 Since secure HTTP connections are encrypted SSL sessions between your browser
1978 and the secure site, and are meant to be reliably <emphasis>secure</emphasis>,
1979 there is little that <application>Privoxy</application> can do but hand the raw
1980 gibberish data though from one end to the other unprocessed.
1983 The only exception to this is blocking by host patterns, as the client needs
1984 to tell <application>Privoxy</application> the name of the remote server,
1985 so that <application>Privoxy</application> can establish the connection.
1986 If that name matches a host-only pattern, the connection will be blocked.
1989 As far as ad blocking is concerned, this is less of a restriction than it may
1990 seem, since ad sources are often identifiable by the host name, and often
1991 the banners to be placed in an encrypted page come unencrypted nonetheless
1992 for efficiency reasons, which exposes them to the full power of
1993 <application>Privoxy</application>'s ad blocking.
1996 <quote>Content cookies</quote> (those that are embedded in the actual HTML or
1997 JS page content, see <literal><ulink
1998 url="../user-manual/actions-file.html#FILTER-CONTENT-COOKIES">filter{content-cookies}</ulink></literal>),
1999 in an SSL transaction will be impossible to block under these conditions.
2000 Fortunately, this does not seem to be a very common scenario since most
2001 cookies come by traditional means.
2006 <sect2 renderas="sect3" id="secure">
2007 <title>Privoxy runs as a <quote>server</quote>. How
2008 secure is it? Do I need to take any special precautions?</title>
2010 On Unix-like systems, <application>Privoxy</application> can run as a non-privileged
2011 user, which is how we recommend it be run. Also, by default
2012 <application>Privoxy</application> listens to requests from <quote>localhost</quote>
2016 The server aspect of <application>Privoxy</application> is not itself directly
2017 exposed to the Internet in this configuration. If you want to have
2018 <application>Privoxy</application> serve as a LAN proxy, this will have to
2019 be opened up to allow for LAN requests. In this case, we'd recommend
2020 you specify only the LAN gateway address, e.g. 192.168.1.1, in the main
2021 <application>Privoxy</application> configuration file and check all <ulink
2022 url="../user-manual/config.html#ACCESS-CONTROL">access control and security
2023 options</ulink>. All LAN hosts can then use this as their proxy address
2024 in the browser proxy configuration, but <application>Privoxy</application>
2025 will not listen on any external interfaces. ACLs can be defined in addition,
2026 and using a firewall is always good too. Better safe than sorry.
2031 <sect2 renderas="sect3" id="turnoff">
2032 <title>Can I temporarily disable Privoxy?</title>
2034 &my-app; doesn't have a transparent proxy mode,
2035 but you can toggle off blocking and content filtering.
2038 The easiest way to do that is to point your browser
2039 to the remote toggle URL: <ulink
2040 url="http://config.privoxy.org/toggle">http://config.privoxy.org/toggle</ulink>.
2043 See the <ulink url="../user-manual/appendix.html#BOOKMARKLETS">Bookmarklets section</ulink>
2044 of the <citetitle>User Manual</citetitle> for an easy way to access this
2045 feature. Note that this is a feature that may need to be enabled in the main
2046 <filename>config</filename> file.
2051 <sect2 renderas="sect3" id="reallyoff">
2052 <title>When <quote>disabled</quote> is Privoxy totally
2053 out of the picture?</title>
2055 No, this just means all optional filtering and actions are disabled.
2056 <application>Privoxy</application> is still acting as a proxy, but just
2057 doing less of the things that <application>Privoxy</application> would
2058 normally be expected to do. It is still a <quote>middle-man</quote> in
2059 the interaction between your browser and web sites. See below to bypass
2064 <sect2 renderas="sect3" id="turnoff2">
2065 <title>How can I tell Privoxy to totally ignore certain sites?</title>
2067 Bypassing a proxy, or proxying based on arbitrary criteria, is purely a browser
2068 configuration issue, not a &my-app; issue. Modern browsers typically do have
2069 settings for not proxying certain sites. Check your browser's help files.
2074 <sect2 renderas="sect3" id="crunch">
2075 <title>My logs show Privoxy <quote>crunches</quote>
2076 ads, but also its own internal CGI pages. What is a <quote>crunch</quote>?</title>
2078 A <quote>crunch</quote> simply means <application>Privoxy</application> intercepted
2079 <emphasis>something</emphasis>, nothing more. Often this is indeed ads or
2080 banners, but <application>Privoxy</application> uses the same mechanism for
2081 trapping requests for its own internal pages. For instance, a request for
2082 <application>Privoxy's</application> configuration page at: <ulink
2083 url="http://config.privoxy.org">http://config.privoxy.org</ulink>, is
2084 intercepted (i.e. it does not go out to the 'net), and the familiar CGI
2085 configuration is returned to the browser, and the log consequently will show
2086 a <quote>crunch</quote>.
2089 Since version 3.0.7, Privoxy will also log the crunch reason.
2090 If you are using an older version you might want to upgrade.
2094 <sect2 renderas="sect3" id="downloads">
2095 <title>Can Privoxy affect files that I download
2096 from a webserver? FTP server?</title>
2098 From the webserver's perspective, there is no difference between
2099 viewing a document (i.e. a page), and downloading a file. The same is true of
2100 <application>Privoxy</application>. If there is a match for a <literal><ulink
2101 url="../user-manual/actions-file.html#BLOCK">block</ulink></literal> pattern,
2102 it will still be blocked, and of course this is obvious.
2105 Filtering is potentially more of a concern since the results are not always
2106 so obvious, and the effects of filtering are there whether the file is simply
2107 viewed, or downloaded. And potentially whether the content is some obnoxious
2108 advertisement, or Mr. Jimmy's latest/greatest source code jewel. Of course,
2109 one of these presumably is <quote>bad</quote> content that we don't want, and
2110 the other is <quote>good</quote> content that we do want.
2111 <application>Privoxy</application> is blind to the differences, and can only
2112 distinguish <quote>good from bad</quote> by the configuration parameters
2113 <emphasis>we</emphasis> give it.
2116 <application>Privoxy</application> knows the differences in files according
2117 to the <quote>Content Type</quote> as reported by the webserver. If this is
2118 reported accurately (e.g. <quote>application/zip</quote> for a zip archive),
2119 then <application>Privoxy</application> knows to ignore these where
2120 appropriate. <application>Privoxy</application> potentially can filter HTML
2121 as well as plain text documents, subject to configuration parameters of
2122 course. Also, documents that are of an unknown type (generally assumed to be
2123 <quote>text/plain</quote>) can be filtered, as will those that might be
2124 incorrectly reported by the webserver. If such a file is a downloaded file
2125 that is intended to be saved to disk, then any content that might have been
2126 altered by filtering, will be saved too, for these (probably rare) cases.
2129 Note that versions later than 3.0.2 do NOT filter document types reported as
2130 <quote>text/plain</quote>. Prior to this, <application>Privoxy</application>
2131 did filter this document type.
2134 In short, filtering is <quote>ON</quote> if a) the content type as reported
2135 by the webserver is appropriate <emphasis>and</emphasis> b) the configuration
2136 allows it (or at least does not disallow it). That's it. There is no magic
2137 cookie anywhere to say this is <quote>good</quote> and this is
2138 <quote>bad</quote>. It's the configuration that lets it all happen or not.
2141 If you download text files, you probably do not want these to be filtered,
2142 particularly if the content is source code, or other critical content. Source
2143 code sometimes might be mistaken for Javascript (i.e. the kind that might
2144 open a pop-up window). It is recommended to turn off filtering for download
2145 sites (particularly if the content may be plain text files and you are using
2146 version 3.0.2 or earlier) in your <filename>user.action</filename> file. And
2147 also, for any site or page where making <emphasis>any</emphasis> changes at
2148 all to the content is to be avoided.
2151 <application>Privoxy</application> does not do FTP at all, only HTTP
2152 and HTTPS (SSL) protocols.
2156 <sect2 renderas="sect3" id="downloads2">
2157 <title>I just downloaded a Perl script, and Privoxy
2158 altered it! Yikes, what is wrong!</title>
2164 <sect2 renderas="sect3" id="hostsfile">
2165 <title>Should I continue to use a <quote>HOSTS</quote> file for ad-blocking?</title>
2167 One time-tested technique to defeat common ads is to trick the local DNS
2168 system by giving a phony IP address for the ad generator in the local
2169 <filename>HOSTS</filename> file, typically using <literal>127.0.0.1</literal>, aka
2170 <literal>localhost</literal>. This effectively blocks the ad.
2173 There is no reason to use this technique in conjunction with
2174 <application>Privoxy</application>. <application>Privoxy</application>
2175 does essentially the same thing, much more elegantly and with much more
2176 flexibility. A large <filename>HOSTS</filename> file, in fact, not only
2177 duplicates effort, but may get in the way and seriously slow down your system.
2178 It is recommended to remove such entries from your <filename>HOSTS</filename> file. If you think
2179 your hosts list is neglected by <application>Privoxy's </application>
2180 configuration, consider adding your list to your <filename>user.action</filename> file:
2187 ads.galore.example.com
2188 etc.example.com</screen>
2192 <sect2 renderas="sect3" id="seealso">
2193 <title>Where can I find more information about Privoxy
2194 and related issues?</title>
2195 <!-- Include seealso.sgml boilerplate: -->
2197 <!-- end boilerplate -->
2202 <ulink url="../user-manual/seealso.html">user-manual</ulink> for
2208 <sect2 renderas="sect3" id="microsuck">
2209 <title>I've noticed that Privoxy changes <quote>Microsoft</quote> to
2210 <quote>MicroSuck</quote>! Why are you manipulating my browsing?</title>
2213 We're not. The text substitutions that you are seeing are disabled
2214 in the default configuration as shipped. You have either manually
2215 activated the <quote><literal>fun</literal></quote> filter which
2216 is clearly labeled <quote>Text replacements for subversive browsing
2217 fun!</quote> or you are using an older Privoxy version and have implicitly
2218 activated it by choosing the <quote>Advanced</quote> profile in the
2219 web-based editor. Please upgrade.
2223 <sect2 renderas="sect3" id="valid">
2224 <title>Does Privoxy produce <quote>valid</quote> HTML (or XHTML)?</title>
2227 Privoxy generates HTML in both its own <quote>templates</quote>, and possibly
2228 whenever there are text substitutions via a &my-app; filter. While this
2229 should always conform to the HTML 4.01 specifications, it has not been
2230 validated against this or any other standard.
2234 <sect2 renderas="sect3" id="surprise-privoxy">
2235 <title>How did you manage to get Privoxy on my computer without my consent?</title>
2238 We didn't. We make Privoxy available for download, but we don't go
2239 around installing it on other people's systems behind their back.
2240 If you discover Privoxy running on your system and are sure you didn't
2241 install it yourself, somebody else did. You may not even be running
2242 the real Privoxy, but maybe something else that only pretends to be
2243 Privoxy, or maybe something that is based on the real Privoxy,
2244 but has been modified.
2247 Lately there have been reports of problems with some kind of
2248 "parental control" software based on Privoxy that came preinstalled on
2249 certain <ulink url="https://sourceforge.net/p/ijbswa/bugs/813/">ASUS Netbooks</ulink>.
2250 The problems described are inconsistent with the behaviour of official
2251 Privoxy versions, which suggests that the preinstalled software may
2252 contain vendor modifications that we don't know about and thus can't debug.
2255 Privoxy's <link linkend="copyright">license</link> allows vendor
2256 modifications, but the vendor has to comply with the license,
2257 which involves informing the user about the changes and to make
2258 the changes available under the same license as Privoxy itself.
2261 If you are having trouble with a modified Privoxy version,
2262 please try to talk to whoever made the modifications before
2263 reporting the problem to us. Please also try to convince
2264 whoever made the modifications to talk to us. If you think
2265 somebody gave you a modified Privoxy version without complying
2266 to the license, please let us know.
2274 <!-- ~~~~~ New section ~~~~~ -->
2276 <sect1 id="trouble">
2277 <title>Troubleshooting</title>
2279 <sect2 renderas="sect3" id="refused">
2280 <title>I cannot connect to any websites. Or, I am getting
2281 <quote>connection refused</quote> message with every web page. Why?</title>
2283 There are several possibilities:
2288 <application>Privoxy</application> is not running. Solution: verify
2289 that &my-app; is installed correctly, has not crashed, and is indeed running.
2290 Turn on <application>Privoxy's</application> logging, and look at the logs to see what they say.
2292 <listitem><para>Or your browser is configured for a different port than what
2293 <application>Privoxy</application> is using. Solution: verify that &my-app;
2294 and your browser are set to the same port (<literal>listen-address</literal>).
2296 <listitem><para>Or if using a forwarding rule, you have a configuration problem or a
2297 problem with a host in the forwarding chain. Solution: temporarily alter your
2298 configuration and take the forwarders out of the equation.
2301 Or you have a firewall that is interfering and blocking you. Solution:
2302 try disabling or removing the firewall as a simple test.
2309 <!-- ~~~~~ New section ~~~~~ -->
2310 <sect2 renderas="sect3" id="error503">
2311 <title>Why am I getting a 503 Error (WSAECONNREFUSED) on every page?</title>
2313 More than likely this is a problem with your TCP/IP networking. ZoneAlarm has
2314 been reported to cause this symptom -- even if not running! The solution is
2315 to either fight the ZA configuration, or uninstall ZoneAlarm, and then find
2316 something better behaved in its place. Other personal firewall type products
2317 may cause similar type problems if not configured correctly.
2321 <sect2 renderas="sect3" id="flushit">
2322 <title>I just added a new rule, but the steenkin ad is
2323 still getting through. How?</title>
2325 If the ad had been displayed before you added its URL, it will probably be
2326 held in the browser's cache for some time, so it will be displayed without
2327 the need for any request to the server, and <application>Privoxy</application>
2328 will not be involved. Flush the browser's caches, and then try again.
2332 If this doesn't help, you probably have an error in the rule you
2333 applied. Try pasting the full URL of the offending ad into <ulink
2334 url="http://config.privoxy.org/show-url-info">http://config.privoxy.org/show-url-info</ulink>
2335 and see if it really matches your new rule. Blocking ads is like blocking
2336 spam: a lot of tinkering is required to stay ahead of the game. And
2337 remember you need to block the URL of the ad in question, which may be
2338 entirely different from the site URL itself. Most ads are hosted on different
2339 servers than the main site itself. If you right-click on the ad, you should
2340 be able to get all the relevant information you need. Alternately, you can
2341 find the correct URL by looking at <application>Privoxy's</application> logs
2342 (you may need to enable logging in the main config file if its disabled).
2345 Below is a slightly modified real-life log snippet that originates with one
2346 requested URL: <literal>www.example.com</literal> (name of site was changed
2347 for this example, the number of requests is real). You can see in this the
2348 complexity of what goes into making up this one <quote>page</quote>. There
2349 are eight different domains involved here, with thirty two separate URLs
2350 requested in all, making up all manner of images, Shockwave Flash,
2351 JavaScript, CSS stylesheets, scripts, and other related content. Some of this
2352 content is obviously <quote>good</quote> or <quote>bad</quote>, but not all.
2353 Many of the more questionable looking requests, are going to outside domains
2354 that seem to be identifying themselves with suspicious looking names, making
2355 our job a little easier. &my-app; has <quote>crunched</quote> (meaning caught
2356 and BLOCKED) quite a few items in this example, but perhaps missed a few as well.
2361 Request: www.example.com/
2362 Request: www.example.com/favicon.ico
2363 Request: img.example.com/main.css
2364 Request: img.example.com/sr.js
2365 Request: example.betamarker.com/example.html
2366 Request: www.lik-sang.com/Banners/bestsellers/skyscraper.php?likref=BSellers
2367 Request: img.example.com/pb.png
2368 Request: www.google-analytics.com/urchin.js crunch! (Blocked)
2369 Request: www.advertising-department.com/ats/switch.ps.php?26856 crunch! (Blocked)
2370 Request: img.example.com/p.gif
2371 Request: www.popuptraffic.com/assign.php?l=example&mode=behind crunch! (Blocked)
2372 Request: www.popuptraffic.com/scripts/popup.php?hid=5c3cf&tmpl=PBa.tmpl crunch! (Blocked)
2373 Request: www.popuptraffic.com/assign.php?l=example crunch! (Blocked)
2374 Request: www.lik-sang.com/Banners/best_sellers/best_sellers.css
2375 Request: www.adtrak.net/adx.js crunch! (Blocked)
2376 Request: img.example.com/hbg.gif
2377 Request: img.example.com/example.jpg
2378 Request: img.example.com/mt.png
2379 Request: img.example.com/mm.png
2380 Request: img.example.com/mb.png
2381 Request: www.popuptraffic.com/scripts/popup.php?hid=a71b91fa5&tmpl=Ua.tmp crunch! (Blocked)
2382 Request: www.example.com/tracker.js
2383 Request: www.lik-sang.com/Banners/best_sellers/lsi_head.gif
2384 Request: www.adtrak.net/adjs.php?n=020548130&what=zone:61 crunch! (Blocked)
2385 Request: www.adtrak.net/adjs.php?n=463594413&what=zone:58&source=Ua crunch! (Blocked)
2386 Request: www.lik-sang.com/Banners/best_sellers/bottomani.swf
2387 Request: mmm.elitemediagroup.net/install.php?allowpop=no&popupmincook=0&allowsp2=1 crunch! (Blocked)
2388 Request: www.example.com/tracker.js?screen=1400x1050&win=962x693
2389 Request: www.adtrak.net/adlog.php?bannerid=1309&clientid=439&zoneid=61 crunch! (Blocked)
2390 Request: 66.70.21.80/scripts/click.php?hid=5c3cf599a9efd0320d26&si
2391 Request: 66.70.21.80/img/pixel.gif
2392 Request: www.adtrak.net/adlog.php?bannerid=1309&clientid=439&zoneid=58&source=Ua&block=86400 crunch! (Blocked)
2393 Request: 66.70.21.80/scripts/click.php?hid=a71b9f6504b0c5681fa5&si=Ua
2398 Despite 12 out of 32 requests being blocked, the page looked, and seemed to
2399 behave perfectly <quote>normal</quote> (minus some ads, of course).
2404 <sect2 renderas="sect3" id="badsite">
2405 <title>One of my favorite sites does not work with Privoxy.
2406 What can I do?</title>
2409 First verify that it is indeed a <application>Privoxy</application> problem,
2410 by toggling off <application>Privoxy</application> through <ulink
2411 url="http://config.privoxy.org/toggle">http://config.privoxy.org/toggle</ulink>
2412 (the toggle feature may need to be enabled in the main
2413 <filename>config</filename>),
2414 and then shift-reloading the problem page (i.e. holding down the shift key
2415 while clicking reload. Alternatively, flush your browser's disk and memory
2420 If the problem went away, we know we have a configuration related problem.
2422 url="http://config.privoxy.org/show-url-info">http://config.privoxy.org/show-url-info</ulink>
2423 and paste the full URL of the page in question into the prompt. See which
2424 actions are being applied to the URL, and which matches in which actions
2425 files are responsible for that. It might be helpful also to look at your logs
2426 for this site too, to see what else might be happening (note: logging may need
2427 to be enabled in the main config file). Many sites are
2428 complex and require a number of related pages to help present their content.
2429 Look at what else might be used by the page in question, and what of that
2430 might be <emphasis>required</emphasis>.
2431 Now, armed with this information, go to
2433 url="http://config.privoxy.org/show-status">http://config.privoxy.org/show-status</ulink>
2434 and select the appropriate actions files for editing. </para>
2436 You can now either look for a section which disables the actions that
2437 you suspect to cause the problem and add a pattern for your site there,
2438 or make up a completely new section for your site. In any case, the recommended
2439 way is to disable only the prime suspect, reload the problem page, and only
2440 if the problem persists, disable more and more actions until you have
2441 identified the culprit. You may or may not want to turn the other actions
2442 on again. Remember to flush your browser's caches in between any such changes!
2445 Alternately, if you are comfortable with a text editor, you can accomplish
2446 the same thing by editing the appropriate actions file. Probably the easiest
2447 way to deal with such problems when editing by hand is to add your
2448 site to a <literal>{ fragile }</literal> section in <filename>user.action</filename>,
2449 which is an alias that turns off most <quote>dangerous</quote>
2450 actions, but is also likely to turn off more actions then needed, and thus lower
2451 your privacy and protection more than necessary,
2454 Troubleshooting actions is discussed in more detail in the <ulink
2455 url="../user-manual/appendix.html#ACTIONSANAT">User Manual appendix,
2456 Troubleshooting: the Anatomy of an Action</ulink>.
2457 There is also an <ulink
2458 url="../user-manual/actions-file.html#ACT-EXAMPLES">actions tutorial</ulink>
2459 with general configuration information and examples.
2462 As a last resort, you can always see if your browser has a setting that will
2463 bypass the proxy setting for selective sites. Modern browsers can do this.
2469 <!-- ~~~~~ New section ~~~~~ -->
2470 <sect2 id="dun" renderas="sect3">
2471 <title>After installing Privoxy, I have to log in
2472 every time I start IE. What gives?</title>
2475 This is a quirk that affects the installation of
2476 <application>Privoxy</application>, in conjunction with Internet Explorer and
2477 Internet Connection Sharing on Windows 2000 and Windows XP. The symptoms may
2478 appear to be corrupted or invalid DUN settings, or passwords.
2482 When setting up an NT based Windows system with
2483 <application>Privoxy</application> you may find that things do not seem to be
2484 doing what you expect. When you set your system up you will probably have set
2485 up Internet Connection Sharing (ICS) with Dial up Networking (DUN) when
2486 logged in with administrator privileges. You will probably have made this DUN
2487 connection available to other accounts that you may have set-up on your
2488 system. E.g. Mum or Dad sets up the system and makes accounts suitably
2489 configured for the kids.
2493 When setting up <application>Privoxy</application> in this environment you
2494 will have to alter the proxy set-up of Internet Explorer (IE) for the
2495 specific DUN connection on which you wish to use
2496 <application>Privoxy</application>. When you do this the ICS DUN set-up
2497 becomes user specific. In this instance you will see no difference if you
2498 change the DUN connection under the account used to set-up the connection.
2499 However when you do this from another user you will notice that the DUN
2500 connection changes to make available to "Me only". You will also find that
2501 you have to store the password under each different user!
2505 The reason for this is that each user's set-up for IE is user specific. Each
2506 set-up DUN connection and each LAN connection in IE store the settings for
2507 each user individually. As such this enforces individual configurations
2508 rather than common ones. Hence the first time you use a DUN connection after
2509 re-booting your system it may not perform as you expect, and prompt you for
2510 the password. Just set and save the password again and all should be OK.
2514 [Thanks to Ray Griffith for this submission.]
2519 <!-- ~~~~~ New section ~~~~~ -->
2520 <sect2 id="ftp" renderas="sect3">
2521 <title>I cannot connect to any FTP sites. Privoxy
2522 is blocking me.</title>
2524 <application>Privoxy</application> cannot act as a proxy for FTP traffic,
2525 so do not configure your browser to use <application>Privoxy</application>
2526 as an FTP proxy. The same is true for <emphasis>any protocol other than HTTP
2527 or HTTPS (SSL)</emphasis>.
2530 Most browsers understand FTP as well as HTTP. If you connect to a site, with
2531 a URL like <literal>ftp://ftp.example.com</literal>, your browser is making
2532 an FTP connection, and not a HTTP connection. So while your browser may
2533 speak FTP, <application>Privoxy</application> does not, and cannot proxy
2537 To complicate matters, some systems may have a generic <quote>proxy</quote>
2538 setting, which will enable various protocols, including
2539 <emphasis>both</emphasis> HTTP and FTP proxying! So it is possible to
2540 accidentally enable FTP proxying in these cases. And of course, if this
2541 happens, <application>Privoxy</application> will indeed cause problems since
2542 it does not know FTP. <![%p-newstuff;[Newer version will give a sane error
2543 message if a FTP connection is attempted.]]> Just disable the FTP setting
2544 and all will be well again.
2547 Will <application>Privoxy</application> ever proxy FTP traffic? Unlikely.
2548 There just is not much reason, and the work to make this happen is more than
2553 <!-- ~~~~~ New section ~~~~~ -->
2554 <sect2 id="macosxie" renderas="sect3">
2555 <title>In Mac OS X, I can't configure Microsoft Internet Explorer to use
2556 Privoxy as the HTTP proxy.</title>
2558 Microsoft Internet Explorer (in versions like 5.1) respects system-wide
2559 network settings. In order to change the HTTP proxy, open System
2560 Preferences, and click on the Network icon. In the settings pane that
2561 comes up, click on the Proxies tab. Ensure the "Web Proxy (HTTP)" checkbox
2562 is checked and enter <literal>127.0.0.1</literal> in the entry field.
2563 Enter <literal>8118</literal> in the Port field. The next time you start
2564 IE, it should reflect these values.
2568 <!-- ~~~~~ New section ~~~~~ -->
2569 <sect2 renderas="sect3" id="macosxuninstall">
2570 <title>In Mac OS X, I dragged the Privoxy folder to the trash in order to
2571 uninstall it. Now the finder tells me I don't have sufficient privileges to
2572 empty the trash.</title>
2574 Note: This ONLY applies to privoxy 3.0.6 and earlier.
2577 Just dragging the <application>Privoxy</application> folder to the trash is
2578 not enough to delete it. <application>Privoxy</application> supplies an
2579 <application>uninstall.command</application> file that takes care of
2580 these details. Open the trash, drag the <application>uninstall.command</application>
2581 file out of the trash and double-click on it. You will be prompted for
2582 confirmation and the administration password.
2585 The trash may still appear full after this command; emptying the trash
2586 from the desktop should make it appear empty again.
2590 <!-- ~~~~~ New section ~~~~~ -->
2591 <sect2 renderas="sect3" id="macosximages">
2592 <title>In Mac OS X Panther (10.3), images often fail to load and/or I
2593 experience random delays in page loading. I'm using
2594 <literal>localhost</literal> as my browser's proxy setting.</title>
2596 We believe this is due to an IPv6-related bug in Mac OS X, but don't fully
2597 understand the issue yet. In any case, changing the proxy setting to
2598 <literal>127.0.0.1</literal> instead of <literal>localhost</literal>
2599 works around the problem.
2603 <!-- ~~~~~ New section ~~~~~ -->
2604 <sect2 renderas="sect3" id="macosxaccountdeletion">
2605 <title>I just upgraded to Mac OS X 10.9 (Mavericks) and now &my-app; has stopped
2608 The upgrade process to Mac OS X Mavericks (10.9) from an earlier version of OS
2609 X deletes all user accounts that are either not part of OS X itself or are
2610 not interactive user accounts (ones you log in with). Since, for the sake of
2611 security, &my-app; runs as a non-privileged user that is created by its
2612 installer (_privoxy), it can no longer start up once that account gets deleted.
2613 The solution is to perform a complete uninstall using the supplied
2614 <application>uninstall.command</application> script (either back up your
2615 configuration files or select to not have the uninstaller remove them when it
2616 prompts you) and then reinstall &my-app; using the installer package and merge
2617 in your configuration.
2621 <!-- ~~~~~ New section ~~~~~ -->
2622 <!-- XXX: Is this still relevant now that we have gzip support? -->
2623 <sect2 renderas="sect3" id="blankpage">
2624 <title>I get a completely blank page at one site. <quote>View Source</quote>
2625 shows only: <markup><![CDATA[<html><body></body></html>]]></markup>. Without
2626 Privoxy the page loads fine.</title>
2628 Chances are that the site suffers from a bug in
2629 <ulink url="http://www.php.net/"><application>PHP</application></ulink>,
2630 which results in empty pages being sent if the client explicitly requests
2631 an uncompressed page, like <application>Privoxy</application> does.
2632 This bug has been fixed in PHP 4.2.3.
2635 To find out if this is in fact the source of the problem, try adding
2636 the site to a <literal>-prevent-compression</literal> section in
2637 <filename>user.action</filename>:
2640 # Make exceptions for ill-behaved sites:
2642 {-prevent-compression}
2643 .example.com</screen>
2645 If that works, you may also want to report the problem to the
2646 site's webmasters, telling them to use zlib.output_compression
2647 instead of ob_gzhandler in their PHP applications (workaround)
2648 or upgrade to PHP 4.2.3 or later (fix).
2652 <sect2 renderas="sect3" id="nohostname">
2653 <title>My logs show many <quote>Unable to get my own hostname</quote> lines.
2656 <application>Privoxy</application> tries to get the hostname of the system
2657 its running on from the IP address of the system interface it is bound to
2658 (from the <filename>config</filename> file
2659 <emphasis>listen-address</emphasis> setting). If the system cannot supply
2660 this information, <application>Privoxy</application> logs this condition.
2663 Typically, this would be considered a minor system configuration error. It is
2664 not a fatal error to <application>Privoxy</application> however, but may
2665 result in a much slower response from <application>Privoxy</application> on
2666 some platforms due to DNS timeouts.
2669 This can be caused by a problem with the local <filename>hosts</filename>
2670 file. If this file has been changed from the original, try reverting it to
2671 see if that helps. Make sure whatever name(s) are used for the local system,
2672 that they resolve both ways.
2675 You should also be able to work around the problem with the
2676 <ulink url="../user-manual/config.html#HOSTNAME">hostname option</ulink>.
2680 <sect2 renderas="sect3" id="inuse">
2681 <title>When I try to launch Privoxy, I get an
2682 error message <quote>port 8118 is already in use</quote> (or similar wording).
2685 Port 8118 is <application>Privoxy's</application> default TCP
2686 <quote>listening</quote> port. Typically this message would mean that there
2687 is already one instance of <application>Privoxy</application> running, and
2688 your system is actually trying to start a second
2689 <application>Privoxy</application> on the same port, which will not work.
2690 (You can have multiple instances but they must be assigned different ports.)
2691 How and why this might happen varies from platform to platform, but you need
2692 to check your installation and start-up procedures.
2696 <sect2 renderas="sect3" id="demoronizer">
2698 Pages with UTF-8 fonts are garbled.
2701 This may be the result of an overly aggressive filter. The filters that
2702 are enabled in the default configuration aren't expected to cause problems
2703 like this. If you enabled the <quote>demoronizer</quote> filter, please
2704 try temporarily disabling it.
2707 If that doesn't help, temporarily disable all filters to see if another
2708 filter could be the culprit. If the problem disappears, enable the filters
2709 one by one, until the problem reappears and the offending filter is found.
2712 Once the problem-causing filter is known, it can be fixed or disabled.
2715 Upgrading <application>Privoxy</application>, or going to the most recent
2716 <filename>default.action</filename> file available from <ulink
2717 url="https://sourceforge.net/project/showfiles.php?group_id=11118">SourceForge</ulink>
2718 might be worth a try, too.
2722 <sect2 renderas="sect3" id="demoronizer2">
2724 Why are binary files (such as images) corrupted when Privoxy
2728 This may also be caused by an (<link linkend="DEMORONIZER">overly aggressive
2729 filter</link> in conjunction with a web server that is misreporting the content
2730 type. By default binary files are exempted from
2731 <application>Privoxy's</application> filtering
2732 (unless the web server by mistake says the file is something else).
2736 <sect2 renderas="sect3" id="demoronizer3">
2738 What is the <quote>demoronizer</quote> and why is it there?
2741 The original demoronizer was a Perl script that cleaned up HTML pages which
2742 were created with certain Microsoft products. MS has used proprietary extensions
2743 to standardized font encodings (ISO 8859-1), which has caused problems for pages
2744 that are viewed with non-Microsoft products (and are expecting to see a
2745 standard set of fonts). The demoronizer corrected these errors so the pages
2746 displayed correctly. <application>Privoxy</application> borrowed from this
2747 script, introducing a filter based on the original demoronizer, which in turn could
2748 correct these errors on the fly.
2751 But this is only needed in some situations, and will cause serious problems in some
2755 If you are using Microsoft products, you do not need it. If you need to view
2756 pages with UTF-8 characters (such as Cyrillic or Chinese), then it will
2757 cause corruption of the fonts, and thus <emphasis>should not be on</emphasis>.
2760 On the other hand, if you use non-Microsoft products, and you occasionally
2761 notice weird characters on pages, you might want to try it.
2765 <sect2 renderas="sect3" id="windowopen">
2767 Why do I keep seeing <quote>PrivoxyWindowOpen()</quote> in raw source code?
2770 <application>Privoxy</application> is attempting to disable malicious
2771 <ulink url="http://en.wikipedia.org/wiki/Javascript">Javascript</ulink>
2772 in this case, with the <literal>unsolicited-popups</literal>
2773 filter. <application>Privoxy</application> cannot tell very well
2774 <quote>good</quote> code snippets from <quote>bad</quote> code snippets.
2777 If you see this in HTML source, and the page displays without problems, then
2778 this is good, and likely some pop-up window was disabled. If you see this
2779 where it is causing a problem, such as a downloaded program source code file,
2780 then you should set an exception for this site or page such that the
2781 integrity of the page stays in tact by disabling all filtering.
2785 <sect2 renderas="sect3" id="dnserrors">
2787 I am getting too many DNS errors like <quote>404 No Such Domain</quote>. Why
2788 can't Privoxy do this better?
2791 There are potentially several factors here. First of all, the DNS resolution
2792 is done by the underlying operating system -- not
2793 <application>Privoxy</application> itself. <application>Privoxy</application>
2794 merely initiates the process and hands it off, and then later reports
2795 whatever the outcome was and tries to give a coherent message if there seems
2796 to be a problem. In some cases, this might otherwise be mitigated by the
2797 browser itself which might try some work-arounds and alternate approaches (e.g
2798 adding <quote>www.</quote> to the URL).
2801 In other cases, if <application>Privoxy</application> is being chained
2802 with another proxy, this could complicate the issue, and cause undue
2803 delays and timeouts. In the case of a <quote>socks4a</quote> proxy, the socks
2804 server handles all the DNS. <application>Privoxy</application> would just be
2805 the <quote>messenger</quote> which is reporting whatever problem occurred
2806 downstream, and not the root cause of the error.
2810 In any case, versions newer than 3.0.3 include various improvements to help
2811 <application>Privoxy</application> better handle these cases.
2815 <sect2 renderas="sect3" id="allcpu">
2817 At one site Privoxy just hangs, and starts taking
2818 all CPU. Why is this?
2821 This is probably a manifestation of the <quote>100% cpu</quote> problem that
2822 occurs on pages containing many (thousands upon thousands) of blank lines. The blank lines
2823 are in the raw HTML source of the page, and the browser just ignores them. But the
2824 pattern matching in <application>Privoxy's</application> page filtering
2825 mechanism is trying to match against absurdly long strings and this becomes
2826 very CPU-intensive, taking a long, long time to complete.
2829 Until a better solution comes along, disable filtering on these pages,
2830 particularly the <literal>js-annoyances</literal> and
2831 <literal>unsolicited-popups</literal> filters. If you run into this problem
2832 with a recent &my-app; version, please send a problem report.
2836 <sect2 renderas="sect3" id="slowcrawl">
2837 <title>I just installed Privoxy, and all my
2838 browsing has slowed to a crawl. What gives? </title>
2840 This should not happen, and for the overwhelming number of users world-wide,
2841 it does not happen. I would suspect some inadvertent interaction of software
2842 components such as anti-virus software, spyware protectors, personal
2843 firewalls or similar components. Try disabling (or uninstalling) these one
2844 at a time and see if that helps. Either way, if you are using a
2845 recent &my-app; version, please report the problem.
2849 <sect2 renderas="sect3" id="preventcomp">
2850 <title>Why do my filters work on some sites but not on others? </title>
2852 It's probably due to compression. It is a common practice for web servers to
2853 send their content <quote>compressed</quote> in order to speed things up, and
2854 then let the browser <quote>uncompress</quote> them. When compiled with zlib support
2855 &my-app; can decompress content before filtering, otherwise you may want to enable
2857 url="../user-manual/actions-file.html#PREVENT-COMPRESSION">prevent-compression</ulink>.
2860 As of &my-app; 3.0.9, zlib support is enabled in the default builds.
2865 <sect2 renderas="sect3" id="ssl-warnings">
2866 <title>On some HTTPS sites my browser warns me about unauthenticated content,
2867 the URL bar doesn't get highlighted and the lock symbol appears to be broken.
2868 What's going on?</title>
2870 Probably the browser is requesting ads through HTTPS and &my-app;
2871 is blocking the requests. Privoxy's error messages are delivered
2872 unencrypted and while it's obvious for the browser that the HTTPS
2873 request is already blocked by the proxy, some warn about unauthenticated
2877 To work around the problem you can redirect those requests to an invalid
2878 local address instead of blocking them. While the redirects aren't
2879 encrypted either, many browsers don't care. They simply follow the
2880 redirect, fail to reach a server and display an error message instead
2884 To do that, enable logging to figure out which requests get blocked by
2885 &my-app; and add the hosts (no path patterns) to a section like this:
2890 {+redirect{http://127.0.0.1:0/} -block -limit-connect}
2896 Additionally you have to configure your browser to contact
2897 <quote>127.0.0.1:0</quote> directly (instead of through &my-app;).
2900 To add a proxy exception in <application>Mozilla Firefox</application>
2901 open the <quote>Preferences</quote>, click the <quote>Settings</quote>
2902 button located on the <quote>Network</quote> tab in the <quote>Advanced</quote>
2903 section, and add <quote>127.0.0.1:0</quote> in the <quote>No Proxy for:</quote>
2909 <sect2 renderas="sect3" id="se-linux">
2910 <title>I get selinux error messages. How can I fix this?</title>
2912 Please report the problem to the creator of your selinux policies.
2915 The problem is that some selinux policy writers aren't familiar
2916 with the application they are trying to <quote>secure</quote> and
2917 thus create policies that make no sense.
2920 In <application>Privoxy's</application> case the problem usually
2921 is that the policy only allows outgoing connections for certain
2922 destination ports (e.g. 80 and 443). While this may cover the
2923 standard ports, websites occasionally use other ports as well.
2924 This isn't a security problem and therefore <application>Privoxy's</application>
2925 default configuration doesn't block these requests.
2928 If you really want to block these ports (and don't be able
2929 to load websites that don't use standard ports), you should
2930 configure Privoxy to block these ports as well, so it doesn't
2931 trigger the selinux warnings.
2936 <sect2 renderas="sect3" id="gentoo-ricers">
2937 <title>I compiled &my-app; with Gentoo's portage and it appears to be very slow. Why?</title>
2939 Probably you unintentionally compiled &my-app; without threading support
2940 in which case requests have to be serialized and only one can be served
2944 Check your <quote>USE</quote> flags and make sure they include
2945 <quote>threads</quote>. If they don't, add the flag and rebuild &my-app;.
2948 If you compiled &my-app; with threading support (on POSIX-based systems),
2949 the <quote>Conditional #defines</quote> section on <ulink
2950 url="http://config.privoxy.org/show-status">http://config.privoxy.org/show-status</ulink>
2951 will list <quote>FEATURE_PTHREAD</quote> as <quote>enabled</quote>.
2955 <sect2 renderas="sect3" id="tainted-sockets">
2956 <title>What are tainted sockets and how do I prevent them?</title>
2958 &my-app; marks sockets as tainted when it can't use them to
2959 serve additional requests.
2960 This does not necessarily mean that something went wrong and
2961 information about tainted sockets is only logged if connection
2962 debugging is enabled (debug 2).
2965 For example server sockets that were used for CONNECT requests
2966 (which are used to tunnel https:// requests) are considered tainted
2967 once the client closed its connection to &my-app;.
2968 Technically &my-app; could keep the connection to the server open,
2969 but the server would not accept requests that do not belong to the
2970 previous TLS/SSL session (and the client may even have terminated
2974 Server sockets are also marked tainted when a client requests a
2975 resource, but closes the connection before &my-app; has completely
2976 received (and forwarded) the resource to the client.
2977 In this case the server would (probably) accept additional requests,
2978 but &my-app; could not get the response without completely reading
2979 the leftovers from the previous response.
2982 These are just two examples, there are currently a bit more than
2983 25 scenarios in which a socket is considered tainted.
2986 While sockets can also be marked tainted as a result of a technical
2987 problem that may be worth fixing, the problem will be explicitly
2994 <!-- ~~~~~ New section ~~~~~ -->
2995 <sect1 id="contact"><title>Contacting the developers, Bug Reporting and Feature Requests</title>
2996 <!-- Include contacting.sgml -->
2998 <!-- end contacting -->
3001 <!-- ~~~~~ New section ~~~~~ -->
3002 <sect1 id="copyright"><title>Privoxy Copyright, License and History</title>
3004 <!-- Include copyright.sgml -->
3010 Portions of this document are <quote>borrowed</quote> from the original
3011 <application>Junkbuster</application> (tm) FAQ, and modified as
3012 appropriate for <application>Privoxy</application>.
3015 <!-- ~~~~~ New section ~~~~~ -->
3016 <sect2><title>License</title>
3017 <!-- Include copyright.sgml: -->
3019 <!-- end copyright -->
3021 <!-- ~ End section ~ -->
3023 <!-- ~~~~~ New section ~~~~~ -->
3024 <sect2><title>History</title>
3025 <!-- Include history.sgml -->
3031 <!-- ~ End section ~ -->
3034 <!-- ~~~~~ New section ~~~~~ -->
3036 <sect1 id="seealso"><title>See also</title>
3038 <!-- Include seealso.sgml -->
3048 This program is free software; you can redistribute it
3049 and/or modify it under the terms of the GNU General
3050 Public License as published by the Free Software
3051 Foundation; either version 2 of the License, or (at
3052 your option) any later version.
3054 This program is distributed in the hope that it will
3055 be useful, but WITHOUT ANY WARRANTY; without even the
3056 implied warranty of MERCHANTABILITY or FITNESS FOR A
3057 PARTICULAR PURPOSE. See the GNU General Public
3058 License for more details.
3060 The GNU General Public License should be included with
3061 this file. If not, you can view it at
3062 http://www.gnu.org/copyleft/gpl.html
3063 or write to the Free Software Foundation, Inc.,
3064 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA