You are viewing a plain text version of this content. The canonical link for it is here.
Posted to modperl-cvs@perl.apache.org by st...@apache.org on 2003/03/06 05:32:06 UTC
cvs commit: modperl-docs/src/docs/2.0/user/handlers http.pod http_cycle.dia http_cycle.gif http_cycle.png server.pod
stas 2003/03/05 20:32:06
Modified: src/docs/2.0/user/handlers http.pod http_cycle.dia
http_cycle.gif http_cycle.png server.pod
Log:
note that if any of the phases aborts the HTTP cycle Apache skips to the
logging phase (update the diagram as well)
Revision Changes Path
1.17 +3 -1 modperl-docs/src/docs/2.0/user/handlers/http.pod
Index: http.pod
===================================================================
RCS file: /home/cvs/modperl-docs/src/docs/2.0/user/handlers/http.pod,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- http.pod 19 Feb 2003 22:28:28 -0000 1.16
+++ http.pod 6 Mar 2003 04:32:06 -0000 1.17
@@ -54,7 +54,9 @@
=back
It's possible that the cycle will not be completed if any of the
-phases terminates it, usually when an error happens.
+phases terminates it, usually when an error happens. In that case
+Apache skips to the logging phase (mod_perl executes all registered
+C<PerlLogHandler> handlers) and finally the cleanup phase happens.
Notice that when the response handler is reading the input data it can
be filtered through request input filters, which are preceded by
1.2 +13 -11 modperl-docs/src/docs/2.0/user/handlers/http_cycle.dia
<<Binary file>>
1.2 +109 -71 modperl-docs/src/docs/2.0/user/handlers/http_cycle.gif
<<Binary file>>
1.2 +98 -65 modperl-docs/src/docs/2.0/user/handlers/http_cycle.png
<<Binary file>>
1.6 +3 -2 modperl-docs/src/docs/2.0/user/handlers/server.pod
Index: server.pod
===================================================================
RCS file: /home/cvs/modperl-docs/src/docs/2.0/user/handlers/server.pod,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- server.pod 18 Feb 2003 05:15:36 -0000 1.5
+++ server.pod 6 Mar 2003 04:32:06 -0000 1.6
@@ -93,7 +93,7 @@
say("process $$ now exits");
return Apache::OK;
}
-
+
sub say {
my($caller) = (caller(1))[3] =~ /([^:]+)$/;
if (defined $log_fh) {
@@ -172,7 +172,8 @@
The I<open_logs> phase happens just before the I<post_config> phase.
Handlers registered by C<PerlOpenLogsHandler> are usually used for
-opening module-specific log files.
+opening module-specific log files (e.g., httpd core and mod_ssl open
+their log files during this phase).
At this stage the C<STDERR> stream is not yet redirected to
I<error_log>, and therefore any messages to that stream will be