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.
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 keywordsFILTER:, 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
@@ -96,7 +97,7 @@
'<' should be save, while '?' will sooner or later cause conflicts with $url.
The non-standard option letter T (trivial) prevents parsing for backreferences in the
substitute. Use it if you want to include text like '$&' in your substitute without quoting.