From b2c9c43588c5ff98570ef510e9b0c7dd44385226 Mon Sep 17 00:00:00 2001 From: Joshua Slive Date: Thu, 21 Nov 2002 21:02:12 +0000 Subject: [PATCH] When I changed the status to extension, I should have also removed this warning paragraph. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@97587 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/mod/mod_ext_filter.xml | 23 +++++++++-------------- 1 file changed, 9 insertions(+), 14 deletions(-) diff --git a/docs/manual/mod/mod_ext_filter.xml b/docs/manual/mod/mod_ext_filter.xml index 351432db3b..0712d2f4d2 100644 --- a/docs/manual/mod/mod_ext_filter.xml +++ b/docs/manual/mod/mod_ext_filter.xml @@ -11,20 +11,14 @@ delivery to the client ext_filter_module -

This is an experimental module and should - be used with care. Test your mod_ext_filter - configuration carefully to ensure that it performs the desired - function. You may wish to review - this information for background on the Apache filtering - model.

-

mod_ext_filter presents a simple and familiar - programming model for filters. With this module, a program - which reads from stdin and writes to stdout (i.e., a Unix-style - filter command) can be a filter for Apache. This filtering - mechanism is much slower than using a filter which is specially - written for the Apache API and runs inside of the Apache server - process, but it does have the following benefits:

+ programming model for filters. With + this module, a program which reads from stdin and writes to stdout + (i.e., a Unix-style filter command) can be a filter for + Apache. This filtering mechanism is much slower than using a + filter which is specially written for the Apache API and runs + inside of the Apache server process, but it does have the + following benefits:

-The filter documentation +Filters
Examples -- 2.40.0