>
>-----Original Message-----
>From: Lyle Brooks
>To: Geoffrey Young
>Cc: 'mod_perl list '
>Sent: 9/19/01 5:57 PM
>Subject: RE: [OT] New Micro$oft vulnerability?
>
>This helps alot. I've been looking for a concise map of the various
>phases and what returns codes take me where. I'll probably post it on
>my wall.
:)
>> all phases up to and including content generation ought to behave
>exactly
>> the same...
>>
>> - DECLINED moves to the next handler in the phase
>> - DONE bypasses content generation, closes the connection, and goes
>directly
>> to the logging phase
>> - anything other than DONE, OK, or DECLINED terminates the phase and
>enters
>> the ErrorDocument cycle (where there may or may not be an actual
>> ErrorDocument configured)
>>
>
>A couple follow-up questions. What phases are run during the
>ErrorDocument cycle?
ErrorDocuments (either set from httpd_conf or via $r->custom_response) will
follow the same route as $r->internal_redirect. that is, the entire request
is run (unlike for a subrequest, which skips around).
>
>One motivation I have is for these virus attacks, I'd like to send out
>a 403 - Forbidden right at the beginning (say, when someone asks for
>default.ida) and then I'd like to have the option of not logging it to
>keep it from growing my logs and distorting my log reports.
>
>Is there anyway to selectively tell a request not to even log this?
>Disable the log handler for the current request, maybe?
well, you could always disable any and all PerlLogHandlers using
$r->set_handlers(PerlLogHandler => undef);
which does not affect anything on the Apache C module side (like
mod_log_config), since you can't really control these from mod_perl.
--Geoff
