I believe this should be reflected in the documentation. Because after
reading Eagle book one gets absolutely different understanding. It
doesn't diffirentiate Perl stacked handlers and Apache handlers. From
Doug's words (and from practice :) those are slightly different in the
way how their
At least that's what I thought !
In fact now Apache lets me use more then one
PerlTransHandler, but it doesn't care
of what is the return codes are!!!
Even I return OK, it still calls
next registered handlers. Really weird!
mod_perl does care. but, mod_perl stacked handlers are not
Thanks for the answers!
I was using RedHat rpm and it was giving the problem
as it was suggested. After I built mod_perl with apache
(mod_perl 1.21, apache 1.3.9, the problem was resolved.
At least that's what I thought !
In fact now Apache lets me use more then one
PerlTransHandler, but it
Waa!!! So far nobody who answered even doubted that
it should be possible to have more then one
PerlTransHandler. The "Eagle" book also says
that it should be possible. People suggested that
either my mod_perl built with wrong flags or I messed
up return codes OK/DECLINED (which I didn't!).
Is
On Thu, 16 Dec 1999, you wrote:
Waa!!! So far nobody who answered even doubted that
it should be possible to have more then one
PerlTransHandler. The "Eagle" book also says
that it should be possible. People suggested that
either my mod_perl built with wrong flags or I messed
up return
