Hi Stas,
Yes indeed,
<Proxy www.xyz.com> SetOutputFilter bladibla </Proxy>
works.
The 'bladibla' output filter consists of a sed command (using mod_ext_filter). The Apache::bladibla filter is based on the modperl-2.0 documentation of the Obfuscation filter, where the substitution of the carriage return (in the obfuscation filter) is replaced by the substitution as defined earlier via sed in the bladibla filter. As I said before: Apache::bladibla works just fine as long as it's not defined between <Proxy></Proxy> directives.
Just wondering: the scope of PerlSetOutputFilter is [Dir]. could that be a/the reason why it isn't working in a proxied environment? But if this is the answer, is there an alternative solution?
MyApache::FilterObfuscate is a request filter.
What's inside bladibla, how did you configured it?
I don't seem to be able to include any filters from <Proxy>, e.g.:
<Proxy localhost.localdomain:80>
Order Deny,Allow
Deny from 10.0.0.1
Allow from all
SetOutputFilter DEFLATE
SetOutputFilter INCLUDES
#Options Indexes FollowSymLinks IncludesNoExec
</Proxy>runs none of these filters. According to the docs: http://httpd.apache.org/docs-2.0/mod/mod_proxy.html#proxy
<Proxy http://example.com/foo/*> SetOutputFilter INCLUDES </Proxy>
should work. Did I miss something? Do you have any other relevant config parts?
I can see that PerlOutputFilterHandler's dir_merge is run, but it never gets a chance to be inserted, I suppose because mod_proxy doesn't merge it with the current requests's config.
It looks like mod_include is [Dir] too: http://httpd.apache.org/docs-2.0/mod/mod_include.html#enabling
__________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
-- Reporting bugs: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html
