<[EMAIL PROTECTED]> writes:
> This information is most helpful in understanding what is going on.
> That would be the logical thing to think that the during the perlhandler
> phase the content() gets sucked up and isn't available for
[...]
> This is what I have below, the problem I'm trying to
t;0, output=>'text',
error=>"Paramterts: >^..^< content: $content ",
logfile=>'/var/apache_logfile'
});
return OK;
}
-Original Message-
From: Tom Schindl [mailto:[EMAIL PRO
Hi,
I'm not sure whether I'm right or wrong. Your problem is that the
logging phase is coming after the PerlHandler-phase and that $r->content
from the PerlHandler-phase has already consumed the posted data.
To come across this problem you could use Apache::Request which works as
a singleton a
I don't know if this is possible or not, but I took parts of DBILogger and wanted to
extend what I could
do with it. What I would like to do is for a given request to a cgi program (or
mason) if the script causes
an internal error (which should not happen in production, but does) I would like to
