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 buildsource SYSTEM "buildsource.sgml">
8 <!entity contacting SYSTEM "contacting.sgml">
9 <!entity history SYSTEM "history.sgml">
10 <!entity copyright SYSTEM "copyright.sgml">
11 <!entity license SYSTEM "license.sgml">
12 <!entity p-authors SYSTEM "p-authors.sgml">
13 <!entity config SYSTEM "p-config.sgml">
14 <!entity p-version SYSTEM "doc_version.tmp">
15 <!entity p-status SYSTEM "doc_status.tmp">
16 <!entity % p-authors-formal "INCLUDE"> <!-- include additional text, etc -->
17 <!entity % p-not-stable "IGNORE">
18 <!entity % p-stable "IGNORE">
19 <!entity % p-text "IGNORE"> <!-- define we are not a text only doc -->
20 <!entity % p-doc "INCLUDE"> <!-- and we are a formal doc -->
21 <!entity % p-readme "IGNORE">
22 <!entity % user-man "IGNORE">
23 <!entity % config-file "IGNORE">
24 <!entity % p-supp-userman "IGNORE"> <!-- Omit some from supported.sgml -->
25 <!entity my-copy "©"> <!-- kludge for docbook2man -->
26 <!entity % draft "IGNORE"> <!-- WIP stuff -->
29 File : $Source: /cvsroot/ijbswa/current/doc/source/user-manual.sgml,v $
32 This file belongs into
33 ijbswa.sourceforge.net:/home/groups/i/ij/ijbswa/htdocs/
35 $Id: user-manual.sgml,v 1.125 2002/06/03 00:28:17 hal9 Exp $
37 Copyright (C) 2001, 2002 Privoxy Developers <developers@privoxy.org>
40 ========================================================================
41 NOTE: Please read developer-manual/documentation.html before touching
42 anything in this, or other Privoxy documentation.
43 ========================================================================
50 <title>Privoxy User Manual</title>
54 <!-- Completely the wrong markup, but very little is allowed -->
55 <!-- in this part of an article. FIXME -->
56 <link linkend="copyright">Copyright</link> &my-copy; 2001, 2002 by
57 <ulink url="http://www.privoxy.org">Privoxy Developers</ulink>
61 <pubdate>$Id: user-manual.sgml,v 1.125 2002/06/03 00:28:17 hal9 Exp $</pubdate>
65 Note: the following should generate a separate page, and a live link to it,
66 all nicely done. But it doesn't for some mysterious reason. Please leave
67 commented unless it can be fixed proper. For the time being, the
68 copyright/license declarations will be in their own sgml.
75 <holder>Privoxy Developers</holder>
78 <legalnotice id="legalnotice">
80 text goes here ........
92 This is here to keep vim syntax file from breaking :/
93 If I knew enough to fix it, I would.
94 PLEASE DO NOT REMOVE! HB: hal@foobox.net
100 The <citetitle>User Manual</citetitle> gives users information on how to
101 install, configure and use <ulink
102 url="http://www.privoxy.org/"><application>Privoxy</application></ulink>.
105 <!-- Include privoxy.sgml boilerplate: -->
107 <!-- end privoxy.sgml -->
110 You can find the latest version of the <citetitle>User Manual</citetitle> at <ulink
111 url="http://www.privoxy.org/user-manual/">http://www.privoxy.org/user-manual/</ulink>.
112 Please see the <ulink url="contact.html">Contact section</ulink> on how to
113 contact the developers.
117 <!-- Feel free to send a note to the developers at <email>ijbswa-developers@lists.sourceforge.net</email>. -->
123 <!-- ~~~~~ New section ~~~~~ -->
124 <sect1 label="1" id="introduction"><title>Introduction</title>
126 This documentation is included with the current &p-status; version of
127 <application>Privoxy</application>, v.&p-version;<![%p-not-stable;[,
128 and is mostly complete at this point. The most up to date reference for the
129 time being is still the comments in the source files and in the individual
130 configuration files. Development of version 3.0 is currently nearing
131 completion, and includes many significant changes and enhancements over
132 earlier versions. The target release date for
133 stable v3.0 is <quote>soon</quote> ;-)]]>.
136 <!-- include only in non-stable versions -->
139 Since this is a &p-status; version, not all new features are well tested. This
140 documentation may be slightly out of sync as a result (especially with
141 CVS sources). And there <emphasis>may be</emphasis> bugs, though hopefully
146 <!-- ~~~~~ New section ~~~~~ -->
147 <sect2 id="features"><title>Features</title>
149 In addition to <application>Internet Junkbuster's</application> traditional
150 features of ad and banner blocking and cookie management,
151 <application>Privoxy</application> provides new features<![%p-not-stable;[,
152 some of them currently under development]]>:
154 <!-- Include newfeatures.sgml boilerplate here: -->
156 <!-- end boilerplate -->
161 <!-- ~ End section ~ -->
164 <!-- ~~~~~ New section ~~~~~ -->
165 <sect1 id="installation"><title>Installation</title>
168 <application>Privoxy</application> is available both in convenient pre-compiled
169 packages for a wide range of operating systems, and as raw source code.
170 For most users, we recommend using the packages, which can be downloaded from our
171 <ulink url="http://sourceforge.net/projects/ijbswa/">Privoxy Project
176 Note: If you have a previous <application>Junkbuster</application> or
177 <application>Privoxy</application> installation on your system, you
178 will need to remove it. On some platforms, this may be done for you as part
179 of their installation procedure. (See below for your platform). In any case
180 <emphasis>be sure to backup your old configuration if it is valuable to
181 you.</emphasis> See the <link linkend="upgradersnote">note to
182 upgraders</link> section below.
185 <!-- ~~~~~ New section ~~~~~ -->
186 <sect2 id="installation-packages"><title>Binary Packages</title>
188 How to install the binary packages depends on your operating system:
191 <!-- ~~~~~ New section ~~~~~ -->
192 <sect3 id="installation-pack-rpm"><title>Red Hat, SuSE and Conectiva RPMs</title>
195 RPMs can be installed with <literal>rpm -Uvh privoxy-&p-version;-1.rpm</literal>,
196 and will use <filename>/etc/privoxy</filename> for the location
197 of configuration files.
201 Note that on Red Hat, <application>Privoxy</application> will
202 <emphasis>not</emphasis> be automatically started on system boot. You will
203 need to enable that using <command>chkconfig</command>,
204 <command>ntsysv</command>, or similar methods. Note that SuSE will
205 automatically start Privoxy in the boot process.
209 If you have problems with failed dependencies, try rebuilding the SRC RPM:
210 <literal>rpm --rebuild privoxy-&p-version;-1.src.rpm</literal>. This
211 will use your locally installed libraries and RPM version.
215 Also note that if you have a <application>Junkbuster</application> RPM installed
216 on your system, you need to remove it first, because the packages conflict.
217 Otherwise, RPM will try to remove <application>Junkbuster</application>
218 automatically, before installing <application>Privoxy</application>.
222 <!-- ~~~~~ New section ~~~~~ -->
223 <sect3 id="installation-deb"><title>Debian</title>
225 DEBs can be installed with <literal>dpkg -i
226 privoxy_&p-version;-1.deb</literal>, and will use
227 <filename>/etc/privoxy</filename> for the location of configuration
232 <!-- ~~~~~ New section ~~~~~ -->
233 <sect3 id="installation-pack-win"><title>Windows</title>
236 Just double-click the installer, which will guide you through
237 the installation process. You will find the configuration files
238 in the same directory as you installed Privoxy in. We do not
239 use the registry of Windows.
243 <!-- ~~~~~ New section ~~~~~ -->
244 <sect3 id="installation-pack-bintgz"><title>Solaris, NetBSD, FreeBSD, HP-UX</title>
247 Create a new directory, <literal>cd</literal> to it, then unzip and
248 untar the archive. For the most part, you'll have to figure out where
249 things go. <!-- FIXME, more info needed? -->
253 <!-- ~~~~~ New section ~~~~~ -->
254 <sect3 id="installation-os2"><title>OS/2</title>
257 First, make sure that no previous installations of
258 <application>Junkbuster</application> and / or
259 <application>Privoxy</application> are left on your
260 system. Check that no <application>Junkbuster</application>
261 or <application>Privoxy</application> objects are in
267 Then, just double-click the WarpIN self-installing archive, which will
268 guide you through the installation process. A shadow of the
269 <application>Privoxy</application> executable will be placed in your
270 startup folder so it will start automatically whenever OS/2 starts.
274 The directory you choose to install <application>Privoxy</application>
275 into will contain all of the configuration files.
279 <!-- ~~~~~ New section ~~~~~ -->
280 <sect3 id="installation-mac"><title>Max OSX</title>
282 Unzip the downloaded package (you can either double-click on the file
283 in the finder, or on the desktop if you downloaded it there). Then,
284 double-click on the package installer icon and follow the installation
286 <application>Privoxy</application> will be installed in the subdirectory
287 <literal>/Applications/Privoxy.app</literal>.
288 <application>Privoxy</application> will set itself up to start
289 automatically on system bring-up via
290 <literal>/System/Library/StartupItems/Privoxy</literal>.
294 <!-- ~~~~~ New section ~~~~~ -->
295 <sect3 id="installation-amiga"><title>AmigaOS</title>
297 Copy and then unpack the <filename>lha</filename> archive to a suitable location.
298 All necessary files will be installed into <application>Privoxy</application>
299 directory, including all configuration and log files. To uninstall, just
300 remove this directory.
305 <!-- ~~~~~ New section ~~~~~ -->
306 <sect2 id="installation-source"><title>Building from Source</title>
309 The most convenient way to obtain the <application>Privoxy</application> sources
310 is to download the source tarball from our <ulink url="http://sf.net/projects/ijbswa/">project
315 If you like to live on the bleeding edge and are not afraid of using
316 possibly unstable development versions, you can check out the up-to-the-minute
317 version directly from <ulink url="http://sourceforge.net/cvs/?group_id=11118">the
318 CVS repository</ulink> or simply download <ulink
319 url="http://cvs.sourceforge.net/cvstarballs/ijbswa-cvsroot.tar.gz">the nightly CVS
323 <!-- include buildsource.sgml boilerplate: -->
325 <!-- end boilerplate -->
331 <!-- ~ End section ~ -->
333 <!-- ~~~~~ New section ~~~~~ -->
334 <sect1 id="upgradersnote">
335 <title>Note to Upgraders</title>
337 There are very significant changes from earlier
338 <application>Junkbuster</application> versions to the current
339 <application>Privoxy</application>. The number, names, syntax, and
340 purposes of configuration files have substantially changed.
341 <application>Junkbuster 2.0.x</application> configuration
342 files will not migrate, <application>Junkbuster 2.9.x</application>
343 and <application>Privoxy</application> configurations will need to be
344 ported. The functionalities of the old <filename>blockfile</filename>,
345 <filename>cookiefile</filename> and <filename>imagelist</filename>
346 are now combined into the <link linkend="actions-file"><quote>actions
347 files</quote></link>.
348 <filename>default.action</filename>, is the main actions file. Local
349 exceptions should best be put into <filename>user.action</filename>.
352 A <link linkend="filter-file"><quote>filter file</quote></link> (typically
353 <filename>default.filter</filename>) is new as of <application>Privoxy
354 2.9.x</application>, and provides some of the new sophistication (explained
355 below). <filename>config</filename> is much the same as before.
358 If upgrading from a 2.0.x version, you will have to use the new config
359 files, and possibly adapt any personal rules from your older files.
360 When porting personal rules over from the old <filename>blockfile</filename>
361 to the new actions files, please note that even the pattern syntax has
362 changed. If upgrading from 2.9.x development versions, it is still
363 recommended to use the new configuration files.
366 A quick list of things to be aware of before upgrading:
374 The default listening port is now 8118 due to a conflict with another
380 Some installers may remove earlier versions completely. Save any
381 important configuration files!
386 <application>Privoxy</application> is controllable with a web browser
387 at the special URL: <ulink
388 url="http://config.privoxy.org/">http://config.privoxy.org/</ulink>
389 (Shortcut: <ulink url="http://p.p/">http://p.p/</ulink>). Many
390 aspects of configuration can be done here, including temporarily disabling
391 <application>Privoxy</application>.
396 The primary configuration files for cookie management, ad and banner
397 blocking, and many other aspects of <application>Privoxy</application>
398 configuration are the <link linkend="actions-file">actions
399 files</link>. It is strongly recommended to become familiar with the new
400 actions concept below, before modifying these files. Locally defined rules
401 should go into <filename>user.action</filename>.
406 <!-- I think it is best to keep this somewhat vague, in case -->
407 <!-- the situation changes under our feet. -->
408 Some installers may not automatically start
409 <application>Privoxy</application> after installation.
417 <!-- ~~~~~ New section ~~~~~ -->
418 <sect1 id="quickstart"><title>Quickstart to Using <application>Privoxy</application></title>
424 If upgrading, from versions before 2.9.16, please back up any configuration
425 files. See the <link linkend="upgradersnote">Note to Upgraders</link> Section.
431 Install <application>Privoxy</application>. See the <link
432 linkend="installation">Installation Section</link> below for platform specific
439 Advanced users and those who want to offer <application>Privoxy</application>
440 service to more than just their local machine should check the <link
441 linkend="config">main config file</link>, especially the <link
442 linkend="access-control">security-relevant</link> options. These are
449 Start <application>Privoxy</application>, if the installation program has
450 not done this already (may vary according to platform). See the section
451 <link linkend="startup">Starting <application>Privoxy</application></link>.
457 Set your browser to use <application>Privoxy</application> as HTTP and
458 HTTPS proxy by setting the proxy configuration for address of
459 <literal>127.0.0.1</literal> and port <literal>8118</literal>.
460 (<application>Junkbuster</application> and earlier versions of
461 <application>Privoxy</application> used port 8000.) See the section <link
462 linkend="startup">Starting <application>Privoxy</application></link> below
463 for more details on this.
469 Flush your browser's disk and memory caches, to remove any cached ad images.
475 A default installation should provide a reasonable starting point for
476 most. There will undoubtedly be occasions where you will want to adjust the
477 configuration, but that can be dealt with as the need arises. Little
478 to no initial configuration is required in most cases.
481 See the <link linkend="configuration">Configuration section</link> for more
482 configuration options, and how to customize your installation.
483 <![%draft;[ You might also want to look at the <link
484 linkend="quickstart-ad-blocking">next section</link> for a quick
485 introduction to how <application>Privoxy</application> blocks ads and
492 If you experience ads that slipped through, innocent images that are
493 blocked, or otherwise feel the need to fine-tune
494 <application>Privoxy's</application> behaviour, take a look at the <link
495 linkend="actions-file">actions files</link>. As a quick start, you might
496 find the <link linkend="act-examples">richly commented examples</link>
497 helpful. You can also view and edit the actions files through the <ulink
498 url="http://config.privoxy.org">web-based user interface</ulink>. The
499 Appendix <quote><link linkend="actionsanat">Anatomy of an
500 Action</link></quote> has hints how to debug actions that
501 <quote>misbehave</quote>.
507 Please see the section <link linkend="contact">Contacting the
508 Developers</link> on how to report bugs or problems with websites or to get
515 Now enjoy surfing with enhanced comfort and privacy!
523 <!-- ~~~~~ New section ~~~~~ -->
525 <sect2 id="quickstart-ad-blocking">
526 <title>Quickstart to Ad Blocking</title>
528 NOTE: This section is deliberately redundant for those that don't
529 want to read the whole thing (which is getting lengthy).
532 Ad blocking is but one of <application>Privoxy's</application>
533 array of features. Many of these features are for the technically minded advanced
534 user. But, ad and banner blocking is surely common ground for everybody.
537 This section will provide a quick summary of ad blocking so
538 you can get up to speed quickly without having to read the more extensive
539 information provided below, though this is highly recommended.
542 First a bit of a warning ... blocking ads is much like blocking SPAM: the
543 more aggressive you are about it, the more likely you are to block
544 things that were not intended. So there is a trade off here. If you want
545 extreme ad free browsing, be prepared to deal with more
546 <quote>problem</quote> sites, and to spend more time adjusting the
547 configuration to solve these unintended consequences. In short, there is
548 not an easy way to eliminate <emphasis>all</emphasis> ads. Either take
549 the easy way and settle for <emphasis>most</emphasis> ads blocked with the
550 default configuration, or jump in and tweak it for your personal surfing
551 habits and preferences.
554 Secondly, a brief explanation of <application>Privoxy's </application>
555 <quote>actions</quote>. <quote>Actions</quote> in this context, are
556 the directives we use to tell <application>Privoxy</application> to perform
557 some task relating to HTTP transactions (i.e. web browsing). We tell
558 <application>Privoxy</application> to take some <quote>action</quote>. Each
559 action has a unique name and function. While there are many potential
560 <application>actions</application> in <application>Privoxy's</application>
561 arsenal, only a few are used for ad blocking. <link
562 linkend="actions">Actions</link>, and <link linkend="actions-file">action
563 configuration files</link>, are explained in depth below.
566 Actions are specified in <application>Privoxy's</application> configuration,
567 followed by one or more URLs to which the action should apply. URLs
568 can actually be URL type <link linkend="af-patterns">patterns</link> that use
569 wildcards so they can apply potentially to a range of similar URLs. The
570 actions, together with the URL patterns are called a section.
573 When you connect to a website, the full URL will either match one or more
574 of the sections as defined in <application>Privoxy's</application> configuration,
575 or not. If so, then <application>Privoxy</application> will perform the
576 respective actions. If not, then nothing special happens. Furthermore, web
577 pages may contain embedded, secondary URLs that your web browser will
578 use to load additional components of the page, as it parses the
579 original page's HTML content. An ad image for instance, is just an URL
580 embedded in the page somewhere. The image itself may be on the same server,
581 or a server somewhere else on the Internet. Complex web pages will have many
586 The actions we need to know about for ad blocking are: <literal><link
587 linkend="block">block</link></literal>, <literal><link
588 linkend="handle-as-image">handle-as-image</link></literal>, and
589 <literal><link linkend="set-image-blocker">set-image-blocker</link></literal>:
597 <literal><link linkend="block">block</link></literal> - this action stops
598 any contact between your browser and any URL patterns that match this
599 action's configuration. It can be used for blocking ads, but also anything
600 that is determined to be unwanted. By itself, it simply stops any
601 communication with the remote server and sends <application>Privoxy</application>'s
602 own built-in BLOCKED page instead to let you now what has happened.
608 <literal><link linkend="handle-as-image">handle-as-image</link></literal> -
609 tells <application>Privoxy</application> to treat this URL as an image.
610 <application>Privoxy</application>'s default configuration already does this
611 for all common image types (e.g. GIF), but there are many situations where this
612 is not so easy to determine. So we'll force it in these cases. This is particularly
613 important for ad blocking, since only if we know that it's an image of
614 some kind, can we replace it with an image of our choosing, instead of the
615 <application>Privoxy</application> BLOCKED page (which would only result in
616 a <quote>broken image</quote> icon). There are some limitations to this
617 though. For instance, you can't just brute-force an image substitution for
618 an entire HTML page in most situations.
625 linkend="set-image-blocker">set-image-blocker</link></literal> - tells
626 <application>Privoxy</application> what to display in place of an ad image that
627 has hit a block rule. For this to come into play, the URL must match a
628 <literal><link linkend="block">block</link></literal> action somewhere in the
629 configuration, <emphasis>and</emphasis>, it must also match an
630 <literal><link linkend="handle-as-image">handle-as-image</link></literal> action.
633 The configuration options on what to display instead of the ad are:
637 <emphasis>pattern</emphasis> - a checkerboard pattern, so that an ad
638 replacement is obvious. This is the default.
643 <emphasis>blank</emphasis> - A very small empty GIF image is displayed.
644 This is the so-called <quote>invisible</quote> configuration option.
649 <emphasis>http://<URL></emphasis> - A redirect to any image anywhere
650 of the user's choosing (advanced usage).
659 The quickest way to adjust any of these settings is with your browser through
660 the special <application>Privoxy</application> editor at <ulink
661 url="http://config.privoxy.org/show-status">http://config.privoxy.org/show-status</ulink>
662 (shortcut: <ulink url="http://p.p/">http://p.p/show-status</ulink>). This
663 is an internal page, and does not require Internet access. Select the
664 appropriate <quote>actions</quote> file, and click
665 <quote><guibutton>Edit</guibutton></quote>. It is best to put personal or
666 local preferences in <filename>user.action</filename> since this is not
667 meant to be overwritten during upgrades, and will over-ride the settings in
668 other files. Here you can insert new <quote>actions</quote>, and URLs for ad
669 blocking or other purposes, and make other adjustments to the configuration.
670 <application>Privoxy</application> will detect these changes automatically.
674 A quick and simple step by step example:
682 Right click on the ad image to be blocked, then select
683 <quote><guimenuitem>Copy Link Location</guimenuitem></quote> from the
691 url="http://config.privoxy.org/show-status">http://config.privoxy.org/show-status</ulink>
696 Find <filename>user.action</filename> in the top section, and click
697 on <quote><guibutton>Edit</guibutton></quote>:
700 <!-- image of editor and actions files selections -->
702 <figure pgwide="0" float="0"><title>Actions Files in Use</title>
705 <imagedata fileref="../images/files-in-use.jpg" format="jpg">
708 <phrase>[ Screenshot of Actions Files in Use ]</phrase>
717 You should have a section with only
718 <literal><link linkend="block">block</link></literal> listed under
719 <quote>Actions:</quote>.
720 If not, click a <quote><guibutton>Insert new section below</guibutton></quote>
721 button, and in the new section that just appeared, click the
722 <guibutton>Edit</guibutton> button right under the word <quote>Actions:</quote>.
723 This will bring up a list of all actions. Find
724 <literal><link linkend="block">block</link></literal> near the top, and click
725 in the <quote>Enabled</quote> column, then <quote><guibutton>Submit</guibutton></quote>
731 Now, in the <literal><link linkend="block">block</link></literal> actions section,
732 click the <quote><guibutton>Add</guibutton></quote> button, and paste the URL the
733 browser got from <quote><guimenuitem>Copy Link Location</guimenuitem></quote>.
734 Remove the <literal>http://</literal> at the beginning of the URL. Then, click
735 <quote><guibutton>Submit</guibutton></quote> (or
736 <quote><guibutton>OK</guibutton></quote> if in a pop-up window).
741 Now go back to the original page, and press <keycap>SHIFT-Reload</keycap>
742 (or flush all browser caches). The image should be gone now.
750 This is a very crude and simple example. There might be good reasons to use a
751 wildcard pattern match to include potentially similar images from the same
752 site. For a more extensive explanation of <quote>patterns</quote>, and
753 the entire actions concept, see <link linkend="actions-file">the Actions
758 For advanced users who want to hand edit their config files, you might want
759 to now go to the <link linkend="act-examples">Actions Files Tutorial</link>.
760 The ideas explained therein also apply to the web-based editor.
767 <!-- ~ End section ~ -->
770 <!-- ~~~~~ New section ~~~~~ -->
772 <title>Starting <application>Privoxy</application></title>
774 Before launching <application>Privoxy</application> for the first time, you
775 will want to configure your browser(s) to use
776 <application>Privoxy</application> as a HTTP and HTTPS proxy. The default is
777 127.0.0.1 (or localhost) for the proxy address, and port 8118 (earlier versions
778 used port 8000). This is the one configuration step that must be done!
781 <!-- image of Mozilla Proxy configuration -->
783 <figure pgwide="0" float="0"><title>Proxy Configuration (Mozilla)</title>
786 <imagedata fileref="../images/proxy_setup.jpg" format="jpg">
789 <phrase>[ Screenshot of Mozilla Proxy Configuration ]</phrase>
796 With <application>Netscape</application> (and
797 <application>Mozilla</application>), this can be set under:
801 <!-- Mix ascii and gui art, something for everybody -->
802 <!-- spacing on this is tricky -->
803 <guibutton>Edit</guibutton>
805 <guibutton>Preferences</guibutton>
807 <guibutton>Advanced</guibutton>
809 <guibutton>Proxies</guibutton>
811 <guibutton>HTTP Proxy</guibutton>
815 For <application>Internet Explorer</application>:
819 <!-- Mix ascii and gui art, something for everybody -->
820 <!-- spacing on this is tricky -->
821 <guibutton>Tools</guibutton>
823 <guibutton>Internet Properties</guibutton>
825 <guibutton>Connections</guibutton>
827 <guibutton>LAN Settings</guibutton>
831 Then, check <quote>Use Proxy</quote> and fill in the appropriate info
832 (Address: 127.0.0.1, Port: 8118). Include HTTPS (SSL), if you want HTTPS
837 After doing this, flush your browser's disk and memory caches to force a
838 re-reading of all pages and to get rid of any ads that may be cached. You
839 are now ready to start enjoying the benefits of using
840 <application>Privoxy</application>!
844 <application>Privoxy</application> is typically started by specifying the
845 main configuration file to be used on the command line. If no configuration
846 file is specified on the command line, <application>Privoxy</application>
847 will look for a file named <filename>config</filename> in the current
848 directory. Except on Win32 where it will try <filename>config.txt</filename>.
851 <sect2 id="start-redhat">
852 <title>Red Hat and Conectiva</title>
854 We use a script. Note that Red Hat does not start Privoxy upon booting per
855 default. It will use the file <filename>/etc/privoxy/config</filename> as
856 its main configuration file.
860 # /etc/rc.d/init.d/privoxy start
865 <sect2 id="start-debian">
866 <title>Debian</title>
868 We use a script. Note that Debian starts Privoxy upon booting per
869 default. It will use the file
870 <filename>/etc/privoxy/config</filename> as its main configuration
875 # /etc/init.d/privoxy start
880 <sect2 id="start-suse">
883 We use a script. It will use the file <filename>/etc/privoxy/config</filename>
884 as its main configuration file. Note that SuSE starts Privoxy upon booting
894 <sect2 id="start-windows">
895 <title>Windows</title>
897 Click on the Privoxy Icon to start Privoxy. If no configuration file is
898 specified on the command line, <application>Privoxy</application> will look
899 for a file named <filename>config.txt</filename>. Note that Windows will
900 automatically start Privoxy upon booting you PC.
904 <sect2 id="start-unices">
905 <title>Solaris, NetBSD, FreeBSD, HP-UX and others</title>
907 Example Unix startup command:
911 # /usr/sbin/privoxy /etc/privoxy/config
916 <sect2 id="start-os2">
919 During installation, <application>Privoxy</application> is configured to
920 start automatically when the system restarts. You can start it manually by
921 double-clicking on the <application>Privoxy</application> icon in the
922 <application>Privoxy</application> folder.
926 <sect2 id="start-macosx">
927 <title>MAX OSX</title>
929 During installation, <application>Privoxy</application> is configured to
930 start automatically when the system restarts. You can start it manually
931 through the Terminal with these commands:
935 cd /Applications/Privoxy.app
941 <sect2 id="start-amigaos">
942 <title>AmigaOS</title>
944 Start <application>Privoxy</application> (with RUN <>NIL:) in your
945 <filename>startnet</filename> script (AmiTCP), in
946 <filename>s:user-startup</filename> (RoadShow), as startup program in your
947 startup script (Genesis), or as startup action (Miami and MiamiDx).
948 <application>Privoxy</application> will automatically quit when you quit your
949 TCP/IP stack (just ignore the harmless warning your TCP/IP stack may display that
950 <application>Privoxy</application> is still running).
957 See the section <link linkend="cmdoptions">Command line options</link> for
961 must find a better place for this paragraph
964 The included default configuration files should give a reasonable starting
965 point. Most of the per site configuration is done in the
966 <ulink url="actions-file.html"><quote>actions</quote></ulink> files. These are
967 where various cookie actions are defined, ad and banner blocking, and other
968 aspects of <application>Privoxy</application> configuration. There are several
969 such files included, with varying levels of aggressiveness.
973 You will probably want to keep an eye out for sites for which you may prefer
974 persistent cookies, and add these to your actions configuration as needed. By
975 default, most of these will be accepted only during the current browser
976 session (aka <quote>session cookies</quote>), unless you add them to the
977 configuration. If you want the browser to handle this instead, you will need
978 to edit <filename>user.action</filename> (or through the web based interface)
979 and disable this feature. If you use more than one browser, it would make
980 more sense to let <application>Privoxy</application> handle this. In which
981 case, the browser(s) should be set to accept all cookies.
985 Another feature where you will probably want to define exceptions for trusted
986 sites is the popup-killing (through the <ulink
987 url="actions-file.html#KILL-POPUPS"><quote>+kill-popups</quote></ulink> and
989 url="actions-file.html#FILTER-POPUPS"><quote>+filter{popups}</quote></ulink>
990 actions), because your favorite shopping, banking, or leisure site may need
991 popups (explained below).
995 <application>Privoxy</application> is HTTP/1.1 compliant, but not all of
996 the optional 1.1 features are as yet supported. In the unlikely event that
997 you experience inexplicable problems with browsers that use HTTP/1.1 per default
998 (like <application>Mozilla</application> or recent versions of I.E.), you might
999 try to force HTTP/1.0 compatibility. For Mozilla, look under <literal>Edit ->
1000 Preferences -> Debug -> Networking</literal>.
1001 Alternatively, set the <quote>+downgrade-http-version</quote> config option in
1002 <filename>default.action</filename> which will downgrade your browser's HTTP
1003 requests from HTTP/1.1 to HTTP/1.0 before processing them.
1007 After running <application>Privoxy</application> for a while, you can
1008 start to fine tune the configuration to suit your personal, or site,
1009 preferences and requirements. There are many, many aspects that can
1010 be customized. <quote>Actions</quote>
1011 can be adjusted by pointing your browser to
1012 <ulink url="http://config.privoxy.org/">http://config.privoxy.org/</ulink>
1013 (shortcut: <ulink url="http://p.p/">http://p.p/</ulink>),
1014 and then follow the link to <quote>View & Change the Current Configuration</quote>.
1015 (This is an internal page and does not require Internet access.)
1019 In fact, various aspects of <application>Privoxy</application>
1020 configuration can be viewed from this page, including
1021 current configuration parameters, source code version numbers,
1022 the browser's request headers, and <quote>actions</quote> that apply
1023 to a given URL. In addition to the actions file
1024 editor mentioned above, <application>Privoxy</application> can also
1025 be turned <quote>on</quote> and <quote>off</quote> (toggled) from this page.
1029 If you encounter problems, try loading the page without
1030 <application>Privoxy</application>. If that helps, enter the URL where
1031 you have the problems into <ulink url="http://p.p/show-url-info">the browser
1032 based rule tracing utility</ulink>. See which rules apply and why, and
1033 then try turning them off for that site one after the other, until the problem
1034 is gone. When you have found the culprit, you might want to turn the rest on
1039 If the above paragraph sounds gibberish to you, you might want to <ulink
1040 url="actions-file.html#ACTIONSFILE">read more about the actions concept</ulink>
1041 or even dive deep into the <ulink url="appendix.html#ACTIONSANAT">Appendix
1046 If you can't get rid of the problem at all, think you've found a bug in
1047 Privoxy, want to propose a new feature or smarter rules, please see the
1048 section <ulink url="contact.html"><quote>Contacting the
1049 Developers</quote></ulink> below.
1054 <!-- ~~~~~ New section ~~~~~ -->
1055 <sect2 id="cmdoptions">
1056 <title>Command Line Options</title>
1058 <application>Privoxy</application> may be invoked with the following
1059 command-line options:
1067 <emphasis>--version</emphasis>
1070 Print version info and exit. Unix only.
1075 <emphasis>--help</emphasis>
1078 Print short usage info and exit. Unix only.
1083 <emphasis>--no-daemon</emphasis>
1086 Don't become a daemon, i.e. don't fork and become process group
1087 leader, and don't detach from controlling tty. Unix only.
1092 <emphasis>--pidfile FILE</emphasis>
1096 On startup, write the process ID to <emphasis>FILE</emphasis>. Delete the
1097 <emphasis>FILE</emphasis> on exit. Failure to create or delete the
1098 <emphasis>FILE</emphasis> is non-fatal. If no <emphasis>FILE</emphasis>
1099 option is given, no PID file will be used. Unix only.
1104 <emphasis>--user USER[.GROUP]</emphasis>
1108 After (optionally) writing the PID file, assume the user ID of
1109 <emphasis>USER</emphasis>, and if included the GID of GROUP. Exit if the
1110 privileges are not sufficient to do so. Unix only.
1115 <emphasis>configfile</emphasis>
1118 If no <emphasis>configfile</emphasis> is included on the command line,
1119 <application>Privoxy</application> will look for a file named
1120 <quote>config</quote> in the current directory (except on Win32
1121 where it will look for <quote>config.txt</quote> instead). Specify
1122 full path to avoid confusion. If no config file is found,
1123 <application>Privoxy</application> will fail to start.
1134 <!-- ~ End section ~ -->
1137 <!-- ~~~~~ New section ~~~~~ -->
1138 <sect1 id="configuration"><title><application>Privoxy</application> Configuration</title>
1140 All <application>Privoxy</application> configuration is stored
1141 in text files. These files can be edited with a text editor.
1142 Many important aspects of <application>Privoxy</application> can
1143 also be controlled easily with a web browser.
1147 <!-- ~~~~~ New section ~~~~~ -->
1150 <title>Controlling <application>Privoxy</application> with Your Web Browser</title>
1152 <application>Privoxy</application>'s user interface can be reached through the special
1153 URL <ulink url="http://config.privoxy.org/">http://config.privoxy.org/</ulink>
1154 (shortcut: <ulink url="http://p.p/">http://p.p/</ulink>),
1155 which is a built-in page and works without Internet access.
1156 You will see the following section:
1160 <!-- Needs to be put in a table and colorized -->
1163 <bridgehead renderas="sect2"> Privoxy Menu</bridgehead>
1167 ▪ <ulink url="http://config.privoxy.org/show-status">View & change the current configuration</ulink>
1170 ▪ <ulink url="http://config.privoxy.org/show-version">View the source code version numbers</ulink>
1173 ▪ <ulink url="http://config.privoxy.org/show-request">View the request headers.</ulink>
1176 ▪ <ulink url="http://config.privoxy.org/show-url-info">Look up which actions apply to a URL and why</ulink>
1179 ▪ <ulink url="http://config.privoxy.org/toggle">Toggle Privoxy on or off</ulink>
1187 This should be self-explanatory. Note the first item leads to an editor for the
1188 <link linkend="actions-file">actions files</link>, which is where the ad, banner,
1189 cookie, and URL blocking magic is configured as well as other advanced features of
1190 <application>Privoxy</application>. This is an easy way to adjust various
1191 aspects of <application>Privoxy</application> configuration. The actions
1192 file, and other configuration files, are explained in detail below.
1196 <quote>Toggle Privoxy On or Off</quote> is handy for sites that might
1197 have problems with your current actions and filters. You can in fact use
1198 it as a test to see whether it is <application>Privoxy</application>
1199 causing the problem or not. <application>Privoxy</application> continues
1200 to run as a proxy in this case, but all manipulation is disabled, i.e.
1201 <application>Privoxy</application> acts like a normal forwarding proxy. There
1202 is even a toggle <link linkend="bookmarklets">Bookmarklet</link> offered, so
1203 that you can toggle <application>Privoxy</application> with one click from
1209 <!-- ~ End section ~ -->
1214 <!-- ~~~~~ New section ~~~~~ -->
1216 <sect2 id="confoverview">
1217 <title>Configuration Files Overview</title>
1219 For Unix, *BSD and Linux, all configuration files are located in
1220 <filename>/etc/privoxy/</filename> by default. For MS Windows, OS/2, and
1221 AmigaOS these are all in the same directory as the
1222 <application>Privoxy</application> executable. <![%p-not-stable;[ The name
1223 and number of configuration files has changed from previous versions, and is
1224 subject to change as development progresses.]]>
1228 The installed defaults provide a reasonable starting point, though
1229 some settings may be aggressive by some standards. For the time being, the
1230 principle configuration files are:
1238 The <link linkend="config">main configuration file</link> is named <filename>config</filename>
1239 on Linux, Unix, BSD, OS/2, and AmigaOS and <filename>config.txt</filename>
1240 on Windows. This is a required file.
1246 <filename>default.action</filename> (the main <link linkend="actions-file">actions file</link>)
1247 is used to define which <quote>actions</quote> relating to banner-blocking, images, pop-ups,
1248 content modification, cookie handling etc should be applied by default. It also defines many
1249 exceptions (both positive and negative) from this default set of actions that enable
1250 <application>Privoxy</application> to selectively eliminate the junk, and only the junk, on
1251 as many websites as possible.
1254 Multiple actions files may be defined in <filename>config</filename>. These
1255 are processed in the order they are defined. Local customizations and locally
1256 preferred exceptions to the default policies as defined in
1257 <filename>default.action</filename> (which you will most probably want
1258 to define sooner or later) are probably best applied in
1259 <filename>user.action</filename>, where you can preserve them across
1260 upgrades. <filename>standard.action</filename> is for
1261 <application>Privoxy's</application> internal use.
1264 There is also a web based editor that can be accessed from
1266 url="http://config.privoxy.org/show-status">http://config.privoxy.org/show-status</ulink>
1268 url="http://p.p/show-status">http://p.p/show-status</ulink>) for the
1269 various actions files.
1275 <filename>default.filter</filename> (the <link linkend="filter-file">filter
1276 file</link>) can be used to re-write the raw page content, including
1277 viewable text as well as embedded HTML and JavaScript, and whatever else
1278 lurks on any given web page. The filtering jobs are only pre-defined here;
1279 whether to apply them or not is up to the actions files.
1287 All files use the <quote><literal>#</literal></quote> character to denote a
1288 comment (the rest of the line will be ignored) and understand line continuation
1289 through placing a backslash ("<literal>\</literal>") as the very last character
1290 in a line. If the <literal>#</literal> is preceded by a backslash, it looses
1291 its special function. Placing a <literal>#</literal> in front of an otherwise
1292 valid configuration line to prevent it from being interpreted is called "commenting
1297 The actions files and <filename>default.filter</filename>
1298 can use Perl style <link linkend="regex">regular expressions</link> for
1299 maximum flexibility.
1303 After making any changes, there is no need to restart
1304 <application>Privoxy</application> in order for the changes to take
1305 effect. <application>Privoxy</application> detects such changes
1306 automatically. Note, however, that it may take one or two additional
1307 requests for the change to take effect. When changing the listening address
1308 of <application>Privoxy</application>, these <quote>wake up</quote> requests
1309 must obviously be sent to the <emphasis>old</emphasis> listening address.
1314 While under development, the configuration content is subject to change.
1315 The below documentation may not be accurate by the time you read this.
1316 Also, what constitutes a <quote>default</quote> setting, may change, so
1317 please check all your configuration files on important issues.
1323 <!-- ~ End section ~ -->
1326 <!-- ~~~~~~~~ New section Header ~~~~~~~~~ -->
1328 <!-- **************************************************** -->
1329 <!-- Include config.sgml here -->
1330 <!-- This is where the entire config file is detailed. -->
1332 <!-- end include -->
1335 <!-- ~ End section ~ -->
1339 <!-- ~~~~~~~~ New section Header ~~~~~~~~~ -->
1341 <sect1 id="actions-file"><title>Actions Files</title>
1344 The actions files are used to define what actions
1345 <application>Privoxy</application> takes for which URLs, and thus determine
1346 how ad images, cookies and various other aspects of HTTP content and
1347 transactions are handled, and on which sites (or even parts thereof). There
1348 are three such files included with <application>Privoxy</application> (as of
1349 version 2.9.15), with differing purposes:
1356 <filename>default.action</filename> - is the primary action file
1357 that sets the initial values for all actions. It is intended to
1358 provide a base level of functionality for
1359 <application>Privoxy's</application> array of features. So it is
1360 a set of broad rules that should work reasonably well for users everywhere.
1361 This is the file that the developers are keeping updated, and making
1367 <filename>user.action</filename> - is intended to be for local site
1368 preferences and exceptions. As an example, if your ISP or your bank
1369 has specific requirements, and need special handling, this kind of
1370 thing should go here. This file will not be upgraded.
1375 <filename>standard.action</filename> - is used by the web based editor,
1376 to set various pre-defined sets of rules for the default actions section
1377 in <filename>default.action</filename>. These have increasing levels of
1378 aggressiveness <emphasis>and have no influence on your browsing unless
1379 you select them explicitly in the editor</emphasis>. It is not recommend
1387 The list of actions files to be used are defined in the main configuration
1388 file, and are processed in the order they are defined. The content of these
1389 can all be viewed and edited from <ulink
1390 url="http://config.privoxy.org/show-status">http://config.privoxy.org/show-status</ulink>.
1394 An actions file typically has multiple sections. If you want to use
1395 <quote>aliases</quote> in an actions file, you have to place the (optional)
1396 <link linkend="aliases">alias section</link> at the top of that file.
1397 Then comes the default set of rules which will apply universally to all
1398 sites and pages (be <emphasis>very careful</emphasis> with using such a
1399 universal set in <filename>user.action</filename> or any other actions file after
1400 <filename>default.action</filename>, because it will override the result
1401 from consulting any previous file). And then below that,
1402 exceptions to the defined universal policies. You can regard
1403 <filename>user.action</filename> as an appendix to <filename>default.action</filename>,
1404 with the advantage that is a separate file, which makes preserving your
1405 personal settings across <application>Privoxy</application> upgrades easier.
1409 Actions can be used to block anything you want, including ads, banners, or
1410 just some obnoxious URL that you would rather not see. Cookies can be accepted
1411 or rejected, or accepted only during the current browser session (i.e. not
1412 written to disk), content can be modified, JavaScripts tamed, user-tracking
1413 fooled, and much more. See below for a <link linkend="actions">complete list
1417 <!-- ~~~~~ New section ~~~~~ -->
1419 <title>Finding the Right Mix</title>
1421 Note that some <link linkend="actions">actions</link>, like cookie suppression
1422 or script disabling, may render some sites unusable that rely on these
1423 techniques to work properly. Finding the right mix of actions is not always easy and
1424 certainly a matter of personal taste. In general, it can be said that the more
1425 <quote>aggressive</quote> your default settings (in the top section of the
1426 actions file) are, the more exceptions for <quote>trusted</quote> sites you
1427 will have to make later. If, for example, you want to kill popup windows per
1428 default, you'll have to make exceptions from that rule for sites that you
1429 regularly use and that require popups for actually useful content, like maybe
1430 your bank, favorite shop, or newspaper.
1434 We have tried to provide you with reasonable rules to start from in the
1435 distribution actions files. But there is no general rule of thumb on these
1436 things. There just are too many variables, and sites are constantly changing.
1437 Sooner or later you will want to change the rules (and read this chapter again :).
1441 <!-- ~~~~~ New section ~~~~~ -->
1443 <title>How to Edit</title>
1445 The easiest way to edit the actions files is with a browser by
1446 using our browser-based editor, which can be reached from <ulink
1447 url="http://config.privoxy.org/show-status">http://config.privoxy.org/show-status</ulink>.
1448 The editor allows both fine-grained control over every single feature on a
1449 per-URL basis, and easy choosing from wholesale sets of defaults like
1450 <quote>Cautious</quote>, <quote>Medium</quote> or <quote>Advanced</quote>.
1454 If you prefer plain text editing to GUIs, you can of course also directly edit the
1455 the actions files. Look at <filename>default.action</filename> which is richly
1461 <sect2 id="actions-apply">
1462 <title>How Actions are Applied to URLs</title>
1464 Actions files are divided into sections. There are special sections,
1465 like the <quote><link linkend="aliases">alias</link></quote> sections which will
1466 be discussed later. For now let's concentrate on regular sections: They have a
1467 heading line (often split up to multiple lines for readability) which consist
1468 of a list of actions, separated by whitespace and enclosed in curly braces.
1469 Below that, there is a list of URL patterns, each on a separate line.
1473 To determine which actions apply to a request, the URL of the request is
1474 compared to all patterns in each action file file. Every time it matches, the list of
1475 applicable actions for the URL is incrementally updated, using the heading
1476 of the section in which the pattern is located. If multiple matches for
1477 the same URL set the same action differently, the last match wins. If not,
1478 the effects are aggregated. E.g. a URL might match a regular section with
1479 a heading line of <literal>{
1480 +<ulink url="actions-file.html#HANDLE-AS-IMAGE">handle-as-image</ulink> }</literal>,
1481 then later another one with just <literal>{
1482 +<ulink url="actions-file.html#BLOCK">block</ulink> }</literal>, resulting
1483 in <emphasis>both</emphasis> actions to apply.
1487 You can trace this process for any given URL by visiting <ulink
1488 url="http://config.privoxy.org/show-url-info">http://config.privoxy.org/show-url-info</ulink>.
1492 More detail on this is provided in the Appendix, <link linkend="ACTIONSANAT">
1493 Anatomy of an Action</link>.
1497 <!-- ~~~~~ New section ~~~~~ -->
1498 <sect2 id="af-patterns">
1499 <title>Patterns</title>
1501 Generally, a pattern has the form <literal><domain>/<path></literal>,
1502 where both the <literal><domain></literal> and <literal><path></literal>
1503 are optional. (This is why the pattern <literal>/</literal> matches all URLs).
1508 <term><literal>www.example.com/</literal></term>
1511 is a domain-only pattern and will match any request to <literal>www.example.com</literal>,
1512 regardless of which document on that server is requested.
1517 <term><literal>www.example.com</literal></term>
1520 means exactly the same. For domain-only patterns, the trailing <literal>/</literal> may
1526 <term><literal>www.example.com/index.html</literal></term>
1529 matches only the single document <literal>/index.html</literal>
1530 on <literal>www.example.com</literal>.
1535 <term><literal>/index.html</literal></term>
1538 matches the document <literal>/index.html</literal>, regardless of the domain,
1539 i.e. on <emphasis>any</emphasis> web server.
1544 <term><literal>index.html</literal></term>
1547 matches nothing, since it would be interpreted as a domain name and
1548 there is no top-level domain called <literal>.html</literal>.
1555 <!-- ~~~~~ New section ~~~~~ -->
1556 <sect3><title>The Domain Pattern</title>
1559 The matching of the domain part offers some flexible options: if the
1560 domain starts or ends with a dot, it becomes unanchored at that end.
1566 <term><literal>.example.com</literal></term>
1569 matches any domain that <emphasis>ENDS</emphasis> in
1570 <literal>.example.com</literal>
1575 <term><literal>www.</literal></term>
1578 matches any domain that <emphasis>STARTS</emphasis> with
1579 <literal>www.</literal>
1584 <term><literal>.example.</literal></term>
1587 matches any domain that <emphasis>CONTAINS</emphasis> <literal>.example.</literal>
1588 (Correctly speaking: It matches any FQDN that contains <literal>example</literal> as a domain.)
1595 Additionally, there are wild-cards that you can use in the domain names
1596 themselves. They work pretty similar to shell wild-cards: <quote>*</quote>
1597 stands for zero or more arbitrary characters, <quote>?</quote> stands for
1598 any single character, you can define character classes in square
1599 brackets and all of that can be freely mixed:
1604 <term><literal>ad*.example.com</literal></term>
1607 matches <quote>adserver.example.com</quote>,
1608 <quote>ads.example.com</quote>, etc but not <quote>sfads.example.com</quote>
1613 <term><literal>*ad*.example.com</literal></term>
1616 matches all of the above, and then some.
1621 <term><literal>.?pix.com</literal></term>
1624 matches <literal>www.ipix.com</literal>,
1625 <literal>pictures.epix.com</literal>, <literal>a.b.c.d.e.upix.com</literal> etc.
1630 <term><literal>www[1-9a-ez].example.c*</literal></term>
1633 matches <literal>www1.example.com</literal>,
1634 <literal>www4.example.cc</literal>, <literal>wwwd.example.cy</literal>,
1635 <literal>wwwz.example.com</literal> etc., but <emphasis>not</emphasis>
1636 <literal>wwww.example.com</literal>.
1644 <!-- ~ End section ~ -->
1647 <!-- ~~~~~ New section ~~~~~ -->
1648 <sect3><title>The Path Pattern</title>
1651 <application>Privoxy</application> uses Perl compatible regular expressions
1652 (through the <ulink url="http://www.pcre.org/">PCRE</ulink> library) for
1657 There is an <link linkend="regex">Appendix</link> with a brief quick-start into regular
1658 expressions, and full (very technical) documentation on PCRE regex syntax is available on-line
1659 at <ulink url="http://www.pcre.org/man.txt">http://www.pcre.org/man.txt</ulink>.
1660 You might also find the Perl man page on regular expressions (<literal>man perlre</literal>)
1661 useful, which is available on-line at <ulink
1662 url="http://www.perldoc.com/perl5.6/pod/perlre.html">http://www.perldoc.com/perl5.6/pod/perlre.html</ulink>.
1666 Note that the path pattern is automatically left-anchored at the <quote>/</quote>,
1667 i.e. it matches as if it would start with a <quote>^</quote> (regular expression speak
1668 for the beginning of a line).
1672 Please also note that matching in the path is <emphasis>CASE INSENSITIVE</emphasis>
1673 by default, but you can switch to case sensitive at any point in the pattern by using the
1674 <quote>(?-i)</quote> switch: <literal>www.example.com/(?-i)PaTtErN.*</literal> will match
1675 only documents whose path starts with <literal>PaTtErN</literal> in
1676 <emphasis>exactly</emphasis> this capitalization.
1682 <!-- ~ End section ~ -->
1685 <!-- ~~~~~ New section ~~~~~ -->
1687 <sect2 id="actions">
1688 <title>Actions</title>
1690 All actions are disabled by default, until they are explicitly enabled
1691 somewhere in an actions file. Actions are turned on if preceded with a
1692 <quote>+</quote>, and turned off if preceded with a <quote>-</quote>. So a
1693 <literal>+action</literal> means <quote>do that action</quote>, e.g.
1694 <literal>+block</literal> means <quote>please block URLs that match the
1695 following patterns</quote>, and <literal>-block</literal> means <quote>don't
1696 block URLs that match the following patterns, even if <literal>+block</literal>
1697 previously applied.</quote>
1702 Again, actions are invoked by placing them on a line, enclosed in curly braces and
1703 separated by whitespace, like in
1704 <literal>{+some-action -some-other-action{some-parameter}}</literal>,
1705 followed by a list of URL patterns, one per line, to which they apply.
1706 Together, the actions line and the following pattern lines make up a section
1707 of the actions file.
1711 There are three classes of actions:
1718 Boolean, i.e the action can only be <quote>enabled</quote> or
1719 <quote>disabled</quote>. Syntax:
1723 +<replaceable class="function">name</replaceable> # enable action <replaceable class="parameter">name</replaceable>
1724 -<replaceable class="function">name</replaceable> # disable action <replaceable class="parameter">name</replaceable></screen>
1727 Example: <literal>+block</literal>
1734 Parameterized, where some value is required in order to enable this type of action.
1739 +<replaceable class="function">name</replaceable>{<replaceable class="parameter">param</replaceable>} # enable action and set parameter to <replaceable class="parameter">param</replaceable>,
1740 # overwriting parameter from previous match if necessary
1741 -<replaceable class="function">name</replaceable> # disable action. The parameter can be omitted</screen>
1744 Note that if the URL matches multiple positive forms of a parameterized action,
1745 the last match wins, i.e. the params from earlier matches are simply ignored.
1748 Example: <literal>+hide-user-agent{ Mozilla 1.0 }</literal>
1754 Multi-value. These look exactly like parameterized actions,
1755 but they behave differently: If the action applies multiple times to the
1756 same URL, but with different parameters, <emphasis>all</emphasis> the parameters
1757 from <emphasis>all</emphasis> matches are remembered. This is used for actions
1758 that can be executed for the same request repeatedly, like adding multiple
1759 headers, or filtering through multiple filters. Syntax:
1763 +<replaceable class="function">name</replaceable>{<replaceable class="parameter">param</replaceable>} # enable action and add <replaceable class="parameter">param</replaceable> to the list of parameters
1764 -<replaceable class="function">name</replaceable>{<replaceable class="parameter">param</replaceable>} # remove the parameter <replaceable class="parameter">param</replaceable> from the list of parameters
1765 # If it was the last one left, disable the action.
1766 <replaceable class="parameter">-name</replaceable> # disable this action completely and remove all parameters from the list</screen>
1769 Examples: <literal>+add-header{X-Fun-Header: Some text}</literal> and
1770 <literal>+filter{html-annoyances}</literal>
1778 If nothing is specified in any actions file, no <quote>actions</quote> are
1779 taken. So in this case <application>Privoxy</application> would just be a
1780 normal, non-blocking, non-anonymizing proxy. You must specifically enable the
1781 privacy and blocking features you need (although the provided default actions
1782 files will give a good starting point).
1786 Later defined actions always over-ride earlier ones. So exceptions
1787 to any rules you make, should come in the latter part of the file (or
1788 in a file that is processed later when using multiple actions files). For
1789 multi-valued actions, the actions are applied in the order they are specified.
1790 Actions files are processed in the order they are defined in
1791 <filename>config</filename> (the default installation has three actions
1792 files). It also quite possible for any given URL pattern to match more than
1793 one pattern and thus more than one set of actions!
1796 <!-- start actions listing -->
1798 The list of valid <application>Privoxy</application> actions are:
1802 <!-- ********************************************************** -->
1803 <!-- Please note the below defined actions use id's that are -->
1804 <!-- probably linked from other places, so please don't change. -->
1806 <!-- ********************************************************** -->
1809 <!-- ~~~~~ New section ~~~~~ -->
1811 <sect3 renderas="sect4" id="add-header">
1812 <title>add-header</title>
1816 <term>Typical use:</term>
1818 <para>Confuse log analysis, custom applications</para>
1823 <term>Effect:</term>
1826 Sends a user defined HTTP header to the web server.
1833 <!-- boolean, parameterized, Multi-value -->
1835 <para>Multi-value.</para>
1840 <term>Parameter:</term>
1843 Any string value is possible. Validity of the defined HTTP headers is not checked.
1844 It is recommended that you use the <quote><literal>X-</literal></quote> prefix
1854 This action may be specified multiple times, in order to define multiple
1855 headers. This is rarely needed for the typical user. If you don't know what
1856 <quote>HTTP headers</quote> are, you definitely don't need to worry about this
1863 <term>Example usage:</term>
1866 <screen>+add-header{X-User-Tracking: sucks}</screen>
1874 <!-- ~~~~~ New section ~~~~~ -->
1875 <sect3 renderas="sect4" id="block">
1876 <title>block</title>
1880 <term>Typical use:</term>
1882 <para>Block ads or other obnoxious content</para>
1887 <term>Effect:</term>
1890 Requests for URLs to which this action applies are blocked, i.e. the requests are not
1891 forwarded to the remote server, but answered locally with a substitute page or image,
1892 as determined by the <literal><link linkend="handle-as-image">handle-as-image</link></literal>
1893 and <literal><link linkend="set-image-blocker">set-image-blocker</link></literal> actions.
1900 <!-- boolean, parameterized, Multi-value -->
1902 <para>Boolean.</para>
1907 <term>Parameter:</term>
1917 <application>Privoxy</application> sends a special <quote>BLOCKED</quote> page
1918 for requests to blocked pages. This page contains links to find out why the request
1919 was blocked, and a click-through to the blocked content (the latter only if compiled with the
1920 force feature enabled). The <quote>BLOCKED</quote> page adapts to the available
1921 screen space -- it displays full-blown if space allows, or miniaturized and text-only
1922 if loaded into a small frame or window. If you are using <application>Privoxy</application>
1923 right now, you can take a look at the
1924 <ulink url="http://ads.bannerserver.example.com/nasty-ads/sponsor.html"><quote>BLOCKED</quote>
1928 A very important exception occurs if <emphasis>both</emphasis>
1929 <literal>block</literal> and <literal><link linkend="handle-as-image">handle-as-image</link></literal>,
1930 apply to the same request: it will then be replaced by an image. If
1931 <literal><link linkend="set-image-blocker">set-image-blocker</link></literal>
1932 (see below) also applies, the type of image will be determined by its parameter,
1933 if not, the standard checkerboard pattern is sent.
1936 It is important to understand this process, in order
1937 to understand how <application>Privoxy</application> deals with
1938 ads and other unwanted content.
1941 The <literal><link linkend="filter">filter</link></literal>
1942 action can perform a very similar task, by <quote>blocking</quote>
1943 banner images and other content through rewriting the relevant URLs in the
1944 document's HTML source, so they don't get requested in the first place.
1945 Note that this is a totally different technique, and it's easy to confuse the two.
1951 <term>Example usage (section):</term>
1954 <screen>{+block} # Block and replace with "blocked" page
1955 .nasty-stuff.example.com
1957 {+block +handle-as-image} # Block and replace with image
1968 <!-- ~~~~~ New section ~~~~~ -->
1969 <sect3 renderas="sect4" id="crunch-incoming-cookies">
1970 <title>crunch-incoming-cookies</title>
1974 <term>Typical use:</term>
1977 Prevent the web server from setting any cookies on your system
1983 <term>Effect:</term>
1986 Deletes any <quote>Set-Cookie:</quote> HTTP headers from server replies.
1993 <!-- Boolean, Parameterized, Multi-value -->
1995 <para>Boolean.</para>
2000 <term>Parameter:</term>
2012 This action is only concerned with <emphasis>incoming</emphasis> cookies. For
2013 <emphasis>outgoing</emphasis> cookies, use
2014 <literal><link linkend="crunch-outgoing-cookies">crunch-outgoing-cookies</link></literal>.
2015 Use <emphasis>both</emphasis> to disable cookies completely.
2018 It makes <emphasis>no sense at all</emphasis> to use this action in conjunction
2019 with the <literal><link linkend="session-cookies-only">session-cookies-only</link></literal> action,
2020 since it would prevent the session cookies from being set.
2026 <term>Example usage:</term>
2029 <screen>+crunch-incoming-cookies</screen>
2037 <!-- ~~~~~ New section ~~~~~ -->
2038 <sect3 renderas="sect4" id="crunch-outgoing-cookies">
2039 <title>crunch-outgoing-cookies</title>
2043 <term>Typical use:</term>
2046 Prevent the web server from reading any cookies from your system
2052 <term>Effect:</term>
2055 Deletes any <quote>Cookie:</quote> HTTP headers from client requests.
2062 <!-- Boolean, Parameterized, Multi-value -->
2064 <para>Boolean.</para>
2069 <term>Parameter:</term>
2081 This action is only concerned with <emphasis>outgoing</emphasis> cookies. For
2082 <emphasis>incoming</emphasis> cookies, use
2083 <literal><link linkend="crunch-incoming-cookies">crunch-incoming-cookies</link></literal>.
2084 Use <emphasis>both</emphasis> to disable cookies completely.
2087 It makes <emphasis>no sense at all</emphasis> to use this action in conjunction
2088 with the <literal><link linkend="session-cookies-only">session-cookies-only</link></literal> action,
2089 since it would prevent the session cookies from being read.
2095 <term>Example usage:</term>
2098 <screen>+crunch-outgoing-cookies</screen>
2107 <!-- ~~~~~ New section ~~~~~ -->
2108 <sect3 renderas="sect4" id="deanimate-gifs">
2109 <title>deanimate-gifs</title>
2113 <term>Typical use:</term>
2115 <para>Stop those annoying, distracting animated GIF images.</para>
2120 <term>Effect:</term>
2123 De-animate GIF animations, i.e. reduce them to their first or last image.
2130 <!-- boolean, parameterized, Multi-value -->
2132 <para>Parameterized.</para>
2137 <term>Parameter:</term>
2140 <quote>last</quote> or <quote>first</quote>
2149 This will also shrink the images considerably (in bytes, not pixels!). If
2150 the option <quote>first</quote> is given, the first frame of the animation
2151 is used as the replacement. If <quote>last</quote> is given, the last
2152 frame of the animation is used instead, which probably makes more sense for
2153 most banner animations, but also has the risk of not showing the entire
2154 last frame (if it is only a delta to an earlier frame).
2157 You can safely use this action with patterns that will also match non-GIF
2158 objects, because no attempt will be made at anything that doesn't look like
2165 <term>Example usage:</term>
2168 <screen>+deanimate-gifs{last}</screen>
2175 <!-- ~~~~~ New section ~~~~~ -->
2176 <sect3 renderas="sect4" id="downgrade-http-version">
2177 <title>downgrade-http-version</title>
2181 <term>Typical use:</term>
2183 <para>Work around (very rare) problems with HTTP/1.1</para>
2188 <term>Effect:</term>
2191 Downgrades HTTP/1.1 client requests and server replies to HTTP/1.0.
2198 <!-- boolean, parameterized, Multi-value -->
2200 <para>Boolean.</para>
2205 <term>Parameter:</term>
2217 This is a left-over from the time when <application>Privoxy</application>
2218 didn't support important HTTP/1.1 features well. It is left here for the
2219 unlikely case that you experience HTTP/1.1 related problems with some server
2220 out there. Not all (optional) HTTP/1.1 features are supported yet, so there
2221 is a chance you might need this action.
2227 <term>Example usage (section):</term>
2230 <screen>{+downgrade-http-version}
2231 problem-host.example.com</screen>
2239 <!-- ~~~~~ New section ~~~~~ -->
2240 <sect3 renderas="sect4" id="fast-redirects">
2241 <title>fast-redirects</title>
2245 <term>Typical use:</term>
2247 <para>Fool some click-tracking scripts and speed up indirect links</para>
2252 <term>Effect:</term>
2255 Cut off all but the last valid URL from requests.
2262 <!-- boolean, parameterized, Multi-value -->
2264 <para>Boolean.</para>
2269 <term>Parameter:</term>
2281 Many sites, like yahoo.com, don't just link to other sites. Instead, they
2282 will link to some script on their own servers, giving the destination as a
2283 parameter, which will then redirect you to the final target. URLs
2284 resulting from this scheme typically look like:
2285 <emphasis>http://some.place/click-tracker.cgi?target=http://some.where.else</emphasis>.
2288 Sometimes, there are even multiple consecutive redirects encoded in the
2289 URL. These redirections via scripts make your web browsing more traceable,
2290 since the server from which you follow such a link can see where you go
2291 to. Apart from that, valuable bandwidth and time is wasted, while your
2292 browser ask the server for one redirect after the other. Plus, it feeds
2296 This feature is currently not very smart and is scheduled for improvement.
2297 It is likely to break some sites. You should expect to need possibly
2298 many exceptions to this action, if it is enabled by default in
2299 <filename>default.action</filename>. Some sites just don't work without
2306 <term>Example usage:</term>
2309 <screen>{+fast-redirects}</screen>
2318 <!-- ~~~~~ New section ~~~~~ -->
2319 <sect3 renderas="sect4" id="filter">
2320 <title>filter</title>
2324 <term>Typical use:</term>
2326 <para>Get rid of HTML and JavaScript annoyances, banner advertisements (by size), do fun text replacements, etc.</para>
2331 <term>Effect:</term>
2334 Text documents, including HTML and JavaScript, to which this action applies, are filtered on-the-fly
2335 through the specified regular expression based substitutions.
2342 <!-- boolean, parameterized, Multi-value -->
2344 <para>Parameterized.</para>
2349 <term>Parameter:</term>
2352 The name of a filter, as defined in the <link linkend="filter-file">filter file</link>
2353 (typically <filename>default.filter</filename>, set by the
2354 <literal><link linkend="filterfile">filterfile</link></literal>
2355 option in the <link linkend="config">config file</link>)
2364 For your convenience, there are a bunch of pre-defined filters available
2365 in the distribution filter file that you can use. See the example below for
2369 This is potentially a very powerful feature! But <quote>rolling your own</quote>
2370 filters requires a knowledge of regular expressions and HTML.
2373 Filtering requires buffering the page content, which may appear to
2374 slow down page rendering since nothing is displayed until all content has
2375 passed the filters. (It does not really take longer, but seems that way
2376 since the page is not incrementally displayed.) This effect will be more
2377 noticeable on slower connections.
2380 At this time, <application>Privoxy</application> cannot (yet!) uncompress compressed
2381 documents. If you want filtering to work on all documents, even those that
2382 would normally be sent compressed, use the
2383 <literal><link linkend="prevent-compression">prevent-compression</link></literal>
2384 action in conjunction with <literal>filter</literal>.
2387 Filtering can achieve some of the effects as the
2388 <literal><link linkend="block">block</link></literal>
2389 action, i.e. it can be used to block ads and banners.
2392 <link linkend="contact">Feedback</link> with suggestions for new or improved filters is particularly
2399 <term>Example usage (with filters from the distribution <filename>default.filter</filename> file):</term>
2402 <anchor id="filter-html-annoyances">
2403 <screen>+filter{html-annoyances} # Get rid of particularly annoying HTML abuse.</screen>
2406 <anchor id="filter-js-annoyances">
2407 <screen>+filter{js-annoyances} # Get rid of particularly annoying JavaScript abuse</screen>
2410 <anchor id="filter-banners-by-size">
2411 <screen>+filter{banners-by-size} # Kill banners by size (<emphasis>very</emphasis> efficient!)</screen>
2414 <anchor id="filter-content-cookies">
2415 <screen>+filter{content-cookies} # Kill cookies that come sneaking in the HTML or JS content</screen>
2418 <anchor id="filter-popups">
2419 <screen>+filter{popups} # Kill all popups in JS and HTML</screen>
2422 <anchor id="filter-webbugs">
2423 <screen>+filter{webbugs} # Squish WebBugs (1x1 invisible GIFs used for user tracking)</screen>
2426 <anchor id="filter-fun">
2427 <screen>+filter{fun} # Text replacements for subversive browsing fun!</screen>
2430 <anchor id="filter-frameset-borders">
2431 <screen>+filter{frameset-borders} # Give frames a border and make them resizeable</screen>
2434 <anchor id="filter-refresh-tags">
2435 <screen>+filter{refresh-tags} # Kill automatic refresh tags (for dial-on-demand setups)</screen>
2438 <anchor id="filter-nimda">
2439 <screen>+filter{nimda} # Remove Nimda (virus) code.</screen>
2442 <anchor id="filter-shockwave-flash">
2443 <screen>+filter{shockwave-flash} # Kill embedded Shockwave Flash objects</screen>
2446 <anchor id="filter-crude-parental">
2447 <screen>+filter{crude-parental} # Kill all web pages that contain the words "sex" or "warez"</screen>
2455 <!-- ~~~~~ New section ~~~~~ -->
2456 <sect3 renderas="sect4" id="handle-as-image">
2457 <title>handle-as-image</title>
2461 <term>Typical use:</term>
2463 <para>Mark URLs as belonging to images (so they'll be replaced by images <emphasis>if they get blocked</emphasis>)</para>
2468 <term>Effect:</term>
2471 This action alone doesn't do anything noticeable. It just marks URLs as images.
2472 If the <literal><link linkend="block">block</link></literal> action <emphasis>also applies</emphasis>,
2473 the presence or absence of this mark decides whether an HTML <quote>blocked</quote>
2474 page, or a replacement image (as determined by the <literal><link
2475 linkend="set-image-blocker">set-image-blocker</link></literal> action) will be sent to the
2476 client as a substitute for the blocked content.
2483 <!-- Boolean, Parameterized, Multi-value -->
2485 <para>Boolean.</para>
2490 <term>Parameter:</term>
2502 The below generic example section is actually part of <filename>default.action</filename>.
2503 It marks all URLs with well-known image file name extensions as images and should
2507 Users will probably only want to use the handle-as-image action in conjunction with
2508 <literal><link linkend="block">block</link></literal>, to block sources of banners, whose URLs don't
2509 reflect the file type, like in the second example section.
2512 Note that you cannot treat HTML pages as images in most cases. For instance, (in-line) ad
2513 frames require an HTML page to be sent, or they won't display properly.
2514 Forcing <literal>handle-as-image</literal> in this situation will not replace the
2515 ad frame with an image, but lead to error messages.
2521 <term>Example usage (sections):</term>
2524 <screen># Generic image extensions:
2527 /.*\.(gif|jpg|jpeg|png|bmp|ico)$
2529 # These don't look like images, but they're banners and should be
2530 # blocked as images:
2532 {+block +handle-as-image}
2533 some.nasty-banner-server.com/junk.cgi?output=trash
2535 # Banner source! Who cares if they also have non-image content?
2545 <!-- ~~~~~ New section ~~~~~ -->
2546 <sect3 renderas="sect4" id="hide-forwarded-for-headers">
2547 <title>hide-forwarded-for-headers</title>
2551 <term>Typical use:</term>
2553 <para>Improve privacy by hiding the true source of the request</para>
2558 <term>Effect:</term>
2561 Deletes any existing <quote>X-Forwarded-for:</quote> HTTP header from client requests,
2562 and prevents adding a new one.
2569 <!-- Boolean, Parameterized, Multi-value -->
2571 <para>Boolean.</para>
2576 <term>Parameter:</term>
2588 It is fairly safe to leave this on.
2591 This action is scheduled for improvement: It should be able to generate forged
2592 <quote>X-Forwarded-for:</quote> headers using random IP addresses from a specified network,
2593 to make successive requests from the same client look like requests from a pool of different
2594 users sharing the same proxy.
2600 <term>Example usage:</term>
2603 <screen>+hide-forwarded-for-headers</screen>
2611 <!-- ~~~~~ New section ~~~~~ -->
2612 <sect3 renderas="sect4" id="hide-from-header">
2613 <title>hide-from-header</title>
2617 <term>Typical use:</term>
2619 <para>Keep your (old and ill) browser from telling web servers your email address</para>
2624 <term>Effect:</term>
2627 Deletes any existing <quote>From:</quote> HTTP header, or replaces it with the
2635 <!-- Boolean, Parameterized, Multi-value -->
2637 <para>Parameterized.</para>
2642 <term>Parameter:</term>
2645 Keyword: <quote>block</quote>, or any user defined value.
2654 The keyword <quote>block</quote> will completely remove the header
2655 (not to be confused with the <literal><link linkend="block">block</link></literal>
2659 Alternately, you can specify any value you prefer to be sent to the web
2660 server. If you do, it is a matter of fairness not to use any address that
2661 is actually used by a real person.
2664 This action is rarely needed, as modern web browsers don't send
2665 <quote>From:</quote> headers anymore.
2671 <term>Example usage:</term>
2674 <screen>+hide-from-header{block}</screen> or
2675 <screen>+hide-from-header{spam-me-senseless@sittingduck.example.com}</screen>
2683 <!-- ~~~~~ New section ~~~~~ -->
2684 <sect3 renderas="sect4" id="hide-referrer">
2685 <title>hide-referrer</title>
2686 <anchor id="hide-referer">
2689 <term>Typical use:</term>
2691 <para>Conceal which link you followed to get to a particular site</para>
2696 <term>Effect:</term>
2699 Deletes the <quote>Referer:</quote> (sic) HTTP header from the client request,
2700 or replaces it with a forged one.
2707 <!-- Boolean, Parameterized, Multi-value -->
2709 <para>Parameterized.</para>
2714 <term>Parameter:</term>
2718 <para><quote>block</quote> to delete the header completely.</para>
2721 <para><quote>forge</quote> to pretend to be coming from the homepage of the server we are talking to.</para>
2724 <para>Any other string to set a user defined referrer.</para>
2734 <quote>forge</quote> is the preferred option here, since some servers will
2735 not send images back otherwise, in an attempt to prevent their valuable
2736 content from being embedded elsewhere (and hence, without being surrounded
2737 by <emphasis>their</emphasis> banners).
2740 <literal>hide-referer</literal> is an alternate spelling of
2741 <literal>hide-referrer</literal> and the two can be can be freely
2742 substituted with each other. (<quote>referrer</quote> is the
2743 correct English spelling, however the HTTP specification has a bug - it
2744 requires it to be spelled as <quote>referer</quote>.)
2750 <term>Example usage:</term>
2753 <screen>+hide-referrer{forge}</screen> or
2754 <screen>+hide-referrer{http://www.yahoo.com/}</screen>
2762 <!-- ~~~~~ New section ~~~~~ -->
2763 <sect3 renderas="sect4" id="hide-user-agent">
2764 <title>hide-user-agent</title>
2768 <term>Typical use:</term>
2770 <para>Conceal your type of browser and client operating system</para>
2775 <term>Effect:</term>
2778 Replaces the value of the <quote>User-Agent:</quote> HTTP header
2779 in client requests with the specified value.
2786 <!-- Boolean, Parameterized, Multi-value -->
2788 <para>Parameterized.</para>
2793 <term>Parameter:</term>
2796 Any user-defined string.
2806 This breaks many web sites that depend on looking at this header in order
2807 to customize their content for different browsers (which, by the
2808 way, is <emphasis>NOT</emphasis> a <ulink
2809 url="http://www.javascriptkit.com/javaindex.shtml">smart way to do
2814 Using this action in multi-user setups or wherever different types of
2815 browsers will access the same <application>Privoxy</application> is
2816 <emphasis>not recommended</emphasis>. In single-user, single-browser
2817 setups, you might use it to delete your OS version information from
2818 the headers, because it is an invitation to exploit known bugs for your
2819 OS. It is also occasionally useful to forge this in order to access
2820 sites that won't let you in otherwise (though there may be a good
2821 reason in some cases). Example of this: some MSN sites will not
2822 let <application>Mozilla</application> enter, yet forging to a
2823 <application>Netscape 6.1</application> user-agent works just fine.
2824 (Must be just a silly MS goof, I'm sure :-).
2827 This action is scheduled for improvement.
2833 <term>Example usage:</term>
2836 <screen>+hide-user-agent{Netscape 6.1 (X11; I; Linux 2.4.18 i686)}</screen>
2844 <!-- ~~~~~ New section ~~~~~ -->
2845 <sect3 renderas="sect4" id="kill-popups">
2846 <title>kill-popups<anchor id="kill-popup"></title>
2850 <term>Typical use:</term>
2852 <para>Eliminate those annoying pop-up windows</para>
2857 <term>Effect:</term>
2860 While loading the document, replace JavaScript code that opens
2861 pop-up windows with (syntactically neutral) dummy code on the fly.
2868 <!-- Boolean, Parameterized, Multi-value -->
2870 <para>Boolean.</para>
2875 <term>Parameter:</term>
2887 This action is easily confused with the built-in, hardwired <literal><link linkend="filter">filter</link></literal>
2888 action, but there are important differences: For <literal>kill-popups</literal>,
2889 the document need not be buffered, so it can be incrementally rendered while
2890 downloading. But <literal>kill-popups</literal> doesn't catch as many pop-ups as
2892 linkend="filter">filter</link>{<replaceable>popups</replaceable>}</literal>
2896 Think of it as a fast and efficient replacement for a filter that you
2897 can use if you don't want any filtering at all. Note that it doesn't make
2898 sense to combine it with any <literal><link linkend="filter">filter</link></literal> action,
2899 since as soon as one <literal><link linkend="filter">filter</link></literal> applies,
2900 the whole document needs to be buffered anyway, which destroys the advantage of
2901 the <literal>kill-popups</literal> action over its filter equivalent.
2904 Killing all pop-ups is a dangerous business. Many shops and banks rely on
2905 pop-ups to display forms, shopping carts etc, and killing only the unwanted pop-ups
2906 would require artificial intelligence in <application>Privoxy</application>.
2907 If the only kind of pop-ups that you want to kill are exit consoles (those
2908 <emphasis>really nasty</emphasis> windows that appear when you close an other
2909 one), you might want to use
2911 linkend="filter">filter</link>{<replaceable>js-annoyances</replaceable>}</literal>
2917 An alternate spelling is <literal>+kill-popup</literal>, which is
2925 <term>Example usage:</term>
2927 <para><screen>+kill-popups</screen></para>
2934 <!-- ~~~~~ New section ~~~~~ -->
2935 <sect3 renderas="sect4" id="limit-connect">
2936 <title>limit-connect</title>
2940 <term>Typical use:</term>
2942 <para>Prevent abuse of <application>Privoxy</application> as a TCP proxy relay</para>
2947 <term>Effect:</term>
2950 Specifies to which ports HTTP CONNECT requests are allowable.
2957 <!-- Boolean, Parameterized, Multi-value -->
2959 <para>Parameterized.</para>
2964 <term>Parameter:</term>
2967 A comma-separated list of ports or port ranges (the latter using dashes, with the minimum
2968 defaulting to 0 and the maximum to 65K).
2977 By default, i.e. if no <literal>limit-connect</literal> action applies,
2978 <application>Privoxy</application> only allows HTTP CONNECT
2979 requests to port 443 (the standard, secure HTTPS port). Use
2980 <literal>limit-connect</literal> if more fine-grained control is desired
2981 for some or all destinations.
2984 The CONNECT methods exists in HTTP to allow access to secure websites
2985 (<quote>https://</quote> URLs) through proxies. It works very simply:
2986 the proxy connects to the server on the specified port, and then
2987 short-circuits its connections to the client and to the remote server.
2988 This can be a big security hole, since CONNECT-enabled proxies can be
2989 abused as TCP relays very easily.
2992 If you don't know what any of this means, there probably is no reason to
2993 change this one, since the default is already very restrictive.
2999 <term>Example usages:</term>
3001 <!-- I had trouble getting the spacing to look right in my browser -->
3002 <!-- I probably have the wrong font setup, bollocks. -->
3003 <!-- Apparently the emphasis tag uses a proportional font no matter what -->
3005 <screen>+limit-connect{443} # This is the default and need not be specified.
3006 +limit-connect{80,443} # Ports 80 and 443 are OK.
3007 +limit-connect{-3, 7, 20-100, 500-} # Ports less than 3, 7, 20 to 100 and above 500 are OK.
3008 +limit-connect{-} # All ports are OK (gaping security hole!)</screen>
3015 <!-- ~~~~~ New section ~~~~~ -->
3016 <sect3 renderas="sect4" id="prevent-compression">
3017 <title>prevent-compression</title>
3021 <term>Typical use:</term>
3024 Ensure that servers send the content uncompressed, so it can be
3025 passed through <literal><link linkend="filter">filter</link></literal>s
3031 <term>Effect:</term>
3034 Adds a header to the request that asks for uncompressed transfer.
3041 <!-- Boolean, Parameterized, Multi-value -->
3043 <para>Boolean.</para>
3048 <term>Parameter:</term>
3060 More and more websites send their content compressed by default, which
3061 is generally a good idea and saves bandwidth. But for the <literal><link
3062 linkend="filter">filter</link></literal>, <literal><link linkend="deanimate-gifs">deanimate-gifs</link></literal>
3063 and <literal><link linkend="kill-popups">kill-popups</link></literal> actions to work,
3064 <application>Privoxy</application> needs access to the uncompressed data.
3065 Unfortunately, <application>Privoxy</application> can't yet(!) uncompress, filter, and
3066 re-compress the content on the fly. So if you want to ensure that all websites, including
3067 those that normally compress, can be filtered, you need to use this action.
3070 This will slow down transfers from those websites, though. If you use any of the above-mentioned
3071 actions, you will typically want to use <literal>prevent-compression</literal> in conjunction
3075 Note that some (rare) ill-configured sites don't handle requests for uncompressed
3076 documents correctly (they send an empty document body). If you use <literal>prevent-compression</literal>
3077 per default, you'll have to add exceptions for those sites. See the example for how to do that.
3083 <term>Example usage (sections):</term>
3086 <screen># Set default:
3088 {+prevent-compression}
3091 # Make exceptions for ill sites:
3093 {-prevent-compression}
3095 www.pclinuxonline.com</screen>
3104 <!-- ~~~~~ New section ~~~~~ -->
3105 <sect3 renderas="sect4" id="send-vanilla-wafer">
3106 <title>send-vanilla-wafer</title>
3110 <term>Typical use:</term>
3113 Feed log analysis scripts with useless data.
3119 <term>Effect:</term>
3122 Sends a cookie with each request stating that you do not accept any copyright
3123 on cookies sent to you, and asking the site operator not to track you.
3130 <!-- Boolean, Parameterized, Multi-value -->
3132 <para>Boolean.</para>
3137 <term>Parameter:</term>
3149 The vanilla wafer is a (relatively) unique header and could conceivably be used to track you.
3152 This action is rarely used and not enabled in the default configuration.
3158 <term>Example usage:</term>
3161 <screen>+send-vanilla-wafer</screen>
3170 <!-- ~~~~~ New section ~~~~~ -->
3171 <sect3 renderas="sect4" id="send-wafer">
3172 <title>send-wafer</title>
3176 <term>Typical use:</term>
3179 Send custom cookies or feed log analysis scripts with even more useless data.
3185 <term>Effect:</term>
3188 Sends a custom, user-defined cookie with each request.
3195 <!-- Boolean, Parameterized, Multi-value -->
3197 <para>Multi-value.</para>
3202 <term>Parameter:</term>
3205 A string of the form <quote><replaceable class="option">name</replaceable>=<replaceable
3206 class="parameter">value</replaceable></quote>.
3215 Being multi-valued, multiple instances of this action can apply to the same request,
3216 resulting in multiple cookies being sent.
3219 This action is rarely used and not enabled in the default configuration.
3224 <term>Example usage (section):</term>
3227 <screen>{+send-wafer{UsingPrivoxy=true}}
3228 my-internal-testing-server.void</screen>
3236 <!-- ~~~~~ New section ~~~~~ -->
3237 <sect3 renderas="sect4" id="session-cookies-only">
3238 <title>session-cookies-only</title>
3242 <term>Typical use:</term>
3245 Allow only temporary <quote>session</quote> cookies (for the current browser session <emphasis>only</emphasis>).
3251 <term>Effect:</term>
3254 Deletes the <quote>expires</quote> field from <quote>Set-Cookie:</quote> server headers.
3255 Most browsers will not store such cookies permanently and forget them in between sessions.
3262 <!-- Boolean, Parameterized, Multi-value -->
3264 <para>Boolean.</para>
3269 <term>Parameter:</term>
3281 This is less strict than <literal><link linkend="crunch-incoming-cookies">crunch-incoming-cookies</link></literal> /
3282 <literal><link linkend="crunch-outgoing-cookies">crunch-outgoing-cookies</link></literal> and allows you to browse
3283 websites that insist or rely on setting cookies, without compromising your privacy too badly.
3286 Most browsers will not permanently store cookies that have been processed by
3287 <literal>session-cookies-only</literal> and will forget about them between sessions.
3288 This makes profiling cookies useless, but won't break sites which require cookies so
3289 that you can log in for transactions. This is generally turned on for all
3290 sites, and is the recommended setting.
3293 It makes <emphasis>no sense at all</emphasis> to use <literal>session-cookies-only</literal>
3294 together with <literal><link linkend="crunch-incoming-cookies">crunch-incoming-cookies</link></literal> or
3295 <literal><link linkend="crunch-outgoing-cookies">crunch-outgoing-cookies</link></literal>. If you do, cookies
3296 will be plainly killed.
3299 Note that it is up to the browser how it handles such cookies without an <quote>expires</quote>
3300 field. If you use an exotic browser, you might want to try it out to be sure.
3306 <term>Example usage:</term>
3309 <screen>+session-cookies-only</screen>
3317 <!-- ~~~~~ New section ~~~~~ -->
3318 <sect3 renderas="sect4" id="set-image-blocker">
3319 <title>set-image-blocker</title>
3323 <term>Typical use:</term>
3325 <para>Choose the replacement for blocked images</para>
3330 <term>Effect:</term>
3333 This action alone doesn't do anything noticeable. If <emphasis>both</emphasis>
3334 <literal><link linkend="block">block</link></literal> <emphasis>and</emphasis> <literal><link
3335 linkend="handle-as-image">handle-as-image</link></literal> <emphasis>also</emphasis>
3336 apply, i.e. if the request is to be blocked as an image,
3337 <emphasis>then</emphasis> the parameter of this action decides what will be
3338 sent as a replacement.
3345 <!-- Boolean, Parameterized, Multi-value -->
3347 <para>Parameterized.</para>
3352 <term>Parameter:</term>
3357 <quote>pattern</quote> to send a built-in checkerboard pattern image. The image is visually
3358 decent, scales very well, and makes it obvious where banners were busted.
3363 <quote>blank</quote> to send a built-in transparent image. This makes banners disappear
3364 completely, but makes it hard to detect where <application>Privoxy</application> has blocked
3365 images on a given page and complicates troubleshooting if <application>Privoxy</application>
3366 has blocked innocent images, like navigation icons.
3371 <quote><replaceable class="parameter">target-url</replaceable></quote> to
3372 send a redirect to <replaceable class="parameter">target-url</replaceable>. You can redirect
3373 to any image anywhere, even in your local filesystem (via <quote>file:///</quote> URL).
3376 A good application of redirects is to use special <application>Privoxy</application>-built-in
3377 URLs, which send the built-in images, as <replaceable class="parameter">target-url</replaceable>.
3378 This has the same visual effect as specifying <quote>blank</quote> or <quote>pattern</quote> in
3379 the first place, but enables your browser to cache the replacement image, instead of requesting
3380 it over and over again.
3391 The URLs for the built-in images are <quote>http://config.privoxy.org/send-banner?type=<replaceable
3392 class="parameter">type</replaceable></quote>, where <replaceable class="parameter">type</replaceable> is
3393 either <quote>blank</quote> or <quote>pattern</quote>.
3396 There is a third (advanced) type, called <quote>auto</quote>. It is <emphasis>NOT</emphasis> to be
3397 used in <literal>set-image-blocker</literal>, but meant for use from <link linkend="filter-file">filters</link>.
3398 Auto will select the type of image that would have applied to the referring page, had it been an image.
3404 <term>Example usage:</term>
3410 <screen>+set-image-blocker{pattern}</screen>
3413 Redirect to the BSD devil:
3416 <screen>+set-image-blocker{http://www.freebsd.org/gifs/dae_up3.gif}</screen>
3419 Redirect to the built-in pattern for better caching:
3422 <screen>+set-image-blocker{http://config.privoxy.org/send-banner?type=pattern}</screen>
3430 <!-- ~~~~~ New section ~~~~~ -->
3432 <title>Summary</title>
3434 Note that many of these actions have the potential to cause a page to
3435 misbehave, possibly even not to display at all. There are many ways
3436 a site designer may choose to design his site, and what HTTP header
3437 content, and other criteria, he may depend on. There is no way to have hard
3438 and fast rules for all sites. See the <link
3439 linkend="ACTIONSANAT">Appendix</link> for a brief example on troubleshooting
3445 <!-- ~~~~~ New section ~~~~~ -->
3446 <sect2 id="aliases">
3447 <title>Aliases</title>
3449 Custom <quote>actions</quote>, known to <application>Privoxy</application>
3450 as <quote>aliases</quote>, can be defined by combining other actions.
3451 These can in turn be invoked just like the built-in actions.
3452 Currently, an alias name can contain any character except space, tab,
3454 <quote>{</quote> and <quote>}</quote>, but we <emphasis>strongly
3455 recommend</emphasis> that you only use <quote>a</quote> to <quote>z</quote>,
3456 <quote>0</quote> to <quote>9</quote>, <quote>+</quote>, and <quote>-</quote>.
3457 Alias names are not case sensitive, and are not required to start with a
3458 <quote>+</quote> or <quote>-</quote> sign, since they are merely textually
3462 Aliases can be used throughout the actions file, but they <emphasis>must be
3463 defined in a special section at the top of the file!</emphasis>
3464 And there can only be one such section per actions file. Each actions file may
3465 have its own alias section, and the aliases defined in it are only visible
3469 There are two main reasons to use aliases: One is to save typing for frequently
3470 used combinations of actions, the other one is a gain in flexibility: If you
3471 decide once how you want to handle shops by defining an alias called
3472 <quote>shop</quote>, you can later change your policy on shops in
3473 <emphasis>one</emphasis> place, and your changes will take effect everywhere
3474 in the actions file where the <quote>shop</quote> alias is used. Calling aliases
3475 by their purpose also makes your actions files more readable.
3478 Currently, there is one big drawback to using aliases, though:
3479 <application>Privoxy</application>'s built-in web-based action file
3480 editor honors aliases when reading the actions files, but it expands
3481 them before writing. So the effects of your aliases are of course preserved,
3482 but the aliases themselves are lost when you edit sections that use aliases
3484 This is likely to change in future versions of <application>Privoxy</application>.
3488 Now let's define some aliases...
3493 # Useful custom aliases we can use later.
3495 # Note the (required!) section header line and that this section
3496 # must be at the top of the actions file!
3500 # These aliases just save typing later:
3501 # (Note that some already use other aliases!)
3503 +crunch-all-cookies = +crunch-incoming-cookies +crunch-outgoing-cookies
3504 -crunch-all-cookies = -crunch-incoming-cookies -crunch-outgoing-cookies
3505 block-as-image = +block +handle-as-image
3506 mercy-for-cookies = -crunch-all-cookies -session-cookies-only
3508 # These aliases define combinations of actions
3509 # that are useful for certain types of sites:
3511 fragile = -block -crunch-all-cookies -filter -fast-redirects -hide-referer -kill-popups
3512 shop = -crunch-all-cookies -filter{popups} -kill-popups
3514 # Short names for other aliases, for really lazy people ;-)
3516 c0 = +crunch-all-cookies
3517 c1 = -crunch-all-cookies</screen>
3521 ...and put them to use. These sections would appear in the lower part of an
3522 actions file and define exceptions to the default actions (as specified further
3523 up for the <quote>/</quote> pattern):
3528 # These sites are either very complex or very keen on
3529 # user data and require minimal interference to work:
3532 .office.microsoft.com
3533 .windowsupdate.microsoft.com
3537 # Allow cookies (for setting and retrieving your customer data)
3541 .worldpay.com # for quietpc.com
3544 # These shops require pop-ups:
3546 {shop -kill-popups -filter{popups}}
3548 .overclockers.co.uk</screen>
3552 Aliases like <quote>shop</quote> and <quote>fragile</quote> are often used for
3553 <quote>problem</quote> sites that require some actions to be disabled
3554 in order to function properly.
3558 <!-- ~~~~~ New section ~~~~~ -->
3559 <sect2 id="act-examples">
3560 <title>Actions Files Tutorial</title>
3562 The above chapters have shown <link linkend="actions-file">which actions files
3563 there are and how they are organized</link>, how actions are <link
3564 linkend="actions">specified</link> and <link linkend="actions-apply">applied
3565 to URLs</link>, how <link linkend="af-patterns">patterns</link> work, and how to
3566 define and use <link linkend="aliases">aliases</link>. Now, let's look at an
3567 example <filename>default.action</filename> and <filename>user.action</filename>
3568 file and see how all these pieces come together:
3571 <sect3><title>default.action</title>
3574 Every config file should start with a short comment stating its purpose:
3578 <screen># Sample default.action file <developers@privoxy.org></screen>
3582 Then, since this is the <filename>default.action</filename> file, the
3583 first section is a special section for internal use that you needn't
3584 change or worry about:
3589 ##########################################################################
3590 # Settings -- Don't change! For internal Privoxy use ONLY.
3591 ##########################################################################
3594 for-privoxy-version=3.0</screen>
3598 After that comes the (optional) alias section. We'll use the example
3599 section from the above <link linkend="aliases">chapter on aliases</link>,
3600 that also explains why and how aliases are used:
3605 ##########################################################################
3607 ##########################################################################
3610 # These aliases just save typing later:
3611 # (Note that some already use other aliases!)
3613 +crunch-all-cookies = +crunch-incoming-cookies +crunch-outgoing-cookies
3614 -crunch-all-cookies = -crunch-incoming-cookies -crunch-outgoing-cookies
3615 block-as-image = +block +handle-as-image
3616 mercy-for-cookies = -crunch-all-cookies -session-cookies-only
3618 # These aliases define combinations of actions
3619 # that are useful for certain types of sites:
3621 fragile = -block -crunch-all-cookies -filter -fast-redirects -hide-referer -kill-popups
3622 shop = mercy-for-cookies -filter{popups} -kill-popups</screen>
3626 Now come the regular sections, i.e. sets of actions, accompanied
3627 by URL patterns to which they apply. Remember <emphasis>all actions
3628 are disabled when matching starts</emphasis>, so we have to explicitly
3629 enable the ones we want.
3633 The first regular section is probably the most important. It has only
3634 one pattern, <quote><literal>/</literal></quote>, but this pattern
3635 <link linkend="af-patterns">matches all URLs</link>. Therefore, the
3636 set of actions used in this <quote>default</quote> section <emphasis>will
3637 be applied to all requests as a start</emphasis>. It can be partly or
3638 wholly overridden by later matches further down this file, or in user.action,
3639 but it will still be largely responsible for your overall browsing
3644 Again, at the start of matching, all actions are disabled, so there is
3645 no real need to disable any actions here, but we will do that nonetheless,
3646 to have a complete listing for your reference. (Remember: a <quote>+</quote>
3647 preceding the action name enables the action, a <quote>-</quote> disables!).
3648 Also note how this long line has been made more readable by splitting it into
3649 multiple lines with line continuation.
3654 ##########################################################################
3655 # "Defaults" section:
3656 ##########################################################################
3658 -<link linkend="ADD-HEADER">add-header</link> \
3659 -<link linkend="BLOCK">block</link> \
3660 -<link linkend="CRUNCH-INCOMING-COOKIES">crunch-incoming-cookies</link> \
3661 -<link linkend="CRUNCH-OUTGOING-COOKIES">crunch-outgoing-cookies</link> \
3662 +<link linkend="DEANIMATE-GIFS">deanimate-gifs</link> \
3663 -<link linkend="DOWNGRADE-HTTP-VERSION">downgrade-http-version</link> \
3664 +<link linkend="FAST-REDIRECTS">fast-redirects</link> \
3665 +<link linkend="FILTER-HTML-ANNOYANCES">filter{html-annoyances}</link> \
3666 +<link linkend="FILTER-JS-ANNOYANCES">filter{js-annoyances}</link> \
3667 -<link linkend="FILTER-CONTENT-COOKIES">filter{content-cookies}</link> \
3668 +<link linkend="FILTER-POPUPS">filter{popups}</link> \
3669 +<link linkend="FILTER-WEBBUGS">filter{webbugs}</link> \
3670 -<link linkend="FILTER-REFRESH-TAGS">filter{refresh-tags}</link> \
3671 -<link linkend="FILTER-FUN">filter{fun}</link> \
3672 +<link linkend="FILTER-NIMDA">filter{nimda}</link> \
3673 +<link linkend="FILTER-BANNERS-BY-SIZE">filter{banners-by-size}</link> \
3674 -<link linkend="FILTER-SHOCKWAVE-FLASH">filter{shockwave-flash}</link> \
3675 -<link linkend="FILTER-CRUDE-PARENTAL">filter{crude-parental}</link> \
3676 -<link linkend="HANDLE-AS-IMAGE">handle-as-image</link> \
3677 +<link linkend="HIDE-FORWARDED-FOR-HEADERS">hide-forwarded-for-headers</link> \
3678 +<link linkend="HIDE-FROM-HEADER">hide-from-header{block}</link> \
3679 +<link linkend="HIDE-REFERER">hide-referrer{forge}</link> \
3680 -<link linkend="HIDE-USER-AGENT">hide-user-agent</link> \
3681 -<link linkend="KILL-POPUPS">kill-popups</link> \
3682 -<link linkend="LIMIT-CONNECT">limit-connect</link> \
3683 +<link linkend="PREVENT-COMPRESSION">prevent-compression</link> \
3684 -<link linkend="SEND-VANILLA-WAFER">send-vanilla-wafer</link> \
3685 -<link linkend="SEND-WAFER">send-wafer</link> \
3686 +<link linkend="SESSION-COOKIES-ONLY">session-cookies-only</link> \
3687 +<link linkend="SET-IMAGE-BLOCKER">set-image-blocker{pattern}</link> \
3689 / # forward slash will match *all* potential URL patterns.</screen>
3693 The default behavior is now set. Note that some actions, like not hiding
3694 the user agent, are part of a <quote>general policy</quote> that applies
3695 universally and won't get any exceptions defined later. Other choices,
3696 like not blocking (which is <emphasis>understandably</emphasis> the
3697 default!) need exceptions, i.e. we need to specify explicitly what we
3698 want to block in later sections.
3699 We will also want to make exceptions from our general pop-up-killing,
3700 and use our defined aliases for that.
3704 The first of our specialized sections is concerned with <quote>fragile</quote>
3705 sites, i.e. sites that require minimum interference, because they are either
3706 very complex or very keen on tracking you (and have mechanisms in place that
3707 make them unusable for people who avoid being tracked). We will simply use
3708 our pre-defined <literal>fragile</literal> alias instead of stating the list
3709 of actions explicitly:
3714 ##########################################################################
3715 # Exceptions for sites that'll break under the default action set:
3716 ##########################################################################
3718 # "Fragile" Use a minimum set of actions for these sites (see alias above):
3721 .office.microsoft.com # surprise, surprise!
3722 .windowsupdate.microsoft.com</screen>
3726 Shopping sites are not as fragile, but they typically
3727 require cookies to log in, and pop-up windows for shopping
3728 carts or item details. Again, we'll use a pre-defined alias:
3737 .worldpay.com # for quietpc.com
3739 .scan.co.uk</screen>
3743 Then, there are sites which rely on pop-up windows (yuck!) to work.
3744 Since we made pop-up-killing our default above, we need to make exceptions
3745 now. <ulink url="http://www.mozilla.org/">Mozilla</ulink> users, who
3746 can turn on smart handling of unwanted pop-ups in their browsers, can
3748 -<literal><link linkend="FILTER-POPUPS">filter{popups}</link></literal> (and
3749 -<literal><link linkend="KILL-POPUPS">kill-popups</link></literal>) above
3750 and hence don't need this section. Anyway, disabling an already disabled
3751 action doesn't hurt, so we'll define our exceptions regardless of what was
3752 chosen in the defaults section:
3757 # These sites require pop-ups too :(
3759 { -<link linkend="KILL-POPUPS">kill-popups</link> -<link linkend="FILTER-POPUPS">filter{popups}</link> }
3762 .deutsche-bank-24.de</screen>
3766 The <literal><link linkend="FAST-REDIRECTS">fast-redirects</link></literal>
3767 action, which we enabled per default above, breaks some sites. So disable
3768 it for popular sites where we know it misbehaves:
3773 { -<link linkend="FAST-REDIRECTS">fast-redirects</link> }
3777 .altavista.com/.*(like|url|link):http
3778 .altavista.com/trans.*urltext=http
3779 .nytimes.com</screen>
3783 It is important that <application>Privoxy</application> knows which
3784 URLs belong to images, so that <emphasis>if</emphasis> they are to
3785 be blocked, a substitute image can be sent, rather than an HTML page.
3786 Contacting the remote site to find out is not an option, since it
3787 would destroy the loading time advantage of banner blocking, and it
3788 would feed the advertisers (in terms of money <emphasis>and</emphasis>
3789 information). We can mark any URL as an image with the <literal><link
3790 linkend="handle-as-image">handle-as-image</link></literal> action,
3791 and marking all URLs that end in a known image file extension is a
3797 ##########################################################################
3799 ##########################################################################
3801 # Define which file types will be treated as images, in case they get
3802 # blocked further down this file:
3804 { +<link linkend="HANDLE-AS-IMAGE">handle-as-image</link> }
3805 /.*\.(gif|jpe?g|png|bmp|ico)$</screen>
3809 And then there are known banner sources. They often use scripts to
3810 generate the banners, so it won't be visible from the URL that the
3811 request is for an image. Hence we block them <emphasis>and</emphasis>
3812 mark them as images in one go, with the help of our
3813 <literal>block-as-image</literal> alias defined above. (We could of
3814 course just as well use <literal>+<link linkend="block">block</link>
3815 +<link linkend="handle-as-image">handle-as-image</link></literal> here.)
3816 Remember that the type of the replacement image is chosen by the
3817 <literal><link linkend="set-image-blocker">set-image-blocker</link></literal>
3818 action. Since all URLs have matched the default section with its
3819 <literal>+<link linkend="set-image-blocker">set-image-blocker</link>{pattern}</literal>
3820 action before, it still applies and needn't be repeated:
3825 # Known ad generators:
3830 .ad.*.doubleclick.net
3831 .a.yimg.com/(?:(?!/i/).)*$
3832 .a[0-9].yimg.com/(?:(?!/i/).)*$
3839 One of the most important jobs of <application>Privoxy</application>
3840 is to block banners. A huge bunch of them are already <quote>blocked</quote>
3841 by the <literal><link linkend="filter">filter</link>{banners-by-size}</literal>
3842 action, which we enabled above, and which deletes the references to banner
3843 images from the pages while they are loaded, so the browser doesn't request
3844 them anymore, and hence they don't need to be blocked here. But this naturally
3845 doesn't catch all banners, and some people choose not to use filters, so we
3846 need a comprehensive list of patterns for banner URLs here, and apply the
3847 <literal><link linkend="block">block</link></literal> action to them.
3850 First comes a bunch of generic patterns, which do most of the work, by
3851 matching typical domain and path name components of banners. Then comes
3852 a list of individual patterns for specific sites, which is omitted here
3853 to keep the example short:
3858 ##########################################################################
3859 # Block these fine banners:
3860 ##########################################################################
3861 { <link linkend="BLOCK">+block</link> }
3869 /.*count(er)?\.(pl|cgi|exe|dll|asp|php[34]?)
3870 /(?:.*/)?(publicite|werbung|rekla(ma|me|am)|annonse|maino(kset|nta|s)?)/
3872 # Site-specific patterns (abbreviated):
3874 .hitbox.com</screen>
3878 You wouldn't believe how many advertisers actually call their banner
3879 servers ads.<replaceable>company</replaceable>.com, or call the directory
3880 in which the banners are stored simply <quote>banners</quote>. So the above
3881 generic patterns are surprisingly effective.
3884 But being very generic, they necessarily also catch URLs that we don't want
3885 to block. The pattern <literal>.*ads.</literal> e.g. catches
3886 <quote>nasty-<emphasis>ads</emphasis>.nasty-corp.com</quote> as intended,
3887 but also <quote>downlo<emphasis>ads</emphasis>.sourcefroge.net</quote> or
3888 <quote><emphasis>ads</emphasis>l.some-provider.net.</quote> So here come some
3889 well-known exceptions to the <literal>+<link linkend="BLOCK">block</link></literal>
3893 Note that these are exceptions to exceptions from the default! Consider the URL
3894 <quote>downloads.sourcefroge.net</quote>: Initially, all actions are deactivated,
3895 so it wouldn't get blocked. Then comes the defaults section, which matches the
3896 URL, but just deactivates the <literal><link linkend="BLOCK">block</link></literal>
3897 action once again. Then it matches <literal>.*ads.</literal>, an exception to the
3898 general non-blocking policy, and suddenly
3899 <literal><link linkend="BLOCK">+block</link></literal> applies. And now, it'll match
3900 <literal>.*loads.</literal>, where <literal><link linkend="BLOCK">-block</link></literal>
3901 applies, so (unless it matches <emphasis>again</emphasis> further down) it ends up
3902 with no <literal><link linkend="BLOCK">block</link></literal> action applying.
3907 ##########################################################################
3908 # Save some innocent victims of the above generic block patterns:
3909 ##########################################################################
3913 { -<link linkend="BLOCK">block</link> }
3914 adv[io]*. # (for advogato.org and advice.*)
3915 adsl. # (has nothing to do with ads)
3916 ad[ud]*. # (adult.* and add.*)
3917 .edu # (universities don't host banners (yet!))
3918 .*loads. # (downloads, uploads etc)
3926 www.globalintersec.com/adv # (adv = advanced)
3927 www.ugu.com/sui/ugu/adv</screen>
3931 Filtering source code can have nasty side effects,
3932 so make an exception for our friends at sourceforge.net,
3933 and all paths with <quote>cvs</quote> in them. Note that
3934 <literal>-<link linkend="FILTER">filter</link></literal>
3935 disables <emphasis>all</emphasis> filters in one fell swoop!
3940 # Don't filter code!
3942 { -<link linkend="FILTER">filter</link> }
3944 .sourceforge.net</screen>
3948 The actual <filename>default.action</filename> is of course more
3949 comprehensive, but we hope this example made clear how it works.
3954 <sect3><title>user.action</title>
3957 So far we are painting with a broad brush by setting general policies,
3958 which would be a reasonable starting point for many people. Now,
3959 you might want to be more specific and have customized rules that
3960 are more suitable to your personal habits and preferences. These would
3961 be for narrowly defined situations like your ISP or your bank, and should
3962 be placed in <filename>user.action</filename>, which is parsed after all other
3963 actions files and hence has the last word, over-riding any previously
3964 defined actions. <filename>user.action</filename> is also a
3965 <emphasis>safe</emphasis> place for your personal settings, since
3966 <filename>default.action</filename> is actively maintained by the
3967 <application>Privoxy</application> developers and you'll probably want
3968 to install updated versions from time to time.
3972 So let's look at a few examples of things that one might typically do in
3973 <filename>user.action</filename>:
3977 <!-- brief sample user.action here -->
3981 # My user.action file. <fred@foobar.com></screen>
3985 As <link linkend="aliases">aliases</link> are local to the actions
3986 file that they are defined in, you can't use the ones from
3987 <filename>default.action</filename>, unless you repeat them here:
3992 # (Re-)define aliases for this file:
3995 -crunch-all-cookies = -crunch-incoming-cookies -crunch-outgoing-cookies
3996 mercy-for-cookies = -crunch-all-cookies -session-cookies-only
3997 fragile = -block -crunch-all-cookies -filter -fast-redirects -hide-referer -kill-popups
3998 shop = mercy-for-cookies -filter{popups} -kill-popups
3999 allow-ads = -block -filter{banners-by-size} # (see below)</screen>
4004 Say you have accounts on some sites that you visit regularly, and
4005 you don't want to have to log in manually each time. So you'd like
4006 to allow persistent cookies for these sites. The
4007 <literal>mercy-for-cookies</literal> alias defined above does exactly
4008 that, i.e. it disables crunching of cookies in any direction, and
4009 processing of cookies to make them temporary.
4014 { mercy-for-cookies }
4019 .redhat.com</screen>
4023 Your bank needs popups and is allergic to some filter, but you don't
4024 know which, so you disable them all:
4029 { -<link linkend="FILTER">filter</link> -<link linkend="KILL-POPUPS">kill-popups</link> }
4030 .your-home-banking-site.com</screen>
4034 While browsing the web with <application>Privoxy</application> you
4035 noticed some ads that sneaked through, but you were too lazy to
4036 report them through our fine and easy <link linkend="contact">feedback</link>
4037 system, so you have added them here:
4042 { +<link linkend="BLOCK">block</link> }
4043 www.a-popular-site.com/some/unobvious/path
4044 another.popular.site.net/more/junk/here/</screen>
4048 Note that, assuming the banners in the above example have regular image
4049 extensions (most do),
4050 <literal>+<link linkend="HANDLE-AS-IMAGE">handle-as-image</link></literal>
4051 need not be specified, since all URLs ending in these extensions will
4052 already have been tagged as images in the relevant section of
4053 <filename>default.action</filename> by now.
4057 Then you noticed that the default configuration breaks Forbes Magazine,
4058 but you were too lazy to find out which action is the culprit, and you
4059 were again too lazy to give <link linkend="contact">feedback</link>, so
4060 you just used the <literal>fragile</literal> alias on the site, and
4061 -- whoa! -- it worked:
4067 .forbes.com</screen>
4071 You like the <quote>fun</quote> text replacements in <filename>default.filter</filename>,
4072 but it is disabled in the distributed actions file. (My colleagues on the team just
4073 don't have a sense of humour, that's why! ;-). So you'd like to turn it on in your private,
4074 update-safe config, once and for all:
4079 { +<link linkend="filter-fun">filter{fun}</link> }
4080 / # For ALL sites!</screen>
4084 Note that the above is not really a good idea: There are exceptions
4085 to the filters in <filename>default.action</filename> for things that
4086 really shouldn't be filtered, like code on CVS->Web interfaces. Since
4087 <filename>user.action</filename> has the last word, these exceptions
4088 won't be valid for the <quote>fun</quote> filtering specified here.
4092 Finally, you might think about how your favourite free websites are
4093 funded, and find that they rely on displaying banner advertisements
4094 to survive. So you might want to specifically allow banners for those
4095 sites that you feel provide value to you:
4107 Note that <literal>allow-ads</literal> has been aliased to
4108 <literal>-<link linkend="block">block</link></literal>
4109 <literal>-<link linkend="filter-banners-by-size">filter{banners-by-size}</link></literal>
4115 <!-- ~ End section ~ -->
4119 <!-- ~ End section ~ -->
4121 <!-- ~~~~~~~~ New section Header ~~~~~~~~~ -->
4123 <sect1 id="filter-file">
4124 <title>The Filter File</title>
4127 All text substitutions that can be invoked through the
4128 <literal><link linkend="filter">filter</link></literal> action
4129 must first be defined in the filter file, which is typically
4130 called <filename>default.filter</filename> and which can be
4131 selected through the <literal>
4132 <link linkend="filterfile">filterfile</link></literal> config
4137 Typical reasons for doing such substitutions are to eliminate
4138 common annoyances in HTML and JavaScript, such as pop-up windows,
4139 exit consoles, crippled windows without navigation tools, the
4140 infamous <BLINK> tag etc, to suppress images with certain
4141 width and height attributes (standard banner sizes or web-bugs),
4142 or just to have fun. The possibilities are endless.
4146 Filtering works on any text-based document type, including plain
4147 text, HTML, JavaScript, CSS etc. (all <literal>text/*</literal>
4148 MIME types). Substitutions are made at the source level, so if
4149 you want to <quote>roll your own</quote> filters, you should be
4150 familiar with HTML syntax.
4154 Just like the <link linkend="actions-file">actions files</link>, the
4155 filter file is organized in sections, which are called <emphasis>filters</emphasis>
4156 here. Each filter consists of a heading line, that starts with the
4157 <emphasis>keyword</emphasis> <literal>FILTER:</literal>, followed by
4158 the filter's <emphasis>name</emphasis>, and a short (one line)
4159 <emphasis>description</emphasis> of what it does. Below that line
4160 come the <emphasis>jobs</emphasis>, i.e. lines that define the actual
4161 text substitutions. By convention, the name of a filter
4162 should describe what the filter <emphasis>eliminates</emphasis>. The
4163 comment is used in the <ulink url="http://config.privoxy.org/">web-based
4164 user interface</ulink>.
4168 Once a filter called <replaceable>name</replaceable> has been defined
4169 in the filter file, it can be invoked by using an action of the form
4170 +<literal><link linkend="filter">filter</link>{<replaceable>name</replaceable>}</literal>
4171 in any <link linkend="actions-file">actions file</link>.
4175 A filter header line for a filter called <quote>foo</quote> could look
4180 <screen>FILTER: foo Replace all "foo" with "bar"</screen>
4184 Below that line, and up to the next header line, come the jobs that
4185 define what text replacements the filter executes. They are specified
4186 in a syntax that imitates <ulink url="http://www.perl.org/">Perl</ulink>'s
4187 <literal>s///</literal> operator. If you are familiar with Perl, you
4188 will find this to be quite intuitive, and may want to look at the
4189 <ulink url="http://www.oesterhelt.org/pcrs/pcrs.1.html">PCRS man page</ulink>
4190 for the subtle differences to Perl behaviour. Most notably, the non-standard
4191 option letter <literal>U</literal> is supported, which turns the default
4192 to ungreedy matching.
4196 If you are new to regular expressions, you might want to take a look at
4197 the <link linkend="regex">Appendix on regular expressions</link>, and
4198 see the <ulink url="http://perldoc.com/perl5.6.1/pod/perl.html">Perl
4200 <ulink url="http://perldoc.com/perl5.6.1/pod/perlop.html#s-PATTERN-REPLACEMENT-egimosx">the
4201 <literal>s///</literal> operator's syntax</ulink> and <ulink
4202 url="http://perldoc.com/perl5.6.1/pod/perlre.html">Perl-style regular
4203 expressions</ulink> in general.
4204 The below examples might also help to get you started.
4207 <!-- ~~~~~~~~ New section Header ~~~~~~~~~ -->
4209 <sect2><title>Filter File Tutorial</title>
4211 Now, let's complete our <quote>foo</quote> filter. We have already defined
4212 the heading, but the jobs are still missing. Since all it does is to replace
4213 <quote>foo</quote> with <quote>bar</quote>, there is only one (trivial) job
4218 <screen>s/foo/bar/</screen>
4222 But wait! Didn't the comment say that <emphasis>all</emphasis> occurrences
4223 of <quote>foo</quote> should be replaced? Our current job will only take
4224 care of the first <quote>foo</quote> on each page. For global substitution,
4225 we'll need to add the <literal>g</literal> option:
4229 <screen>s/foo/bar/g</screen>
4233 Our complete filter now looks like this:
4236 <screen>FILTER: foo Replace all "foo" with "bar"
4237 s/foo/bar/g</screen>
4241 Let's look at some real filters for more interesting examples. Here you see
4242 a filter that protects against some common annoyances that arise from JavaScript
4243 abuse. Let's look at its jobs one after the other:
4249 FILTER: js-annoyances Get rid of particularly annoying JavaScript abuse
4251 # Get rid of JavaScript referrer tracking. Test page: http://www.randomoddness.com/untitled.htm
4253 s|(<script.*)document\.referrer(.*</script>)|$1"Not Your Business!"$2|Usg</screen>
4257 Following the header line and a comment, you see the job. Note that it uses
4258 <literal>|</literal> as the delimiter instead of <literal>/</literal>, because
4259 the pattern contains a forward slash, which would otherwise have to be escaped
4260 by a backslash (<literal>\</literal>).
4264 Now, let's examine the pattern: it starts with the text <literal><script.*</literal>
4265 enclosed in parentheses. Since the dot matches any character, and <literal>*</literal>
4266 means: <quote>Match an arbitrary number of the element left of myself</quote>, this
4267 matches <quote><script</quote>, followed by <emphasis>any</emphasis> text, i.e.
4268 it matches the whole page, from the start of the first <script> tag.
4272 That's more than we want, but the pattern continues: <literal>document\.referrer</literal>
4273 matches only the exact string <quote>document.referrer</quote>. The dot needed to
4274 be <emphasis>escaped</emphasis>, i.e. preceded by a backslash, to take away its
4275 special meaning as a joker, and make it just a regular dot. So far, the meaning is:
4276 Match from the start of the first <script> tag in a the page, up to, and including,
4277 the text <quote>document.referrer</quote>, if <emphasis>both</emphasis> are present
4278 in the page (and appear in that order).
4282 But there's still more pattern to go. The next element, again enclosed in parentheses,
4283 is <literal>.*</script></literal>. You already know what <literal>.*</literal>
4284 means, so the whole pattern translates to: Match from the start of the first <script>
4285 tag in a page to the end of the last <script> tag, provided that the text
4286 <quote>document.referrer</quote> appears somewhere in between.
4290 This is still not the whole story, since we have ignored the options and the parentheses:
4291 The portions of the page matched by sub-patterns that are enclosed in parentheses, will be
4292 remembered and be available through the variables <literal>$1, $2, ...</literal> in
4293 the substitute. The <literal>U</literal> option switches to ungreedy matching, which means
4294 that the first <literal>.*</literal> in the pattern will only <quote>eat up</quote> all
4295 text in between <quote><script</quote> and the <emphasis>first</emphasis> occurrence
4296 of <quote>document.referrer</quote>, and that the second <literal>.*</literal> will
4297 only span the text up to the <emphasis>first</emphasis> <quote></script></quote>
4298 tag. Furthermore, the <literal>s</literal> option says that the match may span
4299 multiple lines in the page, and the <literal>g</literal> option again means that the
4300 substitution is global.
4304 So, to summarize, the pattern means: Match all scripts that contain the text
4305 <quote>document.referrer</quote>. Remember the parts of the script from
4306 (and including) the start tag up to (and excluding) the string
4307 <quote>document.referrer</quote> as <literal>$1</literal>, and the part following
4308 that string, up to and including the closing tag, as <literal>$2</literal>.
4312 Now the pattern is deciphered, but wasn't this about substituting things? So
4313 lets look at the substitute: <literal>$1"Not Your Business!"$2</literal> is
4314 easy to read: The text remembered as <literal>$1</literal>, followed by
4315 <literal>"Not Your Business!"</literal> (<emphasis>including</emphasis>
4316 the quotation marks!), followed by the text remembered as <literal>$2</literal>.
4317 This produces an exact copy of the original string, with the middle part
4318 (the <quote>document.referrer</quote>) replaced by <literal>"Not Your
4319 Business!"</literal>.
4323 The whole job now reads: Replace <quote>document.referrer</quote> by
4324 <literal>"Not Your Business!"</literal> wherever it appears inside a
4325 <script> tag. Note that this job won't break JavaScript syntax,
4326 since both the original and the replacement are syntactically valid
4327 string objects. The script just won't have access to the referrer
4328 information anymore.
4332 We'll show you two other jobs from the JavaScript taming department, but
4333 this time only point out the constructs of special interest:
4338 # The status bar is for displaying link targets, not pointless blahblah
4340 s/window\.status\s*=\s*['"].*?['"]/dUmMy=1/ig</screen>
4344 <literal>\s</literal> stands for whitespace characters (space, tab, newline,
4345 carriage return, form feed), so that <literal>\s*</literal> means: <quote>zero
4346 or more whitespace</quote>. The <literal>?</literal> in <literal>.*?</literal>
4347 makes this matching of arbitrary text ungreedy. (Note that the <literal>U</literal>
4348 option is not set). The <literal>['"]</literal> construct means: <quote>a single
4349 <emphasis>or</emphasis> a double quote</quote>.
4353 So what does this job do? It replaces assignments of single- or double-quoted
4354 strings to the <quote>window.status</quote> object with a dummy assignment
4355 (using a variable name that is hopefully odd enough not to conflict with
4356 real variables in scripts). Thus, it catches many cases where e.g. pointless
4357 descriptions are displayed in the status bar instead of the link target when
4358 you move your mouse over links.
4363 # Kill OnUnload popups. Yummy. Test: http://www.zdnet.com/zdsubs/yahoo/tree/yfs.html
4365 s/(<body .*)onunload(.*>)/$1never$2/iU</screen>
4370 <ulink url="http://www.w3.org/TR/2000/REC-DOM-Level-2-Events-20001113/events.html#Events-eventgroupings-htmlevents">OnUnload
4371 event binding</ulink> in the HTML DOM was a <emphasis>CRIME</emphasis>.
4372 When I close a browser window, I want it to close and die. Basta.
4373 This job replaces the <quote>onunload</quote> attribute in
4374 <quote><body></quote> tags with the dummy word <literal>never</literal>.
4375 Note that the <literal>i</literal> option makes the pattern matching
4380 The last example is from the fun department:
4385 FILTER: fun Fun text replacements
4387 # Spice the daily news:
4389 s/microsoft(?!\.com)/MicroSuck/ig</screen>
4393 Note the <literal>(?!\.com)</literal> part (a so-called negative lookahead)
4394 in the job's pattern, which means: Don't match, if the string
4395 <quote>.com</quote> appears directly following <quote>microsoft</quote>
4396 in the page. This prevents links to microsoft.com from being messed, while
4397 still replacing the word everywhere else.
4402 # Buzzword Bingo (example for extended regex syntax)
4404 s* industry[ -]leading \
4406 | award[ -]winning # Comments are OK, too! \
4407 | high[ -]performance \
4408 | solutions[ -]based \
4412 *<font color="red"><b>BINGO!</b></font> \
4417 The <literal>x</literal> option in this job turns on extended syntax, and allows for
4418 e.g. the liberal use of (non-interpreted!) whitespace for nicer formatting.
4427 <!-- ~ End section ~ -->
4431 <!-- ~~~~~ New section ~~~~~ -->
4433 <sect1 id="templates">
4434 <title>Templates</title>
4436 All <application>Privoxy</application> built-in pages, i.e. error pages such as the
4437 <ulink url="http://show-the-404-error.page"><quote>404 - No Such Domain</quote>
4438 error page</ulink>, the <ulink
4439 url="http://ads.bannerserver.example.com/nasty-ads/sponsor.html"><quote>BLOCKED</quote>
4441 and all pages of its <ulink url="http://config.privoxy.org/">web-based
4442 user interface</ulink>, are generated from <emphasis>templates</emphasis>.
4443 (<application>Privoxy</application> must be running for the above links to work as
4448 These templates are stored in a subdirectory of the <link linkend="confdir">configuration
4449 directory</link> called <filename>templates</filename>. On Unixish platforms,
4451 <ulink url="file:///etc/privoxy/templates/"><filename>/etc/privoxy/templates/</filename></ulink>.
4455 The templates are basically normal HTML files, but with place-holders (called symbols
4456 or exports), which <application>Privoxy</application> fills at run time. You can
4457 edit the templates with a normal text editor, should you want to customize them.
4458 (<emphasis>Not recommended for the casual user</emphasis>). Note that
4459 just like in configuration files, lines starting with <literal>#</literal> are
4460 ignored when the templates are filled in.
4464 The place-holders are of the form <literal>@name@</literal>, and you will
4465 find a list of available symbols, which vary from template to template,
4466 in the comments at the start of each file. Note that these comments are not
4467 always accurate, and that it's probably best to look at the existing HTML
4468 code to find out which symbols are supported and what they are filled in with.
4472 A special application of this substitution mechanism is to make whole
4473 blocks of HTML code disappear when a specific symbol is set. We use this
4474 for many purposes, one of them being to include the beta warning in all
4475 our user interface (CGI) pages when <application>Privoxy</application>
4476 in in an alpha or beta development stage:
4481 <!-- @if-unstable-start -->
4483 ... beta warning HTML code goes here ...
4485 <!-- if-unstable-end@ --></screen>
4489 If the "unstable" symbol is set, everything in between and including
4490 <literal>@if-unstable-start</literal> and <literal>if-unstable-end@</literal>
4491 will disappear, leaving nothing but an empty comment:
4495 <screen><!-- --></screen>
4499 There's also an if-then-else construct and an <literal>#include</literal>
4500 mechanism, but you'll sure find out if you are inclined to edit the
4505 All templates refer to a style located at
4506 <ulink url="http://config.privoxy.org/send-stylesheet"><literal>http://config.privoxy.org/send-stylesheet</literal></ulink>.
4507 This is, of course, locally served by <application>Privoxy</application>
4508 and the source for it can be found and edited in the
4509 <filename>cgi-style.css</filename> template.
4514 <!-- ~ End section ~ -->
4518 <!-- ~~~~~ New section ~~~~~ -->
4520 <sect1 id="contact"><title>Contacting the Developers, Bug Reporting and Feature
4523 <!-- Include contacting.sgml boilerplate: -->
4525 <!-- end boilerplate -->
4529 <!-- ~ End section ~ -->
4532 <!-- ~~~~~ New section ~~~~~ -->
4533 <sect1 id="copyright"><title><application>Privoxy</application> Copyright, License and History</title>
4535 <!-- Include copyright.sgml: -->
4537 <!-- end copyright -->
4539 <!-- ~~~~~ New section ~~~~~ -->
4540 <sect2><title>License</title>
4541 <!-- Include copyright.sgml: -->
4543 <!-- end copyright -->
4545 <!-- ~ End section ~ -->
4548 <!-- ~~~~~ New section ~~~~~ -->
4550 <sect2 id="history"><title>History</title>
4551 <!-- Include history.sgml: -->
4553 <!-- end history -->
4556 <sect2 id="authors"><title>Authors</title>
4557 <!-- Include p-authors.sgml: -->
4559 <!-- end authors -->
4564 <!-- ~ End section ~ -->
4567 <!-- ~~~~~ New section ~~~~~ -->
4568 <sect1 id="seealso"><title>See Also</title>
4569 <!-- Include seealso.sgml: -->
4571 <!-- end seealso -->
4576 <!-- ~~~~~ New section ~~~~~ -->
4577 <sect1 id="appendix"><title>Appendix</title>
4580 <!-- ~~~~~ New section ~~~~~ -->
4582 <title>Regular Expressions</title>
4584 <application>Privoxy</application> uses Perl-style <quote>regular
4585 expressions</quote> in its <link linkend="actions-file">actions
4586 files</link> and <link linkend="filter-file">filter file</link>,
4587 through the <ulink url="http://www.pcre.org/">PCRE</ulink> and
4588 <ulink url="http://www.oesterhelt.org/pcrs/">PCRS</ulink> libraries.
4592 If you are reading this, you probably don't understand what <quote>regular
4593 expressions</quote> are, or what they can do. So this will be a very brief
4594 introduction only. A full explanation would require a <ulink
4595 url="http://www.oreilly.com/catalog/regex/">book</ulink> ;-)
4599 Regular expressions provide a language to describe patterns that can be
4600 run against strings of characters (letter, numbers, etc), to see if they
4601 match the string or not. The patterns are themselves (sometimes complex)
4602 strings of literal characters, combined with wild-cards, and other special
4603 characters, called meta-characters. The <quote>meta-characters</quote> have
4604 special meanings and are used to build complex patterns to be matched against.
4605 Perl Compatible Regular Expressions are an especially convenient
4606 <quote>dialect</quote> of the regular expression language.
4610 To make a simple analogy, we do something similar when we use wild-card
4611 characters when listing files with the <command>dir</command> command in DOS.
4612 <literal>*.*</literal> matches all filenames. The <quote>special</quote>
4613 character here is the asterisk which matches any and all characters. We can be
4614 more specific and use <literal>?</literal> to match just individual
4615 characters. So <quote>dir file?.text</quote> would match
4616 <quote>file1.txt</quote>, <quote>file2.txt</quote>, etc. We are pattern
4617 matching, using a similar technique to <quote>regular expressions</quote>!
4621 Regular expressions do essentially the same thing, but are much, much more
4622 powerful. There are many more <quote>special characters</quote> and ways of
4623 building complex patterns however. Let's look at a few of the common ones,
4624 and then some examples:
4629 <emphasis>.</emphasis> - Matches any single character, e.g. <quote>a</quote>,
4630 <quote>A</quote>, <quote>4</quote>, <quote>:</quote>, or <quote>@</quote>.
4632 </simplelist></para>
4636 <emphasis>?</emphasis> - The preceding character or expression is matched ZERO or ONE
4639 </simplelist></para>
4643 <emphasis>+</emphasis> - The preceding character or expression is matched ONE or MORE
4646 </simplelist></para>
4650 <emphasis>*</emphasis> - The preceding character or expression is matched ZERO or MORE
4653 </simplelist></para>
4657 <emphasis>\</emphasis> - The <quote>escape</quote> character denotes that
4658 the following character should be taken literally. This is used where one of the
4659 special characters (e.g. <quote>.</quote>) needs to be taken literally and
4660 not as a special meta-character. Example: <quote>example\.com</quote>, makes
4661 sure the period is recognized only as a period (and not expanded to its
4662 meta-character meaning of any single character).
4664 </simplelist></para>
4668 <emphasis>[]</emphasis> - Characters enclosed in brackets will be matched if
4669 any of the enclosed characters are encountered. For instance, <quote>[0-9]</quote>
4670 matches any numeric digit (zero through nine). As an example, we can combine
4671 this with <quote>+</quote> to match any digit one of more times: <quote>[0-9]+</quote>.
4673 </simplelist></para>
4677 <emphasis>()</emphasis> - parentheses are used to group a sub-expression,
4678 or multiple sub-expressions.
4680 </simplelist></para>
4684 <emphasis>|</emphasis> - The <quote>bar</quote> character works like an
4685 <quote>or</quote> conditional statement. A match is successful if the
4686 sub-expression on either side of <quote>|</quote> matches. As an example:
4687 <quote>/(this|that) example/</quote> uses grouping and the bar character
4688 and would match either <quote>this example</quote> or <quote>that
4689 example</quote>, and nothing else.
4691 </simplelist></para>
4694 These are just some of the ones you are likely to use when matching URLs with
4695 <application>Privoxy</application>, and is a long way from a definitive
4696 list. This is enough to get us started with a few simple examples which may
4697 be more illuminating:
4701 <emphasis><literal>/.*/banners/.*</literal></emphasis> - A simple example
4702 that uses the common combination of <quote>.</quote> and <quote>*</quote> to
4703 denote any character, zero or more times. In other words, any string at all.
4704 So we start with a literal forward slash, then our regular expression pattern
4705 (<quote>.*</quote>) another literal forward slash, the string
4706 <quote>banners</quote>, another forward slash, and lastly another
4707 <quote>.*</quote>. We are building
4708 a directory path here. This will match any file with the path that has a
4709 directory named <quote>banners</quote> in it. The <quote>.*</quote> matches
4710 any characters, and this could conceivably be more forward slashes, so it
4711 might expand into a much longer looking path. For example, this could match:
4712 <quote>/eye/hate/spammers/banners/annoy_me_please.gif</quote>, or just
4713 <quote>/banners/annoying.html</quote>, or almost an infinite number of other
4714 possible combinations, just so it has <quote>banners</quote> in the path
4719 A now something a little more complex:
4723 <emphasis><literal>/.*/adv((er)?ts?|ertis(ing|ements?))?/</literal></emphasis> -
4724 We have several literal forward slashes again (<quote>/</quote>), so we are
4725 building another expression that is a file path statement. We have another
4726 <quote>.*</quote>, so we are matching against any conceivable sub-path, just so
4727 it matches our expression. The only true literal that <emphasis>must
4728 match</emphasis> our pattern is <application>adv</application>, together with
4729 the forward slashes. What comes after the <quote>adv</quote> string is the
4734 Remember the <quote>?</quote> means the preceding expression (either a
4735 literal character or anything grouped with <quote>(...)</quote> in this case)
4736 can exist or not, since this means either zero or one match. So
4737 <quote>((er)?ts?|ertis(ing|ements?))</quote> is optional, as are the
4738 individual sub-expressions: <quote>(er)</quote>,
4739 <quote>(ing|ements?)</quote>, and the <quote>s</quote>. The <quote>|</quote>
4740 means <quote>or</quote>. We have two of those. For instance,
4741 <quote>(ing|ements?)</quote>, can expand to match either <quote>ing</quote>
4742 <emphasis>OR</emphasis> <quote>ements?</quote>. What is being done here, is an
4743 attempt at matching as many variations of <quote>advertisement</quote>, and
4744 similar, as possible. So this would expand to match just <quote>adv</quote>,
4745 or <quote>advert</quote>, or <quote>adverts</quote>, or
4746 <quote>advertising</quote>, or <quote>advertisement</quote>, or
4747 <quote>advertisements</quote>. You get the idea. But it would not match
4748 <quote>advertizements</quote> (with a <quote>z</quote>). We could fix that by
4749 changing our regular expression to:
4750 <quote>/.*/adv((er)?ts?|erti(s|z)(ing|ements?))?/</quote>, which would then match
4755 <emphasis><literal>/.*/advert[0-9]+\.(gif|jpe?g)</literal></emphasis> - Again
4756 another path statement with forward slashes. Anything in the square brackets
4757 <quote>[]</quote> can be matched. This is using <quote>0-9</quote> as a
4758 shorthand expression to mean any digit one through nine. It is the same as
4759 saying <quote>0123456789</quote>. So any digit matches. The <quote>+</quote>
4760 means one or more of the preceding expression must be included. The preceding
4761 expression here is what is in the square brackets -- in this case, any digit
4762 one through nine. Then, at the end, we have a grouping: <quote>(gif|jpe?g)</quote>.
4763 This includes a <quote>|</quote>, so this needs to match the expression on
4764 either side of that bar character also. A simple <quote>gif</quote> on one side, and the other
4765 side will in turn match either <quote>jpeg</quote> or <quote>jpg</quote>,
4766 since the <quote>?</quote> means the letter <quote>e</quote> is optional and
4767 can be matched once or not at all. So we are building an expression here to
4768 match image GIF or JPEG type image file. It must include the literal
4769 string <quote>advert</quote>, then one or more digits, and a <quote>.</quote>
4770 (which is now a literal, and not a special character, since it is escaped
4771 with <quote>\</quote>), and lastly either <quote>gif</quote>, or
4772 <quote>jpeg</quote>, or <quote>jpg</quote>. Some possible matches would
4773 include: <quote>//advert1.jpg</quote>,
4774 <quote>/nasty/ads/advert1234.gif</quote>,
4775 <quote>/banners/from/hell/advert99.jpg</quote>. It would not match
4776 <quote>advert1.gif</quote> (no leading slash), or
4777 <quote>/adverts232.jpg</quote> (the expression does not include an
4778 <quote>s</quote>), or <quote>/advert1.jsp</quote> (<quote>jsp</quote> is not
4779 in the expression anywhere).
4783 We are barely scratching the surface of regular expressions here so that you
4784 can understand the default <application>Privoxy</application>
4785 configuration files, and maybe use this knowledge to customize your own
4786 installation. There is much, much more that can be done with regular
4787 expressions. Now that you know enough to get started, you can learn more on
4792 More reading on Perl Compatible Regular expressions:
4793 <ulink url="http://www.perldoc.com/perl5.6/pod/perlre.html">http://www.perldoc.com/perl5.6/pod/perlre.html</ulink>
4797 For information on regular expression based substitutions and their applications
4798 in filters, please see the <link linkend="filter-file">filter file tutorial</link>
4803 <!-- ~ End section ~ -->
4806 <!-- ~~~~~ New section ~~~~~ -->
4808 <title><application>Privoxy</application>'s Internal Pages</title>
4811 Since <application>Privoxy</application> proxies each requested
4812 web page, it is easy for <application>Privoxy</application> to
4813 trap certain special URLs. In this way, we can talk directly to
4814 <application>Privoxy</application>, and see how it is
4815 configured, see how our rules are being applied, change these
4816 rules and other configuration options, and even turn
4817 <application>Privoxy's</application> filtering off, all with
4823 The URLs listed below are the special ones that allow direct access
4824 to <application>Privoxy</application>. Of course,
4825 <application>Privoxy</application> must be running to access these. If
4826 not, you will get a friendly error message. Internet access is not
4839 <ulink url="http://config.privoxy.org/">http://config.privoxy.org/</ulink>
4843 There is a shortcut: <ulink url="http://p.p/">http://p.p/</ulink> (But it
4844 doesn't provide a fall-back to a real page, in case the request is not
4845 sent through <application>Privoxy</application>)
4851 Show information about the current configuration, including viewing and
4852 editing of actions files:
4856 <ulink url="http://config.privoxy.org/show-status">http://config.privoxy.org/show-status</ulink>
4863 Show the source code version numbers:
4867 <ulink url="http://config.privoxy.org/show-version">http://config.privoxy.org/show-version</ulink>
4874 Show the browser's request headers:
4878 <ulink url="http://config.privoxy.org/show-request">http://config.privoxy.org/show-request</ulink>
4885 Show which actions apply to a URL and why:
4889 <ulink url="http://config.privoxy.org/show-url-info">http://config.privoxy.org/show-url-info</ulink>
4896 Toggle Privoxy on or off. In this case, <quote>Privoxy</quote> continues
4897 to run, but only as a pass-through proxy, with no actions taking place:
4901 <ulink url="http://config.privoxy.org/toggle">http://config.privoxy.org/toggle</ulink>
4905 Short cuts. Turn off, then on:
4909 <ulink url="http://config.privoxy.org/toggle?set=disable">http://config.privoxy.org/toggle?set=disable</ulink>
4914 <ulink url="http://config.privoxy.org/toggle?set=enable">http://config.privoxy.org/toggle?set=enable</ulink>
4923 These may be bookmarked for quick reference. See next.
4927 <sect3 id="bookmarklets">
4928 <title>Bookmarklets</title>
4930 Below are some <quote>bookmarklets</quote> to allow you to easily access a
4931 <quote>mini</quote> version of some of <application>Privoxy's</application>
4932 special pages. They are designed for MS Internet Explorer, but should work
4933 equally well in Netscape, Mozilla, and other browsers which support
4934 JavaScript. They are designed to run directly from your bookmarks - not by
4935 clicking the links below (although that should work for testing).
4938 To save them, right-click the link and choose <quote>Add to Favorites</quote>
4939 (IE) or <quote>Add Bookmark</quote> (Netscape). You will get a warning that
4940 the bookmark <quote>may not be safe</quote> - just click OK. Then you can run the
4941 Bookmarklet directly from your favorites/bookmarks. For even faster access,
4942 you can put them on the <quote>Links</quote> bar (IE) or the <quote>Personal
4943 Toolbar</quote> (Netscape), and run them with a single click.
4952 url="javascript:void(window.open('http://config.privoxy.org/toggle?mini=y&set=enabled','ijbstatus','width=250,height=100,resizable=yes,scrollbars=no,toolbar=no,location=no,directories=no,status=no,menubar=no,copyhistory=no').focus());">Privoxy - Enable</ulink>
4959 url="javascript:void(window.open('http://config.privoxy.org/toggle?mini=y&set=disabled','ijbstatus','width=250,height=100,resizable=yes,scrollbars=no,toolbar=no,location=no,directories=no,status=no,menubar=no,copyhistory=no').focus());">Privoxy - Disable</ulink>
4966 url="javascript:void(window.open('http://config.privoxy.org/toggle?mini=y&set=toggle','ijbstatus','width=250,height=100,resizable=yes,scrollbars=no,toolbar=no,location=no,directories=no,status=no,menubar=no,copyhistory=no').focus());">Privoxy - Toggle Privoxy</ulink> (Toggles between enabled and disabled)
4973 url="javascript:void(window.open('http://config.privoxy.org/toggle?mini=y','ijbstatus','width=250,height=2,resizable=yes,scrollbars=no,toolbar=no,location=no,directories=no,status=no,menubar=no,copyhistory=no').focus());">Privoxy- View Status</ulink>
4979 <ulink url="javascript:w=Math.floor(screen.width/2);h=Math.floor(screen.height*0.9);void(window.open('http://www.privoxy.org/actions/index.php?url='+escape(location.href),'Feedback','screenx='+w+',width='+w+',height='+h+',scrollbars=yes,toolbar=no,location=no,directories=no,status=no,menubar=no,copyhistory=no').focus());">Privoxy - Submit Actions File Feedback</ulink>
4984 <ulink url="javascript:void(window.open('http://config.privoxy.org/show-url-info?url='+escape(location.href),'Why').focus());">Privoxy - Why?</ulink>
4991 Credit: The site which gave us the general idea for these bookmarklets is
4992 <ulink url="http://www.bookmarklets.com">www.bookmarklets.com</ulink>. They
4993 have more information about bookmarklets.
5002 <!-- ~~~~~ New section ~~~~~ -->
5004 <title>Chain of Events</title>
5006 Let's take a quick look at the basic sequence of events when a web page is
5007 requested by your browser and <application>Privoxy</application> is on duty:
5014 First, your web browser requests a web page. The browser knows to send
5015 the request to <application>Privoxy</application>, which will in turn,
5016 relay the request to the remote web server after passing the following
5022 <application>Privoxy</application> traps any request for its own internal CGI
5023 pages (e.g http://p.p/) and sends the CGI page back to the browser.
5028 Next, <application>Privoxy</application> checks to see if the URL
5030 linkend="BLOCK"><quote>+block</quote></link> patterns. If
5031 so, the URL is then blocked, and the remote web server will not be contacted.
5032 <link linkend="HANDLE-AS-IMAGE"><quote>+handle-as-image</quote></link>
5033 is then checked and if it does not match, an
5034 HTML <quote>BLOCKED</quote> page is sent back. Otherwise, if it does match,
5035 an image is returned. The type of image depends on the setting of <link
5036 linkend="SET-IMAGE-BLOCKER"><quote>+set-image-blocker</quote></link>
5037 (blank, checkerboard pattern, or an HTTP redirect to an image elsewhere).
5042 Untrusted URLs are blocked. If URLs are being added to the
5043 <filename>trust</filename> file, then that is done.
5048 If the URL pattern matches the <link
5049 linkend="FAST-REDIRECTS"><quote>+fast-redirects</quote></link> action,
5050 it is then processed. Unwanted parts of the requested URL are stripped.
5055 Now the rest of the client browser's request headers are processed. If any
5056 of these match any of the relevant actions (e.g. <link
5057 linkend="HIDE-USER-AGENT"><quote>+hide-user-agent</quote></link>,
5058 etc.), headers are suppressed or forged as determined by these actions and
5064 Now the web server starts sending its response back (i.e. typically a web page and related
5070 First, the server headers are read and processed to determine, among other
5071 things, the MIME type (document type) and encoding. The headers are then
5072 filtered as deterimined by the
5073 <link linkend="CRUNCH-INCOMING-COOKIES"><quote>+crunch-incoming-cookies</quote></link>,
5074 <link linkend="SESSION-COOKIES-ONLY"><quote>+session-cookies-only</quote></link>,
5075 and <link linkend="DOWNGRADE-HTTP-VERSION"><quote>+downgrade-http-version</quote></link>
5081 If the <link linkend="KILL-POPUPS"><quote>+kill-popups</quote></link>
5082 action applies, and it is an HTML or JavaScript document, the popup-code in the
5083 response is filtered on-the-fly as it is received.
5088 If a <link linkend="FILTER"><quote>+filter</quote></link>
5090 linkend="DEANIMATE-GIFS"><quote>+deanimate-gifs</quote></link>
5091 action applies (and the document type fits the action), the rest of the page is
5092 read into memory (up to a configurable limit). Then the filter rules (from
5093 <filename>default.filter</filename>) are processed against the buffered
5094 content. Filters are applied in the order they are specified in the
5095 <filename>default.filter</filename> file. Animated GIFs, if present, are
5096 reduced to either the first or last frame, depending on the action
5097 setting.The entire page, which is now filtered, is then sent by
5098 <application>Privoxy</application> back to your browser.
5101 If neither <link linkend="FILTER"><quote>+filter</quote></link>
5103 linkend="DEANIMATE-GIFS"><quote>+deanimate-gifs</quote></link>
5104 matches, then <application>Privoxy</application> passes the raw data through
5105 to the client browser as it becomes available.
5110 As the browser receives the now (probably filtered) page content, it
5111 reads and then requests any URLs that may be embedded within the page
5112 source, e.g. ad images, stylesheets, JavaScript, other HTML documents (e.g.
5113 frames), sounds, etc. For each of these objects, the browser issues a new
5114 request. And each such request is in turn processed as above. Note that a
5115 complex web page may have many such embedded URLs.
5125 <!-- ~~~~~ New section ~~~~~ -->
5126 <sect2 id="actionsanat">
5127 <title>Anatomy of an Action</title>
5130 The way <application>Privoxy</application> applies
5131 <link linkend="ACTIONS">actions</link> and <link linkend="FILTER">filters</link>
5132 to any given URL can be complex, and not always so
5133 easy to understand what is happening. And sometimes we need to be able to
5134 <emphasis>see</emphasis> just what <application>Privoxy</application> is
5135 doing. Especially, if something <application>Privoxy</application> is doing
5136 is causing us a problem inadvertently. It can be a little daunting to look at
5137 the actions and filters files themselves, since they tend to be filled with
5138 <link linkend="regex">regular expressions</link> whose consequences are not
5143 One quick test to see if <application>Privoxy</application> is causing a problem
5144 or not, is to disable it temporarily. This should be the first troubleshooting
5145 step. See <link linkend="bookmarklets">the Bookmarklets</link> section on a quick
5146 and easy way to do this (be sure to flush caches afterward!).
5150 <application>Privoxy</application> also provides the
5151 <ulink url="http://config.privoxy.org/show-url-info">http://config.privoxy.org/show-url-info</ulink>
5152 page that can show us very specifically how <application>actions</application>
5153 are being applied to any given URL. This is a big help for troubleshooting.
5157 First, enter one URL (or partial URL) at the prompt, and then
5158 <application>Privoxy</application> will tell us
5159 how the current configuration will handle it. This will not
5160 help with filtering effects (i.e. the <link
5161 linkend="FILTER"><quote>+filter</quote></link> action) from
5162 the <filename>default.filter</filename> file since this is handled very
5163 differently and not so easy to trap! It also will not tell you about any other
5164 URLs that may be embedded within the URL you are testing. For instance, images
5165 such as ads are expressed as URLs within the raw page source of HTML pages. So
5166 you will only get info for the actual URL that is pasted into the prompt area
5167 -- not any sub-URLs. If you want to know about embedded URLs like ads, you
5168 will have to dig those out of the HTML source. Use your browser's <quote>View
5169 Page Source</quote> option for this. Or right click on the ad, and grab the
5174 Let's try an example, <ulink url="http://google.com">google.com</ulink>,
5175 and look at it one section at a time:
5180 Matches for http://google.com:
5182 In file: default.action <guibutton>[ View ]</guibutton> <guibutton>[ Edit ]</guibutton>
5186 -crunch-outgoing-cookies
5187 -crunch-incoming-cookies
5188 +deanimate-gifs{last}
5189 -downgrade-http-version
5193 -filter{shockwave-flash}
5194 -filter{crude-parental}
5195 +filter{html-annoyances}
5196 +filter{js-annoyances}
5197 +filter{content-cookies}
5199 +filter{refresh-tags}
5201 +filter{banners-by-size}
5202 +hide-forwarded-for-headers
5203 +hide-from-header{block}
5204 +hide-referer{forge}
5209 +prevent-compression
5212 +session-cookies-only
5213 +set-image-blocker{pattern} }
5216 { -session-cookies-only }
5222 In file: user.action <guibutton>[ View ]</guibutton> <guibutton>[ Edit ]</guibutton>
5223 (no matches in this file)
5228 This tells us how we have defined our
5229 <link linkend="ACTIONS"><quote>actions</quote></link>, and
5230 which ones match for our example, <quote>google.com</quote>. The first listing
5231 is any matches for the <filename>standard.action</filename> file. No hits at
5232 all here on <quote>standard</quote>. Then next is <quote>default</quote>, or
5233 our <filename>default.action</filename> file. The large, multi-line listing,
5234 is how the actions are set to match for all URLs, i.e. our default settings.
5235 If you look at your <quote>actions</quote> file, this would be the section
5236 just below the <quote>aliases</quote> section near the top. This will apply to
5237 all URLs as signified by the single forward slash at the end of the listing
5238 -- <quote>/</quote>.
5242 But we can define additional actions that would be exceptions to these general
5243 rules, and then list specific URLs (or patterns) that these exceptions would
5244 apply to. Last match wins. Just below this then are two explicit matches for
5245 <quote>.google.com</quote>. The first is negating our previous cookie setting,
5247 linkend="SESSION-COOKIES-ONLY"><quote>+session-cookies-only</quote></link>
5248 (i.e. not persistent). So we will allow persistent cookies for google. The
5249 second turns <emphasis>off</emphasis> any
5251 linkend="FAST-REDIRECTS"><quote>+fast-redirects</quote></link>
5252 action, allowing this to take place unmolested. Note that there is a leading
5253 dot here -- <quote>.google.com</quote>. This will match any hosts and
5254 sub-domains, in the google.com domain also, such as
5255 <quote>www.google.com</quote>. So, apparently, we have these two actions
5256 defined somewhere in the lower part of our <filename>default.action</filename>
5257 file, and <quote>google.com</quote> is referenced somewhere in these latter
5262 Then, for our <filename>user.action</filename> file, we again have no hits.
5266 And finally we pull it all together in the bottom section and summarize how
5267 <application>Privoxy</application> is applying all its <quote>actions</quote>
5268 to <quote>google.com</quote>:
5279 -crunch-outgoing-cookies
5280 -crunch-incoming-cookies
5281 +deanimate-gifs{last}
5282 -downgrade-http-version
5286 -filter{shockwave-flash}
5287 -filter{crude-parental}
5288 +filter{html-annoyances}
5289 +filter{js-annoyances}
5290 +filter{content-cookies}
5292 +filter{refresh-tags}
5294 +filter{banners-by-size}
5295 +hide-forwarded-for-headers
5296 +hide-from-header{block}
5297 +hide-referer{forge}
5302 +prevent-compression
5305 -session-cookies-only
5306 +set-image-blocker{pattern}
5311 Notice the only difference here to the previous listing, is to
5312 <quote>fast-redirects</quote> and <quote>session-cookies-only</quote>.
5316 Now another example, <quote>ad.doubleclick.net</quote>:
5322 { +block +handle-as-image }
5325 { +block +handle-as-image }
5328 { +block +handle-as-image }
5334 We'll just show the interesting part here, the explicit matches. It is
5335 matched three different times. Each as an <quote>+block +handle-as-image</quote>,
5336 which is the expanded form of one of our aliases that had been defined as:
5337 <quote>+imageblock</quote>. (<link
5338 linkend="ALIASES"><quote>Aliases</quote></link> are defined in
5339 the first section of the actions file and typically used to combine more
5344 Any one of these would have done the trick and blocked this as an unwanted
5345 image. This is unnecessarily redundant since the last case effectively
5346 would also cover the first. No point in taking chances with these guys
5347 though ;-) Note that if you want an ad or obnoxious
5348 URL to be invisible, it should be defined as <quote>ad.doubleclick.net</quote>
5349 is done here -- as both a <link
5350 linkend="BLOCK"><quote>+block</quote></link>
5351 <emphasis>and</emphasis> an
5353 linkend="HANDLE-AS-IMAGE"><quote>+handle-as-image</quote></link>.
5354 The custom alias <quote>+imageblock</quote> just simplifies the process and make
5359 One last example. Let's try <quote>http://www.rhapsodyk.net/adsl/HOWTO/</quote>.
5360 This one is giving us problems. We are getting a blank page. Hmmm ...
5366 Matches for http://www.rhapsodyk.net/adsl/HOWTO/:
5368 In file: default.action <guibutton>[ View ]</guibutton> <guibutton>[ Edit ]</guibutton>
5372 -crunch-incoming-cookies
5373 -crunch-outgoing-cookies
5375 -downgrade-http-version
5377 +filter{html-annoyances}
5378 +filter{js-annoyances}
5379 +filter{kill-popups}
5382 +filter{banners-by-size}
5385 +hide-forwarded-for-headers
5386 +hide-from-header{block}
5387 +hide-referer{forge}
5391 +prevent-compression
5394 +session-cookies-only
5395 +set-image-blocker{blank} }
5398 { +block +handle-as-image }
5404 Ooops, the <quote>/adsl/</quote> is matching <quote>/ads</quote>! But
5405 we did not want this at all! Now we see why we get the blank page. We could
5406 now add a new action below this that explicitly does <emphasis>not</emphasis>
5407 block (<quote>{-block}</quote>) paths with <quote>adsl</quote>. There are
5408 various ways to handle such exceptions. Example:
5420 Now the page displays ;-) Be sure to flush your browser's caches when
5421 making such changes. Or, try using <literal>Shift+Reload</literal>.
5425 But now what about a situation where we get no explicit matches like
5432 { +block +handle-as-image }
5438 That actually was very telling and pointed us quickly to where the problem
5439 was. If you don't get this kind of match, then it means one of the default
5440 rules in the first section is causing the problem. This would require some
5441 guesswork, and maybe a little trial and error to isolate the offending rule.
5442 One likely cause would be one of the <quote>{+filter}</quote> actions. Try
5443 adding the URL for the site to one of aliases that turn off <quote>+filter</quote>:
5451 .worldpay.com # for quietpc.com
5459 <quote>{shop}</quote> is an <quote>alias</quote> that expands to
5460 <quote>{ -filter -session-cookies-only }</quote>.
5461 Or you could do your own exception to negate filtering:
5474 This would probably be most appropriately put in <filename>user.action</filename>,
5475 for local site exceptions.
5479 <quote>{fragile}</quote> is an alias that disables most actions. This can be
5480 used as a last resort for problem sites. Remember to flush caches! If this
5481 still does not work, you will have to go through the remaining actions one by
5482 one to find which one(s) is causing the problem.
5491 This program is free software; you can redistribute it
5492 and/or modify it under the terms of the GNU General
5493 Public License as published by the Free Software
5494 Foundation; either version 2 of the License, or (at
5495 your option) any later version.
5497 This program is distributed in the hope that it will
5498 be useful, but WITHOUT ANY WARRANTY; without even the
5499 implied warranty of MERCHANTABILITY or FITNESS FOR A
5500 PARTICULAR PURPOSE. See the GNU General Public
5501 License for more details.
5503 The GNU General Public License should be included with
5504 this file. If not, you can view it at
5505 http://www.gnu.org/copyleft/gpl.html
5506 or write to the Free Software Foundation, Inc., 59
5507 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
5509 $Log: user-manual.sgml,v $
5510 Revision 1.125 2002/06/03 00:28:17 hal9
5511 Sync with various changes from 3.0 branch. Add two new files for config stuff.
5513 Revision 1.123.2.5 2002/05/29 02:01:02 hal9
5514 This is break out of the entire config section from u-m, so it can
5515 eventually be used to generate the comments, etc in the main config file
5516 so that these are in sync with each other.
5518 Revision 1.123.2.4 2002/05/27 03:28:45 hal9
5519 Ooops missed something from David.
5521 Revision 1.123.2.3 2002/05/27 03:23:17 hal9
5522 Fix FIXMEs for OS2 and OSX startup. Fix Redhat typos (should be Red Hat).
5523 That's a wrap, I think.
5525 Revision 1.123.2.2 2002/05/26 19:02:09 hal9
5526 Move Amiga stuff around to take of FIXME in start up section.
5528 Revision 1.123.2.1 2002/05/26 17:04:25 hal9
5529 -Spellcheck, very minor edits, and sync across branches
5531 Revision 1.123 2002/05/24 23:19:23 hal9
5532 Include new image (Proxy setup). More fun with guibutton.
5533 Minor corrections/clarifications here and there.
5535 Revision 1.122 2002/05/24 13:24:08 oes
5536 Added Bookmarklet for one-click pre-filled access to show-url-info
5538 Revision 1.121 2002/05/23 23:20:17 oes
5539 - Changed more (all?) references to actions to the
5540 <literal><link> style.
5541 - Small fixes in the actions chapter
5542 - Small clarifications in the quickstart to ad blocking
5543 - Removed <emphasis> from <title>s since the new doc CSS
5544 renders them red (bad in TOC).
5546 Revision 1.120 2002/05/23 19:16:43 roro
5547 Correct Debian specials (installation and startup).
5549 Revision 1.119 2002/05/22 17:17:05 oes
5552 Revision 1.118 2002/05/21 04:54:55 hal9
5553 -New Section: Quickstart to Ad Blocking
5554 -Reformat Actions Anatomy to match new CGI layout
5556 Revision 1.117 2002/05/17 13:56:16 oes
5557 - Reworked & extended Templates chapter
5558 - Small changes to Regex appendix
5559 - #included authors.sgml into (C) and hist chapter
5561 Revision 1.116 2002/05/17 03:23:46 hal9
5562 Fixing merge conflict in Quickstart section.
5564 Revision 1.115 2002/05/16 16:25:00 oes
5565 Extended the Filter File chapter & minor fixes
5567 Revision 1.114 2002/05/16 09:42:50 oes
5568 More ulink->link, added some hints to Quickstart section
5570 Revision 1.113 2002/05/15 21:07:25 oes
5571 Extended and further commented the example actions files
5573 Revision 1.112 2002/05/15 03:57:14 hal9
5574 Spell check. A few minor edits here and there for better syntax and
5577 Revision 1.111 2002/05/14 23:01:36 oes
5580 Revision 1.110 2002/05/14 19:10:45 oes
5581 Restored alphabetical order of actions
5583 Revision 1.109 2002/05/14 17:23:11 oes
5584 Renamed the prevent-*-cookies actions, extended aliases section and moved it before the example AFs
5586 Revision 1.108 2002/05/14 15:29:12 oes
5587 Completed proofreading the actions chapter
5589 Revision 1.107 2002/05/12 03:20:41 hal9
5590 Small clarifications for 127.0.0.1 vs localhost for listen-address since this
5591 apparently an important distinction for some OS's.
5593 Revision 1.106 2002/05/10 01:48:20 hal9
5594 This is mostly proposed copyright/licensing additions and changes. Docs
5595 are still GPL, but licensing and copyright are more visible. Also, copyright
5596 changed in doc header comments (eliminate references to JB except FAQ).
5598 Revision 1.105 2002/05/05 20:26:02 hal9
5599 Sorting out license vs copyright in these docs.
5601 Revision 1.104 2002/05/04 08:44:45 swa
5604 Revision 1.103 2002/05/04 00:40:53 hal9
5605 -Remove the TOC first page kludge. It's fixed proper now in ldp.dsl.in.
5606 -Some minor additions to Quickstart.
5608 Revision 1.102 2002/05/03 17:46:00 oes
5609 Further proofread & reactivated short build instructions
5611 Revision 1.101 2002/05/03 03:58:30 hal9
5612 Move the user-manual config directive to top of section. Add note about
5613 Privoxy needing read permissions for configs, and write for logs.
5615 Revision 1.100 2002/04/29 03:05:55 hal9
5616 Add clarification on differences of new actions files.
5618 Revision 1.99 2002/04/28 16:59:05 swa
5619 more structure in starting section
5621 Revision 1.98 2002/04/28 05:43:59 hal9
5622 This is the break up of configuration.html into multiple files. This
5623 will probably break links elsewhere :(
5625 Revision 1.97 2002/04/27 21:04:42 hal9
5626 -Rewrite of Actions File example.
5627 -Add section for user-manual directive in config.
5629 Revision 1.96 2002/04/27 05:32:00 hal9
5630 -Add short section to Filter Files to tie in with +filter action.
5631 -Start rewrite of examples in Actions Examples (not finished).
5633 Revision 1.95 2002/04/26 17:23:29 swa
5634 bookmarks cleaned, changed structure of user manual, screen and programlisting cleanups, and numerous other changes that I forgot
5636 Revision 1.94 2002/04/26 05:24:36 hal9
5637 -Add most of Andreas suggestions to Chain of Events section.
5638 -A few other minor corrections and touch up.
5640 Revision 1.92 2002/04/25 18:55:13 hal9
5641 More catchups on new actions files, and new actions names.
5642 Other assorted cleanups, and minor modifications.
5644 Revision 1.91 2002/04/24 02:39:31 hal9
5645 Add 'Chain of Events' section.
5647 Revision 1.90 2002/04/23 21:41:25 hal9
5648 Linuxconf is deprecated on RH, substitute chkconfig.
5650 Revision 1.89 2002/04/23 21:05:28 oes
5651 Added hint for startup on Red Hat
5653 Revision 1.88 2002/04/23 05:37:54 hal9
5654 Add AmigaOS install stuff.
5656 Revision 1.87 2002/04/23 02:53:15 david__schmidt
5657 Updated OSX installation section
5658 Added a few English tweaks here an there
5660 Revision 1.86 2002/04/21 01:46:32 hal9
5661 Re-write actions section.
5663 Revision 1.85 2002/04/18 21:23:23 hal9
5664 Fix ugly typo (mine).
5666 Revision 1.84 2002/04/18 21:17:13 hal9
5667 Spell Redhat correctly (ie Red Hat). A few minor grammar corrections.
5669 Revision 1.83 2002/04/18 18:21:12 oes
5670 Added RPM install detail
5672 Revision 1.82 2002/04/18 12:04:50 oes
5675 Revision 1.81 2002/04/18 11:50:24 oes
5676 Extended Install section - needs fixing by packagers
5678 Revision 1.80 2002/04/18 10:45:19 oes
5679 Moved text to buildsource.sgml, renamed some filters, details
5681 Revision 1.79 2002/04/18 03:18:06 hal9
5682 Spellcheck, and minor touchups.
5684 Revision 1.78 2002/04/17 18:04:16 oes
5687 Revision 1.77 2002/04/17 13:51:23 oes
5688 Proofreading, part one
5690 Revision 1.76 2002/04/16 04:25:51 hal9
5691 -Added 'Note to Upgraders' and re-ordered the 'Quickstart' section.
5692 -Note about proxy may need requests to re-read config files.
5694 Revision 1.75 2002/04/12 02:08:48 david__schmidt
5695 Remove OS/2 building info... it is already in the developer-manual
5697 Revision 1.74 2002/04/11 00:54:38 hal9
5698 Add small section on submitting actions.
5700 Revision 1.73 2002/04/10 18:45:15 swa
5703 Revision 1.72 2002/04/10 04:06:19 hal9
5704 Added actions feedback to Bookmarklets section
5706 Revision 1.71 2002/04/08 22:59:26 hal9
5707 Version update. Spell chkconfig correctly :)
5709 Revision 1.70 2002/04/08 20:53:56 swa
5712 Revision 1.69 2002/04/06 05:07:29 hal9
5713 -Add privoxy-man-page.sgml, for man page.
5714 -Add authors.sgml for AUTHORS (and p-authors.sgml)
5715 -Reworked various aspects of various docs.
5716 -Added additional comments to sub-docs.
5718 Revision 1.68 2002/04/04 18:46:47 swa
5719 consistent look. reuse of copyright, history et. al.
5721 Revision 1.67 2002/04/04 17:27:57 swa
5722 more single file to be included at multiple points. make maintaining easier
5724 Revision 1.66 2002/04/04 06:48:37 hal9
5725 Structural changes to allow for conditional inclusion/exclusion of content
5726 based on entity toggles, e.g. 'entity % p-not-stable "INCLUDE"'. And
5727 definition of internal entities, e.g. 'entity p-version "2.9.13"' that will
5728 eventually be set by Makefile.
5729 More boilerplate text for use across multiple docs.
5731 Revision 1.65 2002/04/03 19:52:07 swa
5732 enhance squid section due to user suggestion
5734 Revision 1.64 2002/04/03 03:53:43 hal9
5735 A few minor bug fixes, and touch ups. Ready for review.
5737 Revision 1.63 2002/04/01 16:24:49 hal9
5738 Define entities to include boilerplate text. See doc/source/*.
5740 Revision 1.62 2002/03/30 04:15:53 hal9
5741 - Fix privoxy.org/config links.
5742 - Paste in Bookmarklets from Toggle page.
5743 - Move Quickstart nearer top, and minor rework.
5745 Revision 1.61 2002/03/29 01:31:08 hal9
5748 Revision 1.60 2002/03/27 01:57:34 hal9
5749 Added more to Anatomy section.
5751 Revision 1.59 2002/03/27 00:54:33 hal9
5752 Touch up intro for new name.
5754 Revision 1.58 2002/03/26 22:29:55 swa
5755 we have a new homepage!
5757 Revision 1.57 2002/03/24 20:33:30 hal9
5758 A few minor catch ups with name change.
5760 Revision 1.56 2002/03/24 16:17:06 swa
5761 configure needs to be generated.
5763 Revision 1.55 2002/03/24 16:08:08 swa
5764 we are too lazy to make a block-built
5765 privoxy logo. hence removed the option.
5767 Revision 1.54 2002/03/24 15:46:20 swa
5768 name change related issue.
5770 Revision 1.53 2002/03/24 11:51:00 swa
5771 name change. changed filenames.
5773 Revision 1.52 2002/03/24 11:01:06 swa
5776 Revision 1.51 2002/03/23 15:13:11 swa
5777 renamed every reference to the old name with foobar.
5778 fixed "application foobar application" tag, fixed
5779 "the foobar" with "foobar". left junkbustser in cvs
5780 comments and remarks to history untouched.
5782 Revision 1.50 2002/03/23 05:06:21 hal9
5785 Revision 1.49 2002/03/21 17:01:05 hal9
5786 New section in Appendix.
5788 Revision 1.48 2002/03/12 06:33:01 hal9
5789 Catching up to Andreas and re_filterfile changes.
5791 Revision 1.47 2002/03/11 13:13:27 swa
5792 correct feedback channels
5794 Revision 1.46 2002/03/10 00:51:08 hal9
5795 Added section on JB internal pages in Appendix.
5797 Revision 1.45 2002/03/09 17:43:53 swa
5800 Revision 1.44 2002/03/09 17:08:48 hal9
5801 New section on Jon's actions file editor, and move some stuff around.
5803 Revision 1.43 2002/03/08 00:47:32 hal9
5804 Added imageblock{pattern}.
5806 Revision 1.42 2002/03/07 18:16:55 swa
5809 Revision 1.41 2002/03/07 16:46:43 hal9
5810 Fix a few markup problems for jade.
5812 Revision 1.40 2002/03/07 16:28:39 swa
5813 provide correct feedback channels
5815 Revision 1.39 2002/03/06 16:19:28 hal9
5816 Note on perceived filtering slowdown per FR.
5818 Revision 1.38 2002/03/05 23:55:14 hal9
5819 Stupid I did it again. Double hyphen in comment breaks jade.
5821 Revision 1.37 2002/03/05 23:53:49 hal9
5822 jade barfs on '- -' embedded in comments. - -user option broke it.
5824 Revision 1.36 2002/03/05 22:53:28 hal9
5825 Add new - - user option.
5827 Revision 1.35 2002/03/05 00:17:27 hal9
5828 Added section on command line options.
5830 Revision 1.34 2002/03/04 19:32:07 oes
5831 Changed default port to 8118
5833 Revision 1.33 2002/03/03 19:46:13 hal9
5834 Emphasis on where/how to report bugs, etc
5836 Revision 1.32 2002/03/03 09:26:06 joergs
5837 AmigaOS changes, config is now loaded from PROGDIR: instead of
5838 AmiTCP:db/junkbuster/ if no configuration file is specified on the
5841 Revision 1.31 2002/03/02 22:45:52 david__schmidt
5844 Revision 1.30 2002/03/02 22:00:14 hal9
5845 Updated 'New Features' list. Ran through spell-checker.
5847 Revision 1.29 2002/03/02 20:34:07 david__schmidt
5848 Update OS/2 build section
5850 Revision 1.28 2002/02/24 14:34:24 jongfoster
5851 Formatting changes. Now changing the doctype to DocBook XML 4.1
5852 will work - no other changes are needed.
5854 Revision 1.27 2002/01/11 14:14:32 hal9
5855 Added a very short section on Templates
5857 Revision 1.26 2002/01/09 20:02:50 hal9
5858 Fix bug re: auto-detect config file changes.
5860 Revision 1.25 2002/01/09 18:20:30 hal9
5861 Touch ups for *.action files.
5863 Revision 1.24 2001/12/02 01:13:42 hal9
5866 Revision 1.23 2001/12/02 00:20:41 hal9
5867 Updates for recent changes.
5869 Revision 1.22 2001/11/05 23:57:51 hal9
5870 Minor update for startup now daemon mode.
5872 Revision 1.21 2001/10/31 21:11:03 hal9
5873 Correct 2 minor errors
5875 Revision 1.18 2001/10/24 18:45:26 hal9
5876 *** empty log message ***
5878 Revision 1.17 2001/10/24 17:10:55 hal9
5879 Catching up with Jon's recent work, and a few other things.
5881 Revision 1.16 2001/10/21 17:19:21 swa
5882 wrong url in documentation
5884 Revision 1.15 2001/10/14 23:46:24 hal9
5885 Various minor changes. Fleshed out SEE ALSO section.
5887 Revision 1.13 2001/10/10 17:28:33 hal9
5890 Revision 1.12 2001/09/28 02:57:04 hal9
5893 Revision 1.11 2001/09/28 02:25:20 hal9
5896 Revision 1.9 2001/09/27 23:50:29 hal9
5897 A few changes. A short section on regular expression in appendix.
5899 Revision 1.8 2001/09/25 00:34:59 hal9
5900 Some additions, and re-arranging.
5902 Revision 1.7 2001/09/24 14:31:36 hal9
5905 Revision 1.6 2001/09/24 14:10:32 hal9
5906 Including David's OS/2 installation instructions.
5908 Revision 1.2 2001/09/13 15:27:40 swa
5911 Revision 1.1 2001/09/12 15:36:41 swa
5912 source files for junkbuster documentation
5914 Revision 1.3 2001/09/10 17:43:59 swa
5915 first proposal of a structure.
5917 Revision 1.2 2001/06/13 14:28:31 swa
5918 docs should have an author.
5920 Revision 1.1 2001/06/13 14:20:37 swa
5921 first import of project's documentation for the webserver.
projects / privoxy.git / blob