You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@httpd.apache.org by "Michael D. Berger" <m_...@yahoo.com> on 2011/04/05 15:52:49 UTC
[users@httpd] cannot run mod_status
On my CentOS 5 box with:
#rpm -q httpd
httpd-2.2.3-43.el5.centos.3
I tried to activate mod_status with:
ExtendedStatus On
<Location /server-status>
SetHandler server-status
Order deny,allow
Deny from all
Allow from 192.168.9.0/24 127.0.0.1
</Location>
I already have:
LoadModule status_module modules/mod_status.so
I tried access from the local box as well as another box
on 192.168.9.0/24 . I get 403.
Any suggestions on what to look at? BTW, I am using VirtualHost.
Thanks,
Mike.
---------------------------------------------------------------------
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@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
[users@httpd] Re: cannot run mod_status
Posted by "Michael D. Berger" <m_...@yahoo.com>.
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_1900@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 name special treatment, but it is not
>> doing it.
>>
>>
> You should get a 404 when you go to /AnyOldJunk, not a 403. Because you
> get a 403, there is probably some other configuration error in the
> vhost.
>
[...]
PROBLEM SOLVED. Following suggestion, I took
a close look at VirtualHost. It was not the problem, but I
note that the reason I get the 403 is because the last line
in my VirtualHost is:
RewriteRule ^.*$ - [F,L]
It is the 'F' that generates the 403. To make the server-status
work, in the VirtualHost I need:
RewriteRule ^/server-status.*$ - [L]
somewhere near the top.
But that is not all. In <Directory "/var/www/html/www"> I need:
RewriteRule ^server-status.*$ - [L]
Note the difference in the '/' between <VirtualHost> and
<Directory>. It must be exactly as shown or it will not
work.
Thanks again for your help.
Mike.
---------------------------------------------------------------------
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@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] Re: cannot run mod_status
Posted by Yehuda Katz <ye...@ymkatz.net>.
[[RESEND]]
On Tue, Apr 5, 2011 at 10:43 AM, Michael D. Berger <
m_d_berger_1900@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 name special
> treatment, but it is not doing it.
>
You should get a 404 when you go to /AnyOldJunk, not a 403.
Because you get a 403, there is probably some other configuration error in
the vhost.
- Y
[users@httpd] Re: cannot run mod_status
Posted by "Michael D. Berger" <m_...@yahoo.com>.
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:
http://my.stuff.net/AnyOldJunk
Since I have no file or directory named "server-status",
I assume that Apache is supposed to give this name special
treatment, but it is not doing it.
Mike.
Mike.
---------------------------------------------------------------------
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@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] Re: cannot run mod_status
Posted by Yehuda Katz <ye...@ymkatz.net>.
On Tue, Apr 5, 2011 at 10:19 AM, Michael D. Berger <
m_d_berger_1900@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 server-status
> > # Order deny,allow
> > # Deny from all
> > # Allow from 192.168.9.0/24 127.0.0.1
>
> </Location>
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
(I meant to include that in my earlier email so I would not flood everyone's
inboxes.)
- Y
[users@httpd] Re: cannot run mod_status
Posted by "Michael D. Berger" <m_...@yahoo.com>.
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 </Location>
>
> Then you will know if it is a problem with those directives or somewhere
> else.
Thanks. I tried it and I still get 403.
Mike.
---------------------------------------------------------------------
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@httpd.apache.org
" from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] cannot run mod_status
Posted by Yehuda Katz <ye...@ymkatz.net>.
On Tue, Apr 5, 2011 at 9:52 AM, Michael D. Berger <m_d_berger_1900@yahoo.com
> wrote:
>
> <Location /server-status>
> SetHandler server-status
> Order deny,allow
> Deny from all
> Allow from 192.168.9.0/24 127.0.0.1
> </Location>
>
> I tried access from the local box as well as another box
> on 192.168.9.0/24 . I get 403.
>
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
</Location>
Then you will know if it is a problem with those directives or somewhere
else.
- Y