Apache2 and SusE 8.2
 

Would anyone know what the reason for apache2 ignoring my .htaccess files?

I have previously installed the same php program called claroline on a mandrake 9.1 and it worked fine, but with SusE 8.2, it just plainly ignores the .htaccess files (they are generated during the installation of the php program)

Does anyone know if there is a place in httpd2.conf I can look to check that apache is looking for .htaccess files?

Thanks

Check that the AccessFileName directive in your http2.conf says to look for .htaccess files and not some other name. That's the first thing to look for. Also, make sure your server has mod_auth enabled. See the fine documentation at http://httpd.apache.org/docs-2.0/howto/auth.html for additional help.

I looked in httpd2.conf and found .htaccess and I mod_auth is enabled, looks like its off to the apache documentation site for me.

Thanks for the tips

you should install mod_php4 for apache2 , because suse does not supply mod_php4 for apache2 by default for security reason. Download it from it's official site
ftp://ftp.suse.com/pub/projects/apache/

check you httpd.conf for a line AllowOveride
default it gets set to none
set it to AuthConfig for start then do some research for more options but that should get it started.
Also if you are using Virtual Hosting make sure you did'nt overide this setting in the VH directives.
HTH

AuthConfig
 

I seem to have etc/apache2 directory with a httpd.conf in it and also a etc/httpd

I have put AllowOverride AuthConfig in both and when I entered my .htaccess directory it challenged me, but this was only once!

I tried it again and it didnt work

I opened up a new instance of a web browser and tried it again, but to no avail,

This is driving me up the wall

Any other tips (apart from reading the apache manual)?

Thanks

success!!
 

After changing every httpd.conf file I had (3 in all!!), the .htaccess is now recognised, although the pages I protect are available by url after you have navigated away from them until you close the browser and open a new instance.

That will do for the mean time.