On-the-fly text substitutions need to be defined in a server-header-filter - to rewrite headers that are send by the server, and
server-header-tagger. - Taggers and filters use the same syntax in the filter files, the differnce + Taggers and filters use the same syntax in the filter files, the difference is that taggers don't modify the text they are filtering, but use a rewritten version of the filtered text as tag. The tags can then be used to change the applying actions through sections with filterfile config directive. The filters - as supplied by the developers will be found in + as supplied by the developers are located in default.filter.
Command tasks for content filters are to eliminate common annoyances in +> Common tasks for content filters are to eliminate common annoyances in HTML and JavaScript, such as pop-up windows, exit consoles, crippled windows without navigation tools, the infamous <BLINK> tag etc, to suppress images with certain width and height attributes (standard banner sizes or web-bugs), or just to have fun.
Content filtering works on any text-based document type, including - HTML, JavaScript, CSS etc. (all text/* - MIME types, except Enabled content filters are applied to any content whose + "Content Type" header is recognised as a sign + of text-based content, with the exception of text/plain). - Substitutions are made at the source level, so if you want to . + Use the force-text-mode action + to also filter other content.
Substitutions are made at the source level, so if you want to "roll your own"
Now, let's complete our 9.2. The Pre-defined Filters9.2. The Pre-defined Filters The distribution