Re: tlug: Use .htaccess, or ?

[Darren Cook <darren@example.com>]

>I'm developing a web site which will be mostly public, but one part will be
>accessible only to members of the organization, and at this point it looks
>like they will probably all be sharing one userid and password (yes, I know

I've been using an entry in httpd.conf something like this:

#Change / to the directory you want to protect.
<Location />
AuthType Basic
AuthName somedomain
#NB. next file is relative to server root.
AuthUserFile userpw.txt
#Next line means allow all people in that file.
require valid-user
</Location>

It will protect all subdirectories as well. I've not used .htaccess, so I
don't know how it differs. userpw.txt is made with htpasswd (except on NT
Apache where it has to be clear text because of US export restrictions (!),
but you can get a patch from a UK site).

>If they do decide to go with an assigned user-id and password for
>each person (I doubt they will), how large should the user database be
>allowed to get before going to a DB or DBM format?
>
>And finally, any and all decent how-to sources on this are gratefully

These newsgroups are good for Apache questions:
  comp.infosystems.www.servers.unix
  comp.infosystems.www.servers.windows

I'd ask your "how-large" question there. I've always used cgi-bin for large
number of users, because generally I also want to store other information
on them and have dynamic pages.

BTW, if you're maintaining Apache servers it's worth reading this:
http://www.apache.org/info/three-config-files.html
(basically, keep everything in httpd.conf, and lose srm.conf and access.conf).

Darren

---------------------------------------------------------------
Next Nomikai: 20 November, 19:30 Tengu TokyoEkiMae 03-3275-3691
Next Meeting: 12 December, 12:30 Tokyo Station Yaesu central gate
---------------------------------------------------------------
Sponsor: PHT, makers of TurboLinux http://www.pht.co.jp