On Tue, 05 Apr 2011 09:56:08 -0400, Yehuda Katz wrote:
The first thing I always try is removing/commenting the access control
directives, something like this:
Location /server-status
SetHandler server-status
# Order deny,allow
# Deny from all
# Allow from 192.168.9.0/24 127.0.0.1
On Tue, Apr 5, 2011 at 10:19 AM, Michael D. Berger
m_d_berger_1...@yahoo.com wrote:
On Tue, 05 Apr 2011 09:56:08 -0400, Yehuda Katz wrote:
The first thing I always try is removing/commenting the access control
directives, something like this:
Location /server-status
SetHandler
On Tue, 05 Apr 2011 10:31:01 -0400, Yehuda Katz wrote:
Thanks. I tried it and I still get 403.
The next thing that I try is explicitly setting Allow from all: Order
allow,deny
Allow from all
Same result, 403 when I do:
http://my.stuff.net/server-status
I note that I also get 403 for:
[[RESEND]]
On Tue, Apr 5, 2011 at 10:43 AM, Michael D. Berger
m_d_berger_1...@yahoo.com wrote:
Same result, 403 when I do:
/server-status
I note that I also get 403 for:
/AnyOldJunk
Since I have no file or directory named server-status,
I assume that Apache is supposed to give this
On Tue, 05 Apr 2011 14:28:34 -0400, Yehuda Katz wrote:
[[RESEND]]
On Tue, Apr 5, 2011 at 10:43 AM, Michael D. Berger
m_d_berger_1...@yahoo.com wrote:
Same result, 403 when I do:
/server-status
I note that I also get 403 for:
/AnyOldJunk
Since I have no file or directory named
