A CGI can handle this -- initially, you can authenticate to any password
file, database, or LDAP directory and dynamically generate the pages you
want to protect. Links to other protected pages should be CGIs too
which checks cookies so you don't have to authenticate again.
On Fri, 19 Nov 1999, Alan Kong wrote:
> Hi,
>
> This may be off from this list. However I hope someone could advise.
>
> We have our site which allows people to browse. Now we want to restrict
> some pages to certain users only. And I want to use cookies which means
> I need to set up cookie server as well. I wonder whether u could direct
> me to information in writing a cookie server. Apart from the cookie
> server, is there any other suggestions other than using ".htaccess"?
>
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
