1 <!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook V3.1//EN" [
2 <!entity % dummy "INCLUDE">
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">
9 File : $Source: /cvsroot/ijbswa/current/doc/source/user-manual.sgml,v $
12 This file belongs into
13 ijbswa.sourceforge.net:/home/groups/i/ij/ijbswa/htdocs/
15 $Id: user-manual.sgml,v 1.63 2002/04/01 16:24:49 hal9 Exp $
17 Written by and Copyright (C) 2001 the SourceForge
18 Privoxy team. http://www.privoxy.org/
20 Based on the Internet Junkbuster originally written
21 by and Copyright (C) 1997 Anonymous Coders and
22 Junkbusters Corporation. http://www.junkbusters.com
26 Sat 03/02/02 04:53:47 PM
28 This should be ready for BETA release.
30 Hal Burgiss <hal@foobox.net>
35 <title>Privoxy User Manual</title>
37 <pubdate>$Id: user-manual.sgml,v 1.63 2002/04/01 16:24:49 hal9 Exp $</pubdate>
42 <orgname>By: Privoxy Developers</orgname>
51 This is here to keep vim syntax file from breaking :/
52 If I knew enough to fix it, I would.
53 PLEASE DO NOT REMOVE! HB: hal@foobox.net
59 The user manual gives users information on how to install, configure and use
60 <application>Privoxy</application>. <application>Privoxy</application> is a
61 web proxy with advanced filtering capabilities for protecting privacy,
62 filtering web page content, managing cookies, controlling access, and
63 removing ads, banners, pop-ups and other obnoxious Internet
64 Junk. <application>Privoxy</application> has a very flexible configuration
65 and can be customized to suit individual needs and
66 tastes. <application>Privoxy</application> has application for both
67 stand-alone systems and multi-user networks.
70 You can find the latest version of the user manual at <ulink url="http://www.privoxy.org/user-manual/">http://www.privoxy.org/user-manual/</ulink>.
74 <!-- Feel free to send a note to the developers at <email>ijbswa-developers@lists.sourceforge.net</email>. -->
81 <!-- ~~~~~ New section ~~~~~ -->
83 <sect1 id="introduction"><title>Introduction</title>
85 Include privoxy.sgml boilerplate:
90 This documentation is included with the current BETA version of
91 <application>Privoxy</application> and is mostly complete at this
92 point. The most up to date reference for the time being is still the comments
93 in the source files and in the individual configuration files. Development
94 of version 3.0 is currently nearing completion, and includes many significant
95 changes and enhancements over earlier versions. The target release date for
96 stable v3.0 is <quote>soon</quote> ;-)
100 Since this is a BETA version, not all new features are well tested. This
101 documentation may be slightly out of sync as a result (especially with
102 CVS sources). And there <emphasis>may be</emphasis> bugs, though hopefully
107 <!-- ~~~~~ New section ~~~~~ -->
109 <title>New Features</title>
111 In addition to <application>Internet Junkbuster's</application> traditional
112 feature of ad and banner blocking and cookie management,
113 <application>Privoxy</application> provides new features, some of them
114 currently under development:
118 Include newfeatures.sgml here:
127 <!-- ~ End section ~ -->
130 <!-- ~~~~~ New section ~~~~~ -->
131 <sect1 id="installation"><title>Installation</title>
133 <application>Privoxy</application> is available as raw source code, or
134 pre-compiled binaries. See the <ulink
135 url="http://sourceforge.net/projects/ijbswa/">Privoxy Home Page</ulink>
136 for binaries and current release info. <application>Privoxy</application>
137 is also available via <ulink
138 url="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/ijbswa/current/">CVS</ulink>.
139 This is the recommended approach at this time. But please be aware that CVS
140 is constantly changing, and it may break in mysterious ways.
143 <!-- ~~~~~ New section ~~~~~ -->
144 <sect2 id="installation-source"><title>Source</title>
146 For gzipped tar archives, unpack the source:
151 tar xzvf privoxy-2.9.13-beta-src* [.tgz or .tar.gz]
152 cd privoxy-2.9.13-beta
157 For retrieving the current CVS sources, you'll need the CVS
158 package installed first. To download CVS source:
163 cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
164 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa co current
170 This will create a directory named <filename>current/</filename>, which will
171 contain the source tree.
175 Then, in either case, to build from tarball/CVS source:
180 ./configure (--help to see options)
181 make (the make from gnu, gmake for *BSD)
183 make -n install (to see where all the files will go)
184 make install (to really install)
189 For Redhat and SuSE Linux RPM packages, see below.
195 <!-- ~~~~~ New section ~~~~~ -->
196 <sect2 id="installation-rh"><title>Red Hat</title>
198 To build Redhat RPM packages, install source as above. Then:
211 This will create both binary and src RPMs in the usual places. Example:
215 /usr/src/redhat/RPMS/i686/privoxy-2.9.11-1.i686.rpm
218 /usr/src/redhat/SRPMS/privoxy-2.9.11-1.src.rpm
222 To install, of course:
227 rpm -Uvv /usr/src/redhat/RPMS/i686/privoxy-2.9.11-1.i686.rpm
232 This will place the <application>Privoxy</application> configuration
233 files in <filename>/etc/privoxy/</filename>, and log files in
234 <filename>/var/log/privoxy/</filename>.
239 <!-- ~~~~~ New section ~~~~~ -->
240 <sect2 id="installation-suse"><title>SuSE</title>
242 To build SuSE RPM packages, install source as above. Then:
255 This will create both binary and src RPMs in the usual places. Example:
259 /usr/src/packages/RPMS/i686/privoxy-2.9.11-1.i686.rpm
262 /usr/src/packages/SRPMS/privoxy-2.9.11-1.src.rpm
266 To install, of course:
271 rpm -Uvv /usr/src/packages/RPMS/i686/privoxy-2.9.11-1.i686.rpm
276 This will place the <application>Privoxy</application> configuration
277 files in <filename>/etc/privoxy/</filename>, and log files in
278 <filename>/var/log/privoxy/</filename>.
284 <!-- ~~~~~ New section ~~~~~ -->
285 <sect2 id="installation-os2"><title>OS/2</title>
292 <application>Privoxy</application> is packaged in a WarpIN self-
293 installing archive. The self-installing program will be named depending
294 on the release version, something like:
295 <filename>privoxyos2_setup_1.2.3.exe</filename>. In order to install it, simply
296 run this executable or double-click on its icon and follow the WarpIN
297 installation panels. A shadow of the <application>Privoxy</application>
298 executable will be placed in your startup folder so it will start
299 automatically whenever OS/2 starts.
303 The directory you choose to install <application>Privoxy</application>
304 into will contain all of the configuration files.
308 If you would like to build binary images on OS/2 yourself, you will need
309 a few Unix-like tools: autoconf, autoheader and sh. These tools will be
310 used to create the required config.h file, which is not part of the
311 source distribution because it differs based on platform. You will also
313 The distribution has been created using IBM VisualAge compilers, but you
314 can use any compiler you like. GCC/EMX has the disadvantage of needing
315 to be single-threaded due to a limitation of EMX's implementation of the
316 select() socket call.
320 In addition to needing the source code distribution as outlined earlier,
321 you will want to extract the <filename>os2seutp</filename> directory from CVS:
323 cvs -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa login
324 cvs -z3 -d:pserver:anonymous@cvs.ijbswa.sourceforge.net:/cvsroot/ijbswa co os2setup
326 This will create a directory named os2setup/, which will contain the
327 <filename>Makefile.vac</filename> makefile and <filename>os2build.cmd</filename>
328 which is used to completely create the binary distribution. The sequence
329 of events for building the executable for yourself goes something like this:
336 nmake -f Makefile.vac
338 You will see this sequence laid out in <filename>os2build.cmd</filename>.
344 <!-- ~~~~~ New section ~~~~~ -->
345 <sect2 id="installation-win"><title>Windows</title>
346 <para>Click-click. (I need help on this. Not a clue here. Also for
347 configuration section below. HB.)
351 <!-- ~~~~~ New section ~~~~~ -->
352 <sect2 id="installation-other"><title>Other</title>
354 Some quick notes on other Operating Systems.
358 For FreeBSD (and other *BSDs?), the build will require <command>gmake</command>
359 instead of the included <command>make</command>. <command>gmake</command> is
360 available from <ulink url="http://www.gnu.org">http://www.gnu.org</ulink>.
361 The rest should be the same as above for Linux/Unix.
368 <!-- ~ End section ~ -->
371 <!-- ~~~~~ New section ~~~~~ -->
373 <sect1 id="quickstart"><title>Quickstart to Using <application>Privoxy</application></title>
375 Before launching <application>Privoxy</application> for the first time, you
376 will want to configure your browser(s) to use <application>Privoxy</application>
377 as a HTTP and HTTPS proxy. The default is localhost for the proxy address,
378 and port 8118 (earlier versions used port 800). This is the one required
379 configuration that must be done!
383 With <application>Netscape</application> (and
384 <application>Mozilla</application>), this can be set under <literal>Edit
385 -> Preferences -> Advanced -> Proxies -> HTTP Proxy</literal>.
386 For <application>Internet Explorer</application>: <literal>Tools ->
387 Internet Properties -> Connections -> LAN Setting</literal>. Then,
388 check <quote>Use Proxy</quote> and fill in the appropriate info (Address:
389 localhost, Port: 8118). Include if HTTPS proxy support too.
393 After doing this, flush your browser's disk and memory caches to force a
394 re-reading of all pages and get rid of any ads that may be cached. You
395 are now ready to start enjoying the benefits of using
396 <application>Privoxy</application>.
401 <application>Privoxy</application> is typically started by specifying the
402 main configuration file to be used on the command line. Example Unix startup
409 # /usr/sbin/privoxy /etc/privoxy/config
415 An init script is provided for SuSE and Redhat.
419 For for SuSE: /etc/rc.d/privoxy start
423 For RedHat: /etc/rc.d/init.d/privoxy start
428 If no configuration file is specified on the command line,
429 <application>Privoxy</application> will look for a file named
430 <filename>config</filename> in the current directory. Except on Win32 where
431 it will try <filename>config.txt</filename>. If no file is specified on the
432 command line and no default configuration file can be found,
433 <application>Privoxy</application> will fail to start.
438 The included default configuration files should give a reasonable starting
439 point, though may be somewhat aggressive in blocking junk. Most of the
440 per site configuration is done in the <quote>actions</quote> files. These
441 are where various cookie actions are defined, ad and banner blocking,
442 and other aspects of <application>Privoxy</application> configuration. There
443 are several such files included, with varying levels of aggressiveness.
447 You will probably want to keep an eye out for sites that require persistent
448 cookies, and add these to <filename>default.action</filename> as needed. By
449 default, most of these will be accepted only during the current browser
450 session, until you add them to the configuration. If you want the browser to
451 handle this instead, you will need to edit
452 <filename>default.action</filename> and disable this feature. If you use more
453 than one browser, it would make more sense to let
454 <application>Privoxy</application> handle this. In which case, the browser(s)
455 should be set to accept all cookies.
459 <application>Privoxy</application> is HTTP/1.1 compliant, but not all 1.1
460 features are as yet implemented. If browsers that support HTTP/1.1 (like
461 <application>Mozilla</application> or recent versions of I.E.) experience
462 problems, you might try to force HTTP/1.0 compatibility. For Mozilla, look
463 under <literal>Edit -> Preferences -> Debug -> Networking</literal>.
464 Or set the <quote>+downgrade</quote> config option in
465 <filename>default.action</filename>.
469 After running <application>Privoxy</application> for a while, you can
470 start to fine tune the configuration to suit your personal, or site,
471 preferences and requirements. There are many, many aspects that can
472 be customized. <quote>Actions</quote> (as specified in <filename>default.action</filename>)
473 can be adjusted by pointing your browser to
474 <ulink url="http://p.p/">http://p.p/</ulink>,
475 and then follow the link to <quote>edit the actions list</quote>.
476 (This is an internal page and does not require Internet access.)
480 In fact, various aspects of <application>Privoxy</application>
481 configuration can be viewed from this page, including
482 current configuration parameters, source code version numbers,
483 the browser's request headers, and <quote>actions</quote> that apply
484 to a given URL. In addition to the <filename>default.action</filename> file
485 editor mentioned above, <application>Privoxy</application> can also
486 be turned <quote>on</quote> and <quote>off</quote> from this page.
490 If you encounter problems, please verify it is a
491 <application>Privoxy</application> bug, by disabling
492 <application>Privoxy</application>, and then trying the same page.
493 Also, try another browser if possible to eliminate browser or site
494 problems. Before reporting it as a bug, see if there is not a configuration
495 option that is enabled that is causing the page not to load. You can then add
496 an exception for that page or site. For instance, try adding it to the
497 <literal>{fragile}</literal> section of <filename>default.action</filename>.
498 This will turn off most actions for this site. For more on troubleshooting
499 problem sites, see the <ulink
500 url="appendix.html#ACTIONSANAT">Appendix</ulink>. If a bug, please report it
501 to the developers (see below).
505 <!-- ~~~~~ New section ~~~~~ -->
508 <title>Command Line Options</title>
510 <application>Privoxy</application> may be invoked with the following
511 command-line options:
519 <emphasis>--version</emphasis>
522 Print version info and exit, Unix only.
527 <emphasis>--help</emphasis>
530 Print a short usage info and exit, Unix only.
535 <emphasis>--no-daemon</emphasis>
538 Don't become a daemon, i.e. don't fork and become process group
539 leader, don't detach from controlling tty. Unix only.
544 <emphasis>--pidfile FILE</emphasis>
548 On startup, write the process ID to <emphasis>FILE</emphasis>. Delete the
549 <emphasis>FILE</emphasis> on exit. Failiure to create or delete the
550 <emphasis>FILE</emphasis> is non-fatal. If no <emphasis>FILE</emphasis>
551 option is given, no PID file will be used. Unix only.
556 <emphasis>--user USER[.GROUP]</emphasis>
560 After (optionally) writing the PID file, assume the user ID of
561 <emphasis>USER</emphasis>, and if included the GID of GROUP. Exit if the
562 privileges are not sufficient to do so. Unix only.
567 <emphasis>configfile</emphasis>
570 If no <emphasis>configfile</emphasis> is included on the command line,
571 <application>Privoxy</application> will look for a file named
572 <quote>config</quote> in the current directory (except on Win32
573 where it will look for <quote>config.txt</quote> instead). Specify
574 full path to avoid confusion.
585 <!-- ~ End section ~ -->
588 <!-- ~~~~~ New section ~~~~~ -->
589 <sect1 id="configuration"><title><application>Privoxy</application> Configuration</title>
591 All <application>Privoxy</application> configuration is stored
592 in text files. These files can be edited with a text editor.
593 Many important aspects of <application>Privoxy</application> can
594 also be controlled easily with a web browser.
599 <!-- ~~~~~ New section ~~~~~ -->
602 <title>Controlling <application>Privoxy</application> with Your Web Browser</title>
604 <application>Privoxy</application> can be reached by the special
605 URL <ulink url="http://p.p/">http://p.p/</ulink> (or alternately
606 <ulink url="http://config.privoxy.org/">http://config.privoxy.org/</ulink>),
607 which is an internal page. You will see the following section:
614 Please choose from the following options:
616 * Show information about the current configuration
617 * Show the source code version numbers
618 * Show the client's request headers.
619 * Show which actions apply to a URL and why
620 * Toggle Privoxy on or off
621 * Edit the actions list
627 This should be self-explanatory. Note the last item is an editor for the
628 <quote>actions list</quote>, which is where much of the ad, banner, cookie,
629 and URL blocking magic is configured as well as other advanced features of
630 <application>Privoxy</application>. This is an easy way to adjust various
631 aspects of <application>Privoxy</application> configuration. The actions
632 file, and other configuration files, are explained in detail below.
633 <application>Privoxy</application> will automatically detect any changes
638 <quote>Toggle Privoxy On or Off</quote> is handy for sites that might
639 have problems with your current actions and filters, or just to test if
640 a site misbehaves, whether it is <application>Privoxy</application>
641 causing the problem or not. <application>Privoxy</application> continues
642 to run as a proxy in this case, but all filtering is disabled.
648 <!-- ~ End section ~ -->
653 <!-- ~~~~~ New section ~~~~~ -->
656 <title>Configuration Files Overview</title>
658 For Unix, *BSD and Linux, all configuration files are located in
659 <filename>/etc/privoxy/</filename> by default. For MS Windows, OS/2, and
660 AmigaOS these are all in the same directory as the
661 <application>Privoxy</application> executable. The name and number of
662 configuration files has changed from previous versions, and is subject to
663 change as development progresses.
667 The installed defaults provide a reasonable starting point, though possibly
668 aggressive by some standards. For the time being, there are only three
669 default configuration files (this will change in time):
677 The main configuration file is named <filename>config</filename>
678 on Linux, Unix, BSD, OS/2, and AmigaOS and <filename>config.txt</filename>
685 The <filename>default.action</filename> file is used to define various
686 <quote>actions</quote> relating to images, banners, pop-ups, access
687 restrictions, banners and cookies. There is a CGI based editor for this
688 file that can be accessed via <ulink
689 url="http://p.p">http://p.p</ulink>. (Other actions
690 files are included as well with differing levels of filtering
691 and blocking, e.g. <filename>basic.action</filename>.)
697 The <filename>default.filter</filename> file can be used to re-write the raw
698 page content, including viewable text as well as embedded HTML and JavaScript,
699 and whatever else lurks on any given web page.
707 <filename>default.action</filename> and <filename>default.filter</filename>
708 can use Perl style regular expressions for maximum flexibility. All files use
709 the <quote><literal>#</literal></quote> character to denote a comment. Such
710 lines are not processed by <application>Privoxy</application>. After
711 making any changes, there is no need to restart
712 <application>Privoxy</application> in order for the changes to take
713 effect. <application>Privoxy</application> should detect such changes
718 While under development, the configuration content is subject to change.
719 The below documentation may not be accurate by the time you read this.
720 Also, what constitutes a <quote>default</quote> setting, may change, so
721 please check all your configuration files on important issues.
726 <!-- ~~~~~ New section ~~~~~ -->
729 <title>The Main Configuration File</title>
731 Again, the main configuration file is named <filename>config</filename> on
732 Linux/Unix/BSD and OS/2, and <filename>config.txt</filename> on Windows.
733 Configuration lines consist of an initial keyword followed by a list of
734 values, all separated by whitespace (any number of spaces or tabs). For
742 <emphasis>blockfile blocklist.ini</emphasis>
749 Indicates that the blockfile is named <quote>blocklist.ini</quote>. (A
750 default installation does not use this.)
754 A <quote><literal>#</literal></quote> indicates a comment. Any part of a
755 line following a <quote><literal>#</literal></quote> is ignored, except if
756 the <quote><literal>#</literal></quote> is preceded by a
757 <quote><literal>\</literal></quote>.
761 Thus, by placing a <quote><literal>#</literal></quote> at the start of an
762 existing configuration line, you can make it a comment and it will be treated
763 as if it weren't there. This is called <quote>commenting out</quote> an
764 option and can be useful to turn off features: If you comment out the
765 <quote>logfile</quote> line, <application>Privoxy</application> will not
766 log to a file at all. Watch for the <quote>default:</quote> section in each
767 explanation to see what happens if the option is left unset (or commented
772 Long lines can be continued on the next line by using a
773 <quote><literal>\</literal></quote> as the very last character.
777 There are various aspects of <application>Privoxy</application> behavior
782 <!-- ~~~~~ New section ~~~~~ -->
785 <title>Defining Other Configuration Files</title>
788 <application>Privoxy</application> can use a number of other files to tell it
789 what ads to block, what cookies to accept, and perform other functions. This
790 section of the configuration file tells <application>Privoxy</application>
791 where to find all those other files.
795 On <application>Windows</application> and <application>AmigaOS</application>,
796 <application>Privoxy</application> looks for these files in the same
797 directory as the executable. On Unix and OS/2,
798 <application>Privoxy</application> looks for these files in the current
799 working directory. In either case, an absolute path name can be used to
804 When development goes modular and multi-user, the blocker, filter, and
805 per-user config will be stored in subdirectories of <quote>confdir</quote>.
806 For now, only <filename>confdir/templates</filename> is used for storing HTML
807 templates for CGI results.
811 The location of the configuration files:
818 <emphasis>confdir /etc/privoxy</emphasis> # No trailing /, please.
825 The directory where all logging (i.e. <filename>logfile</filename> and
826 <filename>jarfile</filename>) takes place. No trailing
827 <quote><literal>/</literal></quote>, please:
834 <emphasis>logdir /var/log/privoxy</emphasis>
841 Note that all file specifications below are relative to
842 the above two directories!
846 The <quote>default.action</quote> file contains patterns to specify the
847 actions to apply to requests for each site. Default: Cookies to and from all
848 destinations are kept only during the current browser session (i.e. they are
849 not saved to disk). Pop-ups are disabled for all sites. All sites are
850 filtered through selected sections of <quote>default.filter</quote>. No sites
851 are blocked. <application>Privoxy</application> displays a checkboard type
852 pattern for filtered ads and other images. The syntax of this file is
853 explained in detail <link linkend="actionsfile">below</link>. Other
854 <quote>actions</quote> files are included, and you are free to use any of
855 them. They have varying degrees of aggressiveness.
862 <emphasis>actionsfile default.action</emphasis>
869 The <quote>default.filter</quote> file contains content modification rules
870 that use <quote>regular expressions</quote>. These rules permit powerful
871 changes on the content of Web pages, e.g., you could disable your favorite
872 JavaScript annoyances, re-write the actual displayed text, or just have some
873 fun replacing <quote>Microsoft</quote> with <quote>MicroSuck</quote> wherever
874 it appears on a Web page. Default: whatever the developers are playing with
879 Filtering requires buffering the page content, which may appear to slow down
880 page rendering since nothing is displayed until all content has passed
881 the filters. (It does not really take longer, but seems that way since
882 the page is not incrementally displayed.) This effect will be more noticeable
883 on slower connections.
891 <emphasis>filterfile default.filter</emphasis>
898 The logfile is where all logging and error messages are written. The logfile
899 can be useful for tracking down a problem with
900 <application>Privoxy</application> (e.g., it's not blocking an ad you
901 think it should block) but in most cases you probably will never look at it.
905 Your logfile will grow indefinitely, and you will probably want to
906 periodically remove it. On Unix systems, you can do this with a cron job
907 (see <quote>man cron</quote>). For Redhat, a <command>logrotate</command>
908 script has been included.
912 On SuSE Linux systems, you can place a line like <quote>/var/log/privoxy.*
913 +1024k 644 nobody.nogroup</quote> in <filename>/etc/logfiles</filename>, with
914 the effect that cron.daily will automatically archive, gzip, and empty the
915 log, when it exceeds 1M size.
919 Default: Log to the a file named <filename>logfile</filename>.
920 Comment out to disable logging.
927 <emphasis>logfile logfile</emphasis>
934 The <quote>jarfile</quote> defines where
935 <application>Privoxy</application> stores the cookies it intercepts. Note
936 that if you use a <quote>jarfile</quote>, it may grow quite large. Default:
937 Don't store intercepted cookies.
944 <emphasis>#jarfile jarfile</emphasis>
951 If you specify a <quote>trustfile</quote>,
952 <application>Privoxy</application> will only allow access to sites that
953 are named in the trustfile. You can also mark sites as trusted referrers,
954 with the effect that access to untrusted sites will be granted, if a link
955 from a trusted referrer was used. The link target will then be added to the
956 <quote>trustfile</quote>. This is a very restrictive feature that typical
957 users most probably want to leave disabled. Default: Disabled, don't use the
965 <emphasis>#trustfile trust</emphasis>
972 If you use the trust mechanism, it is a good idea to write up some on-line
973 documentation about your blocking policy and to specify the URL(s) here. They
974 will appear on the page that your users receive when they try to access
975 untrusted content. Use multiple times for multiple URLs. Default: Don't
976 display links on the <quote>untrusted</quote> info page.
983 <emphasis>trust-info-url http://www.example.com/why_we_block.html</emphasis>
984 <emphasis>trust-info-url http://www.example.com/what_we_allow.html</emphasis>
992 <!-- ~ End section ~ -->
996 <!-- ~~~~~ New section ~~~~~ -->
999 <title>Other Configuration Options</title>
1002 This part of the configuration file contains options that control how
1003 <application>Privoxy</application> operates.
1007 <quote>Admin-address</quote> should be set to the email address of the proxy
1008 administrator. It is used in many of the proxy-generated pages. Default:
1016 <emphasis>#admin-address fill@me.in.please</emphasis>
1023 <quote>Proxy-info-url</quote> can be set to a URL that contains more info
1024 about this <application>Privoxy</application> installation, it's
1025 configuration and policies. It is used in many of the proxy-generated pages
1026 and its use is highly recommended in multi-user installations, since your
1027 users will want to know why certain content is blocked or modified. Default:
1028 Don't show a link to on-line documentation.
1035 <emphasis>proxy-info-url http://www.example.com/proxy.html</emphasis>
1042 <quote>Listen-address</quote> specifies the address and port where
1043 <application>Privoxy</application> will listen for connections from your
1044 Web browser. The default is to listen on the localhost port 8118, and
1045 this is suitable for most users. (In your web browser, under proxy
1046 configuration, list the proxy server as <quote>localhost</quote> and the
1047 port as <quote>8118</quote>).
1051 If you already have another service running on port 8118, or if you want to
1052 serve requests from other machines (e.g. on your local network) as well, you
1053 will need to override the default. The syntax is
1054 <quote>listen-address [<ip-address>]:<port></quote>. If you leave
1055 out the IP address, <application>Privoxy</application> will bind to all
1056 interfaces (addresses) on your machine and may become reachable from the
1057 Internet. In that case, consider using access control lists (acl's) (see
1058 <quote>aclfile</quote> above), or a firewall.
1062 For example, suppose you are running <application>Privoxy</application> on
1063 a machine which has the address 192.168.0.1 on your local private network
1064 (192.168.0.0) and has another outside connection with a different address.
1065 You want it to serve requests from inside only:
1072 <emphasis>listen-address 192.168.0.1:8118</emphasis>
1079 If you want it to listen on all addresses (including the outside
1087 <emphasis>listen-address :8118</emphasis>
1094 If you do this, consider using ACLs (see <quote>aclfile</quote> above). Note:
1095 you will need to point your browser(s) to the address and port that you have
1096 configured here. Default: localhost:8118 (127.0.0.1:8118).
1100 The debug option sets the level of debugging information to log in the
1101 logfile (and to the console in the Windows version). A debug level of 1 is
1102 informative because it will show you each request as it happens. Higher
1103 levels of debug are probably only of interest to developers.
1110 debug 1 # GPC = show each GET/POST/CONNECT request
1111 debug 2 # CONN = show each connection status
1112 debug 4 # IO = show I/O status
1113 debug 8 # HDR = show header parsing
1114 debug 16 # LOG = log all data into the logfile
1115 debug 32 # FRC = debug force feature
1116 debug 64 # REF = debug regular expression filter
1117 debug 128 # = debug fast redirects
1118 debug 256 # = debug GIF de-animation
1119 debug 512 # CLF = Common Log Format
1120 debug 1024 # = debug kill pop-ups
1121 debug 4096 # INFO = Startup banner and warnings.
1122 debug 8192 # ERROR = Non-fatal errors
1129 It is <emphasis>highly recommended</emphasis> that you enable ERROR
1130 reporting (debug 8192), at least until v3.0 is released.
1134 The reporting of FATAL errors (i.e. ones which crash
1135 <application>Privoxy</application>) is always on and cannot be disabled.
1139 If you want to use CLF (Common Log Format), you should set <quote>debug
1140 512</quote> ONLY, do not enable anything else.
1144 Multiple <quote>debug</quote> directives, are OK - they're logical-OR'd
1152 <emphasis>debug 15 # same as setting the first 4 listed above</emphasis>
1166 <emphasis>debug 1 # URLs</emphasis>
1167 <emphasis>debug 4096 # Info</emphasis>
1168 <emphasis>debug 8192 # Errors - *we highly recommended enabling this*</emphasis>
1175 <application>Privoxy</application> normally uses
1176 <quote>multi-threading</quote>, a software technique that permits it to
1177 handle many different requests simultaneously. In some cases you may wish to
1178 disable this -- particularly if you're trying to debug a problem. The
1179 <quote>single-threaded</quote> option forces
1180 <application>Privoxy</application> to handle requests sequentially.
1181 Default: Multi-threaded mode.
1188 <emphasis>#single-threaded</emphasis>
1195 <quote>toggle</quote> allows you to temporarily disable all
1196 <application>Privoxy's</application> filtering. Just set <quote>toggle
1201 The Windows version of <application>Privoxy</application> puts an icon in
1202 the system tray, which also allows you to change this option. If you
1203 right-click on that icon (or select the <quote>Options</quote> menu), one
1204 choice is <quote>Enable</quote>. Clicking on enable toggles
1205 <application>Privoxy</application> on and off. This is useful if you want
1206 to temporarily disable <application>Privoxy</application>, e.g., to access
1207 a site that requires cookies which you would otherwise have blocked. This can also
1208 be toggled via a web browser at the <application>Privoxy</application>
1209 internal address of <ulink url="http://p.p">http://p.p</ulink> on
1214 <quote>toggle 1</quote> means <application>Privoxy</application> runs
1215 normally, <quote>toggle 0</quote> means that
1216 <application>Privoxy</application> becomes a non-anonymizing non-blocking
1217 proxy. Default: 1 (on).
1224 <emphasis>toggle 1</emphasis>
1231 For content filtering, i.e. the <quote>+filter</quote> and
1232 <quote>+deanimate-gif</quote> actions, it is necessary that
1233 <application>Privoxy</application> buffers the entire document body.
1234 This can be potentially dangerous, since a server could just keep sending
1235 data indefinitely and wait for your RAM to exhaust. With nasty consequences.
1239 The <application>buffer-limit</application> option lets you set the maximum
1240 size in Kbytes that each buffer may use. When the documents buffer exceeds
1241 this size, it is flushed to the client unfiltered and no further attempt to
1242 filter the rest of it is made. Remember that there may multiple threads
1243 running, which might require increasing the <quote>buffer-limit</quote>
1244 Kbytes <emphasis>each</emphasis>, unless you have enabled
1245 <quote>single-threaded</quote> above.
1252 <emphasis>buffer-limit 4069</emphasis>
1259 To enable the web-based <filename>default.action</filename> file editor set
1260 <application>enable-edit-actions</application> to 1, or 0 to disable. Note
1261 that you must have compiled <application>Privoxy</application> with
1262 support for this feature, otherwise this option has no effect. This
1263 internal page can be reached at <ulink
1264 url="http://p.p">http://p.p</ulink>.
1268 Security note: If this is enabled, anyone who can use the proxy
1269 can edit the actions file, and their changes will affect all users.
1270 For shared proxies, you probably want to disable this. Default: enabled.
1277 <emphasis>enable-edit-actions 1</emphasis>
1284 Allow <application>Privoxy</application> to be toggled on and off
1285 remotely, using your web browser. Set <quote>enable-remote-toggle</quote>to
1286 1 to enable, and 0 to disable. Note that you must have compiled
1287 <application>Privoxy</application> with support for this feature,
1288 otherwise this option has no effect.
1292 Security note: If this is enabled, anyone who can use the proxy can toggle
1293 it on or off (see <ulink url="http://p.p">http://p.p</ulink>), and
1294 their changes will affect all users. For shared proxies, you probably want to
1295 disable this. Default: enabled.
1302 <emphasis>enable-remote-toggle 1</emphasis>
1310 <!-- ~ End section ~ -->
1313 <!-- ~~~~~ New section ~~~~~ -->
1316 <title>Access Control List (ACL)</title>
1318 Access controls are included at the request of some ISPs and systems
1319 administrators, and are not usually needed by individual users. Please note
1320 the warnings in the FAQ that this proxy is not intended to be a substitute
1321 for a firewall or to encourage anyone to defer addressing basic security
1326 If no access settings are specified, the proxy talks to anyone that
1327 connects. If any access settings file are specified, then the proxy
1328 talks only to IP addresses permitted somewhere in this file and not
1329 denied later in this file.
1333 Summary -- if using an ACL:
1338 Client must have permission to receive service.
1343 LAST match in ACL wins.
1348 Default behavior is to deny service.
1353 The syntax for an entry in the Access Control List is:
1360 ACTION SRC_ADDR[/SRC_MASKLEN] [ DST_ADDR[/DST_MASKLEN] ]
1367 Where the individual fields are:
1374 <emphasis>ACTION</emphasis> = <quote>permit-access</quote> or <quote>deny-access</quote>
1376 <emphasis>SRC_ADDR</emphasis> = client hostname or dotted IP address
1377 <emphasis>SRC_MASKLEN</emphasis> = number of bits in the subnet mask for the source
1379 <emphasis>DST_ADDR</emphasis> = server or forwarder hostname or dotted IP address
1380 <emphasis>DST_MASKLEN</emphasis> = number of bits in the subnet mask for the target
1388 The field separator (FS) is whitespace (space or tab).
1392 IMPORTANT NOTE: If <application>Privoxy</application> is using a
1393 forwarder (see below) or a gateway for a particular destination URL, the
1394 <literal>DST_ADDR</literal> that is examined is the address of the forwarder
1395 or the gateway and <emphasis>NOT</emphasis> the address of the ultimate
1396 target. This is necessary because it may be impossible for the local
1397 <application>Privoxy</application> to determine the address of the
1398 ultimate target (that's often what gateways are used for).
1402 Here are a few examples to show how the ACL features work:
1406 <quote>localhost</quote> is OK -- no DST_ADDR implies that
1407 <emphasis>ALL</emphasis> destination addresses are OK:
1414 <emphasis>permit-access localhost</emphasis>
1421 A silly example to illustrate permitting any host on the class-C subnet with
1422 <application>Privoxy</application> to go anywhere:
1429 <emphasis>permit-access www.privoxy.com/24</emphasis>
1436 Except deny one particular IP address from using it at all:
1443 <emphasis>deny-access ident.privoxy.com</emphasis>
1450 You can also specify an explicit network address and subnet mask.
1451 Explicit addresses do not have to be resolved to be used.
1458 <emphasis>permit-access 207.153.200.0/24</emphasis>
1465 A subnet mask of 0 matches anything, so the next line permits everyone.
1472 <emphasis>permit-access 0.0.0.0/0</emphasis>
1479 Note, you <emphasis>cannot</emphasis> say:
1486 <emphasis>permit-access .org</emphasis>
1493 to allow all *.org domains. Every IP address listed must resolve fully.
1497 An ISP may want to provide a <application>Privoxy</application> that is
1498 accessible by <quote>the world</quote> and yet restrict use of some of their
1499 private content to hosts on its internal network (i.e. its own subscribers).
1500 Say, for instance the ISP owns the Class-B IP address block 123.124.0.0 (a 16
1501 bit netmask). This is how they could do it:
1508 <emphasis>permit-access 0.0.0.0/0 0.0.0.0/0</emphasis> # other clients can go anywhere
1509 # with the following exceptions:
1511 <emphasis>deny-access</emphasis> 0.0.0.0/0 123.124.0.0/16 # block all external requests for
1512 # sites on the ISP's network
1514 <emphasis>permit 0.0.0.0/0 www.my_isp.com</emphasis> # except for the ISP's main
1517 <emphasis>permit 123.124.0.0/16 0.0.0.0/0</emphasis> # the ISP's clients can go
1525 Note that if some hostnames are listed with multiple IP addresses,
1526 the primary value returned by DNS (via gethostbyname()) is used. Default:
1527 Anyone can access the proxy.
1532 <!-- ~ End section ~ -->
1535 <!-- ~~~~~ New section ~~~~~ -->
1537 <sect3 id="forwarding">
1538 <title>Forwarding</title>
1541 This feature allows chaining of HTTP requests via multiple proxies.
1542 It can be used to better protect privacy and confidentiality when
1543 accessing specific domains by routing requests to those domains
1544 to a special purpose filtering proxy such as lpwa.com. Or to use
1545 a caching proxy to speed up browsing.
1549 It can also be used in an environment with multiple networks to route
1550 requests via multiple gateways allowing transparent access to multiple
1551 networks without having to modify browser configurations.
1555 Also specified here are SOCKS proxies. <application>Privoxy</application>
1556 SOCKS 4 and SOCKS 4A. The difference is that SOCKS 4A will resolve the target
1557 hostname using DNS on the SOCKS server, not our local DNS client.
1561 The syntax of each line is:
1568 <emphasis>forward target_domain[:port] http_proxy_host[:port]</emphasis>
1569 <emphasis>forward-socks4 target_domain[:port] socks_proxy_host[:port] http_proxy_host[:port]</emphasis>
1570 <emphasis>forward-socks4a target_domain[:port] socks_proxy_host[:port] http_proxy_host[:port]</emphasis>
1577 If http_proxy_host is <quote>.</quote>, then requests are not forwarded to a
1578 HTTP proxy but are made directly to the web servers.
1582 Lines are checked in sequence, and the last match wins.
1586 There is an implicit line equivalent to the following, which specifies that
1587 anything not finding a match on the list is to go out without forwarding
1588 or gateway protocol, like so:
1595 <emphasis>forward .* . </emphasis># implicit
1602 In the following common configuration, everything goes to Lucent's LPWA,
1603 except SSL on port 443 (which it doesn't handle):
1610 <emphasis>forward .* lpwa.com:8000</emphasis>
1611 <emphasis>forward :443 .</emphasis>
1619 See the FAQ for instructions on how to automate the login procedure for LPWA.
1621 Some users have reported difficulties related to LPWA's use of
1622 <quote>.</quote> as the last element of the domain, and have said that this
1623 can be fixed with this:
1630 <emphasis>forward lpwa. lpwa.com:8000</emphasis>
1637 (NOTE: the syntax for specifying target_domain has changed since the
1638 previous paragraph was written -- it will not work now. More information
1643 In this fictitious example, everything goes via an ISP's caching proxy,
1644 except requests to that ISP:
1651 <emphasis>forward .* caching.myisp.net:8000</emphasis>
1652 <emphasis>forward myisp.net .</emphasis>
1659 For the @home network, we're told the forwarding configuration is this:
1667 <emphasis>forward .* proxy:8080</emphasis>
1674 Also, we're told they insist on getting cookies and JavaScript, so you should
1675 allow cookies from home.com. We consider JavaScript a potential security risk.
1676 Java need not be enabled.
1680 In this example direct connections are made to all <quote>internal</quote>
1681 domains, but everything else goes through Lucent's LPWA by way of the
1682 company's SOCKS gateway to the Internet.
1689 <emphasis>forward-socks4 .* lpwa.com:8000 firewall.my_company.com:1080</emphasis>
1690 <emphasis>forward my_company.com .</emphasis>
1697 This is how you could set up a site that always uses SOCKS but no forwarders:
1704 <emphasis>forward-socks4a .* . firewall.my_company.com:1080</emphasis>
1711 An advanced example for network administrators:
1715 If you have links to multiple ISPs that provide various special content to
1716 their subscribers, you can configure forwarding to pass requests to the
1717 specific host that's connected to that ISP so that everybody can see all
1718 of the content on all of the ISPs.
1722 This is a bit tricky, but here's an example:
1727 host-a has a PPP connection to isp-a.com. And host-b has a PPP connection to
1728 isp-b.com. host-a can run a <application>Privoxy</application> proxy with
1729 forwarding like this:
1736 <emphasis>forward .* .</emphasis>
1737 <emphasis>forward isp-b.com host-b:8118</emphasis>
1744 host-b can run a <application>Privoxy</application> proxy with forwarding
1752 <emphasis>forward .* .</emphasis>
1753 <emphasis>forward isp-a.com host-a:8118</emphasis>
1760 Now, <emphasis>anyone</emphasis> on the Internet (including users on host-a
1761 and host-b) can set their browser's proxy to <emphasis>either</emphasis>
1762 host-a or host-b and be able to browse the content on isp-a or isp-b.
1766 Here's another practical example, for University of Kent at
1767 Canterbury students with a network connection in their room, who
1768 need to use the University's Squid web cache.
1775 <emphasis>forward *. ssbcache.ukc.ac.uk:3128</emphasis> # Use the proxy, except for:
1776 <emphasis>forward .ukc.ac.uk . </emphasis> # Anything on the same domain as us
1777 <emphasis>forward * . </emphasis> # Host with no domain specified
1778 <emphasis>forward 129.12.*.* . </emphasis> # A dotted IP on our /16 network.
1779 <emphasis>forward 127.*.*.* . </emphasis> # Loopback address
1780 <emphasis>forward localhost.localdomain . </emphasis> # Loopback address
1781 <emphasis>forward www.ukc.mirror.ac.uk . </emphasis> # Specific host
1788 If you intend to chain <application>Privoxy</application> and
1789 <application>squid</application> locally, then chain as
1790 <literal>browser -> squid -> privoxy</literal> is the recommended way.
1794 Your squid configuration could then look like this:
1801 # Define Privoxy as parent cache
1802 <!-- per feedback from user...
1803 cache_peer 127.0.0.1 8118 parent 0 no-query
1805 cache_peer 127.0.0.1 parent 8118 0 no-query
1807 # Define ACL for protocol FTP
1810 # Do not forward ACL FTP to privoxy
1811 always_direct allow FTP
1813 # Do not forward ACL CONNECT (https) to privoxy
1814 always_direct allow CONNECT
1816 # Forward the rest to privoxy
1817 never_direct allow all
1825 <!-- ~ End section ~ -->
1828 <!-- ~~~~~ New section ~~~~~ -->
1831 <title>Windows GUI Options</title>
1833 Removed references to Win32. HB 09/23/01
1836 <application>Privoxy</application> has a number of options specific to the
1837 Windows GUI interface:
1841 If <quote>activity-animation</quote> is set to 1, the
1842 <application>Privoxy</application> icon will animate when
1843 <quote>Privoxy</quote> is active. To turn off, set to 0.
1850 <emphasis>activity-animation 1</emphasis>
1857 If <quote>log-messages</quote> is set to 1,
1858 <application>Privoxy</application> will log messages to the console
1866 <emphasis>log-messages 1</emphasis>
1873 If <quote>log-buffer-size</quote> is set to 1, the size of the log buffer,
1874 i.e. the amount of memory used for the log messages displayed in the
1875 console window, will be limited to <quote>log-max-lines</quote> (see below).
1879 Warning: Setting this to 0 will result in the buffer to grow infinitely and
1880 eat up all your memory!
1887 <emphasis>log-buffer-size 1</emphasis>
1894 <application>log-max-lines</application> is the maximum number of lines held
1895 in the log buffer. See above.
1902 <emphasis>log-max-lines 200</emphasis>
1909 If <quote>log-highlight-messages</quote> is set to 1,
1910 <application>Privoxy</application> will highlight portions of the log
1911 messages with a bold-faced font:
1918 <emphasis>log-highlight-messages 1</emphasis>
1925 The font used in the console window:
1932 <emphasis>log-font-name Comic Sans MS</emphasis>
1939 Font size used in the console window:
1946 <emphasis>log-font-size 8</emphasis>
1953 <quote>show-on-task-bar</quote> controls whether or not
1954 <application>Privoxy</application> will appear as a button on the Task bar
1962 <emphasis>show-on-task-bar 0</emphasis>
1969 If <quote>close-button-minimizes</quote> is set to 1, the Windows close
1970 button will minimize <application>Privoxy</application> instead of closing
1971 the program (close with the exit option on the File menu).
1978 <emphasis>close-button-minimizes 1</emphasis>
1985 The <quote>hide-console</quote> option is specific to the MS-Win console
1986 version of <application>Privoxy</application>. If this option is used,
1987 <application>Privoxy</application> will disconnect from and hide the
2004 <!-- ~ End section ~ -->
2007 <!-- ~~~~~ New section ~~~~~ -->
2008 <sect2 id="actionsfile">
2009 <title>The Actions File</title>
2012 The <quote>default.action</quote> file (formerly
2013 <filename>actionsfile</filename> or <filename>ijb.action</filename>) is used
2014 to define what actions <application>Privoxy</application> takes, and thus
2015 determines how ad images, cookies and various other aspects of HTTP content
2016 and transactions are handled. These can be accepted or rejected for all
2017 sites, or just those sites you choose. See below for a complete list of
2021 Anything you want can blocked, including ads, banners, or just some obnoxious
2022 URL that you would rather not see. Cookies can be accepted or rejected, or
2023 accepted only during the current browser session (i.e. not written to disk).
2024 Changes to <filename>default.action</filename> should be immediately visible
2025 to <application>Privoxy</application> without the need to restart.
2029 Note that some sites may misbehave, or possibly not work at all with some
2030 actions. This may require some tinkering with the rules to get the most
2031 mileage of <application>Privoxy's</application> features, and still be
2032 able to see and enjoy just what you want to. There is no general rule of
2033 thumb on these things. There just are too many variables, and sites are
2039 The easiest way to edit the <quote>actions</quote> file is with a browser by
2040 loading <ulink url="http://p.p/">http://p.p/</ulink>, and then select
2041 <quote>Edit Actions List</quote>. A text editor can also be used.
2045 To determine which actions apply to a request, the URL of the request is
2046 compared to all patterns in this file. Every time it matches, the list of
2047 applicable actions for the URL is incrementally updated. You can trace
2048 this process by visiting <ulink
2049 url="http://p.p/show-url-info">http://p.p/show-url-info</ulink>.
2054 There are four types of lines in this file: comments (begin with a
2055 <quote>#</quote> character), actions, aliases and patterns, all of which are
2056 explained below, as well as the configuration file syntax that
2057 <application>Privoxy</application> understands.
2062 <!-- ~~~~~ New section ~~~~~ -->
2064 <title>URL Domain and Path Syntax</title>
2066 Generally, a pattern has the form <domain>/<path>, where both the
2067 <domain> and <path> part are optional. If you only specify a
2068 domain part, the <quote>/</quote> can be left out:
2072 <emphasis>www.example.com</emphasis> - is a domain only pattern and will match any request to
2073 <quote>www.example.com</quote>.
2077 <emphasis>www.example.com/</emphasis> - means exactly the same.
2081 <emphasis>www.example.com/index.html</emphasis> - matches only the single
2082 document <quote>/index.html</quote> on <quote>www.example.com</quote>.
2086 <emphasis>/index.html</emphasis> - matches the document <quote>/index.html</quote>,
2087 regardless of the domain. So would match any page named <quote>index.html</quote>
2092 <emphasis>index.html</emphasis> - matches nothing, since it would be
2093 interpreted as a domain name and there is no top-level domain called
2094 <quote>.html</quote>.
2098 The matching of the domain part offers some flexible options: if the
2099 domain starts or ends with a dot, it becomes unanchored at that end.
2104 <emphasis>.example.com</emphasis> - matches any domain or sub-domain that
2105 <emphasis>ENDS</emphasis> in <quote>.example.com</quote>.
2109 <emphasis>www.</emphasis> - matches any domain that <emphasis>STARTS</emphasis> with
2114 Additionally, there are wild-cards that you can use in the domain names
2115 themselves. They work pretty similar to shell wild-cards: <quote>*</quote>
2116 stands for zero or more arbitrary characters, <quote>?</quote> stands for
2117 any single character. And you can define character classes in square
2118 brackets and they can be freely mixed:
2122 <emphasis>ad*.example.com</emphasis> - matches <quote>adserver.example.com</quote>,
2123 <quote>ads.example.com</quote>, etc but not <quote>sfads.example.com</quote>.
2127 <emphasis>*ad*.example.com</emphasis> - matches all of the above, and then some.
2131 <emphasis>.?pix.com</emphasis> - matches <quote>www.ipix.com</quote>,
2132 <quote>pictures.epix.com</quote>, <quote>a.b.c.d.e.upix.com</quote>, etc.
2136 <emphasis>www[1-9a-ez].example.com</emphasis> - matches <quote>www1.example.com</quote>,
2137 <quote>www4.example.com</quote>, <quote>wwwd.example.com</quote>,
2138 <quote>wwwz.example.com</quote>, etc., but <emphasis>not</emphasis>
2139 <quote>wwww.example.com</quote>.
2143 If <application>Privoxy</application> was compiled with
2144 <quote>pcre</quote> support (the default), Perl compatible regular expressions
2145 can be used. These are more flexible and powerful than other types
2146 of <quote>regular expressions</quote>. See the <filename>pcre/docs/</filename> directory or <quote>man
2147 perlre</quote> (also available on <ulink
2148 url="http://www.perldoc.com/perl5.6/pod/perlre.html">http://www.perldoc.com/perl5.6/pod/perlre.html</ulink>)
2149 for details. A brief discussion of regular expressions is in the
2150 <link linkend="regex">Appendix</link>. For instance:
2154 <emphasis>/.*/advert[0-9]+\.jpe?g</emphasis> - would match a URL from any
2155 domain, with any path that includes <quote>advert</quote> followed
2156 immediately by one or more digits, then a <quote>.</quote> and ending in
2157 either <quote>jpeg</quote> or <quote>jpg</quote>. So we match
2158 <quote>example.com/ads/advert2.jpg</quote>, and
2159 <quote>www.example.com/ads/banners/advert39.jpeg</quote>, but not
2160 <quote>www.example.com/ads/banners/advert39.gif</quote> (no gifs in the
2165 Please note that matching in the path is case
2166 <emphasis>INSENSITIVE</emphasis> by default, but you can switch to case
2167 sensitive at any point in the pattern by using the
2168 <quote>(?-i)</quote> switch:
2172 <emphasis>www.example.com/(?-i)PaTtErN.*</emphasis> - will match only
2173 documents whose path starts with <quote>PaTtErN</quote> in
2174 <emphasis>exactly</emphasis> this capitalization.
2179 <!-- ~ End section ~ -->
2183 <!-- ~~~~~ New section ~~~~~ -->
2186 <title>Actions</title>
2188 Actions are enabled if preceded with a <quote>+</quote>, and disabled if
2189 preceded with a <quote>-</quote>. Actions are invoked by enclosing the
2190 action name in curly braces (e.g. {+some_action}), followed by a list of
2191 URLs to which the action applies. There are three classes of actions:
2199 Boolean (e.g. <quote>+/-block</quote>):
2205 <emphasis>{+name}</emphasis> # enable this action
2206 <emphasis>{-name}</emphasis> # disable this action
2216 parameterized (e.g. <quote>+/-hide-user-agent</quote>):
2222 <emphasis>{+name{param}}</emphasis> # enable action and set parameter to <quote>param</quote>
2223 <emphasis>{-name}</emphasis> # disable action
2232 Multi-value (e.g. <quote>{+/-add-header{Name: value}}</quote>, <quote>{+/-wafer{name=value}}</quote>):
2238 <emphasis>{+name{param}}</emphasis> # enable action and add parameter <quote>param</quote>
2239 <emphasis>{-name{param}}</emphasis> # remove the parameter <quote>param</quote>
2240 <emphasis>{-name}</emphasis> # disable this action totally
2251 If nothing is specified in this file, no <quote>actions</quote> are taken.
2252 So in this case <application>Privoxy</application> would just be a
2253 normal, non-blocking, non-anonymizing proxy. You must specifically
2254 enable the privacy and blocking features you need (although the
2255 provided default <filename>default.action</filename> file will
2256 give a good starting point).
2260 Later defined actions always over-ride earlier ones. So exceptions
2261 to any rules you make, should come in the latter part of the file. For
2262 multi-valued actions, the actions are applied in the order they are
2267 The list of valid <application>Privoxy</application> <quote>actions</quote> are:
2275 Add the specified HTTP header, which is not checked for validity.
2276 You may specify this many times to specify many different headers:
2282 <emphasis>+add-header{Name: value}</emphasis>
2292 Block this URL totally. In a default installation, a <quote>blocked</quote>
2293 URL will result in bright red banner that says <quote>BLOCKED</quote>,
2294 with a reason why it is being blocked, and an option to see it anyway.
2295 The page displayed for this is the <quote>blocked</quote> template
2302 <emphasis>+block</emphasis>
2312 De-animate all animated GIF images, i.e. reduce them to their last frame.
2313 This will also shrink the images considerably (in bytes, not pixels!). If
2314 the option <quote>first</quote> is given, the first frame of the animation
2315 is used as the replacement. If <quote>last</quote> is given, the last frame
2316 of the animation is used instead, which probably makes more sense for most
2317 banner animations, but also has the risk of not showing the entire last
2318 frame (if it is only a delta to an earlier frame).
2324 <emphasis>+deanimate-gifs{last}</emphasis>
2325 <emphasis>+deanimate-gifs{first}</emphasis>
2334 <quote>+downgrade</quote> will downgrade HTTP/1.1 client requests to
2335 HTTP/1.0 and downgrade the responses as well. Use this action for servers
2336 that use HTTP/1.1 protocol features that
2337 <application>Privoxy</application> doesn't handle well yet. HTTP/1.1
2338 is only partially implemented. Default is not to downgrade requests.
2344 <emphasis>+downgrade</emphasis>
2353 Many sites, like yahoo.com, don't just link to other sites. Instead, they
2354 will link to some script on their own server, giving the destination as a
2355 parameter, which will then redirect you to the final target. URLs resulting
2356 from this scheme typically look like:
2357 http://some.place/some_script?http://some.where-else.
2360 Sometimes, there are even multiple consecutive redirects encoded in the
2361 URL. These redirections via scripts make your web browsing more traceable,
2362 since the server from which you follow such a link can see where you go to.
2363 Apart from that, valuable bandwidth and time is wasted, while your browser
2364 ask the server for one redirect after the other. Plus, it feeds the
2368 The <quote>+fast-redirects</quote> option enables interception of these
2369 types of requests by <application>Privoxy</application>, who will cut off
2370 all but the last valid URL in the request and send a local redirect back to
2371 your browser without contacting the intermediate site(s).
2377 <emphasis>+fast-redirects</emphasis>
2386 Apply the filters in the <literal>section_header</literal>
2387 section of the <filename>default.filter</filename> file to the site(s).
2388 <filename>default.filter</filename> sections are grouped according to like
2389 functionality. <application>Filters</application> can be used to
2390 re-write any of the raw page content. This is a potentially a
2391 very powerful feature!
2398 <emphasis>+filter{section_header}</emphasis>
2405 Filter sections that are pre-defined in the supplied
2406 <filename>default.filter</filename> include:
2412 <emphasis>html-annoyances</emphasis>: Get rid of particularly annoying HTML abuse.
2417 <emphasis>js-annoyances</emphasis>: Get rid of particularly annoying JavaScript abuse
2422 <emphasis>no-poups</emphasis>: Kill all popups in JS and HTML
2427 <emphasis>frameset-borders</emphasis>: Give frames a border
2432 <emphasis>webbugs</emphasis>: Squish WebBugs (1x1 invisible GIFs used for user tracking)
2437 <emphasis>no-refresh</emphasis>: Automatic refresh sucks on auto-dialup lines
2442 <emphasis>fun</emphasis>: Text replacements for subversive browsing fun!
2447 <emphasis>nimda</emphasis>: Remove (virus) Nimda code.
2452 <emphasis>banners-by-size</emphasis>: Kill banners by size
2457 <emphasis>crude-parental</emphasis>: Kill all web pages that contain the words "sex" or "warez"
2466 Block any existing X-Forwarded-for header, and do not add a new one:
2472 <emphasis>+hide-forwarded</emphasis>
2481 If the browser sends a <quote>From:</quote> header containing your e-mail
2482 address, this either completely removes the header (<quote>block</quote>), or
2483 changes it to the specified e-mail address.
2489 <emphasis>+hide-from{block}</emphasis>
2490 <emphasis>+hide-from{spam@sittingduck.xqq}</emphasis>
2499 Don't send the <quote>Referer:</quote> (sic) header to the web site. You
2500 can block it, forge a URL to the same server as the request (which is
2501 preferred because some sites will not send images otherwise) or set it to a
2502 constant, user defined string of your choice.
2508 <emphasis>+hide-referer{block}</emphasis>
2509 <emphasis>+hide-referer{forge}</emphasis>
2510 <emphasis>+hide-referer{http://nowhere.com}</emphasis>
2519 Alternative spelling of <quote>+hide-referer</quote>. It has the same
2520 parameters, and can be freely mixed with, <quote>+hide-referer</quote>.
2521 (<quote>referrer</quote> is the correct English spelling, however the HTTP
2522 specification has a bug - it requires it to be spelled <quote>referer</quote>.)
2528 <emphasis>+hide-referrer{...}</emphasis>
2537 Change the <quote>User-Agent:</quote> header so web servers can't tell your
2538 browser type. Warning! This breaks many web sites. Specify the
2539 user-agent value you want. Example, pretend to be using Netscape on
2546 <emphasis>+hide-user-agent{Mozilla (X11; I; Linux 2.0.32 i586)}</emphasis>
2553 Or to identify yourself explicitly as a <application>Privoxy</application> user:
2559 <emphasis>+hide-user-agent{Privoxy/1.0}</emphasis>
2564 (Don't change the version number from 1.0 - after all, why tell them?)
2571 <emphasis>+hide-user-agent{browser-type}</emphasis>
2581 Treat this URL as an image. This only matters if it's also <quote>+block</quote>ed,
2582 in which case a <quote>blocked</quote> image can be sent rather than a HTML page.
2583 See <quote>+image-blocker{}</quote> below for the control over what is actually sent.
2584 If you want <emphasis>invisible</emphasis> ads, they should be defined as
2585 <emphasis>images</emphasis> and <emphasis>blocked</emphasis>. And also,
2586 <quote>image-blocker</quote> should be set to <quote>blank</quote>. Note you
2587 cannot treat HTML pages as images in most cases. For instance, frames
2588 require an HTML page to display. Forcing an <quote>image</quote> in this
2589 situation just will not work.
2595 <emphasis>+image</emphasis>
2603 <para> Decides what to do with URLs that end up tagged with <quote>{+block
2604 +image}</quote>, e.g an advertizement. There are five options.
2605 <quote>-image-blocker</quote> will send a HTML <quote>blocked</quote> page,
2606 usually resulting in a <quote>broken image</quote> icon.
2607 <!-- <quote>+image-blocker{logo}</quote> will send a -->
2608 <!-- <application>Privoxy</application> logo -->
2610 <quote>+image-blocker{blank}</quote> will send a 1x1 transparent GIF
2611 image. And finally, <quote>+image-blocker{http://xyz.com}</quote> will send a
2612 HTTP temporary redirect to the specified image. This has the advantage of the
2613 icon being being cached by the browser, which will speed up the display.
2614 <quote>+image-blocker{pattern}</quote> will send a checkboard type pattern
2616 <!-- which scales better than the logo (which can get blocky if the browser -->
2617 <!-- enlarges it too much). -->
2623 <!-- <emphasis>+image-blocker{logo}</emphasis> -->
2624 <emphasis>+image-blocker{blank}</emphasis>
2625 <emphasis>+image-blocker{pattern}</emphasis>
2626 <emphasis>+image-blocker{http://p.p/send-banner}</emphasis>
2635 By default (i.e. in the absence of a <quote>+limit-connect</quote>
2636 action), <application>Privoxy</application> will only allow CONNECT
2637 requests to port 443, which is the standard port for https as a
2642 The CONNECT methods exists in HTTP to allow access to secure websites
2643 (https:// URLs) through proxies. It works very simply: the proxy
2644 connects to the server on the specified port, and then short-circuits
2645 its connections to the client <emphasis>and</emphasis> to the remote proxy.
2646 This can be a big security hole, since CONNECT-enabled proxies can
2647 be abused as TCP relays very easily.
2651 If you want to allow CONNECT for more ports than this, or want to forbid
2652 CONNECT altogether, you can specify a comma separated list of ports and
2653 port ranges (the latter using dashes, with the minimum defaulting to 0 and
2661 <emphasis>+limit-connect{443} # This is the default and need no be specified.</emphasis>
2662 <emphasis>+limit-connect{80,443} # Ports 80 and 443 are OK.</emphasis>
2663 <emphasis>+limit-connect{-3, 7, 20-100, 500-} # Port less than 3, 7, 20 to 100</emphasis>
2664 <emphasis> #and above 500 are OK.</emphasis>
2674 <quote>+no-compression</quote> prevents the website from compressing the
2675 data. Some websites do this, which can be a problem for
2676 <application>Privoxy</application>, since <quote>+filter</quote>,
2677 <quote>+no-popup</quote> and <quote>+gif-deanimate</quote> will not work on
2678 compressed data. This will slow down connections to those websites,
2679 though. Default is <quote>no-compression</quote> is turned on.
2686 <emphasis>+nocompression</emphasis>
2695 If the website sets cookies, <quote>no-cookies-keep</quote> will make sure
2696 they are erased when you exit and restart your web browser. This makes
2697 profiling cookies useless, but won't break sites which require cookies so
2698 that you can log in for transactions. Default: on.
2704 <emphasis>+no-cookies-keep</emphasis>
2713 Prevent the website from reading cookies:
2719 <emphasis>+no-cookies-read</emphasis>
2728 Prevent the website from setting cookies:
2734 <emphasis>+no-cookies-set</emphasis>
2743 Filter the website through a built-in filter to disable those obnoxious
2744 JavaScript pop-up windows via window.open(), etc. The two alternative
2745 spellings are equivalent.
2751 <emphasis>+no-popup</emphasis>
2752 <emphasis>+no-popups</emphasis>
2761 This action only applies if you are using a <filename>jarfile</filename>
2762 for saving cookies. It sends a cookie to every site stating that you do not
2763 accept any copyright on cookies sent to you, and asking them not to track
2764 you. Of course, this is a (relatively) unique header they could use to
2771 <emphasis>+vanilla-wafer</emphasis>
2780 This allows you to add an arbitrary cookie. It can be specified multiple
2781 times in order to add as many cookies as you like.
2787 <emphasis>+wafer{name=value}</emphasis>
2798 The meaning of any of the above is reversed by preceding the action with a
2799 <quote>-</quote>, in place of the <quote>+</quote>.
2807 Turn off cookies by default, then allow a few through for specified sites:
2814 # Turn off all persistent cookies
2815 { +no-cookies-read }
2817 # Allow cookies for this browser session ONLY
2818 { +no-cookies-keep }
2820 # Exceptions to the above, sites that benefit from persistent cookies
2821 { -no-cookies-read }
2823 { -no-cookies-keep }
2830 # Alternative way of saying the same thing
2831 {-no-cookies-set -no-cookies-read -no-cookies-keep}
2840 Now turn off <quote>fast redirects</quote>, and then we allow two exceptions:
2850 # Reverse it for these two sites, which don't work right without it.
2852 www.ukc.ac.uk/cgi-bin/wac\.cgi\?
2860 Turn on page filtering according to rules in the defined sections
2861 of <filename>refilterfile</filename>, and make one exception for
2869 # Run everything through the filter file, using only the
2870 # specified sections:
2871 +filter{html-annoyances} +filter{js-annoyances} +filter{no-popups}\
2872 +filter{webbugs} +filter{nimda} +filter{banners-by-size}
2874 # Then disable filtering of code from sourceforge!
2876 .cvs.sourceforge.net
2883 Now some URLs that we want <quote>blocked</quote> (normally generates
2884 the <quote>blocked</quote> banner). Many of these use regular expressions
2885 that will expand to match multiple URLs:
2894 /.*/(.*[-_.])?ads?[0-9]?(/|[-_.].*|\.(gif|jpe?g))
2895 /.*/(.*[-_.])?count(er)?(\.cgi|\.dll|\.exe|[?/])
2896 /.*/(ng)?adclient\.cgi
2897 /.*/(plain|live|rotate)[-_.]?ads?/
2898 /.*/(sponsor)s?[0-9]?/
2899 /.*/_?(plain|live)?ads?(-banners)?/
2901 /.*/ad(sdna_image|gifs?)/
2902 /.*/ad(server|stream|juggler)\.(cgi|pl|dll|exe)
2906 /.*/adv((er)?ts?|ertis(ing|ements?))?/
2910 /.*/cgi-bin/centralad/getimage
2911 /.*/images/addver\.gif
2912 /.*/images/marketing/.*\.(gif|jpe?g)
2916 /.*/sponsors?[0-9]?/
2917 /.*/advert[0-9]+\.jpg
2924 /graphics/defaultAd/
2926 /image\.ng/transactionID
2927 /images/.*/.*_anim\.gif # alvin brattli
2928 /ip_img/.*\.(gif|jpe?g)
2932 /cgi-bin/nph-adclick.exe/
2933 /.*/Image/BannerAdvertising/
2935 /.*/adlib/server\.cgi
2943 Note that many of these actions have the potential to cause a page to
2944 misbehave, possibly even not to display at all. There are many ways
2945 a site designer may choose to design his site, and what HTTP header
2946 content he may depend on. There is no way to have hard and fast rules
2947 for all sites. See the <link linkend="ACTIONSANAT">Appendix</link>
2948 for a brief example on troubleshooting actions.
2954 <!-- ~ End section ~ -->
2957 <!-- ~~~~~ New section ~~~~~ -->
2959 <title>Aliases</title>
2961 Custom <quote>actions</quote>, known to <application>Privoxy</application>
2962 as <quote>aliases</quote>, can be defined by combining other <quote>actions</quote>.
2963 These can in turn be invoked just like the built-in <quote>actions</quote>.
2964 Currently, an alias can contain any character except space, tab, <quote>=</quote>,
2965 <quote>{</quote> or <quote>}</quote>. But please use only <quote>a</quote>-
2966 <quote>z</quote>, <quote>0</quote>-<quote>9</quote>, <quote>+</quote>, and
2967 <quote>-</quote>. Alias names are not case sensitive, and
2968 <emphasis>must be defined before anything</emphasis> else in the
2969 <filename>default.action</filename>file! And there can only be one set of
2970 <quote>aliases</quote> defined.
2974 Now let's define a few aliases:
2981 # Useful customer aliases we can use later. These must come first!
2983 +no-cookies = +no-cookies-set +no-cookies-read
2984 -no-cookies = -no-cookies-set -no-cookies-read
2985 fragile = -block -no-cookies -filter -fast-redirects -hide-referer -no-popups
2986 shop = -no-cookies -filter -fast-redirects
2987 +imageblock = +block +image
2989 #For people who don't like to type too much: ;-)
2992 c2 = -no-cookies-set +no-cookies-read
2993 c3 = +no-cookies-set -no-cookies-read
2994 #... etc. Customize to your heart's content.
3001 Some examples using our <quote>shop</quote> and <quote>fragile</quote>
3009 # These sites are very complex and require
3010 # minimal interference.
3012 .office.microsoft.com
3013 .windowsupdate.microsoft.com
3016 # Shopping sites - still want to block ads.
3019 .worldpay.com # for quietpc.com
3023 # These shops require pop-ups
3033 The <quote>shop</quote> and <quote>fragile</quote> aliases are often used for
3034 <quote>problem</quote> sites that require most actions to be disabled
3035 in order to function properly.
3042 <!-- ~ End section ~ -->
3045 <!-- ~~~~~ New section ~~~~~ -->
3046 <sect2 id="filterfile">
3047 <title>The Filter File</title>
3049 Any web page can be dynamically modified with the filter file. This
3050 modification can be removal, or re-writing, of any web page content,
3051 including tags and non-visible content. The default filter file is
3052 <filename>default.filter</filename>, located in the config directory.
3056 This is potentially a very powerful feature, and requires knowledge of both
3057 <quote>regular expression</quote> and HTML in order create custom
3058 filters. But, there are a number of useful filters included with
3059 <application>Privoxy</application> for many common situations.
3063 The included example file is divided into sections. Each section begins
3064 with the <literal>FILTER</literal> keyword, followed by the identifier
3065 for that section, e.g. <quote>FILTER: webbugs</quote>. Each section performs
3066 a similar type of filtering, such as <quote>html-annoyances</quote>.
3070 This file uses regular expressions to alter or remove any string in the
3071 target page. The expressions can only operate on one line at a time. Some
3072 examples from the included default <filename>default.filter</filename>:
3076 Stop web pages from displaying annoying messages in the status bar by
3077 deleting such references:
3084 FILTER: html-annoyances
3086 # New browser windows should be resizeable and have a location and status
3089 s/resizable="?(no|0)"?/resizable=1/ig s/noresize/yesresize/ig
3090 s/location="?(no|0)"?/location=1/ig s/status="?(no|0)"?/status=1/ig
3091 s/scrolling="?(no|0|Auto)"?/scrolling=1/ig
3092 s/menubar="?(no|0)"?/menubar=1/ig
3094 # The <BLINK> tag was a crime!
3096 s*<blink>|</blink>**ig
3100 #s/framespacing="?(no|0)"?//ig
3101 #s/margin(height|width)=[0-9]*//gi
3108 Just for kicks, replace any occurrence of <quote>Microsoft</quote> with
3109 <quote>MicroSuck</quote>, and have a little fun with topical buzzwords:
3118 s/microsoft(?!.com)/MicroSuck/ig
3122 s/industry-leading|cutting-edge|award-winning/<font color=red><b>BINGO!</b></font>/ig
3129 Kill those pesky little web-bugs:
3136 # webbugs: Squish WebBugs (1x1 invisible GIFs used for user tracking)
3139 s/<img\s+[^>]*?(width|height)\s*=\s*['"]?1\D[^>]*?(width|height)\s*=\s*['"]?1(\D[^>]*?)?>/<!-- Squished WebBug -->/sig
3147 <!-- ~ End section ~ -->
3151 <!-- ~~~~~ New section ~~~~~ -->
3154 <title>Templates</title>
3156 When <application>Privoxy</application> displays one of its internal
3157 pages, such as a 404 Not Found error page, it uses the appropriate template.
3158 On Linux, BSD, and Unix, these are located in
3159 <filename>/etc/privoxy/templates</filename> by default. These may be
3160 customized, if desired.
3163 The default <quote>Blocked</quote> banner page with the bright red top
3164 banner, is called just <quote><filename>blocked</filename></quote>. This
3165 may be customized or replaced with something else if desired.
3172 <!-- ~ End section ~ -->
3176 <!-- ~~~~~ New section ~~~~~ -->
3178 <sect1 id="contact"><title>Contacting the Developers, Bug Reporting and Feature
3181 We value your feedback. However, to provide you with the best support,
3186 <listitem><para>Use the <ulink url="http://sourceforge.net/tracker/?group_id=11118&atid=211118">Sourceforge support forum</ulink> to get
3187 help.</para></listitem>
3189 <listitem><para>Submit bugs only thru our <ulink url="http://sourceforge.net/tracker/?group_id=11118&atid=111118">Sourceforge bug
3193 Make sure that the bug has not already been submitted. Please try to
3194 verify that it is a <application>Privoxy</application> bug, and not a
3195 browser or site bug first. If you are using your own custom configuration,
3196 please try the stock configs to see if the problem is a configuration
3197 related bug. And if not using the latest development snapshot, please try
3198 the latest one. Or even better, CVS sources. Please be sure to include the
3199 <application>Privoxy</application>/<application>Junkbuster</application>
3200 version, platform, browser, any pertinent log data, any other relevant
3201 details (please be specific) and, if possible, some way to reproduce the
3206 <listitem><para>Submit feature requests only thru our <ulink
3207 url="http://sourceforge.net/tracker/?atid=361118&group_id=11118&func=browse">Sourceforge feature request forum</ulink>.</para></listitem>
3215 For any other issues, feel free to use the <ulink url="http://sourceforge.net/mail/?group_id=11118">mailing lists</ulink>.
3219 Anyone interested in actively participating in development and related
3220 discussions can join the appropriate mailing list
3221 <ulink url="http://sourceforge.net/mail/?group_id=11118">here</ulink>.
3222 Archives are available here too.
3228 <!-- ~~~~~ New section ~~~~~ -->
3229 <sect1 id="copyright"><title>Copyright and History</title>
3232 <title>License</title>
3234 <application>Privoxy</application> is free software; you can
3235 redistribute it and/or modify it under the terms of the GNU General Public
3237 <informalfigure float="0">
3240 <imagedata fileref="gnu.jpg" format="jpg">
3243 <phrase>GNU's Pet GNU</phrase>
3248 License as published by the Free Software Foundation; either version 2 of the
3249 License, or (at your option) any later version.
3254 This program is distributed in the hope that it will be useful, but WITHOUT
3255 ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
3256 FOR A PARTICULAR PURPOSE. See the GNU General Public License for more
3257 details, which is available from the Free Software Foundation,
3258 Inc, 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
3262 You should have received a copy of the <ulink
3263 url="http://www.gnu.org/copyleft/gpl.html">GNU General Public License</ulink>
3264 along with this program; if not, write to the Free Software Foundation, Inc.,
3265 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA.
3270 <!-- ~ End section ~ -->
3273 <!-- ~~~~~ New section ~~~~~ -->
3275 <sect2 id="history">
3276 <title>History</title>
3278 <application>Privoxy</application> is evolved, and derived from,
3279 <application>the Internet Junkbuster</application>, with many
3280 improvments and enhancements over the original.
3284 <application>Junkbuster</application> was originally written by Anonymous
3286 url="http://www.junkbusters.com">Junkbuster's
3287 Corporation</ulink>, and was released as free open-source software under the
3288 GNU GPL. <ulink url="http://www.waldherr.org/junkbuster/">Stefan
3289 Waldherr</ulink> made many improvements, and started the <ulink
3290 url="http://sourceforge.net/projects/ijbswa/">SourceForge project
3291 Privoxy</ulink> to rekindle development. There are now several active
3292 developers contributing. The last stable release of
3293 <application>Junkbuster</application> was v2.0.2, which has now
3301 <!-- ~~~~~ New section ~~~~~ -->
3302 <sect1 id="seealso"><title>See Also</title>
3304 Include seealso.sgml:
3312 <!-- ~~~~~ New section ~~~~~ -->
3313 <sect1 id="appendix"><title>Appendix</title>
3316 <!-- ~~~~~ New section ~~~~~ -->
3318 <title>Regular Expressions</title>
3320 <application>Privoxy</application> can use <quote>regular expressions</quote>
3321 in various config files. Assuming support for <quote>pcre</quote> (Perl
3322 Compatible Regular Expressions) is compiled in, which is the default. Such
3323 configuration directives do not require regular expressions, but they can be
3324 used to increase flexibility by matching a pattern with wild-cards against
3329 If you are reading this, you probably don't understand what <quote>regular
3330 expressions</quote> are, or what they can do. So this will be a very brief
3331 introduction only. A full explanation would require a book ;-)
3335 <quote>Regular expressions</quote> is a way of matching one character
3336 expression against another to see if it matches or not. One of the
3337 <quote>expressions</quote> is a literal string of readable characters
3338 (letter, numbers, etc), and the other is a complex string of literal
3339 characters combined with wild-cards, and other special characters, called
3340 meta-characters. The <quote>meta-characters</quote> have special meanings and
3341 are used to build the complex pattern to be matched against. Perl Compatible
3342 Regular Expressions is an enhanced form of the regular expression language
3343 with backward compatibility.
3347 To make a simple analogy, we do something similar when we use wild-card
3348 characters when listing files with the <command>dir</command> command in DOS.
3349 <literal>*.*</literal> matches all filenames. The <quote>special</quote>
3350 character here is the asterisk which matches any and all characters. We can be
3351 more specific and use <literal>?</literal> to match just individual
3352 characters. So <quote>dir file?.text</quote> would match
3353 <quote>file1.txt</quote>, <quote>file2.txt</quote>, etc. We are pattern
3354 matching, using a similar technique to <quote>regular expressions</quote>!
3358 Regular expressions do essentially the same thing, but are much, much more
3359 powerful. There are many more <quote>special characters</quote> and ways of
3360 building complex patterns however. Let's look at a few of the common ones,
3361 and then some examples:
3366 <emphasis>.</emphasis> - Matches any single character, e.g. <quote>a</quote>,
3367 <quote>A</quote>, <quote>4</quote>, <quote>:</quote>, or <quote>@</quote>.
3373 <emphasis>?</emphasis> - The preceding character or expression is matched ZERO or ONE
3380 <emphasis>+</emphasis> - The preceding character or expression is matched ONE or MORE
3387 <emphasis>*</emphasis> - The preceding character or expression is matched ZERO or MORE
3394 <emphasis>\</emphasis> - The <quote>escape</quote> character denotes that
3395 the following character should be taken literally. This is used where one of the
3396 special characters (e.g. <quote>.</quote>) needs to be taken literally and
3397 not as a special meta-character.
3403 <emphasis>[]</emphasis> - Characters enclosed in brackets will be matched if
3404 any of the enclosed characters are encountered.
3410 <emphasis>()</emphasis> - parentheses are used to group a sub-expression,
3411 or multiple sub-expressions.
3417 <emphasis>|</emphasis> - The <quote>bar</quote> character works like an
3418 <quote>or</quote> conditional statement. A match is successful if the
3419 sub-expression on either side of <quote>|</quote> matches.
3425 <emphasis>s/string1/string2/g</emphasis> - This is used to rewrite strings of text.
3426 <quote>string1</quote> is replaced by <quote>string2</quote> in this
3432 These are just some of the ones you are likely to use when matching URLs with
3433 <application>Privoxy</application>, and is a long way from a definitive
3434 list. This is enough to get us started with a few simple examples which may
3435 be more illuminating:
3439 <emphasis><literal>/.*/banners/.*</literal></emphasis> - A simple example
3440 that uses the common combination of <quote>.</quote> and <quote>*</quote> to
3441 denote any character, zero or more times. In other words, any string at all.
3442 So we start with a literal forward slash, then our regular expression pattern
3443 (<quote>.*</quote>) another literal forward slash, the string
3444 <quote>banners</quote>, another forward slash, and lastly another
3445 <quote>.*</quote>. We are building
3446 a directory path here. This will match any file with the path that has a
3447 directory named <quote>banners</quote> in it. The <quote>.*</quote> matches
3448 any characters, and this could conceivably be more forward slashes, so it
3449 might expand into a much longer looking path. For example, this could match:
3450 <quote>/eye/hate/spammers/banners/annoy_me_please.gif</quote>, or just
3451 <quote>/banners/annoying.html</quote>, or almost an infinite number of other
3452 possible combinations, just so it has <quote>banners</quote> in the path
3457 A now something a little more complex:
3461 <emphasis><literal>/.*/adv((er)?ts?|ertis(ing|ements?))?/</literal></emphasis> -
3462 We have several literal forward slashes again (<quote>/</quote>), so we are
3463 building another expression that is a file path statement. We have another
3464 <quote>.*</quote>, so we are matching against any conceivable sub-path, just so
3465 it matches our expression. The only true literal that <emphasis>must
3466 match</emphasis> our pattern is <application>adv</application>, together with
3467 the forward slashes. What comes after the <quote>adv</quote> string is the
3472 Remember the <quote>?</quote> means the preceding expression (either a
3473 literal character or anything grouped with <quote>(...)</quote> in this case)
3474 can exist or not, since this means either zero or one match. So
3475 <quote>((er)?ts?|ertis(ing|ements?))</quote> is optional, as are the
3476 individual sub-expressions: <quote>(er)</quote>,
3477 <quote>(ing|ements?)</quote>, and the <quote>s</quote>. The <quote>|</quote>
3478 means <quote>or</quote>. We have two of those. For instance,
3479 <quote>(ing|ements?)</quote>, can expand to match either <quote>ing</quote>
3480 <emphasis>OR</emphasis> <quote>ements?</quote>. What is being done here, is an
3481 attempt at matching as many variations of <quote>advertisement</quote>, and
3482 similar, as possible. So this would expand to match just <quote>adv</quote>,
3483 or <quote>advert</quote>, or <quote>adverts</quote>, or
3484 <quote>advertising</quote>, or <quote>advertisement</quote>, or
3485 <quote>advertisements</quote>. You get the idea. But it would not match
3486 <quote>advertizements</quote> (with a <quote>z</quote>). We could fix that by
3487 changing our regular expression to:
3488 <quote>/.*/adv((er)?ts?|erti(s|z)(ing|ements?))?/</quote>, which would then match
3493 <emphasis><literal>/.*/advert[0-9]+\.(gif|jpe?g)</literal></emphasis> - Again
3494 another path statement with forward slashes. Anything in the square brackets
3495 <quote>[]</quote> can be matched. This is using <quote>0-9</quote> as a
3496 shorthand expression to mean any digit one through nine. It is the same as
3497 saying <quote>0123456789</quote>. So any digit matches. The <quote>+</quote>
3498 means one or more of the preceding expression must be included. The preceding
3499 expression here is what is in the square brackets -- in this case, any digit
3500 one through nine. Then, at the end, we have a grouping: <quote>(gif|jpe?g)</quote>.
3501 This includes a <quote>|</quote>, so this needs to match the expression on
3502 either side of that bar character also. A simple <quote>gif</quote> on one side, and the other
3503 side will in turn match either <quote>jpeg</quote> or <quote>jpg</quote>,
3504 since the <quote>?</quote> means the letter <quote>e</quote> is optional and
3505 can be matched once or not at all. So we are building an expression here to
3506 match image GIF or JPEG type image file. It must include the literal
3507 string <quote>advert</quote>, then one or more digits, and a <quote>.</quote>
3508 (which is now a literal, and not a special character, since it is escaped
3509 with <quote>\</quote>), and lastly either <quote>gif</quote>, or
3510 <quote>jpeg</quote>, or <quote>jpg</quote>. Some possible matches would
3511 include: <quote>//advert1.jpg</quote>,
3512 <quote>/nasty/ads/advert1234.gif</quote>,
3513 <quote>/banners/from/hell/advert99.jpg</quote>. It would not match
3514 <quote>advert1.gif</quote> (no leading slash), or
3515 <quote>/adverts232.jpg</quote> (the expression does not include an
3516 <quote>s</quote>), or <quote>/advert1.jsp</quote> (<quote>jsp</quote> is not
3517 in the expression anywhere).
3521 <emphasis><literal>s/microsoft(?!.com)/MicroSuck/i</literal></emphasis> - This is
3522 a substitution. <quote>MicroSuck</quote> will replace any occurrence of
3523 <quote>microsoft</quote>. The <quote>i</quote> at the end of the expression
3524 means ignore case. The <quote>(?!.com)</quote> means
3525 the match should fail if <quote>microsoft</quote> is followed by
3526 <quote>.com</quote>. In other words, this acts like a <quote>NOT</quote>
3527 modifier. In case this is a hyperlink, we don't want to break it ;-).
3531 We are barely scratching the surface of regular expressions here so that you
3532 can understand the default <application>Privoxy</application>
3533 configuration files, and maybe use this knowledge to customize your own
3534 installation. There is much, much more that can be done with regular
3535 expressions. Now that you know enough to get started, you can learn more on
3540 More reading on Perl Compatible Regular expressions:
3541 <ulink url="http://www.perldoc.com/perl5.6/pod/perlre.html">http://www.perldoc.com/perl5.6/pod/perlre.html</ulink>
3546 <!-- ~ End section ~ -->
3549 <!-- ~~~~~ New section ~~~~~ -->
3551 <title><application>Privoxy</application>'s Internal Pages</title>
3554 Since <application>Privoxy</application> proxies each requested
3555 web page, it is easy for <application>Privoxy</application> to
3556 trap certain special URLs. In this way, we can talk directly to
3557 <application>Privoxy</application>, and see how it is
3558 configured, see how our rules are being applied, change these
3559 rules and other configuration options, and even turn
3560 <application>Privoxy's</application> filtering off, all with
3566 The URLs listed below are the special ones that allow direct access
3567 to <application>Privoxy</application>. Of course,
3568 <application>Privoxy</application> must be running to access these. If
3569 not, you will get a friendly error message. Internet access is not
3582 <ulink url="http://config.privoxy.org/">http://config.privoxy.org/</ulink>
3586 Alternately, this may be reached at <ulink
3587 url="http://p.p/">http://p.p/</ulink>, but this
3588 variation may not work as reliably as the above in some configurations.
3594 Show information about the current configuration:
3598 <ulink url="http://config.privoxy.org/show-status">http://config.privoxy.org/show-status</ulink>
3605 Show the source code version numbers:
3609 <ulink url="http://config.privoxy.org/show-version">http://config.privoxy.org/show-version</ulink>
3616 Show the client's request headers:
3620 <ulink url="http://config.privoxy.org/show-request">http://config.privoxy.org/show-request</ulink>
3627 Show which actions apply to a URL and why:
3631 <ulink url="http://config.privoxy.org/show-url-info">http://config.privoxy.org/show-url-info</ulink>
3638 Toggle Privoxy on or off. In this case, <quote>Privoxy</quote> continues
3639 to run, but only as a pass-through proxy, with no actions taking place:
3643 <ulink url="http://config.privoxy.org/toggle">http://config.privoxy.org/toggle</ulink>
3647 Short cuts. Turn off, then on:
3651 <ulink url="http://config.privoxy.org/toggle?set=disable">http://config.privoxy.org/toggle?set=disable</ulink>
3656 <ulink url="http://config.privoxy.org/toggle?set=enable">http://config.privoxy.org/toggle?set=enable</ulink>
3663 Edit the actions list file:
3667 <ulink url="http://config.privoxy.org/edit-actions">http://config.privoxy.org/edit-actions</ulink>
3676 These may be bookmarked for quick reference.
3680 <sect3 id="bookmarklets">
3681 <title>Bookmarklets</title>
3683 Here are some bookmarklets to allow you to easily access a
3684 <quote>mini</quote> version of this page. They are designed for MS Internet
3685 Explorer, but should work equally well in Netscape, Mozilla, and other
3686 browsers which support JavaScript. They are designed to run directly from
3687 your bookmarks - not by clicking the links below (although that will work for
3691 To save them, right-click the link and choose <quote>Add to Favorites</quote>
3692 (IE) or <quote>Add Bookmark</quote> (Netscape). You will get a warning that
3693 the bookmark <quote>may not be safe</quote> - just click OK. Then you can run the
3694 Bookmarklet directly from your favourites/bookmarks. For even faster access,
3695 you can put them on the <quote>Links</quote> bar (IE) or the <quote>Personal
3696 Toolbar</quote> (Netscape), and run them with a single click.
3704 <ulink 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());">Enable Privoxy</ulink>
3710 <ulink 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());">Disable Privoxy</ulink>
3716 <ulink 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());">Toggle Privoxy</ulink> (Toggles between enabled and disabled)
3722 <ulink 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());">View Privoxy Status</ulink>
3730 Credit: The site which gave me the general idea for these bookmarklets is
3731 <ulink url="http://www.bookmarklets.com">www.bookmarklets.com</ulink>. They
3732 have more information about bookmarklets.
3741 <!-- ~~~~~ New section ~~~~~ -->
3742 <sect2 id="actionsanat">
3743 <title>Anatomy of an Action</title>
3746 The way <application>Privoxy</application> applies <quote>actions</quote>
3747 and <quote>filters</quote> to any given URL can be complex, and not always so
3748 easy to understand what is happening. And sometimes we need to be able to
3749 <emphasis>see</emphasis> just what <application>Privoxy</application> is
3750 doing. Especially, if something <application>Privoxy</application> is doing
3751 is causing us a problem inadvertantly. It can be a little daunting to look at
3752 the actions and filters files themselves, since they tend to be filled with
3753 <quote>regular expressions</quote> whose consequences are not always
3754 so obvious. <application>Privoxy</application> provides the
3755 <ulink url="http://config.privoxy.org/show-url-info">http://config.privoxy.org/show-url-info</ulink>
3756 page that can show us very specifically how <application>actions</application>
3757 are being applied to any given URL. This is a big help for troubleshooting.
3761 First, enter one URL (or partial URL) at the prompt, and then
3762 <application>Privoxy</application> will tell us
3763 how the current configuration will handle it. This will not
3764 help with filtering effects from the <filename>default.filter</filename> file! It
3765 also will not tell you about any other URLs that may be embedded within the
3766 URL you are testing. For instance, images such as ads are expressed as URLs
3767 within the raw page source of HTML pages. So you will only get info for the
3768 actual URL that is pasted into the prompt area -- not any sub-URLs. If you
3769 want to know about embedded URLs like ads, you will have to dig those out of
3770 the HTML source. Use your browser's <quote>View Page Source</quote> option
3775 Let's look at an example, <ulink url="http://google.com">google.com</ulink>,
3776 one section at a time:
3781 System default actions:
3783 { -add-header -block -deanimate-gifs -downgrade -fast-redirects -filter
3784 -hide-forwarded -hide-from -hide-referer -hide-user-agent -image
3785 -image-blocker -limit-connect -no-compression -no-cookies-keep
3786 -no-cookies-read -no-cookies-set -no-popups -vanilla-wafer -wafer }
3792 This is the top section, and only tells us of the compiled in defaults. This
3793 is basically what <application>Privoxy</application> would do if there
3794 were not any <quote>actions</quote> defined, i.e. it does nothing. Every action
3795 is disabled. This is not particularly informative for our purposes here. OK,
3802 Matches for http://google.com:
3804 { -add-header -block +deanimate-gifs -downgrade +fast-redirects
3805 +filter{html-annoyances} +filter{js-annoyances} +filter{no-popups}
3806 +filter{webbugs} +filter{nimda} +filter{banners-by-size} +filter{hal}
3807 +filter{fun} +hide-forwarded +hide-from{block} +hide-referer{forge}
3808 -hide-user-agent -image +image-blocker{blank} +no-compression
3809 +no-cookies-keep -no-cookies-read -no-cookies-set +no-popups
3810 -vanilla-wafer -wafer }
3813 { -no-cookies-keep -no-cookies-read -no-cookies-set }
3823 This is much more informative, and tells us how we have defined our
3824 <quote>actions</quote>, and which ones match for our example,
3825 <quote>google.com</quote>. The first grouping shows our default
3826 settings, which would apply to all URLs. If you look at your <quote>actions</quote>
3827 file, this would be the section just below the <quote>aliases</quote> section
3828 near the top. This applies to all URLs as signified by the single forward
3829 slash -- <quote>/</quote>.
3834 These are the default actions we have enabled. But we can define additional
3835 actions that would be exceptions to these general rules, and then list
3836 specific URLs that these exceptions would apply to. Last match wins.
3837 Just below this then are two explict matches for <quote>.google.com</quote>.
3838 The first is negating our various cookie blocking actions (i.e. we will allow
3839 cookies here). The second is allowing <quote>fast-redirects</quote>. Note
3840 that there is a leading dot here -- <quote>.google.com</quote>. This will
3841 match any hosts and sub-domains, in the google.com domain also, such as
3842 <quote>www.google.com</quote>. So, apparently, we have these actions defined
3843 somewhere in the lower part of our actions file, and
3844 <quote>google.com</quote> is referenced in these sections.
3849 And now we pull it altogether in the bottom section and summarize how
3850 <application>Privoxy</application> is appying all its <quote>actions</quote>
3851 to <quote>google.com</quote>:
3860 -add-header -block -deanimate-gifs -downgrade -fast-redirects
3861 +filter{html-annoyances} +filter{js-annoyances} +filter{no-popups}
3862 +filter{webbugs} +filter{nimda} +filter{banners-by-size} +filter{hal}
3863 +filter{fun} +hide-forwarded +hide-from{block} +hide-referer{forge}
3864 -hide-user-agent -image +image-blocker{blank} -limit-connect +no-compression
3865 -no-cookies-keep -no-cookies-read -no-cookies-set +no-popups -vanilla-wafer
3872 Now another example, <quote>ad.doubleclick.net</quote>:
3891 We'll just show the interesting part here, the explicit matches. It is
3892 matched three different times. Each as an <quote>+block +image</quote>,
3893 which is the expanded form of one of our aliases that had been defined as:
3894 <quote>+imageblock</quote>. (<quote>Aliases</quote> are defined in the
3895 first section of the actions file and typically used to combine more
3900 Any one of these would have done the trick and blocked this as an unwanted
3901 image. This is unnecessarily redundant since the last case effectively
3902 would also cover the first. No point in taking chances with these guys
3903 though ;-) Note that if you want an ad or obnoxious
3904 URL to be invisible, it should be defined as <quote>ad.doubleclick.net</quote>
3905 is done here -- as both a <quote>+block</quote> <emphasis>and</emphasis> an
3906 <quote>+image</quote>. The custom alias <quote>+imageblock</quote> does this
3911 One last example. Let's try <quote>http://www.rhapsodyk.net/adsl/HOWTO/</quote>.
3912 This one is giving us problems. We are getting a blank page. Hmmm...
3918 Matches for http://www.rhapsodyk.net/adsl/HOWTO/:
3920 { -add-header -block +deanimate-gifs -downgrade +fast-redirects
3921 +filter{html-annoyances} +filter{js-annoyances} +filter{no-popups}
3922 +filter{webbugs} +filter{nimda} +filter{banners-by-size} +filter{hal}
3923 +filter{fun} +hide-forwarded +hide-from{block} +hide-referer{forge}
3924 -hide-user-agent -image +image-blocker{blank} +no-compression
3925 +no-cookies-keep -no-cookies-read -no-cookies-set +no-popups
3926 -vanilla-wafer -wafer }
3936 Ooops, the <quote>/adsl/</quote> is matching <quote>/ads</quote>! But
3937 we did not want this at all! Now we see why we get the blank page. We could
3938 now add a new action below this that explictly does <emphasis>not</emphasis>
3939 block (-block) pages with <quote>adsl</quote>. There are various ways to
3940 handle such exceptions. Example:
3953 Now the page displays ;-) Be sure to flush your browser's caches when
3954 making such changes. Or, try using <literal>Shift+Reload</literal>.
3959 But now what about a situation where we get no explicit matches like
3974 That actually was very telling and pointed us quickly to where the problem
3975 was. If you don't get this kind of match, then it means one of the default
3976 rules in the first section is causing the problem. This would require some
3977 guesswork, and maybe a little trial and error to isolate the offending rule.
3978 One likely cause would be one of the <quote>{+filter}</quote> actions. Try
3979 adding the URL for the site to one of aliases that turn off <quote>+filter</quote>:
3987 .worldpay.com # for quietpc.com
3996 <quote>{shop}</quote> is an <quote>alias</quote> that expands to
3997 <quote>{ -filter -no-cookies -no-cookies-keep }</quote>. Or you could do
3998 your own exception to negate filtering:
4012 <quote>{fragile}</quote> is an alias that disables most actions. This can be
4013 used as a last resort for problem sites. Remember to flush caches! If this
4014 still does not work, you will have to go through the remaining actions one by
4015 one to find which one(s) is causing the problem.
4024 This program is free software; you can redistribute it
4025 and/or modify it under the terms of the GNU General
4026 Public License as published by the Free Software
4027 Foundation; either version 2 of the License, or (at
4028 your option) any later version.
4030 This program is distributed in the hope that it will
4031 be useful, but WITHOUT ANY WARRANTY; without even the
4032 implied warranty of MERCHANTABILITY or FITNESS FOR A
4033 PARTICULAR PURPOSE. See the GNU General Public
4034 License for more details.
4036 The GNU General Public License should be included with
4037 this file. If not, you can view it at
4038 http://www.gnu.org/copyleft/gpl.html
4039 or write to the Free Software Foundation, Inc., 59
4040 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
4042 $Log: user-manual.sgml,v $
4043 Revision 1.63 2002/04/01 16:24:49 hal9
4044 Define entities to include boilerplate text. See doc/source/*.
4046 Revision 1.62 2002/03/30 04:15:53 hal9
4047 - Fix privoxy.org/config links.
4048 - Paste in Bookmarklets from Toggle page.
4049 - Move Quickstart nearer top, and minor rework.
4051 Revision 1.61 2002/03/29 01:31:08 hal9
4054 Revision 1.60 2002/03/27 01:57:34 hal9
4055 Added more to Anatomy section.
4057 Revision 1.59 2002/03/27 00:54:33 hal9
4058 Touch up intro for new name.
4060 Revision 1.58 2002/03/26 22:29:55 swa
4061 we have a new homepage!
4063 Revision 1.57 2002/03/24 20:33:30 hal9
4064 A few minor catch ups with name change.
4066 Revision 1.56 2002/03/24 16:17:06 swa
4067 configure needs to be generated.
4069 Revision 1.55 2002/03/24 16:08:08 swa
4070 we are too lazy to make a block-built
4071 privoxy logo. hence removed the option.
4073 Revision 1.54 2002/03/24 15:46:20 swa
4074 name change related issue.
4076 Revision 1.53 2002/03/24 11:51:00 swa
4077 name change. changed filenames.
4079 Revision 1.52 2002/03/24 11:01:06 swa
4082 Revision 1.51 2002/03/23 15:13:11 swa
4083 renamed every reference to the old name with foobar.
4084 fixed "application foobar application" tag, fixed
4085 "the foobar" with "foobar". left junkbustser in cvs
4086 comments and remarks to history untouched.
4088 Revision 1.50 2002/03/23 05:06:21 hal9
4091 Revision 1.49 2002/03/21 17:01:05 hal9
4092 New section in Appendix.
4094 Revision 1.48 2002/03/12 06:33:01 hal9
4095 Catching up to Andreas and re_filterfile changes.
4097 Revision 1.47 2002/03/11 13:13:27 swa
4098 correct feedback channels
4100 Revision 1.46 2002/03/10 00:51:08 hal9
4101 Added section on JB internal pages in Appendix.
4103 Revision 1.45 2002/03/09 17:43:53 swa
4106 Revision 1.44 2002/03/09 17:08:48 hal9
4107 New section on Jon's actions file editor, and move some stuff around.
4109 Revision 1.43 2002/03/08 00:47:32 hal9
4110 Added imageblock{pattern}.
4112 Revision 1.42 2002/03/07 18:16:55 swa
4115 Revision 1.41 2002/03/07 16:46:43 hal9
4116 Fix a few markup problems for jade.
4118 Revision 1.40 2002/03/07 16:28:39 swa
4119 provide correct feedback channels
4121 Revision 1.39 2002/03/06 16:19:28 hal9
4122 Note on perceived filtering slowdown per FR.
4124 Revision 1.38 2002/03/05 23:55:14 hal9
4125 Stupid I did it again. Double hyphen in comment breaks jade.
4127 Revision 1.37 2002/03/05 23:53:49 hal9
4128 jade barfs on '- -' embedded in comments. - -user option broke it.
4130 Revision 1.36 2002/03/05 22:53:28 hal9
4131 Add new - - user option.
4133 Revision 1.35 2002/03/05 00:17:27 hal9
4134 Added section on command line options.
4136 Revision 1.34 2002/03/04 19:32:07 oes
4137 Changed default port to 8118
4139 Revision 1.33 2002/03/03 19:46:13 hal9
4140 Emphasis on where/how to report bugs, etc
4142 Revision 1.32 2002/03/03 09:26:06 joergs
4143 AmigaOS changes, config is now loaded from PROGDIR: instead of
4144 AmiTCP:db/junkbuster/ if no configuration file is specified on the
4147 Revision 1.31 2002/03/02 22:45:52 david__schmidt
4150 Revision 1.30 2002/03/02 22:00:14 hal9
4151 Updated 'New Features' list. Ran through spell-checker.
4153 Revision 1.29 2002/03/02 20:34:07 david__schmidt
4154 Update OS/2 build section
4156 Revision 1.28 2002/02/24 14:34:24 jongfoster
4157 Formatting changes. Now changing the doctype to DocBook XML 4.1
4158 will work - no other changes are needed.
4160 Revision 1.27 2002/01/11 14:14:32 hal9
4161 Added a very short section on Templates
4163 Revision 1.26 2002/01/09 20:02:50 hal9
4164 Fix bug re: auto-detect config file changes.
4166 Revision 1.25 2002/01/09 18:20:30 hal9
4167 Touch ups for *.action files.
4169 Revision 1.24 2001/12/02 01:13:42 hal9
4172 Revision 1.23 2001/12/02 00:20:41 hal9
4173 Updates for recent changes.
4175 Revision 1.22 2001/11/05 23:57:51 hal9
4176 Minor update for startup now daemon mode.
4178 Revision 1.21 2001/10/31 21:11:03 hal9
4179 Correct 2 minor errors
4181 Revision 1.18 2001/10/24 18:45:26 hal9
4182 *** empty log message ***
4184 Revision 1.17 2001/10/24 17:10:55 hal9
4185 Catching up with Jon's recent work, and a few other things.
4187 Revision 1.16 2001/10/21 17:19:21 swa
4188 wrong url in documentation
4190 Revision 1.15 2001/10/14 23:46:24 hal9
4191 Various minor changes. Fleshed out SEE ALSO section.
4193 Revision 1.13 2001/10/10 17:28:33 hal9
4196 Revision 1.12 2001/09/28 02:57:04 hal9
4199 Revision 1.11 2001/09/28 02:25:20 hal9
4202 Revision 1.9 2001/09/27 23:50:29 hal9
4203 A few changes. A short section on regular expression in appendix.
4205 Revision 1.8 2001/09/25 00:34:59 hal9
4206 Some additions, and re-arranging.
4208 Revision 1.7 2001/09/24 14:31:36 hal9
4211 Revision 1.6 2001/09/24 14:10:32 hal9
4212 Including David's OS/2 installation instructions.
4214 Revision 1.2 2001/09/13 15:27:40 swa
4217 Revision 1.1 2001/09/12 15:36:41 swa
4218 source files for junkbuster documentation
4220 Revision 1.3 2001/09/10 17:43:59 swa
4221 first proposal of a structure.
4223 Revision 1.2 2001/06/13 14:28:31 swa
4224 docs should have an author.
4226 Revision 1.1 2001/06/13 14:20:37 swa
4227 first import of project's documentation for the webserver.
projects / privoxy.git / blob