<[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 solve is getting > the params (text field etc.) that were passed to a cgi script. This > Apache module is being called in my httpd.conf by "PerlLogHandler > Apache::ErrorLogger". Unfortunately there's no good solution for your problem in mp1-land, because the POST data winds up wherever the content handler (or some earlier handler) puts it. Unless that's using Apache::Request as well, I'm afraid there's no way to get at the POST data with libapreq. However, because of the input filtering design built into apache2, you _can_ do what you want with mp2/apreq2, no matter what the content handler is (it doesn't even need to be perl-related). All you'd need to do is make sure mod_apreq's filter gets inserted before the content-handler takes over, and then Apache::Request will provide full access to the parsed POST data. -- Joe Schaefer -- Reporting bugs: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html
