Email address obfuscation in effect -- please
click here to turn it off.
[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
Thanks, Russell and Mikhail.
Here are my changes and answers to your questions - it still causes the same
error.
> Did you make your own .htpasswd file or did you use an existing one?
I don't use .htpasswd, I rather have a central one which I created from
scratch with htpasswd -c - it is outside of the browsable area.
> How about
> require valid-user
No change over require user
> Does your web server have read rights over the password file?
Yes.
> The contents of your Directory section should be in a .htaccess file
> under /path/to/protected/directory. The actual Directory section should
> read:
>
> <Directory /path/to/protected/directory>
> AllowOverride AuthConfig Limit
> Order allow,deny
> Allow from all
> </Directory>
I did this, and I created the .htaccess file with the following contents:
AuthType Basic
AuthName "Access restricted to BE-333 students"
AuthUserFile "/home/www/passwords/passwords"
Require user BE333
(alternatively, require valid-user BE333)
> Also see http://httpd.apache.org/docs-2.0/howto/htaccess.html
Yes, I did. Initially, I tried to follow the section "when not to use
.htaccess files", but you suggest using .htaccess - which I now did (to no
avail)
> The password file should be outside of the browseable area, i.e. under
> /var/www/ (not /var/www/html/).
Yes, this is the case. /home/www/ is not browsable, but /home/www/html is.
Thanks again,
Mark
_______________________________________________
members mailing list
EMAIL:PROTECTED
http://mlug.missouri.edu/mailman/listinfo/members