join the team.
Please note that this document is constantly evolving. This copy represents the
-state at the release of version 3.0.1. You can find the latest version of the
+state at the release of version 3.0.2. You can find the latest version of the
this manual at http://www.privoxy.org/developer-manual/. Please see the Contact
section on how to contact the developers.
* Commonly used "internal entities":
- p-version: the Privoxy version string, e.g. "3.0.1".
+ p-version: the Privoxy version string, e.g. "3.0.2".
p-status: the project status, either "alpha", "beta", or "stable".
p-not-stable: use to conditionally include text in "not stable" releases
(e.g. "beta").
directory. (See "Building and releasing packages" above). Then add a log entry
to debian/changelog, if it is not already there, for example by running:
- debchange -v 3.0.1-stable-1 "New upstream version"
+ debchange -v 3.0.2-stable-1 "New upstream version"
Then, run:
dpkg-buildpackage -rfakeroot -us -uc -b
-This will create ../privoxy_3.0.1-stable-1_i386.deb which can be uploaded. To
+This will create ../privoxy_3.0.2-stable-1_i386.deb which can be uploaded. To
upload the package to Sourceforge, simply issue
make debian-upload
group_id=11118, making sure you are logged in. Find your target platform in the
second column, and click Add Release. You will then need to create a new
release for your package, using the format of $VERSION ($CODE_STATUS), e.g.
-3.0.1 (beta).
+3.0.2 (beta).
Now just follow the prompts. Be sure to add any appropriate Release notes. You
should see your freshly uploaded packages in "Step 2. Add Files To This
9. Privoxy Copyright, License and History
-Copyright © 2001, 2002 by Privoxy Developers <developers@privoxy.org>
+Copyright © 2001 - 2003 by Privoxy Developers <developers@privoxy.org>
Some source code is based on code Copyright © 1997 by Anonymous Coders and
Junkbusters, Inc. and licensed under the GNU General Public License.
inside out, upside down, and then reassembled it, adding many new features
along the way.
-The result of this is Privoxy, whose first stable release, 3.0, was released
+The result of this is Privoxy, whose first stable version, 3.0, was released
August, 2002.
-------------------------------------------------------------------------------
Copyright © 2001, 2002 by Privoxy Developers
-$Id: faq.sgml,v 1.61.2.27 2002/12/01 06:31:58 hal9 Exp $
+$Id: faq.sgml,v 1.61.2.28 2003/03/18 19:37:21 oes Exp $
This FAQ gives quick answers to frequently asked questions about Privoxy. It
can't and doesn't replace the User Manual.
Privoxy is based on Internet Junkbuster (tm).
Please note that this document is constantly evolving. This copy represents the
-state at the release of version 0.0.0. You can find the latest version of the
+state at the release of version 3.0.2. You can find the latest version of the
document at http://www.privoxy.org/faq/. Please see the Contact section if you
want to contact the developers.
3.5. How are actions files configured? What is the easiest way to do this?
3.6. There are several different "actions" files. What are the differences?
3.7. How can I make my Yahoo/Hotmail/GMX account work?
- 3.8. What's the difference between the "Cautious", "Medium" and "Radical"
- defaults?
+ 3.8. What's the difference between the "Cautious", "Medium" and
+ "Adventuresome" defaults?
3.9. Why can I change the configuration with a browser? Does that not raise
security issues?
3.10. What is the default.filter file? What is a "filter"?
inside out, upside down, and then reassembled it, adding many new features
along the way.
-The result of this is Privoxy, whose first stable release, 3.0, was released
+The result of this is Privoxy, whose first stable version, 3.0, was released
August, 2002.
-------------------------------------------------------------------------------
The developers also believed that there are so many changes from the original
code, that it was time to make a clean break from the past and make a name in
-their own right, especially now with the pending release of version 3.0.
+their own right.
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
-3.8. What's the difference between the "Cautious", "Medium" and "Radical"
+3.8. What's the difference between the "Cautious", "Medium" and "Adventuresome"
defaults?
Configuring Privoxy is not entirely trivial. To help you get started, we
settings are, the more exceptions you will have to make later. See the User
Manual for a more deatiled discussion.
-It should be noted that the "Radical" profile (formerly known as the "Advanced"
-profile) is not only more aggressive, but also includes fun and, extreme usage
-of most of Privoxy's features. Use at your own risk!
+It should be noted that the "Adventuresome" profile (formerly known as the
+"Advanced" profile) is not only more aggressive, but also includes fun and,
+extreme usage of most of Privoxy's features. Use at your own risk!
-------------------------------------------------------------------------------
Note that the built-in URLs from earlier versions of Junkbuster / Privoxy,
http://example.com/show-proxy-args and http://i.j.b/, are no longer supported.
If you still use such an old version, you should really consider upgrading to
-0.0.0.
+3.0.2.
-------------------------------------------------------------------------------
We're not. The text substitutions that you are seeing are disabled in the
default configuration as shipped. You have either manually activated the "fun"
filter which is clearly labeled "Text replacements for subversive browsing fun!
-" or you have implicitly activated it by choosing the "Radical" profile in the
-web-based editor (formerly known as the Advanced profile).
+" or you have implicitly activated it by choosing the "Adventuresome" profile
+in the web-based editor (formerly known as the Advanced profile).
-------------------------------------------------------------------------------
7. Privoxy Copyright, License and History
-Copyright © 2001, 2002 by Privoxy Developers <developers@privoxy.org>
+Copyright © 2001 - 2003 by Privoxy Developers <developers@privoxy.org>
Some source code is based on code Copyright © 1997 by Anonymous Coders and
Junkbusters, Inc. and licensed under the GNU General Public License.
inside out, upside down, and then reassembled it, adding many new features
along the way.
-The result of this is Privoxy, whose first stable release, 3.0, was released
+The result of this is Privoxy, whose first stable version, 3.0, was released
August, 2002.
-Privoxy 3.0.1 User Manual
+Privoxy 3.0.2 User Manual
-Copyright © 2001, 2002 by Privoxy Developers
+Copyright © 2001 - 2003 by Privoxy Developers
-$Id: user-manual.sgml,v 1.123.2.27 2003/03/18 19:37:14 oes Exp $
+$Id: user-manual.sgml,v 1.123.2.31 2003/03/26 02:03:43 oes Exp $
The User Manual gives users information on how to install, configure and use
Privoxy.
9. The Filter File
9.1. Filter File Tutorial
+ 9.2. The Pre-defined Filters
10. Templates
11. Contacting the Developers, Bug Reporting and Feature Requests
1. Introduction
This documentation is included with the current stable version of Privoxy,
-v.3.0.1.
+v.3.0.2.
-------------------------------------------------------------------------------
2.1.1. Red Hat, SuSE and Conectiva RPMs
-RPMs can be installed with rpm -Uvh privoxy-3.0.1-1.rpm, and will use /etc/
+RPMs can be installed with rpm -Uvh privoxy-3.0.2-1.rpm, and will use /etc/
privoxy for the location of configuration files.
Note that on Red Hat, Privoxy will not be automatically started on system boot.
that SuSE will automatically start Privoxy in the boot process.
If you have problems with failed dependencies, try rebuilding the SRC RPM: rpm
---rebuild privoxy-3.0.1-1.src.rpm. This will use your locally installed
+--rebuild privoxy-3.0.2-1.src.rpm. This will use your locally installed
libraries and RPM version.
Also note that if you have a Junkbuster RPM installed on your system, you need
2.1.2. Debian
-DEBs can be installed with dpkg -i privoxy_3.0.1-1.deb, and will use /etc/
+DEBs can be installed with dpkg -i privoxy_3.0.2-1.deb, and will use /etc/
privoxy for the location of configuration files.
-------------------------------------------------------------------------------
latest version.
Configuration files are in /etc/privoxy, the documentation is in /usr/share/doc
-/privoxy-3.0.1 and the Log directory is in /var/log/privoxy.
+/privoxy-3.0.2 and the Log directory is in /var/log/privoxy.
-------------------------------------------------------------------------------
When building from a source tarball (either release version or nightly CVS
tarball), first unpack the source:
- tar xzvf privoxy-3.0.1-src* [.tgz or .tar.gz]
- cd privoxy-3.0.1
+ tar xzvf privoxy-3.0.2-src* [.tgz or .tar.gz]
+ cd privoxy-3.0.2
For retrieving the current CVS sources, you'll need CVS installed. Note that
sources from CVS are development quality, and may not be stable, or well
Unix, in local filesystem:
- user-manual file:///usr/share/doc/privoxy-3.0.1/user-manual/
+ user-manual file:///usr/share/doc/privoxy-3.0.2/user-manual/
Windows, in local filesystem, must use forward slash notation:
- user-manual file:/c:/some-dir/privoxy-3.0.1/user-manual/
+ user-manual file:/c:/some-dir/privoxy-3.0.2/user-manual/
Windows, UNC notation (with forward slashes):
- user-manual file://///some-server/some-path/privoxy-3.0.1/user-manual/
+ user-manual file://///some-server/some-path/privoxy-3.0.2/user-manual/
Any platform, on local webserver (called "local-webserver"):
Parameter:
The name of a filter, as defined in the filter file (typically
- default.filter, set by the filterfile option in the config file). Filtering
- can be completely disabled without the use of parameters.
+ default.filter, set by the filterfile option in the config file). When used
+ in its negative form, and without parameters, filtering is completely
+ disabled.
Notes:
in the distribution filter file that you can use. See the examples below
for a list.
- This is potentially a very powerful feature! But "rolling your own" filters
- requires a knowledge of regular expressions and HTML.
-
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.
+ This is very powerful feature, but "rolling your own" filters requires a
+ knowledge of regular expressions and HTML.
+
The amount of data that can be filtered is limited to the buffer-limit
option in the main config file. The default is 4096 KB (4 Megs). Once this
limit is exceeded, the buffered data, and all pending data, is passed
Feedback with suggestions for new or improved filters is particularly
welcome!
-Example usage (with filters from the distribution default.filter file):
+ The below list has only the names and a one-line description of each
+ predefined filter. There are more verbose explanations of what these
+ filters do in the filter file chapter.
+
+Example usage (with filters from the distribution default.filter file). See the
+ Predefined Filters section for more explanation on each:
+filter{js-annoyances} # Get rid of particularly annoying JavaScript abuse
-------------------------------------------------------------------------------
+9.2. The Pre-defined Filters
+
+The distribution default.filter file contains a selection of pre-defined
+filters for your convenience:
+
+js-annoyances
+
+ The purpose of this filter is to get rid of particularly annoying
+ JavaScript abuse. To that end, it
+
+ + replaces JavaScript references to the browser's referrer information
+ with the string "Not Your Business!". This compliments the
+ hide-referrer action on the content level.
+
+ + removes the bindings to the DOM's unload event which we feel has no
+ right to exist and is responsible for most "exit consoles", i.e. nasty
+ windows that pop up when you close another one.
+
+ + removes code that causes new windows to be opened with undesired
+ properties, such as being full-screen, non-resizable, without location,
+ status or menu bar etc.
+
+js-events
+
+ This is a very radical measure. It removes virtually all JavaScript event
+ bindings, which means that scripts can not react to user actions such as
+ mouse movements or clicks, window resizing etc, anymore.
+
+ We strongly discourage using this filter as a default since it breaks many
+ legitimate scripts. It is meant for use only on extra-nasty sites (should
+ you really need to go there).
+
+html-annoyances
+
+ This filter will undo many common instances of HTML based abuse.
+
+ The BLINK and MARQUEE tags are neutralized (yeah baby!), and browser
+ windows will be created as resizable (as of course they should be!), and
+ will have location, scroll and menu bars -- even if specified otherwise.
+
+content-cookies
+
+ Most cookies are set in the HTTP dialogue, where they can be intercepted by
+ the crunch-incoming-cookies and crunch-outgoing-cookies actions. But web
+ sites increasingly make use of HTML meta tags and JavaScript to sneak
+ cookies to the browser on the content level.
+
+ This filter disables HTML and JavaScript code that reads or sets cookies.
+ Use it wherever you would also use the cookie crunch actions.
+
+refresh tags
+
+ Disable any refresh tags if the interval is greater than nine seconds (so
+ that redirections done via refresh tags are not destroyed). This is useful
+ for dial-on-demand setups, or for those who find this HTML feature
+ annoying.
+
+unsolicited-popups
+
+ This filter attempts to prevent only "unsolicited" pop-up windows from
+ opening, yet still allow pop-up windows that the user has explicitly chosen
+ to open. It was added in version 3.0.1, as an improvement over earlier such
+ filters.
+
+ Technical note: The filter works by redefining the window.open JavaScript
+ function to a dummy function during the loading and rendering phase of each
+ HTML page access, and restoring the function afterwards.
+
+all-popups
+
+ Attempt to prevent all pop-up windows from opening. Note this should be
+ used with more discretion than the above, since it is more likely to break
+ some sites that require pop-ups for normal usage. Use with caution.
+
+img-reorder
+
+ This is a helper filter that has no value if used alone. It makes the
+ banners-by-size and banners-by-link (see below) filters more effective and
+ should be enabled together with them.
+
+banners-by-size
+
+ This filter removes image tags purely based on what size they are.
+ Fortunately for us, many ads and banner images tend to conform to certain
+ standardized sizes, which makes this filter quite effective for ad
+ stripping purposes.
+
+ Occasionally this filter will cause false positives on images that are not
+ ads, but just happen to be of one of the standard banner sizes.
+
+banners-by-link
+
+ This is an experimental filter that attempts to kill any banners if their
+ URLs seem to point to known or suspected click trackers. It is currently
+ not of much value and is not recommended for use by default.
+
+webbugs
+
+ Webbugs are small, invisible images (technically 1X1 GIF images), that are
+ used to track users across websites, and collect information on them. As an
+ HTML page is loaded by the browser, an embedded image tag causes the
+ browser to contact a third-party site, disclosing the tracking information
+ through the requested URL and/or cookies for that third-party domain,
+ without the use ever becoming aware of the interaction with the third-party
+ site. HTML-ized spam also uses a similar technique to verify email
+ addresses.
+
+ This filter removes the HTML code that loads such "webbugs".
+
+tiny-textforms
+
+ A rather special-purpose filter that can be used to enlarge textareas
+ (those multi-line text boxes in web forms) and turn off hard word wrap in
+ them. It was written for the sourceforge.net tracker system where such
+ boxes are a nuisance, but it can be handy on other sites, too.
+
+ It is not recommended to use this filter as a default.
+
+jumping-windows
+
+ Many consider windows that move, or resize themselves to be abusive. This
+ filter neutralizes the related JavaScript code. Note that some sites might
+ not display or behave as intended when using this filter.
+
+frameset-borders
+
+ Some web designers seem to assume that everyone in the world will view
+ their web sites using the same browser brand and version, screen resolution
+ etc, because only that assumption could explain why they'd use static frame
+ sizes, yet prevent their frames from being resized by the user, should they
+ be too small to show their whole content.
+
+ This filter removes the related HTML code. It should only be applied to
+ sites which need it.
+
+demoronizer
+
+ Many Microsoft products that generate HTML use non-standard extensions
+ (read: violations) of the ISO 8859-1 aka Latin-1 character set. This causes
+ those HTML documents to display with errors on standard-compliant
+ platforms.
+
+ This filter translates the MS-only characters into Latin-1 equivalents. It
+ is safe for general use, and recommended for non-MS platforms.
+
+shockwave-flash
+
+ A filter for shockwave haters. As the name suggests, this filter strips
+ code out of web pages that is used to embed shockwave flash objects.
+
+quicktime-kioskmode
+
+ Change HTML code that embeds Quicktime objects so that kioskmode, which
+ prevents saving, is disabled.
+
+fun
+
+ Text replacements for subversive browsing fun. Make fun of your favorite
+ Monopolist or play buzzword bingo.
+
+crude-parental
+
+ A demonstration-only filter that shows how Privoxy can be used to delete
+ web content on a keyword basis.
+
+ie-exploits
+
+ A collection of text replacements to disable malicious HTML and JavaScript
+ code that exploits known security holes in Internet Explorer.
+
+ Presently, it only protects against Nimda and a cross-site scripting bug,
+ and would need active maintenance to provide more substantial protection.
+
+site-specifics
+
+ Some web sites have very specific problems, the cure for which doesn't
+ apply anywhere else, or could even cause damage on other sites.
+
+ This is a collection of such site-specific cures which should only be
+ applied to the sites they were intended for, which is what the supplied
+ default.action file does. Users shouldn't need to change anything regarding
+ this filter.
+
+-------------------------------------------------------------------------------
+
10. Templates
All Privoxy built-in pages, i.e. error pages such as the "404 - No Such Domain"
12. Privoxy Copyright, License and History
-Copyright © 2001, 2002 by Privoxy Developers <developers@privoxy.org>
+Copyright © 2001 - 2003 by Privoxy Developers <developers@privoxy.org>
Some source code is based on code Copyright © 1997 by Anonymous Coders and
Junkbusters, Inc. and licensed under the GNU General Public License.
inside out, upside down, and then reassembled it, adding many new features
along the way.
-The result of this is Privoxy, whose first stable release, 3.0, was released
+The result of this is Privoxy, whose first stable version, 3.0, was released
August, 2002.
-------------------------------------------------------------------------------
12.3. Authors
-Current Project Developers:
+Current Developement Team:
+ Hal Burgiss (docs)
Jon Foster
Andreas Oesterhelt
- Stefan Waldherr
+ David Schmidt (OS/2, Mac OSX ports)
+
- Thomas Steudten
- Rodney Stromlund
-Current Project Contributors:
+Current and Former Project Contributors:
Johny Agotnes
Rodrigo Barbosa (RPM specfiles)
Moritz Barsnick
- Hal Burgiss (docs)
Mattes Dolak
Karsten Hopp (Red Hat)
Alexander Lazic
Daniel Leite
Gábor Lipták
- Andrew Lock (Win32)
+ Adam Lock (Win32)
Guy Laroche
Haroon Rafique
Roland Rosenfeld (Debian)
Georg Sauthoff (Gentoo)
- David Schmidt (OS/2, Mac OSX ports)
+ Thomas Steudten
Joerg Strohmayer (Amiga)
+ Rodney Stromlund
Sviatoslav Sviridov
Sarantis Paskalis
+ Stefan Waldherr
Based in part on code originally developed by:
></A
>9. Privoxy Copyright, License and History</H1
><P
-> Copyright © 2001, 2002 by Privoxy Developers <TT
+> Copyright © 2001 - 2003 by Privoxy Developers <TT
CLASS="EMAIL"
><<A
HREF="mailto:developers@privoxy.org"
CLASS="APPLICATION"
>Privoxy</SPAN
>, whose first
- stable release, 3.0, was released August, 2002.
+ stable version, 3.0, was released August, 2002.
</P
></DIV
></DIV
>
version string, e.g. <SPAN
CLASS="QUOTE"
->"3.0.1"</SPAN
+>"3.0.2"</SPAN
>.
</TD
></TR
for anyone who wants to join the team.</P
><P
> Please note that this document is constantly evolving. This copy represents
- the state at the release of version 3.0.1.
+ the state at the release of version 3.0.2.
You can find the latest version of the this manual at <A
HREF="http://www.privoxy.org/developer-manual/"
TARGET="_top"
><TD
><PRE
CLASS="PROGRAMLISTING"
-> debchange -v 3.0.1-stable-1 "New upstream version"</PRE
+> debchange -v 3.0.2-stable-1 "New upstream version"</PRE
></TD
></TR
></TABLE
> This will create
<TT
CLASS="FILENAME"
->../privoxy_3.0.1-stable-1_i386.deb</TT
+>../privoxy_3.0.2-stable-1_i386.deb</TT
>
which can be uploaded. To upload the package to Sourceforge, simply
issue
CLASS="emphasis"
><I
CLASS="EMPHASIS"
->3.0.1
+>3.0.2
(beta)</I
></SPAN
>.
>"Medium"</SPAN
> and <SPAN
CLASS="QUOTE"
->"Radical"</SPAN
+>"Adventuresome"</SPAN
> defaults?</H3
><P
> Configuring <SPAN
><P
> It should be noted that the <SPAN
CLASS="QUOTE"
->"Radical"</SPAN
+>"Adventuresome"</SPAN
> profile (formerly known
as the <SPAN
CLASS="QUOTE"
></A
>7. Privoxy Copyright, License and History</H1
><P
-> Copyright © 2001, 2002 by Privoxy Developers <TT
+> Copyright © 2001 - 2003 by Privoxy Developers <TT
CLASS="EMAIL"
><<A
HREF="mailto:developers@privoxy.org"
CLASS="APPLICATION"
>Privoxy</SPAN
>, whose first
- stable release, 3.0, was released August, 2002.
+ stable version, 3.0, was released August, 2002.
</P
></DIV
></DIV
CLASS="APPLICATION"
>Privoxy</SPAN
>, whose first
- stable release, 3.0, was released August, 2002.
+ stable version, 3.0, was released August, 2002.
</P
></DIV
><DIV
><P
> The developers also believed that there are so many changes from the original
code, that it was time to make a clean break from the past and make
- a name in their own right, especially now with the pending
- release of version 3.0.</P
+ a name in their own right.</P
></DIV
><DIV
CLASS="SECT2"
><BR></P
><P
CLASS="PUBDATE"
->$Id: faq.sgml,v 1.61.2.27 2002/12/01 06:31:58 hal9 Exp $<BR></P
+>$Id: faq.sgml,v 1.61.2.28 2003/03/18 19:37:21 oes Exp $<BR></P
><DIV
><DIV
CLASS="ABSTRACT"
> (tm).</P
><P
> Please note that this document is constantly evolving. This copy represents
- the state at the release of version 0.0.0.
+ the state at the release of version 3.0.2.
You can find the latest version of the document at <A
HREF="http://www.privoxy.org/faq/"
TARGET="_top"
>"Medium"</SPAN
> and <SPAN
CLASS="QUOTE"
->"Radical"</SPAN
+>"Adventuresome"</SPAN
> defaults?</A
></DT
><DT
>Privoxy</SPAN
>, http://example.com/show-proxy-args and http://i.j.b/,
are no longer supported. If you still use such an old version, you should really consider
- upgrading to 0.0.0.</P
+ upgrading to 3.0.2.</P
></DIV
><DIV
CLASS="SECT2"
> or you have implicitly activated it by choosing the
<SPAN
CLASS="QUOTE"
->"Radical"</SPAN
+>"Adventuresome"</SPAN
> profile in the web-based editor (formerly known
as the <SPAN
CLASS="APPLICATION"
Junkbuster</SPAN
> (tm).</P
><P
-> The most recent release is 0.0.0 (UNRELEASED).
+> The most recent release is 3.0.2 (stable).
</P
><P
></P
></P
><P
> <SUB
-> Copyright © 2001, 2002 by Privoxy Developers
+> Copyright © 2001 - 2003 by Privoxy Developers
</SUB
></P
></DIV
<HTML><HEAD><TITLE>Manpage of PRIVOXY</TITLE>
<LINK REL="STYLESHEET" TYPE="text/css" HREF="../p_doc.css"></HEAD><BODY>
<H1>PRIVOXY</H1>
-Section: (1)<BR>Updated:
18 March 2003<BR><A HREF="#index">Index</A>
+Section: (1)<BR>Updated:
25 March 2003<BR><A HREF="#index">Index</A>
<HR>
<A NAME="lbAB"> </A>
<H2>SYNOPSIS</H2>
<P>
-<B>privoxy</B> [<B>--help</B> ] [<B>--version</B> ] [<B>--no-daemon</B> ] [<B>--pidfile </B><I>pidfile</I><B></B> ] [<B>--user </B><I>user[.group]</I><B></B> ] [<B></B><I>configfile</I><B></B> ]<B> (UNIX)</B>
+<B>privoxy</B> [<B>--help</B> ] [<B>--version</B> ] [<B>--no-daemon</B> ] [<B>--pidfile </B><I>pidfile</I><B></B> ] [<B>--user </B><I>user[.group]</I><B></B> ] [<B>--chroot</B> ] [<B></B><I>configfile</I><B></B> ]<B> (UNIX)</B>
<P>
<P>
<B>privoxy.exe</B> [<B></B><I>configfile</I><B></B> ]<B> (Windows)</B>
<P>
<PRE>
+ Hal Burgiss (docs)
Jon Foster
Andreas Oesterhelt
- Stefan Waldherr
- Thomas Steudten
- Rodney Stromlund
+ David Schmidt (OS/2, Mac OSX ports)
+
Johny Agotnes
Rodrigo Barbosa (RPM specfiles)
Moritz Barsnick
- Hal Burgiss (docs)
Mattes Dolak
Karsten Hopp (Red Hat)
Alexander Lazic
Daniel Leite
Gábor Lipták
- Andrew Lock (Win32)
+ Adam Lock (Win32)
Guy Laroche
Haroon Rafique
Roland Rosenfeld (Debian)
Georg Sauthoff (Gentoo)
- David Schmidt (OS/2, Mac OSX ports)
+ Thomas Steudten
Joerg Strohmayer (Amiga)
+ Rodney Stromlund
Sviatoslav Sviridov
Sarantis Paskalis
+ Stefan Waldherr
</PRE>
<A NAME="lbAN"> </A>
<P>
-Copyright (C) 2001
, 2002 by Privoxy Developers <<A HREF="mailto:developers@privoxy.org">developers@privoxy.org</A>>
+Copyright (C) 2001
- 2003 by Privoxy Developers <<A HREF="mailto:developers@privoxy.org">developers@privoxy.org</A>>
<P>
Some source code is based on code Copyright (C) 1997 by Anonymous Coders
This document was created by
man2html,
using the manual pages.<BR>
-Time: 00:37:30 GMT, March 19, 2003
+Time: 02:05:48 GMT, March 26, 2003
</BODY>
</HTML>
>Privoxy - The Privacy Enhancing Proxy</H1
><H2
CLASS="SUBTITLE"
->Project Index Page v0.0.0</H2
+>Project Index Page v3.0.2</H2
><DIV
><DIV
CLASS="ABSTRACT"
></H2
><P
> <SUB
-> Copyright © 2001, 2002 by Privoxy Developers
+> Copyright © 2001 - 2003 by Privoxy Developers
</SUB
></P
></DIV
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="Privoxy 3.0.1 User Manual"
+TITLE="Privoxy 3.0.2 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="The Main Configuration File"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 3.0.1 User Manual</TH
+>Privoxy 3.0.2 User Manual</TH
></TR
><TR
><TD
option in the <A
HREF="config.html"
>config file</A
->). Filtering
- can be completely disabled without the use of parameters.
+>). When used in its negative form,
+ and without parameters, filtering is completely disabled.
</P
></DD
><DT
a list.
</P
><P
-> This is potentially a very powerful feature! But <SPAN
-CLASS="QUOTE"
->"rolling your own"</SPAN
->
- filters requires a knowledge of regular expressions and HTML.
- </P
-><P
> 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
noticeable on slower connections.
</P
><P
+> This is very powerful feature, but <SPAN
+CLASS="QUOTE"
+>"rolling your own"</SPAN
+>
+ filters requires a knowledge of regular expressions and HTML.
+ </P
+><P
> The amount of data that can be filtered is limited to the
<TT
CLASS="LITERAL"
> with suggestions for new or
improved filters is particularly welcome!
</P
+><P
+> The below list has only the names and a one-line description of each
+ predefined filter. There are <A
+HREF="filter-file.html#PREDEFINED-FILTERS"
+>more
+ verbose explanations</A
+> of what these filters do in the <A
+HREF="filter-file.html"
+>filter file chapter</A
+>.
+ </P
></DD
><DT
>Example usage (with filters from the distribution <TT
CLASS="FILENAME"
>default.filter</TT
-> file):</DT
+> file).
+ See <A
+HREF="filter-file.html#PREDEFINED-FILTERS"
+>the Predefined Filters section</A
+> for
+ more explanation on each:</DT
><DD
><P
> <A
><H3
CLASS="SECT3"
><A
-NAME="AEN2914"
+NAME="AEN2918"
></A
>8.5.21. Summary</H3
><P
><H3
CLASS="SECT3"
><A
-NAME="AEN2979"
+NAME="AEN2983"
></A
>8.7.1. default.action</H3
><P
><H3
CLASS="SECT3"
><A
-NAME="AEN3145"
+NAME="AEN3149"
></A
>8.7.2. user.action</H3
><P
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="Privoxy 3.0.1 User Manual"
+TITLE="Privoxy 3.0.2 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="See Also"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 3.0.1 User Manual</TH
+>Privoxy 3.0.2 User Manual</TH
></TR
><TR
><TD
><H2
CLASS="SECT2"
><A
-NAME="AEN3727"
+NAME="AEN3878"
></A
>14.2. <SPAN
CLASS="APPLICATION"
Privoxy main page:
</P
><A
-NAME="AEN3742"
+NAME="AEN3893"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
editing of actions files:
</P
><A
-NAME="AEN3750"
+NAME="AEN3901"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
Show the source code version numbers:
</P
><A
-NAME="AEN3755"
+NAME="AEN3906"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
Show the browser's request headers:
</P
><A
-NAME="AEN3760"
+NAME="AEN3911"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
Show which actions apply to a URL and why:
</P
><A
-NAME="AEN3765"
+NAME="AEN3916"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
to run, but only as a pass-through proxy, with no actions taking place:
</P
><A
-NAME="AEN3771"
+NAME="AEN3922"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
> Short cuts. Turn off, then on:
</P
><A
-NAME="AEN3775"
+NAME="AEN3926"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
</P
></BLOCKQUOTE
><A
-NAME="AEN3778"
+NAME="AEN3929"
></A
><BLOCKQUOTE
CLASS="BLOCKQUOTE"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="Privoxy 3.0.1 User Manual"
+TITLE="Privoxy 3.0.2 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Privoxy Configuration"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 3.0.1 User Manual</TH
+>Privoxy 3.0.2 User Manual</TH
></TR
><TR
><TD
><TD
><PRE
CLASS="SCREEN"
-> user-manual file:///usr/share/doc/privoxy-3.0.1/user-manual/</PRE
+> user-manual file:///usr/share/doc/privoxy-3.0.2/user-manual/</PRE
></TD
></TR
></TABLE
><TD
><PRE
CLASS="SCREEN"
-> user-manual file:/c:/some-dir/privoxy-3.0.1/user-manual/</PRE
+> user-manual file:/c:/some-dir/privoxy-3.0.2/user-manual/</PRE
></TD
></TR
></TABLE
><TD
><PRE
CLASS="SCREEN"
-> user-manual file://///some-server/some-path/privoxy-3.0.1/user-manual/</PRE
+> user-manual file://///some-server/some-path/privoxy-3.0.2/user-manual/</PRE
></TD
></TR
></TABLE
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="Privoxy 3.0.1 User Manual"
+TITLE="Privoxy 3.0.2 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Starting Privoxy"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 3.0.1 User Manual</TH
+>Privoxy 3.0.2 User Manual</TH
></TR
><TR
><TD
><TR
><TD
> ▪ <A
-HREF="http://www.privoxy.org/3.0.1/user-manual/"
+HREF="http://www.privoxy.org/3.0.2/user-manual/"
TARGET="_top"
>Documentation</A
>
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="Privoxy 3.0.1 User Manual"
+TITLE="Privoxy 3.0.2 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Templates"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 3.0.1 User Manual</TH
+>Privoxy 3.0.2 User Manual</TH
></TR
><TR
><TD
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="Privoxy 3.0.1 User Manual"
+TITLE="Privoxy 3.0.2 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Contacting the Developers, Bug Reporting and Feature
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 3.0.1 User Manual</TH
+>Privoxy 3.0.2 User Manual</TH
></TR
><TR
><TD
>Privoxy</SPAN
> Copyright, License and History</H1
><P
-> Copyright © 2001, 2002 by Privoxy Developers <TT
+> Copyright © 2001 - 2003 by Privoxy Developers <TT
CLASS="EMAIL"
><<A
HREF="mailto:developers@privoxy.org"
><H2
CLASS="SECT2"
><A
-NAME="AEN3473"
+NAME="AEN3624"
></A
>12.1. License</H2
><P
CLASS="APPLICATION"
>Privoxy</SPAN
>, whose first
- stable release, 3.0, was released August, 2002.
+ stable version, 3.0, was released August, 2002.
</P
></DIV
><DIV
></A
>12.3. Authors</H2
><P
-> Current Project Developers:</P
+> Current Developement Team:</P
><P
CLASS="LITERALLAYOUT"
-> Jon Foster<br>
+> Hal Burgiss (docs)<br>
+ Jon Foster<br>
Andreas Oesterhelt<br>
- Stefan Waldherr<br>
- <br>
- Thomas Steudten<br>
- Rodney Stromlund</P
+ David Schmidt (OS/2, Mac OSX ports)<br>
+ <br> </P
><P
-> Current Project Contributors:</P
+> Current and Former Project Contributors:</P
><P
CLASS="LITERALLAYOUT"
> Johny Agotnes <br>
Rodrigo Barbosa (RPM specfiles)<br>
Moritz Barsnick<br>
- Hal Burgiss (docs)<br>
Mattes Dolak <br>
Karsten Hopp (Red Hat)<br>
Alexander Lazic<br>
Daniel Leite<br>
Gábor Lipták<br>
- Andrew Lock (Win32)<br>
+ Adam Lock (Win32)<br>
Guy Laroche<br>
Haroon Rafique<br>
Roland Rosenfeld (Debian)<br>
Georg Sauthoff (Gentoo)<br>
- David Schmidt (OS/2, Mac OSX ports)<br>
+ Thomas Steudten<br>
Joerg Strohmayer (Amiga)<br>
+ Rodney Stromlund<br>
Sviatoslav Sviridov<br>
- Sarantis Paskalis</P
+ Sarantis Paskalis<br>
+ Stefan Waldherr</P
><P
> Based in part on code originally developed by:</P
><P
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="Privoxy 3.0.1 User Manual"
+TITLE="Privoxy 3.0.2 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Actions Files"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 3.0.1 User Manual</TH
+>Privoxy 3.0.2 User Manual</TH
></TR
><TR
><TD
><H2
CLASS="SECT2"
><A
-NAME="AEN3271"
+NAME="AEN3275"
></A
>9.1. Filter File Tutorial</H2
><P
><P
> You get the idea?</P
></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="PREDEFINED-FILTERS"
+></A
+>9.2. The Pre-defined Filters</H2
+><P
+>The distribution <TT
+CLASS="FILENAME"
+>default.filter</TT
+> file contains a selection of
+pre-defined filters for your convenience:</P
+><P
+></P
+><DIV
+CLASS="VARIABLELIST"
+><DL
+><DT
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>js-annoyances</I
+></SPAN
+></DT
+><DD
+><P
+> The purpose of this filter is to get rid of particularly annoying JavaScript abuse.
+ To that end, it
+ <P
+></P
+><UL
+><LI
+><P
+> replaces JavaScript references to the browser's referrer information
+ with the string "Not Your Business!". This compliments the <TT
+CLASS="LITERAL"
+><A
+HREF="actions-file.html#HIDE-REFERRER"
+>hide-referrer</A
+></TT
+> action on the content level.
+ </P
+></LI
+><LI
+><P
+> removes the bindings to the DOM's
+ <A
+HREF="http://www.w3.org/TR/2000/REC-DOM-Level-2-Events-20001113/events.html#Events-eventgroupings-htmlevents"
+TARGET="_top"
+>unload
+ event</A
+> which we feel has no right to exist and is responsible for most <SPAN
+CLASS="QUOTE"
+>"exit consoles"</SPAN
+>, i.e.
+ nasty windows that pop up when you close another one.
+ </P
+></LI
+><LI
+><P
+> removes code that causes new windows to be opened with undesired properties, such as being
+ full-screen, non-resizable, without location, status or menu bar etc.
+ </P
+></LI
+></UL
+>
+ </P
+></DD
+><DT
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>js-events</I
+></SPAN
+></DT
+><DD
+><P
+> This is a very radical measure. It removes virtually all JavaScript event bindings, which
+ means that scripts can not react to user actions such as mouse movements or clicks, window
+ resizing etc, anymore.
+ </P
+><P
+> We <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>strongly discourage</I
+></SPAN
+> using this filter as a default since it breaks
+ many legitimate scripts. It is meant for use only on extra-nasty sites (should you really
+ need to go there).
+ </P
+></DD
+><DT
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>html-annoyances</I
+></SPAN
+></DT
+><DD
+><P
+> This filter will undo many common instances of HTML based abuse.
+ </P
+><P
+> The <TT
+CLASS="LITERAL"
+>BLINK</TT
+> and <TT
+CLASS="LITERAL"
+>MARQUEE</TT
+> tags
+ are neutralized (yeah baby!), and browser windows will be created as
+ resizable (as of course they should be!), and will have location,
+ scroll and menu bars -- even if specified otherwise.
+ </P
+></DD
+><DT
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>content-cookies</I
+></SPAN
+></DT
+><DD
+><P
+> Most cookies are set in the HTTP dialogue, where they can be intercepted
+ by the
+ <TT
+CLASS="LITERAL"
+><A
+HREF="actions-file.html#CRUNCH-INCOMING-COOKIES"
+>crunch-incoming-cookies</A
+></TT
+>
+ and <TT
+CLASS="LITERAL"
+><A
+HREF="actions-file.html#CRUNCH-OUTGOING-COOKIES"
+>crunch-outgoing-cookies</A
+></TT
+>
+ actions. But web sites increasingly make use of HTML meta tags and JavaScript
+ to sneak cookies to the browser on the content level.
+ </P
+><P
+> This filter disables HTML and JavaScript code that reads or sets cookies. Use
+ it wherever you would also use the cookie crunch actions.
+ </P
+></DD
+><DT
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>refresh tags</I
+></SPAN
+></DT
+><DD
+><P
+> Disable any refresh tags if the interval is greater than nine seconds (so
+ that redirections done via refresh tags are not destroyed). This is useful
+ for dial-on-demand setups, or for those who find this HTML feature
+ annoying.
+ </P
+></DD
+><DT
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>unsolicited-popups</I
+></SPAN
+></DT
+><DD
+><P
+> This filter attempts to prevent only <SPAN
+CLASS="QUOTE"
+>"unsolicited"</SPAN
+> pop-up
+ windows from opening, yet still allow pop-up windows that the user
+ has explicitly chosen to open. It was added in version 3.0.1,
+ as an improvement over earlier such filters.
+ </P
+><P
+> Technical note: The filter works by redefining the window.open JavaScript
+ function to a dummy function during the loading and rendering phase of each
+ HTML page access, and restoring the function afterwards.
+ </P
+></DD
+><DT
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>all-popups</I
+></SPAN
+></DT
+><DD
+><P
+> Attempt to prevent <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>all</I
+></SPAN
+> pop-up windows from opening.
+ Note this should be used with more discretion than the above, since it is
+ more likely to break some sites that require pop-ups for normal usage. Use
+ with caution.
+ </P
+></DD
+><DT
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>img-reorder</I
+></SPAN
+></DT
+><DD
+><P
+> This is a helper filter that has no value if used alone. It makes the
+ <TT
+CLASS="LITERAL"
+>banners-by-size</TT
+> and <TT
+CLASS="LITERAL"
+>banners-by-link</TT
+>
+ (see below) filters more effective and should be enabled together with them.
+ </P
+></DD
+><DT
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>banners-by-size</I
+></SPAN
+></DT
+><DD
+><P
+> This filter removes image tags purely based on what size they are. Fortunately
+ for us, many ads and banner images tend to conform to certain standardized
+ sizes, which makes this filter quite effective for ad stripping purposes.
+ </P
+><P
+> Occasionally this filter will cause false positives on images that are not ads,
+ but just happen to be of one of the standard banner sizes.
+ </P
+></DD
+><DT
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>banners-by-link</I
+></SPAN
+></DT
+><DD
+><P
+> This is an experimental filter that attempts to kill any banners if
+ their URLs seem to point to known or suspected click trackers. It is currently
+ not of much value and is not recommended for use by default.
+ </P
+></DD
+><DT
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>webbugs</I
+></SPAN
+></DT
+><DD
+><P
+> Webbugs are small, invisible images (technically 1X1 GIF images), that
+ are used to track users across websites, and collect information on them.
+ As an HTML page is loaded by the browser, an embedded image tag causes the
+ browser to contact a third-party site, disclosing the tracking information
+ through the requested URL and/or cookies for that third-party domain, without
+ the use ever becoming aware of the interaction with the third-party site.
+ HTML-ized spam also uses a similar technique to verify email addresses.
+ </P
+><P
+> This filter removes the HTML code that loads such <SPAN
+CLASS="QUOTE"
+>"webbugs"</SPAN
+>.
+ </P
+></DD
+><DT
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>tiny-textforms</I
+></SPAN
+></DT
+><DD
+><P
+> A rather special-purpose filter that can be used to enlarge textareas (those
+ multi-line text boxes in web forms) and turn off hard word wrap in them.
+ It was written for the sourceforge.net tracker system where such boxes are
+ a nuisance, but it can be handy on other sites, too.
+ </P
+><P
+> It is not recommended to use this filter as a default.
+ </P
+></DD
+><DT
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>jumping-windows</I
+></SPAN
+></DT
+><DD
+><P
+> Many consider windows that move, or resize themselves to be abusive. This filter
+ neutralizes the related JavaScript code. Note that some sites might not display
+ or behave as intended when using this filter.
+ </P
+></DD
+><DT
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>frameset-borders</I
+></SPAN
+></DT
+><DD
+><P
+> Some web designers seem to assume that everyone in the world will view their
+ web sites using the same browser brand and version, screen resolution etc,
+ because only that assumption could explain why they'd use static frame sizes,
+ yet prevent their frames from being resized by the user, should they be too
+ small to show their whole content.
+ </P
+><P
+> This filter removes the related HTML code. It should only be applied to sites
+ which need it.
+ </P
+></DD
+><DT
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>demoronizer</I
+></SPAN
+></DT
+><DD
+><P
+> Many Microsoft products that generate HTML use non-standard extensions (read:
+ violations) of the ISO 8859-1 aka Latin-1 character set. This causes those
+ HTML documents to display with errors on standard-compliant platforms.
+ </P
+><P
+> This filter translates the MS-only characters into Latin-1 equivalents. It is
+ safe for general use, and recommended for non-MS platforms.
+ </P
+></DD
+><DT
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>shockwave-flash</I
+></SPAN
+></DT
+><DD
+><P
+> A filter for shockwave haters. As the name suggests, this filter strips code
+ out of web pages that is used to embed shockwave flash objects.
+ </P
+><P
+> </P
+></DD
+><DT
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>quicktime-kioskmode</I
+></SPAN
+></DT
+><DD
+><P
+> Change HTML code that embeds Quicktime objects so that kioskmode, which
+ prevents saving, is disabled.
+ </P
+></DD
+><DT
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>fun</I
+></SPAN
+></DT
+><DD
+><P
+> Text replacements for subversive browsing fun. Make fun of your favorite
+ Monopolist or play buzzword bingo.
+ </P
+></DD
+><DT
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>crude-parental</I
+></SPAN
+></DT
+><DD
+><P
+> A demonstration-only filter that shows how <SPAN
+CLASS="APPLICATION"
+>Privoxy</SPAN
+>
+ can be used to delete web content on a keyword basis.
+ </P
+></DD
+><DT
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>ie-exploits</I
+></SPAN
+></DT
+><DD
+><P
+> A collection of text replacements to disable malicious HTML and JavaScript
+ code that exploits known security holes in Internet Explorer.
+ </P
+><P
+> Presently, it only protects against Nimda and a cross-site scripting bug, and
+ would need active maintenance to provide more substantial protection.
+ </P
+></DD
+><DT
+><SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>site-specifics</I
+></SPAN
+></DT
+><DD
+><P
+> Some web sites have very specific problems, the cure for which doesn't apply
+ anywhere else, or could even cause damage on other sites.
+ </P
+><P
+> This is a collection of such site-specific cures which should only be applied
+ to the sites they were intended for, which is what the supplied
+ <TT
+CLASS="FILENAME"
+>default.action</TT
+> file does. Users shouldn't need to change
+ anything regarding this filter.
+ </P
+></DD
+></DL
+></DIV
+></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
<HTML
><HEAD
><TITLE
->Privoxy 3.0.1 User Manual</TITLE
+>Privoxy 3.0.2 User Manual</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
><A
NAME="AEN2"
></A
->Privoxy 3.0.1 User Manual</H1
+>Privoxy 3.0.2 User Manual</H1
><P
CLASS="PUBDATE"
> <SUB
> <A
HREF="copyright.html"
>Copyright</A
-> © 2001, 2002 by
+> © 2001 - 2003 by
<A
HREF="http://www.privoxy.org/"
TARGET="_top"
><BR></P
><P
CLASS="PUBDATE"
->$Id: user-manual.sgml,v 1.123.2.27 2003/03/18 19:37:14 oes Exp $<BR></P
+>$Id: user-manual.sgml,v 1.123.2.31 2003/03/26 02:03:43 oes Exp $<BR></P
><DIV
><DIV
CLASS="ABSTRACT"
></DT
><DT
>8.5.21. <A
-HREF="actions-file.html#AEN2914"
+HREF="actions-file.html#AEN2918"
>Summary</A
></DT
></DL
><DL
><DT
>8.7.1. <A
-HREF="actions-file.html#AEN2979"
+HREF="actions-file.html#AEN2983"
>default.action</A
></DT
><DT
>8.7.2. <A
-HREF="actions-file.html#AEN3145"
+HREF="actions-file.html#AEN3149"
>user.action</A
></DT
></DL
><DL
><DT
>9.1. <A
-HREF="filter-file.html#AEN3271"
+HREF="filter-file.html#AEN3275"
>Filter File Tutorial</A
></DT
+><DT
+>9.2. <A
+HREF="filter-file.html#PREDEFINED-FILTERS"
+>The Pre-defined Filters</A
+></DT
></DL
></DD
><DT
><DL
><DT
>12.1. <A
-HREF="copyright.html#AEN3473"
+HREF="copyright.html#AEN3624"
>License</A
></DT
><DT
></DT
><DT
>14.2. <A
-HREF="appendix.html#AEN3727"
+HREF="appendix.html#AEN3878"
><SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="Privoxy 3.0.1 User Manual"
+TITLE="Privoxy 3.0.2 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Introduction"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 3.0.1 User Manual</TH
+>Privoxy 3.0.2 User Manual</TH
></TR
><TR
><TD
><P
> RPMs can be installed with <TT
CLASS="LITERAL"
->rpm -Uvh privoxy-3.0.1-1.rpm</TT
+>rpm -Uvh privoxy-3.0.2-1.rpm</TT
>,
and will use <TT
CLASS="FILENAME"
> If you have problems with failed dependencies, try rebuilding the SRC RPM:
<TT
CLASS="LITERAL"
->rpm --rebuild privoxy-3.0.1-1.src.rpm</TT
+>rpm --rebuild privoxy-3.0.2-1.src.rpm</TT
>. This
will use your locally installed libraries and RPM version. </P
><P
> DEBs can be installed with <TT
CLASS="LITERAL"
>dpkg -i
- privoxy_3.0.1-1.deb</TT
+ privoxy_3.0.2-1.deb</TT
>, and will use
<TT
CLASS="FILENAME"
>, the
documentation is in <TT
CLASS="FILENAME"
->/usr/share/doc/privoxy-3.0.1</TT
+>/usr/share/doc/privoxy-3.0.2</TT
>
and the Log directory is in <TT
CLASS="FILENAME"
><TD
><PRE
CLASS="SCREEN"
-> tar xzvf privoxy-3.0.1-src* [.tgz or .tar.gz]
- cd privoxy-3.0.1</PRE
+> tar xzvf privoxy-3.0.2-src* [.tgz or .tar.gz]
+ cd privoxy-3.0.2</PRE
></TD
></TR
></TABLE
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="Privoxy 3.0.1 User Manual"
+TITLE="Privoxy 3.0.2 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
-TITLE="Privoxy 3.0.1 User Manual"
+TITLE="Privoxy 3.0.2 User Manual"
HREF="index.html"><LINK
REL="NEXT"
TITLE="Installation"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 3.0.1 User Manual</TH
+>Privoxy 3.0.2 User Manual</TH
></TR
><TR
><TD
<SPAN
CLASS="APPLICATION"
>Privoxy</SPAN
->, v.3.0.1.</P
+>, v.3.0.2.</P
><DIV
CLASS="SECT2"
><H2
WIDTH="33%"
ALIGN="left"
VALIGN="top"
->Privoxy 3.0.1 User Manual</TD
+>Privoxy 3.0.2 User Manual</TD
><TD
WIDTH="34%"
ALIGN="center"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="Privoxy 3.0.1 User Manual"
+TITLE="Privoxy 3.0.2 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Note to Upgraders"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 3.0.1 User Manual</TH
+>Privoxy 3.0.2 User Manual</TH
></TR
><TR
><TD
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="Privoxy 3.0.1 User Manual"
+TITLE="Privoxy 3.0.2 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Privoxy Copyright, License and History"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 3.0.1 User Manual</TH
+>Privoxy 3.0.2 User Manual</TH
></TR
><TR
><TD
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="Privoxy 3.0.1 User Manual"
+TITLE="Privoxy 3.0.2 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Quickstart to Using Privoxy"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 3.0.1 User Manual</TH
+>Privoxy 3.0.2 User Manual</TH
></TR
><TR
><TD
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="Privoxy 3.0.1 User Manual"
+TITLE="Privoxy 3.0.2 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="The Filter File"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 3.0.1 User Manual</TH
+>Privoxy 3.0.2 User Manual</TH
></TR
><TR
><TD
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
-TITLE="Privoxy 3.0.1 User Manual"
+TITLE="Privoxy 3.0.2 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Installation"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 3.0.1 User Manual</TH
+>Privoxy 3.0.2 User Manual</TH
></TR
><TR
><TD
projects / privoxy.git / commitdiff