From: Bill Stoddard Date: Wed, 27 Mar 2002 15:30:41 +0000 (+0000) Subject: This might be helpful to folks readong code and reading this document to understand X-Git-Tag: 2.0.34~108 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=469412fd8650cf59d8e5d03961fd58a95bd16505;p=apache This might be helpful to folks readong code and reading this document to understand how their filter should work. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@94222 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/developer/filters.html b/docs/manual/developer/filters.html index b8ac610025..4257d8c1bd 100644 --- a/docs/manual/developer/filters.html +++ b/docs/manual/developer/filters.html @@ -23,18 +23,19 @@ There are three basic filter types (each of these is actually broken down into two categories, but that comes later). CONNECTION: Filters of this type are valid for the lifetime of this - connection. + connection. (AP_FTYPE_CONNECTION, AP_FTYPE_NETWORK) PROTOCOL: Filters of this type are valid for the lifetime of this request from the point of view of the client, this means that the request is valid from the time that the request is sent until the time that the response is received. + (AP_FTYPE_PROTOCOL, AP_FTYPE_TRANSCODE) RESOURCE: Filters of this type are valid for the time that this content is used to satisfy a request. For simple requests, this is identical to PROTOCOL, but internal redirects and sub-requests can change the content without ending - the request. + the request. (AP_FTYPE_RESOURCE, AP_FTYPE_CONTENT_SET) It is important to make the distinction between a protocol and a resource filter. A resource filter is tied to a specific resource, it