Dear addressed,
pls, provide.
i want to use the Perl-based Authentication Module
Apache::authDBI
written by Edmund Mergl.
This is tested with
Apache 1.3.6
Mod_perl 1.21
However i want to use it with
Apache 2.0.30
Mod_perl 2.0
This is configured on the System with
On Thu, May 10, 2001 at 11:50:31PM -0600, Mark Holt wrote:
> parsing the .htaccess files is what I'm trying to avoid. I want the standard apache
> module to do that. I just want to control *when*.
have you considered breaking up the apache instances, maybe?
might be a bad idea, but i thot i'd s
Mark,
I am by no means a mod_perl guru... and this may not solve your full
problem... but, you could put something httpd.conf that says something like:
if ($paid) then allow .htaccess files; else don't. In other words,
AllowOverride AuthConfig if paid; else AllowOverride None.
Something alo
parsing the .htaccess files is what I'm trying to avoid. I want the standard apache
module to do that. I just want to control *when*.
Clayton Cottingham aka drfrog wrote:
> hello
>
> is this not something like what Apache::AuthCookie
> or some other Auth scheme does?
> or am i just missing th
hello
is this not something like what Apache::AuthCookie
or some other Auth scheme does?
or am i just missing the boat?
you could use something
like AuthCookie in a dummy situation
get $r->uri
grab the .htaccess from that location and parse?
Time Co-Ordinate Thu, 10 May 2001 23:16:29 -0600,
>
>
> Not really, the current Apache doesn't let you decide on the fly whether
> to challenge the client with basic auth or not unless you use .htaccess.
If I wrote my own PerlAuthHandler, could it then choose whether to pass through
to the standard AuthHandler?
> .htaccess is not used only for
On Thu, 10 May 2001, Mark Holt wrote:
[snipped the situation explanation]
> Now to my question: Is it possible, using mod_perl, to activate
> Apache's standard .htaccess-based authentication scheme on a per-hit
> basis, based on the results of perl code to determine whether the user
> is a payi
OK, let me be more specific. Here is the problem I face:
Hosting of (potentially) millions of websites in a single framework.
Clients are not given their own VirtualHost tag in the config file
(there are too many), but instead their document root is derived from
their hostname. Clients can fluc
