X-Git-Url: http://www.privoxy.org/gitweb/?a=blobdiff_plain;f=doc%2Fwebserver%2Fuser-manual%2Ffilter-file.html;h=a881b3eddbf8a69ed00bcadfe3e81f0bdd99c17b;hb=4a2435132af71a3db7f25939c9706deec2651fe5;hp=42639f7615f5fa5a220f1a62ceafda945f58ceec;hpb=46471693916537291afcf7eadd40e6b93277bfaa;p=privoxy.git diff --git a/doc/webserver/user-manual/filter-file.html b/doc/webserver/user-manual/filter-file.html index 42639f76..a881b3ed 100644 --- a/doc/webserver/user-manual/filter-file.html +++ b/doc/webserver/user-manual/filter-file.html @@ -4,7 +4,7 @@ Filter Files - + @@ -15,7 +15,7 @@
- + @@ -29,12 +29,13 @@

9. Filter Files

On-the-fly text substitutions need to be defined in a "filter file". Once defined, they can then be invoked as an "action".

-

Privoxy supports three different pcrs-based filter actions: Privoxy supports four different pcrs-based filter actions: filter to rewrite the content that is send to the client, client-header-filter to rewrite - headers that are send by the client, and server-header-filter to rewrite headers that are send by the - server.

+ server, and client-body-filter to + rewrite client request body.

Privoxy also supports two tagger actions: client-header-tagger and server-header-tagger. Taggers and filters use the same syntax in @@ -59,9 +60,9 @@

Just like the actions files, the filter file is organized in sections, which are called filters here. Each filter consists of a heading line, that starts with one of the keywords FILTER:, CLIENT-HEADER-FILTER: or SERVER-HEADER-FILTER: followed by the filter's name, and a short (one line) FILTER:, CLIENT-HEADER-FILTER:, SERVER-HEADER-FILTER: or CLIENT-BODY-FILTER: followed by the filter's + name, and a short (one line) description of what it does. Below that line come the jobs, i.e. lines that define the actual text substitutions. By convention, the name of a filter should describe what the filter eliminates. The

Privoxy 3.0.29 User ManualPrivoxy 3.0.30 User Manual
Prev