On 19.10.2017 12:48, Ken Peng wrote:
Hi,
for a common object on server, for example, http://a.com/b.jpg, when it can be
accessed by
client, I want to apply some access control on it, for example, the IP based AC
rules. How
will mod_perl handler deal with this? thanks.
If you do the
With a PerlAccessHandler, see:
https://perl.apache.org/docs/2.0/user/handlers/http.html#PerlAccessHandler
Adam
On 17-10-19 06:48 AM, Ken Peng wrote:
Hi,
for a common object on server, for example, http://a.com/b.jpg, when it
can be accessed by client, I want to apply some access control on
Hi,
for a common object on server, for example, http://a.com/b.jpg, when it can be
accessed by client, I want to apply some access control on it, for example, the
IP based AC rules. How will mod_perl handler deal with this? thanks.
Regards,
Ken Peng
Carl Franks wrote:
Hi,
I'm currently handling access control with "AuthBasicProvider ldap dbd".
I'd like to get rid of the growing list of directives in
our httpd.conf and lookup each request url against a database, to
check whether it requires a login.
Visitors should b
Hi,
I'm currently handling access control with "AuthBasicProvider ldap dbd".
I'd like to get rid of the growing list of directives in
our httpd.conf and lookup each request url against a database, to
check whether it requires a login.
Visitors should be able to browse th
Harkins [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 24, 2004 11:08 AM
To: Larry Leszczynski
Cc: mod_perl List
Subject: Re: Ticket-based access control across multiple domains?
On Wed, 2004-03-24 at 10:47, Larry Leszczynski wrote:
> I've been looking into designs for a mod_perl cook
On Wed, 2004-03-24 at 10:47, Larry Leszczynski wrote:
> I've been looking into designs for a mod_perl cookie-based "single
> sign-on" kind of authentication system that would use a central
> authentication server across multiple products.
Ask Bjorne Hansen and Robert Spier gave a presentation abou
Larry Leszczynski <[EMAIL PROTECTED]> wrote:
>Hi all -
>
>I've been looking into designs for a mod_perl cookie-based "single
>sign-on" kind of authentication system that would use a central
>authentication server across multiple products. I've been looking at
>things like Apache::TicketAccess, Apa
Hi all -
I've been looking into designs for a mod_perl cookie-based "single
sign-on" kind of authentication system that would use a central
authentication server across multiple products. I've been looking at
things like Apache::TicketAccess, Apache::AuthTicket, Authen::Ticket,
etc., but they all
