> As far as I understand, Apache 1 is not able to filter output from a > standalone CGI script (as opposed to a mod_perl handler). At least this > would be consistent with your observation: >
Makes sense. Not knowing myself though, I thought Apache::RegistryFilter may be the answer. > This seems like you didn't get the cgi script to work under > Apache::Registry. Run it as a plain mod_perl handler, that would be the > best solution on your way to A::A::P::Filter support > >> If the latter, wouldn't I have to add code to the MT handler sub to >> register itself with Apache::Filter? > > Having no first hand experience with Apache::Filter, I say yes, AFAIK. Well, the cgi is stock CGI that is a wrapper around the core modules. I did have that cgi also working as a mod_perl PerlHendler also. The core modules have all the handler subs in place for that. So again, being clueless, I think my config was probably right, but the core MT modules just need to be tweaked to register with Apache::Filter Thanks, -=Chris --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
