Thanks for the link. Alas, I still have the problem I reported. :-( -Jonathan httpd2@xxxxxxxxxxxx wrote:
I think error 403 is a custom error message. I do not know whether it should be written to the error file by default.I would expect it to be, just like 404's are. See if this article is of any help to you. http://www.modwest.com/help/kb.phtml?qid=144&cat=1 HTH Keith In theory, theory and practice are the same;In practice they are not.On Tue, 7 Feb 2006, Jonathan S. Abrams wrote:To: users@xxxxxxxxxxxxxxxx From: Jonathan S. Abrams <j.abrams@xxxxxxxxxxxxxxxxxxx> Subject: Re: [users@httpd] 403 Forbidden Error httpd2@xxxxxxxxxxxx wrote:Try changing the LogLevel directive to debug. LogLevel debug This will generate the max amount of error logging. Be carefull you do not run out of disk space though.I have plenty of disk space. The LogLevel was set to warn. Changing to debug has not made a difference though. There are no entries in the error_log file pertaining to this 403 error. After restarting the server with loglevel set to debug, the last entry in the error_log file reads as follows: [Tue Feb 07 12:39:56 2006] [debug] prefork.c(956): AcceptMutex: sysvsem (default: sysvsem) Should a loglevel of warn catch forbidden access errors? If not, what level do you recommend I keep this parameter at? More importantly - if the debug level isn't logging these errors, what is going on? -Jonathan
--------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|