Hi,
I am running a hosting service, and I use mod_perl to filter pages and add
banners. For my paid users, I would like to offer the option of using
.htaccess files for password protection, but I can't afford to check these
files on every hit, only hits to paid sites. I can determine if the
that is not a paid one? If so, how is this
to be done? (Please give code or at least pseudocode where possible.)
For those who have read this far, I appreciate your time and I thank you
for all of your contributions in advance.
Mark Holt
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
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 the
Newbie to the list, apologies if this is a FAQ, but I checked the
archives...
I built a modperl-enabled server, (Apache/1.3.9 Ben-SSL/1.37 (Unix)
mod_perl/1.21) and have been running it for some time. I have the
mod_perl as a shared module, and I recently enabled it to start
development. I have
modules in the
script, and until the database module is used, it starts OK. Is there an
order I must use them in? Apache::DBI installed without a hitch, are there
other pitfalls of which I should be aware?
Perrin Harkins wrote:
On Mon, 22 May 2000, Mark Holt wrote:
Newbie to the list, apologies
