Forum Moderators: phranque

Message Too Old, No Replies

Apache : looking for .htaccess

I don't want it to use .htaccess files

         

Jazeker

4:23 pm on Nov 19, 2004 (gmt 0)

10+ Year Member



Hi,

while you are looking into [webmasterworld.com...] I might as well talk about the instability of Apache 1.3.x with mod_ntlm. :-D

Problem is that since I upgraded to apache 1.3.33, I sometimes get auth problems (it's russian roulette when you start the server btw - you have the problem or not). The logs show :

[Fri Nov 19 16:47:48 2004] [crit] [client 164.***.146.32] (13)Permission denied: q:/browse/docs/.htaccess pcf
g_openfile: unable to check htaccess file, ensure it is readable
[Fri Nov 19 16:47:53 2004] [crit] [client 164.***.146.32] (13)Permission denied: q:/browse/docs/.htaccess pcf
g_openfile: unable to check htaccess file, ensure it is readable

So it seems it tries to find .htaccess files. However... I never use .htaccess files since I can maintain httpd.conf myself. The previous version (apache 1.3.23) never sent me this error. I am wondering what I should do now? Disallow all overrides? I tried that but then it won't let me override the protection of some subdirs which I want to be better protected than the root dir.

Any help would be greatly appreciated.

[edited by: jdMorgan at 6:32 pm (utc) on Nov. 19, 2004]
[edit reason] Obscured IP per TOS [/edit]

jdMorgan

6:34 pm on Nov 19, 2004 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Jazekar,

Welcome to WebmasterWorld!

What is the result if you test with a blank .htaccess file in the Web root directory?
(Trying to separate filesystem-interface errors from Apache-internal errors)

Jim

Jazeker

8:40 pm on Nov 19, 2004 (gmt 0)

10+ Year Member



oh dear... I am ashamed I did not try that myself. I am not worthy of the name of engineer :-(

I will test this first thing on monday morning. I guess I have been too stumped about apache even looking for .htaccess files till now :-)

Jazeker

10:00 am on Nov 23, 2004 (gmt 0)

10+ Year Member



For the moment this is solved by reinstalling my setup on another machine. I will double check the answer the moment I have the same problem again.

thx guys