At 10:57 AM +0200 10/25/00, Stephane Bortzmeyer wrote:
>- make two databases, but I don't really see what can prevent the user to use
>the private one (I have to authorize /cgi-bin/htsearch for everybody). Yes, I
>can make two Web pages with different config (and authorize only one from
>outside) but it seems a lame protection.
You can make a symbolic link and secure one of the URLs, e.g.:
ln -s htsearch htsearch.pr
and then in your server config:
<Location /cgi-bin/htsearch.pr>
AuthType Basic
AuthName ....
AuthUserFile ...
AuthGroupFile ...
<Limit GET POST>
require group foo
</Limit>
</Location>
For example, this is how the ht://Dig bug database is protected for developers.
--
-Geoff Hutchison
Williams Students Online
http://wso.williams.edu/
------------------------------------
To unsubscribe from the htdig mailing list, send a message to
[EMAIL PROTECTED]
You will receive a message to confirm this.
List archives: <http://www.htdig.org/mail/menu.html>
FAQ: <http://www.htdig.org/FAQ.html>
