Return-Path: 
 <modperl-return-23144-apmail-modperl-archive=apache.org@apache.org>
Delivered-To: apmail-modperl-archive@apache.org
Received: (qmail 93476 invoked by uid 500); 27 Feb 2002 18:17:12 -0000
Mailing-List: contact modperl-help@apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:modperl-help@apache.org>
list-unsubscribe: <mailto:modperl-unsubscribe@apache.org>
list-post: <mailto:modperl@apache.org>
Delivered-To: mailing list modperl@apache.org
Received: (qmail 93457 invoked from network); 27 Feb 2002 18:17:12 -0000
Message-ID: <3C7D22AA.C5D70724@modperlcookbook.org>
Date: Wed, 27 Feb 2002 13:17:14 -0500
From: Geoffrey Young <geoff@modperlcookbook.org>
X-Mailer: Mozilla 4.73 [en] (Windows NT 5.0; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: Andy Lester <andy@petdance.com>
CC: modperl@apache.org
Subject: Re: Making perl handlers handle non-Perl
References: <Pine.WNT.4.44.0202271210200.1096-100000@ALESTER>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Andy Lester wrote:
> 
> > ok, SetHandler sets a content handler for a given <Location> - it supersededs everything else.
> >
> > unlike with normal Apache, mod_perl needs two things in order for your handler to be called:
> > the content hander to be perl-script (for Apache) and the name of your handler with PerlHandler (for
> > mod_perl)
> 
> So what we're saying is that with static .html files, there's no way for
> me to get mod_perl to interject itself into Apache's chain?  Or PHP for
> that matter?

oh, no.

if you want to intercept absolutely _everything_ I suspect that 

SetHandler perl-script 

at the server level will do the trick (outside of any <Location> or
other container directive).  just make sure you have a 

PerlHandler My::Foo

somewhere to fill in the mod_perl part, since mod_perl needs both
directives to work.

typically, folks don't want to intercept all requests - it's generally
better to let Apache serve static files itself so that it handles
stuff like HTTP/1.1 conditional headers and the like.

> 
> I want my MyFilter to process EVERYTHING that Apache spits out, whether
> with mod_perl, mod_php or just reading a .html file from the filesystem,
> especially the mod_php stuff.
> 
> Should I be looking at one of the later phases (cleanup?) instead of
> content generation?

the content-generation phase should be fine.

HTH

--Geoff