Hi all,
I'm in the midst of writing a book currently, and am covering the
sections in the book on mod_perl and Apache.
In previous texts for Apache 1.3, it
would show 11 phases. In the document on
http://httpd.apache.org/docs/2.2/developer/request.html, it shows 4
primary phases, each having
Patrick Galbraith wrote:
Hi all,
I'm in the midst of writing a book currently, and am covering the
sections in the book on mod_perl and Apache.
In previous texts for Apache 1.3, it
would show 11 phases. In the document on
http://httpd.apache.org/docs/2.2/developer/request.html, it shows 4
Solutio at Gmail wrote:
Thanks, your version works like a charm...but doesn't
quite meets our needs. I apologize for being too vague
regarding passing parameters on to the filter. Basically,
we would like to somehow link the location and name of the
response dump with the request data, like
Mark Hedges wrote:
[...]
Then the connection output filter can read it from there.
Remove connection and I agree, that's much cleaner than putting it in
a header.
A similar post-request PerlCleanupHandler or PerlLogHandler
could save any info needed after the request was processed.
But
First of all, I thank you both for your expert opinion on the topic. I have
never had to fiddle with this sort of Apache customization, so I'm learning
in the process...
As for the way to communicate the file name to the filter, sure, we would
like to keep it as simple as possible and avoid
Hello all,
I'm writing about the benefits of mod_perl in my book, having taken a
CGI script and using ModPerl::Registry turning it into a mod_perl app...
so on so forth... While testing what I'm writing about, I keep seeing
segfaults in my apache log. I started worrying that I have a bug in
