This file belongs into
ijbswa.sourceforge.net:/home/groups/i/ij/ijbswa/htdocs/
- $Id: user-manual.sgml,v 1.36 2002/03/05 22:53:28 hal9 Exp $
+ $Id: user-manual.sgml,v 1.57 2002/03/24 20:33:30 hal9 Exp $
Written by and Copyright (C) 2001 the SourceForge
- IJBSWA team. http://ijbswa.sourceforge.net
+ Privoxy team. http://www.privoxy.org/
Based on the Internet Junkbuster originally written
by and Copyright (C) 1997 Anonymous Coders and
<article id="index">
<artheader>
-<title>Junkbuster User Manual</title>
+<title>Privoxy User Manual</title>
-<pubdate>$Id: user-manual.sgml,v 1.36 2002/03/05 22:53:28 hal9 Exp $</pubdate>
+<pubdate>$Id: user-manual.sgml,v 1.57 2002/03/24 20:33:30 hal9 Exp $</pubdate>
<authorgroup>
<author>
<affiliation>
- <orgname>By: Junkbuster Developers</orgname>
+ <orgname>By: Privoxy Developers</orgname>
</affiliation>
</author>
</authorgroup>
<abstract>
<para>
- The user manual gives the users information on how to install and configure
- <application>Internet Junkbuster</application>. <application>Internet
- Junkbuster</application> is an application that provides privacy and
- security to users of the World Wide Web.
+ The user manual gives users information on how to install, configure and use
+ <application>Privoxy</application>. <application>Privoxy</application> is a
+ web proxy with advanced filtering capabilities for protecting privacy,
+ filtering web page content, managing cookies, controlling access, and
+ removing ads, banners, pop-ups and other obnoxious Internet
+ Junk. <application>Privoxy</application> has a very flexible configuration
+ and can be customized to suit individual needs and
+ tastes. <application>Privoxy</application> has application for both
+ stand-alone systems and multi-user networks.
</para>
<para>
-You can find the latest version of the user manual at <ulink url="http://ijbswa.sourceforge.net/user-manual/">http://ijbswa.sourceforge.net/user-manual/</ulink>.
+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>.
</para>
- <para>
- Feel free to send a note to the developers at <email>ijbswa-developers@lists.sourceforge.net</email>.
- </para>
+<!-- <para> -->
+<!-- Feel free to send a note to the developers at <email>ijbswa-developers@lists.sourceforge.net</email>. -->
+<!-- </para> -->
</abstract>
</artheader>
<sect1 id="introduction"><title>Introduction</title>
<para>
- <application>Internet Junkbuster</application> is a web proxy with advanced
+ <application>Privoxy</application> is a web proxy with advanced
filtering capabilities for protecting privacy, filtering and modifying web
page content, managing cookies, controlling access, and removing ads,
banners, pop-ups and other obnoxious Internet Junk.
- <application>Junkbuster</application> has a very flexible configuration and
- can be customized to suit individual needs and tastes. <application>Internet
- Junkbuster</application> has application for both stand-alone systems and
+ <application>Privoxy</application> has a very flexible configuration and
+ can be customized to suit individual needs and tastes. <application>Privoxy</application> has application for both stand-alone systems and
multi-user networks.
</para>
+<para>
+ <application>Privoxy</application> is derived from
+ <application>Internet Junkbuster</application> by Junkbusters Corporation,
+ which is no longer under development. Many enhancements and
+ new features have been added.
+
+</para>
+
<para>
This documentation is included with the current BETA version of
- <application>Internet Junkbuster</application> and mostly complete at this
+ <application>Privoxy</application> and is mostly complete at this
point. The most up to date reference for the time being is still the comments
in the source files and in the individual configuration files. Development
of version 3.0 is currently nearing completion, and includes many significant
<para>
Since this is a BETA version, not all new features are well tested. This
- documentation may be slightly out of sync as a result. And there
- <emphasis>may be</emphasis> bugs, though hopefully not many!
+ documentation may be slightly out of sync as a result (especially with
+ CVS sources). And there <emphasis>may be</emphasis> bugs, though hopefully
+ not many!
</para>
<sect2>
<title>New Features</title>
<para>
- In addition to <application>Junkbuster's</application> traditional features
- of ad and banner blocking and cookie management, this is a list of new
- features currently under development:
+ In addition to <application>Internet Junkbuster's</application> traditional
+ feature of ad and banner blocking and cookie management,
+ <application>Privoxy</application> provides new features, some of them
+ currently under development:
</para>
+<!--
+ The section is in both user-manual and faq. Please keep in sync.
+-->
<para>
<itemizedlist>
<listitem>
<para>
Integrated browser based configuration and control utility (<ulink
- url="http://i.j.b">http://i.j.b</ulink>). Browser-based tracing of rule
+ url="http://p.p">http://p.p</ulink>). Browser-based tracing of rule
and filter effects.
</para>
</listitem>
-
+<!--
<listitem>
<para>
Modularized configuration that will allow for system wide settings, and
individual user settings. (not implemented yet, probably a 3.1 feature)
</para>
</listitem>
-
+-->
<listitem>
<para>
Blocking of annoying pop-up browser windows.
<listitem>
<para>
Builds from source on most UNIX-like systems. Packages available for: Linux
- (RedHat, SuSE, or Debian), Windows, Sun Solaris, Mac OSX, OS/2.
+ (RedHat, SuSE, or Debian), Windows, Sun Solaris, Mac OSX, OS/2, HP-UX 11 and AmigaOS.
</para>
</listitem>
<!-- ~~~~~ New section ~~~~~ -->
<sect1 id="installation"><title>Installation</title>
<para>
- <application>Junkbuster</application> is available as raw source code, or
+ <application>Privoxy</application> is available as raw source code, or
pre-compiled binaries. See the <ulink
- url="http://sourceforge.net/projects/ijbswa/">Junkbuster Home Page</ulink>
- for current release info. <application>Junkbuster</application> is also available
- via <ulink
+ url="http://sourceforge.net/projects/ijbswa/">Privoxy Home Page</ulink>
+ for binaries and current release info. <application>Privoxy</application>
+
is also available via <ulink
url="http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/ijbswa/current/">CVS</ulink>.
This is the recommended approach at this time. But please be aware that CVS
is constantly changing, and it may break in mysterious ways.
<para>
<screen>
- tar xzvf ijb_source_* [.tgz or .tar.gz]
- cd ijb_source_2.9.10_beta
+ tar xzvf privoxy-2.9.13-beta-src* [.tgz or .tar.gz]
+ cd privoxy-2.9.13-beta
</screen>
</para>
<para>
<screen>
- autoheader [suggested for CVS source]
- autoconf [suggested for CVS source]
+ autoheader
+ autoconf
./configure
make redhat-dist
</screen>
</para>
<para>
- /usr/src/redhat/RPMS/i686/junkbuster-2.9.11-1.i686.rpm
+ /usr/src/redhat/RPMS/i686/privoxy-2.9.11-1.i686.rpm
</para>
<para>
- /usr/src/redhat/SRPMS/junkbuster-2.9.11-1.src.rpm
+ /usr/src/redhat/SRPMS/privoxy-2.9.11-1.src.rpm
</para>
<para>
<para>
<screen>
- rpm -Uvv /usr/src/redhat/RPMS/i686/junkbuster-2.9.11-1.i686.rpm
+ rpm -Uvv /usr/src/redhat/RPMS/i686/privoxy-2.9.11-1.i686.rpm
</screen>
</para>
<para>
- This will place the <application>Junkbuster</application> configuration
- files in <filename>/etc/junkbuster/</filename>, and log files in
- <filename>/var/log/junkbuster/</filename>.
+ This will place the <application>Privoxy</application> configuration
+ files in <filename>/etc/privoxy/</filename>, and log files in
+ <filename>/var/log/privoxy/</filename>.
</para>
</sect2>
<para>
<screen>
- autoheader [suggested for CVS source]
- autoconf [suggested for CVS source]
+ autoheader
+ autoconf
./configure
make suse-dist
</screen>
</para>
<para>
- /usr/src/packages/RPMS/i686/junkbuster-2.9.11-1.i686.rpm
+ /usr/src/packages/RPMS/i686/privoxy-2.9.11-1.i686.rpm
</para>
<para>
- /usr/src/packages/SRPMS/junkbuster-2.9.11-1.src.rpm
+ /usr/src/packages/SRPMS/privoxy-2.9.11-1.src.rpm
</para>
<para>
<para>
<screen>
- rpm -Uvv /usr/src/packages/RPMS/i686/junkbuster-2.9.11-1.i686.rpm
+ rpm -Uvv /usr/src/packages/RPMS/i686/privoxy-2.9.11-1.i686.rpm
</screen>
</para>
<para>
- This will place the <application>Junkbuster</application> configuration
- files in <filename>/etc/junkbuster/</filename>, and log files in
- <filename>/var/log/junkbuster/</filename>.
+ This will place the <application>Privoxy</application> configuration
+ files in <filename>/etc/privoxy/</filename>, and log files in
+ <filename>/var/log/privoxy/</filename>.
</para>
</sect2>
-->
<para>
- <application>Junkbuster</application> is packaged in a WarpIN self-
+ <application>Privoxy</application> is packaged in a WarpIN self-
installing archive. The self-installing program will be named depending
on the release version, something like:
<filename>ijbos2_setup_1.2.3.exe</filename>. In order to install it, simply
run this executable or double-click on its icon and follow the WarpIN
- installation panels. A shadow of the <application>Junkbuster</application>
+ installation panels. A shadow of the <application>Privoxy</application>
executable will be placed in your startup folder so it will start
automatically whenever OS/2 starts.
</para>
<para>
- The directory you choose to install <application>Junkbuster</application>
+ The directory you choose to install <application>Privoxy</application>
into will contain all of the configuration files.
</para>
<!-- ~~~~~ New section ~~~~~ -->
-<sect1 id="configuration"><title>Invoking and Configuring JunkBuster</title>
+<sect1 id="configuration"><title><application>Privoxy</application> Configuration</title>
+ <para>
+ All <application>Privoxy</application> configuration is kept
+ in text files. These files can be edited with a text editor.
+ Many important aspects of <application>Privoxy</application> can
+ also be controlled easily with a web browser.
+
+ </para>
+
+
+<!-- ~~~~~ New section ~~~~~ -->
+
+<sect2>
+<title>Controlling <application>Privoxy</application> with Your Web Browser</title>
+<para>
+ <application>Privoxy</application> can be reached by the special
+ URL <ulink url="http://p.p/">http://p.p/</ulink> (or alternately
+ <ulink url="http://www.privoxy.org/config/">http://www.privoxy.org/config/</ulink>),
+ which is an internal page. You will see the following section:
+
+</para>
+
+<para>
+ <screen>
+
+Please choose from the following options:
+
+ * Show information about the current configuration
+ * Show the source code version numbers
+ * Show the client's request headers.
+ * Show which actions apply to a URL and why
+ * Toggle Privoxy on or off
+ * Edit the actions list
+
+ </screen>
+</para>
+
+<para>
+ This should be self-explanatory. Note the last item is an editor for the
+ <quote>actions list</quote>, which is where much of the ad, banner, cookie,
+ and URL blocking magic is configured as well as other advanced features of
+ <application>Privoxy</application>. This is an easy way to adjust various
+ aspects of <application>Privoxy</application> configuration. The actions
+ file, and other configuration files, are explained in detail below.
+ <application>Privoxy</application> will automatically detect any changes
+ to these files.
+</para>
+
+<para>
+ <quote>Toggle Privoxy On or Off</quote> is handy for sites that might
+ have problems with your current actions and filters, or just to test if
+ a site misbehaves, whether it is <application>Privoxy</application>
+ causing the problem or not. <application>Privoxy</application> continues
+ to run as a proxy in this case, but all filtering is disabled.
+
+</para>
+
+</sect2>
+
+<!-- ~ End section ~ -->
+
+
+
+
+<!-- ~~~~~ New section ~~~~~ -->
+
+<sect2>
+<title>Configuration Files Overview</title>
<para>
For Unix, *BSD and Linux, all configuration files are located in
- <filename>/etc/junkbuster/</filename> by default. For MS Windows, OS/2, and
+ <filename>/etc/privoxy/</filename> by default. For MS Windows, OS/2, and
AmigaOS these are all in the same directory as the
- <application>Junkbuster</application> executable. The name and number of
+ <application>Privoxy</application> executable. The name and number of
configuration files has changed from previous versions, and is subject to
change as development progresses.
</para>
<listitem>
<para>
- The <filename>ijb.action</filename> file is used to define various
+ The <filename>default.action</filename> file is used to define various
<quote>actions</quote> relating to images, banners, pop-ups, access
restrictions, banners and cookies. There is a CGI based editor for this
file that can be accessed via <ulink
- url="http://i.j.b">http://i.j.b</ulink>. This is the easiest method of
- configuring actions. (Other actions
+ url="http://p.p">http://p.p</ulink>. (Other actions
files are included as well with differing levels of filtering
and blocking, e.g. <filename>ijb-basic.action</filename>.)
</para>
<listitem>
<para>
- The <filename>re_filterfile</filename> file can be used to rewrite the raw
- page content, including text as well as embedded HTML and JavaScript.
+ The <filename>default.filter</filename> file can be used to re-write the raw
+ page content, including viewable text as well as embedded HTML and JavaScript,
+ and whatever else lurks on any given web page.
</para>
</listitem>
</para>
<para>
- <filename>ijb.action</filename> and <filename>re_filterfile</filename>
+ <filename>default.action</filename> and <filename>default.filter</filename>
can use Perl style regular expressions for maximum flexibility. All files use
the <quote><literal>#</literal></quote> character to denote a comment. Such
- lines are not processed by <application>Junkbuster</application>. After
+ lines are not processed by <application>Privoxy</application>. After
making any changes, there is no need to restart
- <application>Junkbuster</application> in order for the changes to take
- effect. <application>Junkbuster</application> should detect such changes
+ <application>Privoxy</application> in order for the changes to take
+ effect. <application>Privoxy</application> should detect such changes
automatically.
</para>
Also, what constitutes a <quote>default</quote> setting, may change, so
please check all your configuration files on important issues.
</para>
-
-
-
-<!-- ~~~~~ New section ~~~~~ -->
-
-<sect2>
-<title>Command Line Options</title>
-<para>
- <application>JunkBuster</application> may be invoked with the following
- command-line options:
-</para>
-
-<para>
- <itemizedlist>
-
- <listitem>
- <para>
- <emphasis>--version</emphasis>
- </para>
- <para>
- Print version info and exit, Unix only.
- </para>
- </listitem>
- <listitem>
- <para>
- <emphasis>--help</emphasis>
- </para>
- <para>
- Print a short usage info and exit, Unix only.
- </para>
- </listitem>
- <listitem>
- <para>
- <emphasis>--no-daemon</emphasis>
- </para>
- <para>
- Don't become a daemon, i.e. don't fork and become process group
- leader, don't detach from controlling tty. Unix only.
- </para>
- </listitem>
- <listitem>
- <para>
- <emphasis>--pidfile FILE</emphasis>
-
- </para>
- <para>
- On startup, write the process ID to <emphasis>FILE</emphasis>. Delete the
- <emphasis>FILE</emphasis> on exit. Failiure to create or delete the
- <emphasis>FILE</emphasis> is non-fatal. If no <emphasis>FILE</emphasis>
- option is given, no PID file will be used. Unix only.
- </para>
- </listitem>
- <listitem>
- <para>
- <emphasis>--user USER</emphasis>
-
- </para>
- <para>
- After (optionally) writing the PID file, assume the user ID of
- <emphasis>USER</emphasis>. Exit if the privileges are not sufficient to do
- so. Unix only.
- </para>
- </listitem>
- <listitem>
- <para>
- <emphasis>configfile</emphasis>
- </para>
- <para>
- If no <emphasis>configfile</emphasis> is included on the command line,
- <application>JunkBuster</application> will look for a file named
- <quote>config</quote> in the current directory (except on Win32
- where it will look for <quote>config.txt</quote> instead). Specify
- full path to avoid confusion.
- </para>
- </listitem>
-
-
- </itemizedlist>
-</para>
-
</sect2>
-<!-- ~ End section ~ -->
-
<!-- ~~~~~ New section ~~~~~ -->
</para>
<para>
- Indicates that the blockfile is named <quote>blocklist.ini</quote>.
+ Indicates that the blockfile is named <quote>blocklist.ini</quote>. (A
+ default installation does not use this.)
</para>
<para>
existing configuration line, you can make it a comment and it will be treated
as if it weren't there. This is called <quote>commenting out</quote> an
option and can be useful to turn off features: If you comment out the
- <quote>logfile</quote> line, <application>junkbuster</application> will not
+ <quote>logfile</quote> line, <application>Privoxy</application> will not
log to a file at all. Watch for the <quote>default:</quote> section in each
explanation to see what happens if the option is left unset (or commented
out).
</para>
<para>
- There are various aspects of <application>Junkbuster</application> behavior
+ There are various aspects of <application>Privoxy</application> behavior
that can be tuned.
</para>
<title>Defining Other Configuration Files</title>
<para>
- <application>Junkbuster</application> can use a number of other files to tell it
+ <application>Privoxy</application> can use a number of other files to tell it
what ads to block, what cookies to accept, etc. This section of the
- configuration file tells <application>Junkbuster</application> where to find
+ configuration file tells <application>Privoxy</application> where to find
all those other files.
</para>
<para>
On <application>Windows</application> and <application>AmigaOS</application>,
- <application>Junkbuster</application> looks for these files in the same
+ <application>Privoxy</application> looks for these files in the same
directory as the executable. On Unix and OS/2,
- <application>Junkbuster</application> looks for these files in the current
+ <application>Privoxy</application> looks for these files in the current
working directory. In either case, an absolute path name can be used to
avoid problems.
</para>
<literal>
<msgtext>
<literallayout>
- <emphasis>confdir /etc/junkbuster</emphasis> # No trailing /, please.
+ <emphasis>confdir /etc/privoxy</emphasis> # No trailing /, please.
</literallayout>
</msgtext>
</literal>
<literal>
<msgtext>
<literallayout>
- <emphasis>logdir /var/log/junkbuster</emphasis>
+ <emphasis>logdir /var/log/privoxy</emphasis>
</literallayout>
</msgtext>
</literal>
</para>
<para>
- The <quote>ijb.action</quote> file contains patterns to specify the actions to
- apply to requests for each site. Default: Cookies to and from all
- destinations are kept only during the current browser session (i.e. they
- are not saved to disk). Pop-ups are disabled for all sites. All sites are
- filtered if <quote>re_filterfile</quote> specified. No sites are blocked. An
- empty image is displayed for filtered ads and other images (formerly
- <quote>tinygif</quote>). The syntax of this file is explained in detail <link
- linkend="actionsfile">below</link>.
+ The <quote>default.action</quote> file contains patterns to specify the
+ actions to apply to requests for each site. Default: Cookies to and from all
+ destinations are kept only during the current browser session (i.e. they are
+ not saved to disk). Pop-ups are disabled for all sites. All sites are
+ filtered through selected sections of <quote>default.filter</quote>. No sites
+ are blocked. <application>Privoxy</application> displays a checkboard type
+ pattern for filtered ads and other images. The syntax of this file is
+ explained in detail <link linkend="actionsfile">below</link>. Other
+ <quote>actions</quote> files are included, and you are free to use any of
+ them. They have varying degrees of aggressiveness.
</para>
<para>
<literal>
<msgtext>
<literallayout>
- <emphasis>actionsfile ijb.action</emphasis>
+ <emphasis>actionsfile default.action</emphasis>
</literallayout>
</msgtext>
</literal>
</para>
<para>
- The <quote>re_filterfile</quote> file contains content modification rules.
- These rules permit powerful changes on the content of Web pages, e.g., you
- could disable your favorite JavaScript annoyances, rewrite the actual
- content, or just have some fun replacing <quote>Microsoft</quote> with
- <quote>MicroSuck</quote> wherever it appears on a Web page. Default: No
- content modification, or whatever the developers are playing with :-/
+ The <quote>default.filter</quote> file contains content modification rules
+ that use <quote>regular expressions</quote>. These rules permit powerful
+ changes on the content of Web pages, e.g., you could disable your favorite
+ JavaScript annoyances, re-write the actual displayed text, or just have some
+ fun replacing <quote>Microsoft</quote> with <quote>MicroSuck</quote> wherever
+ it appears on a Web page. Default: whatever the developers are playing with
+ :-/
+</para>
+
+<para>
+ Filtering requires buffering the page content, which may appear to slow down
+ page rendering since nothing is displayed until all content has passed
+ the filters. (It does not really take longer, but seems that way since
+ the page is not incrementally displayed.) This effect will be more noticeable
+ on slower connections.
+
</para>
<para>
<literal>
<msgtext>
<literallayout>
- <emphasis>re_filterfile re_filterfile</emphasis>
+ <emphasis>filterfile default.filter</emphasis>
</literallayout>
</msgtext>
</literal>
<para>
The logfile is where all logging and error messages are written. The logfile
can be useful for tracking down a problem with
- <application>Junkbuster</application> (e.g., it's not blocking an ad you
+ <application>Privoxy</application> (e.g., it's not blocking an ad you
think it should block) but in most cases you probably will never look at it.
</para>
</para>
<para>
- On SuSE Linux systems, you can place a line like <quote>/var/log/junkbuster.*
+ On SuSE Linux systems, you can place a line like <quote>/var/log/privoxy.*
+1024k 644 nobody.nogroup</quote> in <filename>/etc/logfiles</filename>, with
the effect that cron.daily will automatically archive, gzip, and empty the
log, when it exceeds 1M size.
<para>
The <quote>jarfile</quote> defines where
- <application>Junkbuster</application> stores the cookies it intercepts. Note
+ <application>Privoxy</application> stores the cookies it intercepts. Note
that if you use a <quote>jarfile</quote>, it may grow quite large. Default:
Don't store intercepted cookies.
</para>
<para>
If you specify a <quote>trustfile</quote>,
- <application>Junkbuster</application> will only allow access to sites that
+ <application>Privoxy</application> will only allow access to sites that
are named in the trustfile. You can also mark sites as trusted referrers,
with the effect that access to untrusted sites will be granted, if a link
from a trusted referrer was used. The link target will then be added to the
<para>
This part of the configuration file contains options that control how
- <application>Junkbuster</application> operates.
+ <application>Privoxy</application> operates.
</para>
<para>
<para>
<quote>Proxy-info-url</quote> can be set to a URL that contains more info
- about this <application>Junkbuster</application> installation, it's
+ about this <application>Privoxy</application> installation, it's
configuration and policies. It is used in many of the proxy-generated pages
and its use is highly recommended in multi-user installations, since your
users will want to know why certain content is blocked or modified. Default:
<para>
<quote>Listen-address</quote> specifies the address and port where
- <application>Junkbuster</application> will listen for connections from your
+ <application>Privoxy</application> will listen for connections from your
Web browser. The default is to listen on the localhost port 8118, and
this is suitable for most users. (In your web browser, under proxy
configuration, list the proxy server as <quote>localhost</quote> and the
serve requests from other machines (e.g. on your local network) as well, you
will need to override the default. The syntax is
<quote>listen-address [<ip-address>]:<port></quote>. If you leave
- out the IP address, <application>junkbuster</application> will bind to all
+ out the IP address, <application>Privoxy</application> will bind to all
interfaces (addresses) on your machine and may become reachable from the
Internet. In that case, consider using access control lists (acl's) (see
<quote>aclfile</quote> above), or a firewall.
</para>
<para>
- For example, suppose you are running <application>Junkbuster</application> on
+ For example, suppose you are running <application>Privoxy</application> on
a machine which has the address 192.168.0.1 on your local private network
(192.168.0.0) and has another outside connection with a different address.
You want it to serve requests from inside only:
<para>
It is <emphasis>highly recommended</emphasis> that you enable ERROR
- reporting (debug 8192), at least until the next stable release.
+ reporting (debug 8192), at least until v3.0 is released.
</para>
<para>
The reporting of FATAL errors (i.e. ones which crash
- <application>JunkBuster</application>) is always on and cannot be disabled.
+ <application>Privoxy</application>) is always on and cannot be disabled.
</para>
<para>
</para>
<para>
- <application>Junkbuster</application> normally uses
+ <application>Privoxy</application> normally uses
<quote>multi-threading</quote>, a software technique that permits it to
handle many different requests simultaneously. In some cases you may wish to
disable this -- particularly if you're trying to debug a problem. The
<quote>single-threaded</quote> option forces
- <application>Junkbuster</application> to handle requests sequentially.
+ <application>Privoxy</application> to handle requests sequentially.
Default: Multi-threaded mode.
</para>
<para>
<quote>toggle</quote> allows you to temporarily disable all
- <application>Junkbuster's</application> filtering. Just set <quote>toggle
+ <application>Privoxy's</application> filtering. Just set <quote>toggle
0</quote>.
</para>
<para>
- The Windows version of <application>Junkbuster</application> puts an icon in
+ The Windows version of <application>Privoxy</application> puts an icon in
the system tray, which also allows you to change this option. If you
right-click on that icon (or select the <quote>Options</quote> menu), one
choice is <quote>Enable</quote>. Clicking on enable toggles
- <application>Junkbuster</application> on and off. This is useful if you want
- to temporarily disable <application>Junkbuster</application>, e.g., to access
+ <application>Privoxy</application> on and off. This is useful if you want
+ to temporarily disable <application>Privoxy</application>, e.g., to access
a site that requires cookies which you would otherwise have blocked. This can also
- be toggled via a web browser at the <application>Junkbuster</application>
- internal address of <ulink url="http://i.j.b">http://i.j.b</ulink> on
+ be toggled via a web browser at the <application>Privoxy</application>
+ internal address of <ulink url="http://p.p">http://p.p</ulink> on
any platform.
</para>
<para>
- <quote>toggle 1</quote> means <application>Junkbuster</application> runs
+ <quote>toggle 1</quote> means <application>Privoxy</application> runs
normally, <quote>toggle 0</quote> means that
- <application>Junkbuster</application> becomes a non-anonymizing non-blocking
+ <application>Privoxy</application> becomes a non-anonymizing non-blocking
proxy. Default: 1 (on).
</para>
<para>
For content filtering, i.e. the <quote>+filter</quote> and
<quote>+deanimate-gif</quote> actions, it is necessary that
- <application>Junkbuster</application> buffers the entire document body.
+ <application>Privoxy</application> buffers the entire document body.
This can be potentially dangerous, since a server could just keep sending
data indefinitely and wait for your RAM to exhaust. With nasty consequences.
</para>
</para>
<para>
- To enable the web-based <filename>ijb.action</filename> file editor set
+ To enable the web-based <filename>default.action</filename> file editor set
<application>enable-edit-actions</application> to 1, or 0 to disable. Note
- that you must have compiled <application>JunkBuster</application> with
+ that you must have compiled <application>Privoxy</application> with
support for this feature, otherwise this option has no effect. This
internal page can be reached at <ulink
- url="http://i.j.b">http://i.j.b</ulink>.
+ url="http://p.p">http://p.p</ulink>.
</para>
<para>
</para>
<para>
- Allow <application>JunkBuster</application> to be toggled on and off
+ Allow <application>Privoxy</application> to be toggled on and off
remotely, using your web browser. Set <quote>enable-remote-toggle</quote>to
1 to enable, and 0 to disable. Note that you must have compiled
- <application>JunkBuster</application> with support for this feature,
+ <application>Privoxy</application> with support for this feature,
otherwise this option has no effect.
</para>
<para>
Security note: If this is enabled, anyone who can use the proxy can toggle
- it on or off (see <ulink url="http://i.j.b">http://i.j.b</ulink>), and
+ it on or off (see <ulink url="http://p.p">http://p.p</ulink>), and
their changes will affect all users. For shared proxies, you probably want to
disable this. Default: enabled.
</para>
</para>
<para>
- IMPORTANT NOTE: If the <application>junkbuster</application> is using a
+ IMPORTANT NOTE: If <application>Privoxy</application> is using a
forwarder (see below) or a gateway for a particular destination URL, the
<literal>DST_ADDR</literal> that is examined is the address of the forwarder
or the gateway and <emphasis>NOT</emphasis> the address of the ultimate
target. This is necessary because it may be impossible for the local
- <application>Junkbuster</application> to determine the address of the
+ <application>Privoxy</application> to determine the address of the
ultimate target (that's often what gateways are used for).
</para>
<para>
A silly example to illustrate permitting any host on the class-C subnet with
- <application>Junkbuster</application> to go anywhere:
+ <application>Privoxy</application> to go anywhere:
</para>
<para>
<literal>
<msgtext>
<literallayout>
- <emphasis>permit-access www.junkbusters.com/24</emphasis>
+ <emphasis>permit-access www.privoxy.com/24</emphasis>
</literallayout>
</msgtext>
</literal>
<literal>
<msgtext>
<literallayout>
- <emphasis>deny-access ident.junkbusters.com</emphasis>
+ <emphasis>deny-access ident.privoxy.com</emphasis>
</literallayout>
</msgtext>
</literal>
</para>
<para>
- An ISP may want to provide a <application>Junkbuster</application> that is
+ An ISP may want to provide a <application>Privoxy</application> that is
accessible by <quote>the world</quote> and yet restrict use of some of their
private content to hosts on its internal network (i.e. its own subscribers).
Say, for instance the ISP owns the Class-B IP address block 123.124.0.0 (a 16
</para>
<para>
- Also specified here are SOCKS proxies. <application>Junkbuster</application>
+ Also specified here are SOCKS proxies. <application>Privoxy</application>
SOCKS 4 and SOCKS 4A. The difference is that SOCKS 4A will resolve the target
hostname using DNS on the SOCKS server, not our local DNS client.
</para>
</para>
<para>
+<!--
See the FAQ for instructions on how to automate the login procedure for LPWA.
+-->
Some users have reported difficulties related to LPWA's use of
<quote>.</quote> as the last element of the domain, and have said that this
can be fixed with this:
<para>
Also, we're told they insist on getting cookies and JavaScript, so you should
- add home.com to the cookie file. We consider JavaScript a security risk.
+ allow cookies from home.com. We consider JavaScript a potential security risk.
Java need not be enabled.
</para>
<para>
host-a has a PPP connection to isp-a.com. And host-b has a PPP connection to
- isp-b.com. host-a can run a <application>Junkbuster</application> proxy with
+ isp-b.com. host-a can run a <application>Privoxy</application> proxy with
forwarding like this:
</para>
</para>
<para>
- host-b can run a <application>Junkbuster</application> proxy with forwarding
+ host-b can run a <application>Privoxy</application> proxy with forwarding
like this:
</para>
</para>
<para>
- If you intend to chain <application>Junkbuster</application> and
+ If you intend to chain <application>Privoxy</application> and
<application>squid</application> locally, then chain as
- <literal>browser -> squid -> junkbuster</literal> is the recommended way.
+ <literal>browser -> squid -> privoxy</literal> is the recommended way.
</para>
<para>
<literal>
<msgtext>
<literallayout>
- # Define junkbuster as parent cache
+ # Define Privoxy as parent cache
<!-- per feedback from user...
cache_peer 127.0.0.1 8118 parent 0 no-query
-->
# Define ACL for protocol FTP
acl FTP proto FTP
- # Do not forward ACL FTP to junkbuster
+ # Do not forward ACL FTP to privoxy
always_direct allow FTP
- # Do not forward ACL CONNECT (https) to junkbuster
+ # Do not forward ACL CONNECT (https) to privoxy
always_direct allow CONNECT
- # Forward the rest to junkbuster
+ # Forward the rest to privoxy
never_direct allow all
</literallayout>
</msgtext>
Removed references to Win32. HB 09/23/01
-->
<para>
- <application>Junkbuster</application> has a number of options specific to the
+ <application>Privoxy</application> has a number of options specific to the
Windows GUI interface:
</para>
<para>
If <quote>activity-animation</quote> is set to 1, the
- <application>Junkbuster</application> icon will animate when
- <quote>Junkbuster</quote> is active. To turn off, set to 0.
+ <application>Privoxy</application> icon will animate when
+ <quote>Privoxy</quote> is active. To turn off, set to 0.
</para>
<para>
<para>
If <quote>log-messages</quote> is set to 1,
- <application>Junkbuster</application> will log messages to the console
+ <application>Privoxy</application> will log messages to the console
window:
</para>
<para>
If <quote>log-highlight-messages</quote> is set to 1,
- <application>Junkbuster</application> will highlight portions of the log
+ <application>Privoxy</application> will highlight portions of the log
messages with a bold-faced font:
</para>
<para>
<quote>show-on-task-bar</quote> controls whether or not
- <application>Junkbuster</application> will appear as a button on the Task bar
+ <application>Privoxy</application> will appear as a button on the Task bar
when minimized:
</para>
<para>
If <quote>close-button-minimizes</quote> is set to 1, the Windows close
- button will minimize <application>Junkbuster</application> instead of closing
+ button will minimize <application>Privoxy</application> instead of closing
the program (close with the exit option on the File menu).
</para>
<para>
The <quote>hide-console</quote> option is specific to the MS-Win console
- version of <application>JunkBuster</application>. If this option is used,
- <application>Junkbuster</application> will disconnect from and hide the
+ version of <application>Privoxy</application>. If this option is used,
+ <application>Privoxy</application> will disconnect from and hide the
command console.
</para>
<title>The Actions File</title>
<para>
- The <quote>ijb.action</quote> file (formerly
- <filename>actionsfile</filename>) is used to define what actions
- <application>Junkbuster</application> takes, and thus determines how images,
+ The <quote>default.action</quote> file (formerly
+ <filename>actionsfile</filename> or <filename>ijb.action</filename>) is used to define what actions
+ <application>Privoxy</application> takes, and thus determines how images,
cookies and various other aspects of HTTP content and transactions are
handled. Images can be anything you want, including ads, banners, or just
- some obnoxious image that you would rather not see. Cookies can be accepted
+ some obnoxious URL that you would rather not see. Cookies can be accepted
or rejected, or accepted only during the current browser session (i.e.
- not written to disk). Changes to <filename>ijb.action</filename> should
- be immediately visible to <application>Junkbuster</application> without
+ not written to disk). Changes to <filename>default.action</filename> should
+ be immediately visible to <application>Privoxy</application> without
the need to restart.
</para>
+<para>
+ The easiest way to edit <quote>actions</quote> file is with a browser by
+ loading <ulink url="http://p.p/">http://p.p/</ulink>, and then select
+ <quote>Edit Actions List</quote>. A text editor can also be used.
+</para>
+
<para>
To determine which actions apply to a request, the URL of the request is
compared to all patterns in this file. Every time it matches, the list of
applicable actions for the URL is incrementally updated. You can trace
this process by visiting <ulink
- url="http://i.j.b/show-url-info">http://i.j.b/show-url-info</ulink>.
+ url="http://p.p/show-url-info">http://p.p/show-url-info</ulink>.
</para>
-<para>
- The actions file can be edited with a browser by loading
- <ulink url="http://i.j.b/">http://i.j.b/</ulink>, and then select
- <quote>Edit Actions</quote>.
-</para>
<para>
There are four types of lines in this file: comments (begin with a
<quote>#</quote> character), actions, aliases and patterns, all of which are
explained below, as well as the configuration file syntax that
- <application>Junkbuster</application> understands.
+ <application>Privoxy</application> understands.
</para>
</para>
<para>
- If <application>Junkbuster</application> was compiled with
+ If <application>Privoxy</application> was compiled with
<quote>pcre</quote> support (default), Perl compatible regular expressions
can be used. See the <filename>pcre/docs/</filename> directory or <quote>man
perlre</quote> (also available on <ulink
<para>
If nothing is specified in this file, no <quote>actions</quote> are taken.
- So in this case <application>JunkBuster</application> would just be a
+ So in this case <application>Privoxy</application> would just be a
normal, non-blocking, non-anonymizing proxy. You must specifically
enable the privacy and blocking features you need (although the
- provided default <filename>ijb.action</filename> file will
+ provided default <filename>default.action</filename> file will
give a good starting point).
</para>
</para>
<para>
- The list of valid <application>Junkbuster</application> <quote>actions</quote> are:
+ The list of valid <application>Privoxy</application> <quote>actions</quote> are:
</para>
<para>
<listitem>
<para>
- Block this URL totally.
+ Block this URL totally. In a default installation, a <quote>blocked</quote>
+ URL will result in bright red banner that says <quote>BLOCKED</quote>,
+ with a reason why it is being blocked.
</para>
<para>
<literal>
<quote>+downgrade</quote> will downgrade HTTP/1.1 client requests to
HTTP/1.0 and downgrade the responses as well. Use this action for servers
that use HTTP/1.1 protocol features that
- <application>Junkbuster</application> doesn't handle well yet. HTTP/1.1
+ <application>Privoxy</application> doesn't handle well yet. HTTP/1.1
is only partially implemented. Default is not to downgrade requests.
</para>
<para>
</para>
<para>
The <quote>+fast-redirects</quote> option enables interception of these
- requests by <application>Junkbuster</application>, who will cut off all but
+ requests by <application>Privoxy</application>, who will cut off all but
the last valid URL in the request and send a local redirect back to your
browser without contacting the remote site.
</para>
<listitem>
<para>
- Filter the website through the re_filterfile:
- </para>
+ Apply the filters in the <literal>section_header</literal>
+ section of the <filename>default.filter</filename> file to the site(s).
+ <filename>default.filter</filename> sections are grouped according to like
+ functionality.
+ </para>
+
<para>
<literal>
<msgtext>
<literallayout>
- <emphasis>+filter{filename}</emphasis>
+ <emphasis>+filter{section_header}</emphasis>
</literallayout>
</msgtext>
</literal>
</para>
+
+ <para>
+ Filter sections that are pre-defined in the supplied
+ <filename>default.filter</filename> include:
+ </para>
+
+ <blockquote>
+ <simplelist>
+ <member>
+ <emphasis>html-annoyances</emphasis>: Get rid of particularly annoying HTML abuse.
+ </member>
+ </simplelist>
+ <simplelist>
+ <member>
+ <emphasis>js-annoyances</emphasis>: Get rid of particularly annoying JavaScript abuse
+ </member>
+ </simplelist>
+ <simplelist>
+ <member>
+ <emphasis>no-poups</emphasis>: Kill all popups in JS and HTML
+ </member>
+ </simplelist>
+ <simplelist>
+ <member>
+ <emphasis>frameset-borders</emphasis>: Give frames a border
+ </member>
+ </simplelist>
+ <simplelist>
+ <member>
+ <emphasis>webbugs</emphasis>: Squish WebBugs (1x1 invisible GIFs used for user tracking)
+ </member>
+ </simplelist>
+ <simplelist>
+ <member>
+ <emphasis>no-refresh</emphasis>: Automatic refresh sucks on auto-dialup lines
+ </member>
+ </simplelist>
+ <simplelist>
+ <member>
+ <emphasis>fun</emphasis>: Text replacements for subversive browsing fun!
+ </member>
+ </simplelist>
+ <simplelist>
+ <member>
+ <emphasis>nimda</emphasis>: Remove (virus) Nimda code.
+ </member>
+ </simplelist>
+ <simplelist>
+ <member>
+ <emphasis>banners-by-size</emphasis>: Kill banners by size
+ </member>
+ </simplelist>
+ <simplelist>
+ <member>
+ <emphasis>crude-parental</emphasis>: Kill all web pages that contain the words "sex" or "warez"
+ </member>
+ </simplelist>
+ </blockquote>
+
</listitem>
<listitem>
</para>
<!--
<para>
- Or to identify yourself explicitly as a <quote>Junkbuster</quote> user:
+ Or to identify yourself explicitly as a <application>Privoxy</application> user:
</para>
<para>
<literal>
<msgtext>
<literallayout>
- <emphasis>+hide-user-agent{JunkBuster/1.0}</emphasis>
+ <emphasis>+hide-user-agent{Privoxy/1.0}</emphasis>
</literallayout>
</msgtext>
</literal>
<listitem>
<para>
Treat this URL as an image. This only matters if it's also <quote>+block</quote>ed,
- in which case a <quote>blocked</quote> image can be sent rather than a HTML page.
- See <quote>+image-blocker{}</quote> below for the control over what is actually sent.
+ in which case a <quote>blocked</quote> image can be sent rather than a HTML page.
+ See <quote>+image-blocker{}</quote> below for the control over what is actually sent.
+ If you want <emphasis>invisible</emphasis> ads, they should be defined as
+ <emphasis>images</emphasis> and <emphasis>blocked</emphasis>. And also,
+ <quote>image-blocker</quote> should be set to <quote>blank</quote>.
</para>
<para>
<literal>
</listitem>
<listitem>
- <para>
- Decides what to do with URLs that end up tagged with <quote>{+block
- +image}</quote>. There are 4 options. <quote>-image-blocker</quote> will
- send a HTML <quote>blocked</quote> page, usually resulting in a
- <quote>broken image</quote> icon. <quote>+image-blocker{logo}</quote> will
- send a <quote>JunkBuster</quote> image.
- <quote>+image-blocker{blank}</quote> will send a 1x1 transparent GIF image.
- And finally, <quote>+image-blocker{http://xyz.com}</quote> will send a HTTP
- temporary redirect to the specified image. This has the advantage of the
- icon being being cached by the browser, which will speed up the display.
+ <para> Decides what to do with URLs that end up tagged with <quote>{+block
+ +image}</quote>, e.g an advertizement. There are five options.
+ <quote>-image-blocker</quote> will send a HTML <quote>blocked</quote> page,
+ usually resulting in a <quote>broken image</quote> icon.
+<!-- <quote>+image-blocker{logo}</quote> will send a -->
+<!-- <application>Privoxy</application> logo -->
+<!-- image. -->
+<quote>+image-blocker{blank}</quote> will send a 1x1 transparent GIF
+image. And finally, <quote>+image-blocker{http://xyz.com}</quote> will send a
+HTTP temporary redirect to the specified image. This has the advantage of the
+icon being being cached by the browser, which will speed up the display.
+<quote>+image-blocker{pattern}</quote> will send a checkboard type pattern
+<!-- , -->
+<!-- which scales better than the logo (which can get blocky if the browser -->
+<!-- enlarges it too much). -->
</para>
<para>
<literal>
<msgtext>
<literallayout>
- <emphasis>+image-blocker{logo}</emphasis>
+<!-- <emphasis>+image-blocker{logo}</emphasis> -->
<emphasis>+image-blocker{blank}</emphasis>
- <emphasis>+image-blocker{http://i.j.b/send-banner}</emphasis>
+ <emphasis>+image-blocker{pattern}</emphasis>
+ <emphasis>+image-blocker{http://p.p/send-banner}</emphasis>
</literallayout>
</msgtext>
</literal>
<listitem>
<para>
By default (i.e. in the absence of a <quote>+limit-connect</quote>
- action), <application>Junkbuster</application> will only allow CONNECT
+ action), <application>Privoxy</application> will only allow CONNECT
requests to port 443, which is the standard port for https as a
precaution.
</para>
<para>
<quote>+no-compression</quote> prevents the website from compressing the
data. Some websites do this, which can be a problem for
- <application>Junkbuster</application>, since <quote>+filter</quote>,
+ <application>Privoxy</application>, since <quote>+filter</quote>,
<quote>+no-popup</quote> and <quote>+gif-deanimate</quote> will not work on
compressed data. This will slow down connections to those websites,
though. Default is <quote>nocompression</quote> is turned on.
</para>
<para>
- Turn on page filtering, with one exception for sourceforge:
-</para>
+ Turn on page filtering according to rules in the defined sections
+ of <filename>refilterfile</filename>, and make one exception for
+ sourceforge:
+ </para>
<para>
<literal>
<msgtext>
<literallayout>
- # Run everything through the default filter file (<filename>re_filterfile</filename>):
- {+filter}
-
- # But please don't re_filter code from sourceforge!
+ # Run everything through the filter file, using only the
+ # specified sections:
+ +filter{html-annoyances} +filter{js-annoyances} +filter{no-popups}\
+ +filter{webbugs} +filter{nimda} +filter{banners-by-size}
+
+ # Then disable filtering of code from sourceforge!
{-filter}
.cvs.sourceforge.net
</literallayout>
</literal>
</para>
+<para>
+ Note that many of these actions have the potential to cause a page to
+ misbehave, possibly even not to display at all. There are many ways
+ a site designer may choose to design his site, and what HTTP header
+ content he may depend on. There is no way to have hard and fast rules
+ for all sites. See the <link linkend="ACTIONSANAT">Appendix</link>
+ for a brief example on troubleshooting actions.
+
+</para>
+
</sect3>
<!-- ~ End section ~ -->
<sect3>
<title>Aliases</title>
<para>
- Custom <quote>actions</quote>, known to <application>Junkbuster</application>
+ Custom <quote>actions</quote>, known to <application>Privoxy</application>
as <quote>aliases</quote>, can be defined by combining other <quote>actions</quote>.
These can in turn be invoked just like the built-in <quote>actions</quote>.
Currently, an alias can contain any character except space, tab, <quote>=</quote>,
<quote>z</quote>, <quote>0</quote>-<quote>9</quote>, <quote>+</quote>, and
<quote>-</quote>. Alias names are not case sensitive, and
<emphasis>must be defined before anything</emphasis> else in the
- <filename>ijb.action</filename>file ! And there can only be one set of
+ <filename>default.action</filename>file ! And there can only be one set of
<quote>aliases</quote> defined.
</para>
<sect2 id="filterfile">
<title>The Filter File</title>
<para>
- The filter file defines what filtering of web pages
- <application>Junkbuster</application> does. The default filter file is
- <filename>re_filterfile</filename>, located in the config directory. In this
- file, <emphasis>any document content</emphasis>, whether viewable text or
- embedded non-visible content, can be changed.
+ Any web page can be dynamically modified with the filter file. This
+ modification can be removal, or re-writing, of any web page content,
+ including tags and non-visible content. The default filter file is
+ <filename>default.filter</filename>, located in the config directory.
+</para>
+
+<para>
+ The included example file is divided into sections. Each section begins
+ with the <literal>FILTER</literal> keyword, followed by the identifier
+ for that section, e.g. <quote>FILTER: webbugs</quote>. Each section performs
+ a similar type of filtering, such as <quote>html-annoyances</quote>.
+
</para>
<para>
This file uses regular expressions to alter or remove any string in the
- target page. Some examples from the included default <filename>re_filterfile</filename>:
+ target page. The expressions can only operate on one line at a time. Some
+ examples from the included default <filename>default.filter</filename>:
</para>
<para>
<literal>
<msgtext>
<literallayout>
- # The status bar is for displaying link targets, not pointless buzzwords.
- # Again, check it out on http://www.airport-cgn.de/.
- s/status='.*?';*//ig
+ FILTER: html-annoyances
+
+ # New browser windows should be resizeable and have a location and status
+ # bar. Make it so.
+ #
+ s/resizable="?(no|0)"?/resizable=1/ig s/noresize/yesresize/ig
+ s/location="?(no|0)"?/location=1/ig s/status="?(no|0)"?/status=1/ig
+ s/scrolling="?(no|0|Auto)"?/scrolling=1/ig
+ s/menubar="?(no|0)"?/menubar=1/ig
+
+ # The <BLINK> tag was a crime!
+ #
+ s*<blink>|</blink>**ig
+
+ # Is this evil?
+ #
+ #s/framespacing="?(no|0)"?//ig
+ #s/margin(height|width)=[0-9]*//gi
</literallayout>
</msgtext>
</literal>
<para>
Just for kicks, replace any occurrence of <quote>Microsoft</quote> with
- <quote>MicroSuck</quote>:
+ <quote>MicroSuck</quote>, and have a little fun with topical buzzwords:
</para>
<para>
<literal>
<msgtext>
<literallayout>
+ FILTER: fun
+
s/microsoft(?!.com)/MicroSuck/ig
+
+ # Buzzword Bingo:
+ #
+ s/industry-leading|cutting-edge|award-winning/<font color=red><b>BINGO!</b></font>/ig
</literallayout>
</msgtext>
</literal>
</para>
<para>
- Kill those auto-refresh tags:
+ Kill those pesky little web-bugs:
</para>
<para>
<literal>
<msgtext>
<literallayout>
- # Kill refresh tags. I like to refresh myself. Manually.
- # check it out on http://www.airport-cgn.de/ and go to the arrivals page.
- #
- s/<meta[^>]*http-equiv[^>]*refresh.*URL=([^>]*?)"?>/<link rev="x-refresh" href=$1>/i
- s/<meta[^>]*http-equiv="?page-enter"?[^>]*content=[^>]*>/<!--no page enter for me-->/i
+ # webbugs: Squish WebBugs (1x1 invisible GIFs used for user tracking)
+ FILTER: webbugs
+
+ s/<img\s+[^>]*?(width|height)\s*=\s*['"]?1\D[^>]*?(width|height)\s*=\s*['"]?1(\D[^>]*?)?>/<!-- Squished WebBug -->/sig
</literallayout>
</msgtext>
</literal>
<sect2>
<title>Templates</title>
<para>
- When <application>Junkbuster</application> displays one of its internal
+ When <application>Privoxy</application> displays one of its internal
pages, such as a 404 Not Found error page, it uses the appropriate template.
- On Linux, BSD, and Unix, these are locate in
- <filename>/etc/junkbuster/templates</filename> by default. These may be
+ On Linux, BSD, and Unix, these are located in
+ <filename>/etc/privoxy/templates</filename> by default. These may be
customized, if desired.
</para>
<!-- ~~~~~ New section ~~~~~ -->
-<sect1 id="quickstart"><title>Quickstart to Using Junkbuster</title>
+<sect1 id="quickstart"><title>Quickstart to Using <application>Privoxy</application></title>
<para>
- Install package, then run and enjoy! <application>JunkBuster</application>
- accepts only one command line option -- the configuration file to be
- used. Example Unix startup command:
+ Install package, then run and enjoy! <application>Privoxy</application>
+ is typically started by specifying the main configuration file to be
+ used on the command line. Example Unix startup command:
</para>
<para>
<screen>
- # /usr/sbin/junkbuster /etc/junkbuster/config
+ # /usr/sbin/privoxy /etc/privoxy/config
</screen>
</para>
</para>
<para>
-For for SuSE: /etc/rc.d/junkbuster start
+For for SuSE: /etc/rc.d/privoxy start
</para>
<para>
-For RedHat: /etc/rc.d/init.d/junkbuster start
+For RedHat: /etc/rc.d/init.d/privoxy start
</para>
<para>
If no configuration file is specified on the command line,
- <application>Junkbuster</application> will look for a file named
+ <application>Privoxy</application> will look for a file named
<filename>config</filename> in the current directory. Except on Win32 where
it will try <filename>config.txt</filename>. If no file is specified on the
command line and no default configuration file can be found,
- <application>Junkbuster</application> will fail to start.
+ <application>Privoxy</application> will fail to start.
</para>
<para>
The included default configuration files should give a reasonable starting
point, though may be somewhat aggressive in blocking junk. You will probably
want to keep an eye out for sites that require persistent cookies, and add these to
- <filename>ijb.action</filename> as needed. By default, most of these will
+ <filename>default.action</filename> as needed. By default, most of these will
be accepted only during the current browser session, until you add them to
the configuration. If you want the browser to handle this instead, you will
- need to edit <filename>ijb.action</filename> and disable this feature. If you
+ need to edit <filename>default.action</filename> and disable this feature. If you
use more than one browser, it would make more sense to let
- <application>Junkbuster</application> handle this. In which case, the
+ <application>Privoxy</application> handle this. In which case, the
browser(s) should be set to accept all cookies.
</para>
<para>
If a particular site shows problems loading properly, try adding it
to the <literal>{fragile}</literal> section of
- <filename>ijb.action</filename>. This will turn off most actions for
+ <filename>default.action</filename>. This will turn off most actions for
this site.
</para>
<para>
- <application>Junkbuster</application> is HTTP/1.1 compliant, but not all 1.1
+ <application>Privoxy</application> is HTTP/1.1 compliant, but not all 1.1
features are as yet implemented. If browsers that support HTTP/1.1 (like
<application>Mozilla</application> or recent versions of I.E.) experience
problems, you might try to force HTTP/1.0 compatibility. For Mozilla, look
under <literal>Edit -> Preferences -> Debug -> Networking</literal>.
Or set the <quote>+downgrade</quote> config option in
- <filename>ijb.action</filename>.
+ <filename>default.action</filename>.
</para>
<para>
- After running <application>Junkbuster</application> for a while, you can
+ After running <application>Privoxy</application> for a while, you can
start to fine tune the configuration to suit your personal, or site,
preferences and requirements. There are many, many aspects that can
- be customized. <quote>Actions</quote> (as specified in <filename>ijb.action</filename>)
+ be customized. <quote>Actions</quote> (as specified in <filename>default.action</filename>)
can be adjusted by pointing your browser to
- <ulink url="http://i.j.b/">http://i.j.b/</ulink>,
+ <ulink url="http://p.p/">http://p.p/</ulink>,
and then follow the link to <quote>edit the actions list</quote>.
(This is an internal page and does not require Internet access.)
</para>
<para>
- In fact, various aspects of <application>Junkbuster</application>
+ In fact, various aspects of <application>Privoxy</application>
configuration can be viewed from this page, including
current configuration parameters, source code version numbers,
the browser's request headers, and <quote>actions</quote> that apply
- to a given URL. In addition to the <filename>ijb.action</filename> file
- editor mentioned above, <application>Junkbuster</application> can also
+ to a given URL. In addition to the <filename>default.action</filename> file
+ editor mentioned above, <application>Privoxy</application> can also
be turned <quote>on</quote> and <quote>off</quote> from this page.
</para>
<para>
If you encounter problems, please verify it is a
- <application>Junkbuster</application> bug, by disabling
- <application>Junkbuster</application>, and then trying the same page.
+ <application>Privoxy</application> bug, by disabling
+ <application>Privoxy</application>, and then trying the same page.
Also, try another browser if possible to eliminate browser or site
problems. Before reporting it as a bug, see if there is not a configuration
option that is enabled that is causing the page not to load. You can
the developers (see below).
</para>
+
+
+<!-- ~~~~~ New section ~~~~~ -->
+
+<sect2>
+<title>Command Line Options</title>
+<para>
+ <application>Privoxy</application> may be invoked with the following
+ command-line options:
+</para>
+
+<para>
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ <emphasis>--version</emphasis>
+ </para>
+ <para>
+ Print version info and exit, Unix only.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis>--help</emphasis>
+ </para>
+ <para>
+ Print a short usage info and exit, Unix only.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis>--no-daemon</emphasis>
+ </para>
+ <para>
+ Don't become a daemon, i.e. don't fork and become process group
+ leader, don't detach from controlling tty. Unix only.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis>--pidfile FILE</emphasis>
+
+ </para>
+ <para>
+ On startup, write the process ID to <emphasis>FILE</emphasis>. Delete the
+ <emphasis>FILE</emphasis> on exit. Failiure to create or delete the
+ <emphasis>FILE</emphasis> is non-fatal. If no <emphasis>FILE</emphasis>
+ option is given, no PID file will be used. Unix only.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis>--user USER[.GROUP]</emphasis>
+
+ </para>
+ <para>
+ After (optionally) writing the PID file, assume the user ID of
+ <emphasis>USER</emphasis>, and if included the GID of GROUP. Exit if the
+ privileges are not sufficient to do so. Unix only.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis>configfile</emphasis>
+ </para>
+ <para>
+ If no <emphasis>configfile</emphasis> is included on the command line,
+ <application>Privoxy</application> will look for a file named
+ <quote>config</quote> in the current directory (except on Win32
+ where it will look for <quote>config.txt</quote> instead). Specify
+ full path to avoid confusion.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+</para>
+
+</sect2>
+
</sect1>
+<!-- ~ End section ~ -->
+
+
<!-- ~~~~~ New section ~~~~~ -->
+
<sect1 id="contact"><title>Contacting the Developers, Bug Reporting and Feature
Requests</title>
<para>
- Please do not use the mailing lists for feature requests or
- bug reports. They are not as easily tracked this way!
+We value your feedback. However, to provide you with the best support,
+please note:
+
+ <itemizedlist>
+
+ <listitem><para>Use the <ulink url="http://sourceforge.net/tracker/?group_id=11118&atid=211118">Sourceforge support forum</ulink> to get
+ help.</para></listitem>
+
+ <listitem><para>Submit bugs only thru our <ulink url="http://sourceforge.net/tracker/?group_id=11118&atid=111118">Sourceforge bug
+ forum</ulink>.
+Make sure that the bug has not already been submitted. Please try to
+verify that it is a <application>Privoxy</application> bug, and not
+a browser or site bug first. If you are using your own custom configuration,
+please try the stock configs to see if the problem is a configuration
+related bug. And if not using the latest development snapshot, please
+try the latest one. Or even better, CVS sources.</para>
+</listitem>
+
+
+ <listitem><para>Submit feature requests only thru our <ulink
+ url="http://sourceforge.net/tracker/?atid=361118&group_id=11118&func=browse">Sourceforge feature request forum</ulink>.</para></listitem>
+
+
+ </itemizedlist>
</para>
<para>
-<!--
-To be filled. mention the support forums as the primary channel of
-communication (bugs, feature requests, etc.)
--->
- Feature requests and other questions should be posted to the <ulink
- url="http://sourceforge.net/tracker/?atid=361118&group_id=11118&func=browse">Feature
- request page</ulink> at SourceForge. There is also an archive there.
+For any other issues, feel free to use the <ulink url="http://sourceforge.net/mail/?group_id=11118">mailing lists</ulink>.
</para>
<para>
Archives are available here too.
</para>
-<para>
- Please report bugs, using the form at
- <ulink url="http://sourceforge.net/tracker/?group_id=11118&atid=111118">Sourceforge</ulink>.
- Please try to verify that it is a <application>Junkbuster</application> bug,
- and not a browser or site bug first. Also, check to make sure this is not
- already a known bug. If you are using your own custom configuration, please
- try the stock configs to see if the problem is a configuration related bug.
-</para>
-
</sect1>
<sect2>
<title>License</title>
<para>
- <application>Internet Junkbuster</application> is free software; you can
+ <application>Privoxy</application> is free software; you can
redistribute it and/or modify it under the terms of the GNU General Public
License as published by the Free Software Foundation; either version 2 of the
License, or (at your option) any later version.
<sect2>
<title>History</title>
<para>
- <application>Junkbuster</application> was originally written by Anonymous
+ <application>Privoxy</application> is derived from
+ <application>the Internet Junkbuster</application>, with many
+ improvments and enhancements over the original.
+</para>
+
+<para>
+ <application>Junkbuster</application> was originally written by Anonymous
Coders and <ulink
url="http://www.junkbusters.com/ht/en/ijbfaq.html">Junkbuster's
Corporation</ulink>, and was released as free open-source software under the
GNU GPL. <ulink url="http://www.waldherr.org/junkbuster/">Stefan
Waldherr</ulink> made many improvements, and started the <ulink
- url="http://sourceforge.net/projects/ijbswa/">SourceForge project</ulink> to
- rekindle development. There are now several active developers contributing.
- The last stable release was v2.0.2, which has now grown whiskers ;-).
+ url="http://sourceforge.net/projects/ijbswa/">SourceForge project
+ Privoxy</ulink> to rekindle development. There are now several active
+ developers contributing. The last stable release of
+ <application>Junkbuster</application> was v2.0.2, which has now
+ grown whiskers ;-).
</para>
</sect2>
</simplelist>
<simplelist>
<member>
- <ulink url="http://ijbswa.sourceforge.net/">http://ijbswa.sourceforge.net/</ulink>
+ <ulink url="http://www.privoxy.org/">http://www.privoxy.org/</ulink>
</member>
</simplelist>
<simplelist>
<member>
- <ulink url="http://i.j.b/">http://i.j.b/</ulink>
+ <ulink url="http://p.p/">http://p.p/</ulink>
</member>
</simplelist>
<simplelist>
<sect2 id="regex">
<title>Regular Expressions</title>
<para>
- <application>Junkbuster</application> can use <quote>regular expressions</quote>
+ <application>Privoxy</application> can use <quote>regular expressions</quote>
in various config files. Assuming support for <quote>pcre</quote> (Perl
Compatible Regular Expressions) is compiled in, which is the default. Such
configuration directives do not require regular expressions, but they can be
<para>
These are just some of the ones you are likely to use when matching URLs with
- <application>Junkbuster</application>, and is a long way from a definitive
+ <application>Privoxy</application>, and is a long way from a definitive
list. This is enough to get us started with a few simple examples which may
be more illuminating:
</para>
<para>
We are barely scratching the surface of regular expressions here so that you
- can understand the default <application>Junkbuster</application>
+ can understand the default <application>Privoxy</application>
configuration files, and maybe use this knowledge to customize your own
installation. There is much, much more that can be done with regular
expressions. Now that you know enough to get started, you can learn more on
</sect2>
+<!-- ~ End section ~ -->
+
+
+<!-- ~~~~~ New section ~~~~~ -->
+<sect2>
+<title><application>Privoxy</application>'s Internal Pages</title>
+
+<para>
+ Since <application>Privoxy</application> proxies each requested
+ web page, it is easy for <application>Privoxy</application> to
+ trap certain URLs. In this way, we can talk directly to
+ <application>Privoxy</application>, and see how it is
+ configured, see how our rules are being applied, change these
+ rules and other configuration options, and even turn
+ <application>Privoxy's</application> filtering off, all with
+ a web browser.
+
+</para>
+
+<para>
+ The URLs listed below are the special ones that allow direct access
+ to <application>Privoxy</application>. Of course,
+ <application>Privoxy</application> must be running to access these. If
+ not, you will get a friendly error message. Internet access is not
+ necessary either.
+</para>
+
+<para>
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ Privoxy main page:
+ </para>
+ <blockquote>
+ <para>
+ <ulink url="http://www.privoxy.org/config/">http://www.privoxy.org/config/</ulink>
+ </para>
+ </blockquote>
+ <para>
+ Alternately, this may be reached at <ulink
+ url="http://p.p/">http://p.p/</ulink>, but this
+ variation may not work as reliably as the above in some configurations.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Show information about the current configuration:
+ </para>
+ <blockquote>
+ <para>
+ <ulink url="http://www.privoxy.org/config/show-status">http://www.privoxy.org/config/show-status</ulink>
+ </para>
+ </blockquote>
+ </listitem>
+
+ <listitem>
+ <para>
+ Show the source code version numbers:
+ </para>
+ <blockquote>
+ <para>
+ <ulink url="http://www.privoxy.org/config/show-version">http://www.privoxy.org/config/show-version</ulink>
+ </para>
+ </blockquote>
+ </listitem>
+
+ <listitem>
+ <para>
+ Show the client's request headers:
+ </para>
+ <blockquote>
+ <para>
+ <ulink url="http://www.privoxy.org/config/show-request">http://www.privoxy.org/config/show-request</ulink>
+ </para>
+ </blockquote>
+ </listitem>
+
+ <listitem>
+ <para>
+ Show which actions apply to a URL and why:
+ </para>
+ <blockquote>
+ <para>
+ <ulink url="http://www.privoxy.org/config/show-url-info">http://www.privoxy.org/config/show-url-info</ulink>
+ </para>
+ </blockquote>
+ </listitem>
+
+ <listitem>
+ <para>
+ Toggle Privoxy on or off:
+ </para>
+ <blockquote>
+ <para>
+ <ulink url="http://www.privoxy.org/config/toggle">http://www.privoxy.org/config/toggle</ulink>
+ </para>
+ </blockquote>
+ <para>
+ Short cuts. Turn off, then on:
+ </para>
+ <blockquote>
+ <para>
+ <ulink url="http://www.privoxy.org/config/toggle?set=disable">http://www.privoxy.org/config/toggle?set=disable</ulink>
+ </para>
+ </blockquote>
+ <blockquote>
+ <para>
+ <ulink url="http://www.privoxy.org/config/toggle?set=enable">http://www.privoxy.org/config/toggle?set=enable</ulink>
+ </para>
+ </blockquote>
+ </listitem>
+
+ <listitem>
+ <para>
+ Edit the actions list file:
+ </para>
+ <blockquote>
+ <para>
+ <ulink url="http://www.privoxy.org/config/edit-actions">http://www.privoxy.org/config/edit-actions</ulink>
+ </para>
+ </blockquote>
+ </listitem>
+
+ </itemizedlist>
+</para>
+
+<para>
+ These may be bookmarked for quick reference.
+
+</para>
+
+</sect2>
+
+
+<!-- ~~~~~ New section ~~~~~ -->
+<sect2 id="actionsanat">
+<title>Anatomy of an Action</title>
+
+<para>
+ The way <application>Privoxy</application> applies <quote>actions</quote>
+ to any given URL can be complex, and not always so easy to understand what
+ is happening. And sometimes we need to be able to <emphasis>see</emphasis>
+ just what <application>Privoxy</application> is doing. Especially,
+ if something <application>Privoxy</application> is doing is causing
+ us a problem inadvertantly. It can be a little daunting to look at
+ the actions files themselves, since they tend to be filled with
+ <quote>regular expressions</quote> whose consequences are not always
+ so obvious. <application>Privoxy</application> provides the
+ <ulink url="http://www.privoxy.org/config/show-url-info">http://www.privoxy.org/config/show-url-info</ulink>
+ page that can show us very specifically how <application>actions</application>
+ are being applied to any given URL. This is a big help for troubleshooting.
+ </para>
+
+<para>
+ First, enter one URL (or partial URL) at the prompt, and then
+ <application>Privoxy</application> will tell us
+ how the current configuration will handle it. This will not
+ help with filtering effects from the <filename>default.filter</filename> file! It
+ also will not tell you about any other URLs that may be embedded within the
+ URL you are testing. For instance, images such as ads are expressed as URLs
+ within the raw page source of HTML pages. So you will only get info for the
+ actual URL that is pasted into the prompt area -- not any sub-URLs. If you
+ want to know about embedded URLs like ads, you will have to dig those out of
+ the HTML source. Use your browser's <quote>View Page Source</quote> option
+ for this.
+</para>
+
+<para>
+ Let's look at an example, <ulink url="http://google.com">google.com</ulink>,
+ one section at a time:
+</para>
+
+<para>
+ <screen>
+ System default actions:
+
+ { -add-header -block -deanimate-gifs -downgrade -fast-redirects -filter
+ -hide-forwarded -hide-from -hide-referer -hide-user-agent -image
+ -image-blocker -limit-connect -no-compression -no-cookies-keep
+ -no-cookies-read -no-cookies-set -no-popups -vanilla-wafer -wafer }
+
+ </screen>
+</para>
+
+<para>
+ This is the top section, and only tells us of the compiled in defaults. This
+ is basically what <application>Privoxy</application> would do if there
+ were not any <quote>actions</quote> defined, i.e. it does nothing. Every action
+ is disabled. This is not particularly informative for our purposes here. OK,
+ next section:
+</para>
+
+<para>
+ <screen>
+
+ Matches for http://google.com:
+
+ { -add-header -block +deanimate-gifs -downgrade +fast-redirects
+ +filter{html-annoyances} +filter{js-annoyances} +filter{no-popups}
+ +filter{webbugs} +filter{nimda} +filter{banners-by-size} +filter{hal}
+ +filter{fun} +hide-forwarded +hide-from{block} +hide-referer{forge}
+ -hide-user-agent -image +image-blocker{blank} +no-compression
+ +no-cookies-keep -no-cookies-read -no-cookies-set +no-popups
+ -vanilla-wafer -wafer }
+ /
+
+ { -no-cookies-keep -no-cookies-read -no-cookies-set }
+ .google.com
+
+ { -fast-redirects }
+ .google.com
+
+ </screen>
+</para>
+
+<para>
+ This is much more informative, and tells us how we have defined our
+ <quote>actions</quote>, and which ones match for our example,
+ <quote>google.com</quote>. The first grouping shows our default
+ settings, which would apply to all URLs. If you look at your <quote>actions</quote>
+ file, this would be the section just below the <quote>aliases</quote> section
+ near the top. This applies to all URLs as signified by the single forward
+ slash -- <quote>/</quote>.
+
+</para>
+
+<para>
+ These are the default actions we have enabled. But we can define additional
+ actions that would be exceptions to these general rules, and then list
+ specific URLs that these exceptions would apply to. Last match wins.
+ Just below this then are two explict matches for <quote>.google.com</quote>.
+ The first is negating our various cookie blocking actions (i.e. we will allow
+ cookies here). The second is allowing <quote>fast-redirects</quote>. Note
+ that there is a leading dot here -- <quote>.google.com</quote>. This will
+ match any hosts and sub-domains, in the google.com domain also, such as
+ <quote>www.google.com</quote>. So, apparently, we have these actions defined
+ somewhere in the lower part of our actions file, and
+ <quote>google.com</quote> is referenced in these sections.
+
+</para>
+
+<para>
+ And now we pull it altogether in the bottom section and summarize how
+ <application>Privoxy</application> is appying all its <quote>actions</quote>
+ to <quote>google.com</quote>:
+
+</para>
+
+<para>
+ <screen>
+
+ Final results:
+
+ -add-header -block -deanimate-gifs -downgrade -fast-redirects
+ +filter{html-annoyances} +filter{js-annoyances} +filter{no-popups}
+ +filter{webbugs} +filter{nimda} +filter{banners-by-size} +filter{hal}
+ +filter{fun} +hide-forwarded +hide-from{block} +hide-referer{forge}
+ -hide-user-agent -image +image-blocker{blank} -limit-connect +no-compression
+ -no-cookies-keep -no-cookies-read -no-cookies-set +no-popups -vanilla-wafer
+ -wafer
+
+ </screen>
+</para>
+
+<para>
+ Now another example, <quote>ad.doubleclick.net</quote>:
+</para>
+
+<para>
+ <screen>
+
+ { +block +image }
+ .ad.doubleclick.net
+
+ { +block +image }
+ ad*.
+
+ { +block +image }
+ .doubleclick.net
+
+ </screen>
+</para>
+
+<para>
+ We'll just show the interesting part here, the explicit matches. It is
+ matched three different times. Each as an <quote>+block +image</quote>,
+ which is the expanded form of one of our aliases that had been defined as:
+ <quote>+imageblock</quote>. (<quote>Aliases</quote> are defined in the
+ first section of the actions file and typically used to combine more
+ than one action.)
+</para>
+
+<para>
+ Any one of these would have done the trick and blocked this as an unwanted
+ image. This is unnecessarily redundant since the last case effectively
+ would also cover the first. No point in taking chances with these guys
+ though ;-) Note that if you want an ad or obnoxious
+ URL to be invisible, it should be defined as <quote>ad.doubleclick.net</quote>
+ is done here -- as both a <quote>+block</quote> <emphasis>and</emphasis> an
+ <quote>+image</quote>. The custom alias <quote>+imageblock</quote> does this
+ for us.
+</para>
+
+<para>
+ One last example. Let's try <quote>http://www.rhapsodyk.net/adsl/HOWTO/</quote>.
+ This one is giving us problems. We are getting a blank page. Hmmm...
+</para>
+
+<para>
+ <screen>
+
+ Matches for http://www.rhapsodyk.net/adsl/HOWTO/:
+
+ { -add-header -block +deanimate-gifs -downgrade +fast-redirects
+ +filter{html-annoyances} +filter{js-annoyances} +filter{no-popups}
+ +filter{webbugs} +filter{nimda} +filter{banners-by-size} +filter{hal}
+ +filter{fun} +hide-forwarded +hide-from{block} +hide-referer{forge}
+ -hide-user-agent -image +image-blocker{blank} +no-compression
+ +no-cookies-keep -no-cookies-read -no-cookies-set +no-popups
+ -vanilla-wafer -wafer }
+ /
+
+ { +block +image }
+ /ads
+
+ </screen>
+</para>
+
+<para>
+ Ooops, the <quote>/adsl/</quote> is matching <quote>/ads</quote>! But
+ we did not want this at all! Now we see why we get the blank page. We could
+ now add a new action below this that explictly does <emphasis>not</emphasis>
+ block (-block) pages with <quote>adsl</quote>. There are various ways to
+ handle such exceptions. Example:
+</para>
+
+<para>
+ <screen>
+
+ { -block }
+ /adsl
+
+ </screen>
+</para>
+
+<para>
+ Now the page displays ;-)
+
+</para>
+
+</sect2>
+
</sect1>
<!--
Temple Place - Suite 330, Boston, MA 02111-1307, USA.
$Log: user-manual.sgml,v $
+ Revision 1.57 2002/03/24 20:33:30 hal9
+ A few minor catch ups with name change.
+
+ Revision 1.56 2002/03/24 16:17:06 swa
+ configure needs to be generated.
+
+ Revision 1.55 2002/03/24 16:08:08 swa
+ we are too lazy to make a block-built
+ privoxy logo. hence removed the option.
+
+ Revision 1.54 2002/03/24 15:46:20 swa
+ name change related issue.
+
+ Revision 1.53 2002/03/24 11:51:00 swa
+ name change. changed filenames.
+
+ Revision 1.52 2002/03/24 11:01:06 swa
+ name change
+
+ Revision 1.51 2002/03/23 15:13:11 swa
+ renamed every reference to the old name with foobar.
+ fixed "application foobar application" tag, fixed
+ "the foobar" with "foobar". left junkbustser in cvs
+ comments and remarks to history untouched.
+
+ Revision 1.50 2002/03/23 05:06:21 hal9
+ Touch up.
+
+ Revision 1.49 2002/03/21 17:01:05 hal9
+ New section in Appendix.
+
+ Revision 1.48 2002/03/12 06:33:01 hal9
+ Catching up to Andreas and re_filterfile changes.
+
+ Revision 1.47 2002/03/11 13:13:27 swa
+ correct feedback channels
+
+ Revision 1.46 2002/03/10 00:51:08 hal9
+ Added section on JB internal pages in Appendix.
+
+ Revision 1.45 2002/03/09 17:43:53 swa
+ more distros
+
+ Revision 1.44 2002/03/09 17:08:48 hal9
+ New section on Jon's actions file editor, and move some stuff around.
+
+ Revision 1.43 2002/03/08 00:47:32 hal9
+ Added imageblock{pattern}.
+
+ Revision 1.42 2002/03/07 18:16:55 swa
+ looks better
+
+ Revision 1.41 2002/03/07 16:46:43 hal9
+ Fix a few markup problems for jade.
+
+ Revision 1.40 2002/03/07 16:28:39 swa
+ provide correct feedback channels
+
+ Revision 1.39 2002/03/06 16:19:28 hal9
+ Note on perceived filtering slowdown per FR.
+
+ Revision 1.38 2002/03/05 23:55:14 hal9
+ Stupid I did it again. Double hyphen in comment breaks jade.
+
+ Revision 1.37 2002/03/05 23:53:49 hal9
+ jade barfs on '- -' embedded in comments. - -user option broke it.
+
Revision 1.36 2002/03/05 22:53:28 hal9
Add new - - user option.
projects / privoxy.git / blobdiff