Hi,
I'm using mod_perl in a shared hosting environment for some server-side
configuration bits. All dynamic content for the users runs through SuEXEC,
however this obviously doesn't help in the case of mod_perl so I would like
to prevent users from specifying any handlers or other potentially
unde
On 10 Feb 2012, at 11:46, Aaron Knister wrote:
> Hi,
>
> I'm using mod_perl in a shared hosting environment for some server-side
> configuration bits. All dynamic content for the users runs through SuEXEC,
> however this obviously doesn't help in the case of mod_perl so I would like
> to prev
Hi Dave,
Thanks for the feedback. Unfortunately the setup isn't fronted by apache
proxies. Having an apache instance per site would, I think, be painful-- this
is a personal web hosting setup for 80,000+ individual sites (think
mod_userdir).
Sent from my iPhone
On Feb 10, 2012, at 7:20 AM, D
On Friday, 10 February 2012 06:46:01 Aaron Knister wrote:
> I was thinking of something along these lines:
>
> A per-directory config directive called PerlHtaccessOverrides with possible
> values of Handlers, Others, Env, Options, All and None. These names are
> based what seemed to be perceived s
Hi Torsten,
I actually tried that. Problem is when I disable a given handler I can't use it
at all, not even in the configs. I essentially want to be able to configure
access handlers in the apache configs but disallow users from specifying ant
handlers in their htaccess files. I can't turn off
On 10 Feb 2012, at 13:50, Aaron Knister wrote:
> Hi Dave,
>
> Thanks for the feedback. Unfortunately the setup isn't fronted by apache
> proxies. Having an apache instance per site would, I think, be painful-- this
> is a personal web hosting setup for 80,000+ individual sites (think
> mod_us
