I did return DECLINED since I've read the documentation
and it was clear to me that I had to return DECLINED,
however, the handlers seemed to get stacked.

So what happens is that if my PerlTransHandler for virtual host
foo returns declined the My::Foo handler will still run and if
that one also returns DECLINED then will the apache's default handler
run.

--Attila


-----Original Message-----
From: Fred Moyer [mailto:[EMAIL PROTECTED] 
Sent: Mittwoch, 15. Februar 2006 18:52
To: Geoffrey Young
Cc: Frank Wiles; Peter, Attila; modperl@perl.apache.org
Subject: Re: FW: MP2 PerlTransHandler and VirtualHosts

>>  PerlTransHandler Apache2::Const::OK
>
> I didn't take the time to read the entire thread, but based on the 
> suggestion of using default-handler I figured the goal was something 
> like this
>
> PerlTransHandler My::Foo
>
> <VirtualHost foo >
>   # unset the above trans handler
> </VirtualHost>
>
> if that's the case then you want to return DECLINED instead of OK.  OK

> means that translation was completed and the httpd default _should not

> run_, while DECLINED means translation has not yet completed and the 
> httpd default _should run_.

I was initially thinking to use DECLINED but then I thought that the
My::Foo transhandler would run after the vhost handler, ergo
transhandlers in vhosts and the main httpd config would be stacked
(that's where I was wrong), so OK would be appropriate (which it is
not).  Sometimes I wish I had a poster of the request lifecycle loop
from the cookbook on my wall to remind me that apache is still involved
after mod_perl does its work :)

Reply via email to