Return-Path: Delivered-To: apmail-httpd-cvs-archive@www.apache.org Received: (qmail 31466 invoked from network); 17 Nov 2005 18:24:34 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 17 Nov 2005 18:24:34 -0000 Received: (qmail 11056 invoked by uid 500); 17 Nov 2005 18:24:33 -0000 Delivered-To: apmail-httpd-cvs-archive@httpd.apache.org Received: (qmail 11010 invoked by uid 500); 17 Nov 2005 18:24:32 -0000 Mailing-List: contact cvs-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list cvs@httpd.apache.org Received: (qmail 10999 invoked by uid 99); 17 Nov 2005 18:24:32 -0000 X-ASF-Spam-Status: No, hits=-9.4 required=10.0 tests=ALL_TRUSTED,NO_REAL_NAME X-Spam-Check-By: apache.org Received: from [209.237.227.194] (HELO minotaur.apache.org) (209.237.227.194) by apache.org (qpsmtpd/0.29) with SMTP; Thu, 17 Nov 2005 10:24:32 -0800 Received: (qmail 31307 invoked by uid 65534); 17 Nov 2005 18:24:12 -0000 Message-ID: <20051117182412.31304.qmail@minotaur.apache.org> Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r345298 - /httpd/httpd/trunk/docs/manual/filter.xml Date: Thu, 17 Nov 2005 18:24:11 -0000 To: cvs@httpd.apache.org From: slive@apache.org X-Mailer: svnmailer-1.0.5 X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Author: slive Date: Thu Nov 17 10:24:09 2005 New Revision: 345298 URL: http://svn.apache.org/viewcvs?rev=345298&view=rev Log: A few markup and spelling fixes. Modified: httpd/httpd/trunk/docs/manual/filter.xml Modified: httpd/httpd/trunk/docs/manual/filter.xml URL: http://svn.apache.org/viewcvs/httpd/httpd/trunk/docs/manual/filter.xml?rev=345298&r1=345297&r2=345298&view=diff ============================================================================== --- httpd/httpd/trunk/docs/manual/filter.xml (original) +++ httpd/httpd/trunk/docs/manual/filter.xml Thu Nov 17 10:24:09 2005 @@ -67,17 +67,20 @@

Some examples of filtering in the standard Apache distribution are:

    -
  • mod_includes, implements server-side includes.
  • -
  • mod_ssl, implements SSL encryption (https).
  • -
  • mod_deflate, implements compression/decompression on the fly.
  • -
  • mod_charset_lite, transcodes between different character sets.
  • -
  • mod_ext_filter, runs an external program as a filter.
  • +
  • mod_include, implements server-side includes.
  • +
  • mod_ssl, implements SSL encryption (https).
  • +
  • mod_deflate, implements compression/decompression on the fly.
  • +
  • mod_charset_lite, transcodes between different character sets.
  • +
  • mod_ext_filter, runs an external program as a filter.
-

Apache also uses a number of filters internally, to perform +

Apache also uses a number of filters internally to perform functions like chunking and byte-range handling.

-

A wider range of applications are implemented by third-party -filter modules. A few of these are:

+

A wider range of applications are implemented by third-party filter +modules available from modules.apache.org and +elsewhere. A few of these are:

+
  • HTML and XML processing and rewriting
  • XSLT transforms and XIncludes
  • @@ -88,6 +91,7 @@
  • Text search-and-replace editing
+
Smart Filtering

@@ -108,7 +112,7 @@

  • an HTML processing filter will only run if the content is text/html or application/xhtml+xml
  • A compression filter will only run if the input is a -compressable type and not already compressed
  • +compressible type and not already compressed
  • A charset conversion filter will be inserted if a text document is not already in the desired charset
  • @@ -117,11 +121,11 @@
    Using Filters

    There are two ways to use filtering: Simple and Dynamic. -In general, you should use one or the other: mixing them can +In general, you should use one or the other; mixing them can have unexpected consequences (although simple Input filtering -can be mixed freely with either simple or dynamic Output filtering!

    +can be mixed freely with either simple or dynamic Output filtering).

    The Simple Way is the only way to configure input filters, and is -suficient for output filters where you need a static filter chain. +sufficient for output filters where you need a static filter chain. Relevant directives are SetInputFilter, SetOutputFilter, @@ -134,10 +138,13 @@ of output filters, as discussed in the mod_filter page. Relevant directives are FilterChain, - FilterDeclare, + FilterDeclare, and FilterProvider.

    -

    One further directive AddOutputFilterByType is still supported, -but may be problematic and is now deprecated. Use dynamic configuration -instead.

    + +

    One further directive AddOutputFilterByType is still supported, +but may be problematic and is now deprecated. Use dynamic +configuration instead.

    +