Date:  Sun, 1 Apr 2007 20:07:45 +0100
From:  Michael Stauber <bq (at mark) solarspeed.net>
Subject:  [coba-e:09414] Re: Problem with htaccess
To:  coba-e (at mark) bluequartz.org
Message-Id:  <200704012107.45368.bq (at mark) solarspeed.net>
In-Reply-To:  <!&!AAAAAAAAAAAYAAAAAAAAALCkVKWJsdMRhRQAYGMB3kjCowAAEAAAAJ+2mFgygk9HgYs8yyT2IasBAAAAAA== (at mark) pelicanit.co.uk>
References:  <030820072032.11268.45F072D1000B6DD700002C042200761064020A990A0C030D (at mark) comcast.net> <460246D3.4010408 (at mark) dogsbody.org> <!&!AAAAAAAAAAAYAAAAAAAAALCkVKWJsdMRhRQAYGMB3kjCowAAEAAAAJ+2mFgygk9HgYs8yyT2IasBAAAAAA== (at mark) pelicanit.co.uk>
X-Mail-Count: 09414

Hi Richard,

> I have put a .htaccess file in the directory with the following
>
> AuthName " Archive"
> AuthType Basic
> /home/sites/www.site-name/users/.htpasswd
> Require valid-user
>
> And created the password file,
>
> How ever when trying to access the directory we get
>
> Internal server Error
> The server encountered an internal error or misconfiguration and was unable
> to complete your request. Your administrator may not have enabled CGI
> access for this directory.
>
> Any ideas

The syntax for adding password protection in .htaccess files is now different 
from what you (or your clients) may be used to.

Please look at this file on your server:

/root/PAM_AUTH_EXTERNAL.READ-ME

It contains three working examples of how your .htaccess file has to look if 
you want to password protect a directory.

-- 
With best regards,

Michael Stauber
http://www.solarspeed.net