Return-Path: Delivered-To: apmail-apache-cvs-archive@apache.org Received: (qmail 56429 invoked by uid 500); 10 Feb 2001 04:04:13 -0000 Mailing-List: contact apache-cvs-help@apache.org; run by ezmlm Precedence: bulk Reply-To: new-httpd@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list apache-cvs@apache.org Received: (qmail 56418 invoked by uid 500); 10 Feb 2001 04:04:12 -0000 Delivered-To: apmail-httpd-2.0-cvs@apache.org Date: 10 Feb 2001 04:04:12 -0000 Message-ID: <20010210040412.56414.qmail@apache.org> From: slive@apache.org To: httpd-2.0-cvs@apache.org Subject: cvs commit: httpd-2.0/docs/manual/mod core.html directives.html mod_ext_filter.html slive 01/02/09 20:04:12 Modified: docs/manual index.html docs/manual/mod core.html directives.html mod_ext_filter.html Added: docs/manual filter.html Log: Add some VERY basic filter documentation. See followup discussion on apache-docs. Revision Changes Path 1.19 +2 -0 httpd-2.0/docs/manual/index.html Index: index.html =================================================================== RCS file: /home/cvs/httpd-2.0/docs/manual/index.html,v retrieving revision 1.18 retrieving revision 1.19 diff -u -d -b -u -r1.18 -r1.19 --- index.html 2001/01/23 23:24:06 1.18 +++ index.html 2001/02/10 04:04:11 1.19 @@ -133,6 +133,8 @@ Handlers +Filters + Content negotiation Environment Variables 1.1 httpd-2.0/docs/manual/filter.html Index: filter.html =================================================================== Filters - Apache HTTPD

Filters

Related Modules

mod_ext_filter
mod_include
 Related Directives

ExtFilterDefine
ExtFilterOptions
SetInputFilter
SetOutputFilter

A filter is a process which is applied to data that is sent or received by the server. Data sent by clients to the server is processed by input filters while data sent by the server to the client is processed by output filters. Multiple filters can be applied to the data, and the order of the filters can be explicitly specified. In addition, since filters apply to all content, they allow for flexible manipulation of data such as processing the output of CGI scripts for Server Side Includes.

The set of filters which apply to data can be manipulated with the SetInputFilter and SetOutputFilter directives.

The only filter currently included with the Apache distribution is the INCLUDE filter which is provided by mod_include to process output for Server Side Includes. There is also an experimental module called mod_ext_filter which allows for external programs to be defined as filters.

1.186 +69 -0 httpd-2.0/docs/manual/mod/core.html Index: core.html =================================================================== RCS file: /home/cvs/httpd-2.0/docs/manual/mod/core.html,v retrieving revision 1.185 retrieving revision 1.186 diff -u -d -b -u -r1.185 -r1.186 --- core.html 2001/01/28 00:19:28 1.185 +++ core.html 2001/02/10 04:04:12 1.186 @@ -73,6 +73,8 @@
  • ServerSignature
  • ServerTokens
  • ServerType +
  • SetInputFilter +
  • SetOutputFilter
  • TimeOut
  • UseCanonicalName
  • <VirtualHost> @@ -2479,6 +2481,73 @@ standalone will probably be your only option.

    +

    SetInputFilter directive

    +

    Syntax: SetInputFilter filter +[filter] ...
    +Default: none
    +Context: directory
    +Status: core

    + +

    The SetInputFilter directive sets the filters +which will process client requests when they are received by the +server.

    + +

    The order of the arguments determines the order in which the +filters will process the content.

    + +

    See also the Filters documentation.

    + + +

    +

    SetOutputFilter directive

    +

    Syntax: SetOutputFilter filter +[filter] ...
    +Default: none
    +Context: directory
    +Status: core

    + +

    The SetOutputFilter directive sets the filters which +will process responses from the server before they are sent to the +client. For example, the following configuration will process +all files in the /www/data/ directory for +server-side includes.

    + +
    +<Directory /www/data/>
    +  SetOutputFilter INCLUDES
    +</Directory> +
    + +

    The order of the arguments determines the order in which the +filters will process the content.

    + +

    See also the Filters documentation.

    + +

    TimeOut directive

    SetEnvIf
  • SetEnvIfNoCase
  • SetHandler +
  • SetInputFilter +
  • SetOutputFilter
  • StartServers
  • StartThreads
  • ThreadsPerChild 1.4 +4 -4 httpd-2.0/docs/manual/mod/mod_ext_filter.html Index: mod_ext_filter.html =================================================================== RCS file: /home/cvs/httpd-2.0/docs/manual/mod/mod_ext_filter.html,v retrieving revision 1.3 retrieving revision 1.4 diff -u -d -b -u -r1.3 -r1.4 --- mod_ext_filter.html 2000/12/09 19:50:02 1.3 +++ mod_ext_filter.html 2001/02/10 04:04:12 1.4 @@ -86,7 +86,7 @@ <Directory "/export/home/trawick/apacheinst/htdocs/c"> # core directive to cause the new filter to be run on output - AddOutputFilter c-to-heml + SetOutputFilter c-to-heml # mod_mime directive to set the type of .c files to text/c AddType text/c .c @@ -108,7 +108,7 @@ <Location /gzipped> # core directive to cause the gzip filter to be run on output - AddOutputFilter gzip + SetOutputFilter gzip # mod_header directive to add "Content-Encoding: gzip" header field Header set Content-Encoding gzip @@ -127,7 +127,7 @@ # core directive to cause the slowdown filter to be run several times on # output - AddOutputFilter slowdown slowdown slowdown + SetOutputFilter slowdown slowdown slowdown </Location> @@ -173,7 +173,7 @@

    filtername specifies the name of the filter being defined. This name - can then be used in AddOutputFilter directives. It must be unique among all + can then be used in SetOutputFilter directives. It must be unique among all registered filters. At the present time, no error is reported by the register-filter API, so a problem with duplicate names isn't reported to the user.