From: Nick Rout <nick@rout.co.nz>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] apache permssions
Date: Sun, 5 Feb 2006 18:26:16 +1300 [thread overview]
Message-ID: <20060205182616.5f794156.nick@rout.co.nz> (raw)
In-Reply-To: <200602041558.58204.bulliver@badcomputer.org>
On Sat, 4 Feb 2006 15:58:53 -0800
darren kirby <bulliver@badcomputer.org> wrote:
> quoth the Nick Rout:
> > I wanted to use mod_status so I set -D INFO in /etc/conf.d/apache2 and
> > my /etc/httpd.conf cotains the following:
> >
> > <IfDefine INFO>
> > ExtendedStatus On
> > <Location /server-status>
> > SetHandler server-status
> > Order deny,allow
> > Deny from all
> > Allow from localhost
> > </Location>
> > </IfDefine>
> >
> > Looks to me as though it should allow connections from localhost, but
> > it doesn't, I get 403 Forbidden.
>
> Yeah, it should be working, and in fact it is exactly the same as on my system
> where it does work. Is your system having problems resolving localhost? Does
> 127.0.0.1 work?
>
> > If I comment out the lines Deny from all, Allow from localhost it
> > works, but not as it is written i the default file as quoted above.
> >
> > What am I doing wrong?
> >
> > Reading the manual here makes me believe it should be working:
> >
> > http://httpd.apache.org/docs/2.0/mod/mod_access.html#order
>
> -d
Seems to be the same if i make the request to
http://locahost/server-status
the error message in the apache log seems to be the same whether i ask
for loalhost/server-status or 127.0.0.1/server-status.
(asked for 127.0.0.1)
[Sun Feb 05 18:18:35 2006] [error] [client 127.0.0.1] client denied by
server configuration: /var/www/localhost/htdocs/server-status
(asked for localhost)
[Sun Feb 05 18:20:59 2006] [error] [client 127.0.0.1] client denied by
server configuration: /var/www/localhost/htdocs/server-status
resolution for localhost seems to work:
nick@sf ~ $ host localhost
localhost.rout.dyndns.org has address 127.0.0.1
nick@sf ~ $ host 127.0.0.1
1.0.0.127.in-addr.arpa domain name pointer localhost.
More pointers appreciated. I don't particularly need this, it damn
annoys me that it sdoesn't work though.
> --
> darren kirby :: Part of the problem since 1976 :: http://badcomputer.org
> "...the number of UNIX installations has grown to 10, with more expected..."
> - Dennis Ritchie and Ken Thompson, June 1972
>
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-02-05 5:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-04 23:23 [gentoo-user] apache permssions Nick Rout
2006-02-04 23:58 ` darren kirby
2006-02-05 5:26 ` Nick Rout [this message]
2006-02-05 6:38 ` Willie Wong
2006-02-05 20:37 ` Nick Rout
2006-02-05 22:19 ` OT - What is mod_status? (WAS: Re: [gentoo-user] apache permssions) Michael Sullivan
2006-02-05 22:47 ` kashani
2006-02-05 23:00 ` darren kirby
2006-02-05 23:01 ` [gentoo-user] apache permssions darren kirby
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060205182616.5f794156.nick@rout.co.nz \
--to=nick@rout.co.nz \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox