You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by st...@apache.org on 2002/03/27 16:30:41 UTC
cvs commit: httpd-2.0/docs/manual/developer filters.html
stoddard 02/03/27 07:30:41
Modified: docs/manual/developer filters.html
Log:
This might be helpful to folks readong code and reading this document to understand
how their filter should work.
Revision Changes Path
1.2 +3 -2 httpd-2.0/docs/manual/developer/filters.html
Index: filters.html
===================================================================
RCS file: /home/cvs/httpd-2.0/docs/manual/developer/filters.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- filters.html 11 Mar 2002 12:03:43 -0000 1.1
+++ filters.html 27 Mar 2002 15:30:41 -0000 1.2
@@ -23,18 +23,19 @@
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