Re: Making perl handlers handle non-Perl

2002-02-27 Thread Perrin Harkins
Nico Erfurth wrote: > your handler could tie the output-handle (is this possible?) and run a > subrequest. Nope, not possible. You can only do that for mod_perl requests. - Perrin

Re: Making perl handlers handle non-Perl

2002-02-27 Thread Nico Erfurth
Andy Lester wrote: > How can I get mod_perl to handle all Apache output, whether or not it > originates with mod_perl? > > I'm writing a module that needs to analyze all output generated by Apache. > That's easy enough with stacked handlers, but I'm goofing something up > with, say, static HTML.

Re: Making perl handlers handle non-Perl

2002-02-27 Thread Slava Bizyayev
As far as I understand, it should be a chain of handlers. It's very close to one of my current projects. You have to serve one of the early stages of the request to decide what handler is appropriate for the content generation phase in particular conditions, and dynamically install that handler, w

Re: Making perl handlers handle non-Perl

2002-02-27 Thread Perrin Harkins
Andy Lester wrote: > So, my HTML::Lint checking is only going to work on output from the > mod_perl chain. If you aren't terribly concerned about performance, there are several Apache::Proxy modules which should be easy to modify to put your lint checking in. Do a search for "proxy" on CPAN to

Re: Making perl handlers handle non-Perl

2002-02-27 Thread Geoffrey Young
Perrin Harkins wrote: > > Andy Lester wrote: > > 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. > > Assuming you mean you want to look at the generated content

Re: Making perl handlers handle non-Perl

2002-02-27 Thread Andy Lester
> Assuming you mean you want to look at the generated content from > non-mod_perl handlers and do something with it, apache doesn't work that > way. Apache 2.0 does, but that won't help you right now. You might try > using a proxy server setup to do this instead. THAT'S the answer I was looking

Re: Making perl handlers handle non-Perl

2002-02-27 Thread Perrin Harkins
Andy Lester wrote: > 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. Assuming you mean you want to look at the generated content from non-mod_perl handlers and do so

Re: Making perl handlers handle non-Perl

2002-02-27 Thread Geoffrey Young
Andy Lester wrote: > > > ok, SetHandler sets a content handler for a given - 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

Re: Making perl handlers handle non-Perl

2002-02-27 Thread Andy Lester
> ok, SetHandler sets a content handler for a given - 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

Re: Making perl handlers handle non-Perl

2002-02-27 Thread Geoffrey Young
Andy Lester wrote: > > How can I get mod_perl to handle all Apache output, whether or not it > originates with mod_perl? > > I'm writing a module that needs to analyze all output generated by Apache. > That's easy enough with stacked handlers, but I'm goofing something up > with, say, static HTM