"In general, you should never use .htaccess
files unless
you don't have access to the main server configuration file. There is,
for example, a prevailing misconception that user authentication should
always be done in .htaccess
files. This is simply not the
case. You can put user authentication configurations in the main server
configuration, and this is, in fact, the preferred way to do
things."
ref: http://httpd.apache.org/docs/2.0/howto/htaccess.html
create the password file:
htpasswd -c /path/to/pass/file username
(only use -c the first time)
add to httpd.conf, do a graceful
<Directory /dir/path>
AuthType Basic
AuthName "whatever"
AuthUserFile /path/to/pass/file
Require valid-user
</Directory>
On 5/23/06, Darrin Chandler <dwchandler@stilyagin.com> wrote:
> Sounds like you've figured it all out except for the refresh part.
> Right?
>
> Make your bookmark something like
> http://user:pass@www.domain.com/secret.html
Ah, I forgot about being able to do this. If I can get .htaccess to
work, I'll do that. Though I've read it's better to use a Directory
directive. I've not found a good example on how this works and reading
the documentation is not much better.
---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change you mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss