Hi All,
I have set up mod_perl filtering as follows:
Location ~ /(staticweb|jbossweb)
SetHandler modperl
PerlOutputFilterHandler MyOutputHandlers::CustomFilterResponse
allow from all
/Location
staticweb is under htdocs and jbossweb is an app-context deployed in jboss .
On 06/26/2012 09:46 AM, Rommel Sharma wrote:
Location ~ /(staticweb|jbossweb)
SetHandler modperl
You don't need that. SetHandler declares the response handler. But your
response is generated either by the default handler for static content
or by mod_jk. SetHandler modperl should be used
Any ideas on what to look for to determine the problem?
That's amply documented on the homepage: http://perl.apache.org/ → Reporting
Bugs →
http://perl.apache.org/bugs/ → mod_perl 2.0 →
http://perl.apache.org/docs/2.0/user/help/help.html → Resolving
Segmentation Faults →
Rommel Sharma wrote:
Hi All,
I have set up mod_perl filtering as follows:
Location ~ /(staticweb|jbossweb)
SetHandler modperl
PerlOutputFilterHandler MyOutputHandlers::CustomFilterResponse
allow from all
/Location
staticweb is under htdocs and jbossweb is an app-context deployed
Hi Torsten,
removing
SetHandler mod_perl
worked! Both jboss and apache htdocs data are being filtered as expected.
Thanks again, for all the time and inputs!!!
Thanks,
Rommel.
-Original Message-
From: Torsten Förtsch [mailto:torsten.foert...@gmx.net]
Sent: Tuesday, June 26,
Hi André,
Many thanks for the useful information below that helps me in understanding the
working of the filters and the modules.
Realized the mod jk conflict with mod_perl and removed the SetHandler mod_perl
and it worked.
Huge thanks to all the experts on this group for sharing the