RE: [cobalt-users] .htaccess issue

["Andy Brown" <andy.brown@xxxxxxxxxxxxx>]

---cut---
> > > I wonder if anyone can shed any light on this for me.  I have a 
> > > RaQ4i dedicated server with Verio in the UK, and I am 
> having trouble 
> > > with the .htaccess settings.
> > >
> > > I am using the .htaccess files with no problem when it comes to 
> > > turning off directory snooping, making Symlinks and denying IP 
> > > addresses access etc.
> > >
> > > BUT, my problem is as soon as I try to use htpasswd it's 
> falls flat 
> > > on it's face.  That is to say, I create the .htaccess file in a
> > > sub-directory which
> > > looks like this:
> > >
> > > order allow,deny
> > > allow from all
> > > require valid-user
> > > AuthName "Private Area"
> > > Authtype basic
> > > AuthUserFile /home/sites/site1/web/whateverfolder/.htpasswd
> > > AccessList
> > > AuthPAM_Enabled off
> > >
> > > I then create the auth file using:
> > >
> > > htpasswd -c .htpasswd username
> > >
> > > As far as I can tell this is correct.  I then attempt to 
> access the 
> > > password protected folder (which I could access with no problems 
> > > before creating the
> > Are you putting the .htpasswd file in the same directory you are
> protecting?
> >
> > As a habit, we put all the password files out of site (left 
> of .../web 
> > ) Here's an example of a htaccess file we use on a raq2 site.
> > >>>>>>
> > #Access File
> > order allow,deny
> > allow from all
> > require valid-user
> > Authname "ourfaqsite.com Affiliate Zone"
> > AuthPAM_Enabled off
> > Authtype Basic
> > ErrorDocument 404 /Public/Affiliates.html
> > AuthUserFile 
> > /home/sites/www.ourfaqsite.com/xxxxx/AffiliateHTAccessPWDFile
> > <<<<<<
> >
> > Hope that helps.
> >
> > Paul
> 
> I have tried both, but the same result.  I assume SOMETHING 
> must be amiss in my access.conf file?  But I have followed 
> the instructions I have found.
> 
> This is so annoying as I need to password protect a directory ASAP.
> 
---cut---


Not a solution, but advice on whats happening, no matter WHAT htpasswd
file you enter in your htaccess files, the Raqs own username/passwords
are used.

So to create a secure area, create a USER via the browser interface for
that site, then magically their username/password will be allowed access
via your htaccess file.

We still haven't tracked down the problems here, I agree it will be in
the apache configuration, but haven't drilled down far enough to get it
sorted.

Hopefully this might shed some light onto it for somebody!


Andy
andy@xxxxxxxxxxxxxxxxxxxxx
http://ineedlinux.info/