stas 2003/05/27 21:14:28
Modified: src/docs/2.0/user/handlers filters.pod
Log:
various fixes
Revision Changes Path
1.30 +12 -8 modperl-docs/src/docs/2.0/user/handlers/filters.pod
Index: filters.pod
===================================================================
RCS file: /home/cvs/modperl-docs/src/docs/2.0/user/handlers/filters.pod,v
retrieving revision 1.29
retrieving revision 1.30
diff -u -r1.29 -r1.30
--- filters.pod 27 May 2003 02:42:44 -0000 1.29
+++ filters.pod 28 May 2003 04:14:28 -0000 1.30
@@ -110,6 +110,8 @@
use warnings;
use Apache::Filter ();
+ use Apache::RequestRec();
+ use APR::Table;
use Apache::Const -compile => qw(OK);
@@ -136,7 +138,7 @@
filter to all requests that get mapped to files with an I<".html">
extension:
- <Files ~ "\.html">
+ <Files ~ "\.html$">
PerlOutputFilterHandler MyApache::FilterObfuscate
</Files>
@@ -162,11 +164,13 @@
send it out to the client.
As we are going to explain in great detail in the next sections, the
-same filter may be called many times during a single requests, every
-time receiving a chunk of data. For example if the HTML page is 64k
-long, a filter could be invoked 8 times, each time receiving 8k of
-data. The while loop that we just saw is going to read each of these
-8k in 8 calls, since it requests 1k on every read() call.
+same filter may be called many times during a single request, every
+time receiving a chunk of data. For example if the POSTed request data
+is 64k long, an input filter could be invoked 8 times, each time
+receiving 8k of data. The same may happen during response phase, where
+an upstream filter may split 64k output in 8 8k chunks. The while loop
+that we just saw is going to read each of these 8k in 8 calls, since
+it requests 1k on every C<read()> call.
Since it's enough to unset the C<Content-Length> header when the
filter is called the first time, we need to have some flag telling us
@@ -272,8 +276,8 @@
Unlike other Apache handlers, filter handlers may get invoked more
than once during the same request. Filters get invoked as many times
-as the number of bucket brigades sent from the upstream filter or
-content provider.
+as the number of bucket brigades sent from an upstream filter or
+a content provider.
For example if a content generation handler sends a string, and then
forces a flush, following by more data:
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
