+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>The Filter File</TITLE
><META
NAME="GENERATOR"
-CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
-"><LINK
+CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
REL="HOME"
-TITLE="Privoxy 3.1.1 User Manual"
+TITLE="Privoxy 3.0.3 User Manual"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Actions Files"
><TH
COLSPAN="3"
ALIGN="center"
->Privoxy 3.1.1 User Manual</TH
+>Privoxy 3.0.3 User Manual</TH
></TR
><TR
><TD
><H1
CLASS="SECT1"
><A
-NAME="FILTER-FILE">9. The Filter File</H1
+NAME="FILTER-FILE"
+>9. The Filter File</A
+></H1
><P
> All text substitutions that can be invoked through the
- <TT
+ <VAR
CLASS="LITERAL"
><A
HREF="actions-file.html#FILTER"
>filter</A
-></TT
+></VAR
> action
must first be defined in the filter file, which is typically
called <TT
CLASS="FILENAME"
>default.filter</TT
> and which can be
- selected through the <TT
+ selected through the <VAR
CLASS="LITERAL"
> <A
HREF="config.html#FILTERFILE"
>filterfile</A
-></TT
+></VAR
> config
option.</P
><P
width and height attributes (standard banner sizes or web-bugs),
or just to have fun. The possibilities are endless.</P
><P
-> Filtering works on any text-based document type, including plain
- text, HTML, JavaScript, CSS etc. (all <TT
+> Filtering works on any text-based document type, including
+ HTML, JavaScript, CSS etc. (all <VAR
CLASS="LITERAL"
->text/*</TT
+>text/*</VAR
>
- MIME types). Substitutions are made at the source level, so if
- you want to <SPAN
+ MIME types, <SPAN
+CLASS="emphasis"
+><I
+CLASS="EMPHASIS"
+>except</I
+></SPAN
+> <VAR
+CLASS="LITERAL"
+>text/plain</VAR
+>).
+ Substitutions are made at the source level, so if you want to <SPAN
CLASS="QUOTE"
->"roll your own"</SPAN
-> filters, you should be
- familiar with HTML syntax.</P
+>"roll
+ your own"</SPAN
+> filters, you should be familiar with HTML syntax.</P
><P
> Just like the <A
HREF="actions-file.html"
CLASS="EMPHASIS"
>keyword</I
></SPAN
-> <TT
+> <VAR
CLASS="LITERAL"
->FILTER:</TT
+>FILTER:</VAR
>, followed by
the filter's <SPAN
CLASS="emphasis"
user interface</A
>.</P
><P
-> Once a filter called <TT
+> Once a filter called <VAR
CLASS="REPLACEABLE"
-><I
->name</I
-></TT
+>name</VAR
> has been defined
in the filter file, it can be invoked by using an action of the form
- +<TT
+ +<VAR
CLASS="LITERAL"
><A
HREF="actions-file.html#FILTER"
>filter</A
->{<TT
+>{<VAR
CLASS="REPLACEABLE"
-><I
->name</I
-></TT
->}</TT
+>name</VAR
+>}</VAR
>
in any <A
HREF="actions-file.html"
TARGET="_top"
>Perl</A
>'s
- <TT
+ <VAR
CLASS="LITERAL"
->s///</TT
+>s///</VAR
> operator. If you are familiar with Perl, you
will find this to be quite intuitive, and may want to look at the
<A
>PCRS man page</A
>
for the subtle differences to Perl behaviour. Most notably, the non-standard
- option letter <TT
+ option letter <VAR
CLASS="LITERAL"
->U</TT
+>U</VAR
> is supported, which turns the default
to ungreedy matching.</P
><P
HREF="http://perldoc.com/perl5.6.1/pod/perlop.html#s-PATTERN-REPLACEMENT-egimosx"
TARGET="_top"
>the
- <TT
+ <VAR
CLASS="LITERAL"
->s///</TT
+>s///</VAR
> operator's syntax</A
> and <A
HREF="http://perldoc.com/perl5.6.1/pod/perlre.html"
><H2
CLASS="SECT2"
><A
-NAME="AEN3018">9.1. Filter File Tutorial</H2
+NAME="AEN3212"
+>9.1. Filter File Tutorial</A
+></H2
><P
> Now, let's complete our <SPAN
CLASS="QUOTE"
CLASS="QUOTE"
>"foo"</SPAN
> on each page. For global substitution,
- we'll need to add the <TT
+ we'll need to add the <VAR
CLASS="LITERAL"
->g</TT
+>g</VAR
> option:</P
><P
> <TABLE
></P
><P
> Following the header line and a comment, you see the job. Note that it uses
- <TT
+ <VAR
CLASS="LITERAL"
->|</TT
-> as the delimiter instead of <TT
+>|</VAR
+> as the delimiter instead of <VAR
CLASS="LITERAL"
->/</TT
+>/</VAR
>, because
the pattern contains a forward slash, which would otherwise have to be escaped
- by a backslash (<TT
+ by a backslash (<VAR
CLASS="LITERAL"
->\</TT
+>\</VAR
>).</P
><P
-> Now, let's examine the pattern: it starts with the text <TT
+> Now, let's examine the pattern: it starts with the text <VAR
CLASS="LITERAL"
-><script.*</TT
+><script.*</VAR
>
- enclosed in parentheses. Since the dot matches any character, and <TT
+ enclosed in parentheses. Since the dot matches any character, and <VAR
CLASS="LITERAL"
->*</TT
+>*</VAR
>
means: <SPAN
CLASS="QUOTE"
> text, i.e.
it matches the whole page, from the start of the first <script> tag.</P
><P
-> That's more than we want, but the pattern continues: <TT
+> That's more than we want, but the pattern continues: <VAR
CLASS="LITERAL"
->document\.referrer</TT
+>document\.referrer</VAR
>
matches only the exact string <SPAN
CLASS="QUOTE"
in the page (and appear in that order).</P
><P
> But there's still more pattern to go. The next element, again enclosed in parentheses,
- is <TT
+ is <VAR
CLASS="LITERAL"
->.*</script></TT
->. You already know what <TT
+>.*</script></VAR
+>. You already know what <VAR
CLASS="LITERAL"
->.*</TT
+>.*</VAR
>
means, so the whole pattern translates to: Match from the start of the first <script>
tag in a page to the end of the last <script> tag, provided that the text
><P
> This is still not the whole story, since we have ignored the options and the parentheses:
The portions of the page matched by sub-patterns that are enclosed in parentheses, will be
- remembered and be available through the variables <TT
+ remembered and be available through the variables <VAR
CLASS="LITERAL"
->$1, $2, ...</TT
+>$1, $2, ...</VAR
> in
- the substitute. The <TT
+ the substitute. The <VAR
CLASS="LITERAL"
->U</TT
+>U</VAR
> option switches to ungreedy matching, which means
- that the first <TT
+ that the first <VAR
CLASS="LITERAL"
->.*</TT
+>.*</VAR
> in the pattern will only <SPAN
CLASS="QUOTE"
>"eat up"</SPAN
of <SPAN
CLASS="QUOTE"
>"document.referrer"</SPAN
->, and that the second <TT
+>, and that the second <VAR
CLASS="LITERAL"
->.*</TT
+>.*</VAR
> will
only span the text up to the <SPAN
CLASS="emphasis"
CLASS="QUOTE"
>"</script>"</SPAN
>
- tag. Furthermore, the <TT
+ tag. Furthermore, the <VAR
CLASS="LITERAL"
->s</TT
+>s</VAR
> option says that the match may span
- multiple lines in the page, and the <TT
+ multiple lines in the page, and the <VAR
CLASS="LITERAL"
->g</TT
+>g</VAR
> option again means that the
substitution is global.</P
><P
<SPAN
CLASS="QUOTE"
>"document.referrer"</SPAN
-> as <TT
+> as <VAR
CLASS="LITERAL"
->$1</TT
+>$1</VAR
>, and the part following
- that string, up to and including the closing tag, as <TT
+ that string, up to and including the closing tag, as <VAR
CLASS="LITERAL"
->$2</TT
+>$2</VAR
>.</P
><P
> Now the pattern is deciphered, but wasn't this about substituting things? So
- lets look at the substitute: <TT
+ lets look at the substitute: <VAR
CLASS="LITERAL"
->$1"Not Your Business!"$2</TT
+>$1"Not Your Business!"$2</VAR
> is
- easy to read: The text remembered as <TT
+ easy to read: The text remembered as <VAR
CLASS="LITERAL"
->$1</TT
+>$1</VAR
>, followed by
- <TT
+ <VAR
CLASS="LITERAL"
->"Not Your Business!"</TT
+>"Not Your Business!"</VAR
> (<SPAN
CLASS="emphasis"
><I
>including</I
></SPAN
>
- the quotation marks!), followed by the text remembered as <TT
+ the quotation marks!), followed by the text remembered as <VAR
CLASS="LITERAL"
->$2</TT
+>$2</VAR
>.
This produces an exact copy of the original string, with the middle part
(the <SPAN
CLASS="QUOTE"
>"document.referrer"</SPAN
->) replaced by <TT
+>) replaced by <VAR
CLASS="LITERAL"
>"Not Your
- Business!"</TT
+ Business!"</VAR
>.</P
><P
> The whole job now reads: Replace <SPAN
CLASS="QUOTE"
>"document.referrer"</SPAN
> by
- <TT
+ <VAR
CLASS="LITERAL"
->"Not Your Business!"</TT
+>"Not Your Business!"</VAR
> wherever it appears inside a
<script> tag. Note that this job won't break JavaScript syntax,
since both the original and the replacement are syntactically valid
></TABLE
></P
><P
-> <TT
+> <VAR
CLASS="LITERAL"
->\s</TT
+>\s</VAR
> stands for whitespace characters (space, tab, newline,
- carriage return, form feed), so that <TT
+ carriage return, form feed), so that <VAR
CLASS="LITERAL"
->\s*</TT
+>\s*</VAR
> means: <SPAN
CLASS="QUOTE"
>"zero
or more whitespace"</SPAN
->. The <TT
+>. The <VAR
CLASS="LITERAL"
->?</TT
-> in <TT
+>?</VAR
+> in <VAR
CLASS="LITERAL"
->.*?</TT
+>.*?</VAR
>
- makes this matching of arbitrary text ungreedy. (Note that the <TT
+ makes this matching of arbitrary text ungreedy. (Note that the <VAR
CLASS="LITERAL"
->U</TT
+>U</VAR
>
- option is not set). The <TT
+ option is not set). The <VAR
CLASS="LITERAL"
->['"]</TT
+>['"]</VAR
> construct means: <SPAN
CLASS="QUOTE"
>"a single
>or</I
></SPAN
> a double quote"</SPAN
->. Finally, <TT
+>. Finally, <VAR
CLASS="LITERAL"
->\1</TT
+>\1</VAR
> is
- a backreference to the first parenthesis just like <TT
+ a backreference to the first parenthesis just like <VAR
CLASS="LITERAL"
->$1</TT
+>$1</VAR
> above,
with the difference that in the <SPAN
CLASS="emphasis"
<SPAN
CLASS="QUOTE"
>"<body>"</SPAN
-> tags with the dummy word <TT
+> tags with the dummy word <VAR
CLASS="LITERAL"
->never</TT
+>never</VAR
>.
- Note that the <TT
+ Note that the <VAR
CLASS="LITERAL"
->i</TT
+>i</VAR
> option makes the pattern matching
case-insensitive. Also note that ungreedy matching alone doesn't always guarantee
- a minimal match: In the first parenthesis, we had to use <TT
+ a minimal match: In the first parenthesis, we had to use <VAR
CLASS="LITERAL"
->[^>]*</TT
+>[^>]*</VAR
>
- instead of <TT
+ instead of <VAR
CLASS="LITERAL"
->.*</TT
+>.*</VAR
> to prevent the match from exceeding the
<body> tag if it doesn't contain <SPAN
CLASS="QUOTE"
></TABLE
></P
><P
-> Note the <TT
+> Note the <VAR
CLASS="LITERAL"
->(?!\.com)</TT
+>(?!\.com)</VAR
> part (a so-called negative lookahead)
in the job's pattern, which means: Don't match, if the string
<SPAN
></TABLE
></P
><P
-> The <TT
+> The <VAR
CLASS="LITERAL"
->x</TT
+>x</VAR
> option in this job turns on extended syntax, and allows for
e.g. the liberal use of (non-interpreted!) whitespace for nicer formatting. </P
><P
> You get the idea?</P
></DIV
+><DIV
+CLASS="SECT2"
+><H2
+CLASS="SECT2"
+><A
+NAME="PREDEFINED-FILTERS"
+>9.2. The Pre-defined Filters</A
+></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 <VAR
+CLASS="LITERAL"
+><A
+HREF="actions-file.html#HIDE-REFERRER"
+>hide-referrer</A
+></VAR
+> 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 <VAR
+CLASS="LITERAL"
+>BLINK</VAR
+> and <VAR
+CLASS="LITERAL"
+>MARQUEE</VAR
+> 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
+ <VAR
+CLASS="LITERAL"
+><A
+HREF="actions-file.html#CRUNCH-INCOMING-COOKIES"
+>crunch-incoming-cookies</A
+></VAR
+>
+ and <VAR
+CLASS="LITERAL"
+><A
+HREF="actions-file.html#CRUNCH-OUTGOING-COOKIES"
+>crunch-outgoing-cookies</A
+></VAR
+>
+ 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
+ <VAR
+CLASS="LITERAL"
+>banners-by-size</VAR
+> and <VAR
+CLASS="LITERAL"
+>banners-by-link</VAR
+>
+ (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 not necessary when using MS products, and will cause corruption of
+ all documents that use 8-bit character sets other than Latin-1. It's mostly
+ worthwhile for Europeans on non-MS platforms, if wierd garbage characters
+ sometimes appear on some pages.
+ </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"
projects / privoxy.git / blobdiff