On Tue, Feb 21, 2012 at 6:55 PM, Cees Hek wrote:
> On Mon, Feb 13, 2012 at 11:58 PM, Aaron Knister wrote:
> > Hi Tuomo,
> >
> > I don't mean 80,000 virtual hosts. I have over 80k unix accounts for
> which content is being served via mod_userdir. And I consider each one it's
> own "site". It's cr
On Mon, Feb 13, 2012 at 11:58 PM, Aaron Knister wrote:
> Hi Tuomo,
>
> I don't mean 80,000 virtual hosts. I have over 80k unix accounts for which
> content is being served via mod_userdir. And I consider each one it's own
> "site". It's critical to the environment that users be prevented from
>
On Sat, Feb 11, 2012 at 7:23 PM, Aaron Knister wrote:
> I need to allow htaccess files for users to be able to customize their
> websites as required (specify authentication/authorization methods, rewrite
> rules, mime types, custom handlers etc.). I wish I could turn them off but I
> fear that it
Hi Tuomo,
I don't mean 80,000 virtual hosts. I have over 80k unix accounts for which
content is being served via mod_userdir. And I consider each one it's own
"site". It's critical to the environment that users be prevented from
specifying handlers in htaccess files in part exactly for the reas
On Fri, Feb 10, 2012 at 08:50:21AM -0500, Aaron Knister wrote:
> this is a personal web hosting setup for 80,000+ individual sites (think
> mod_userdir).
I might be missing something, but does this not seem to be inherently
impossible? 80 kilosites sharing a perl interpreter that persists any
g
Hi Perrin,
I need to allow htaccess files for users to be able to customize their
websites as required (specify authentication/authorization methods, rewrite
rules, mime types, custom handlers etc.). I wish I could turn them off but
I fear that it's not feasible for me to do so.
Specifically, the
On Fri, Feb 10, 2012 at 6:46 AM, Aaron Knister wrote:
> 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 us
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
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 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 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 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,
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
13 matches
Mail list logo
