This bug still persists in 10.04.2. I can't be that hard to fix guys.
Can it?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/370542
Title:
Accessing http://localhost gives a 403
@Martin Kucej: It is impossible to fix this bug until its root cause is
known, see comments 13 and 14 for details. Please be patient.
** Tags added: maverick natty
** Tags removed: karmic
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
Still affected me on 10.04
nm:0.8-0ubuntu3
uname :Linux 2.6.32-24-generic #38-Ubuntu SMP Mon Jul 5 09:22:14 UTC 2010 i686
GNU/Linux
apache:2.2.14-5ubuntu8
I have encountered so many problems with the Network-Manager,Will Ubuntu switch
to wicd at any chance?
--
Accessing http://localhost gives
** Tags added: jaunty karmic lucid
--
Accessing http://localhost gives a 403 Forbidden when using apache allow
localhost directive
https://bugs.launchpad.net/bugs/370542
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in ubuntu.
The bug still exists in Ubuntu Lucid Lynx (10.04), with the exast same symptoms
amd solutions. At least in my case.
kernel: 2.6.32-23-generic
apache: 2.2.14-5ubuntu8, mpm-prefork
network-manager: 0.8-0ubuntu3
--
Accessing http://localhost gives a 403 Forbidden when using apache allow
localhost
Any news with alpha6 ?
--
Accessing http://localhost gives a 403 Forbidden when using apache allow
localhost directive
https://bugs.launchpad.net/bugs/370542
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in ubuntu.
--
Has someone tried to reproduce this bug in Karmic Alpha2 ?
--
Accessing http://localhost gives a 403 Forbidden when using apache allow
localhost directive
https://bugs.launchpad.net/bugs/370542
You received this bug notification because you are a member of Ubuntu
Server Team, which is
OK. The underlying issue here now seems to be:
On Ubuntu 9.04 Desktop, Network Manager causes a network configuration
that leads Apache to start up listening on IPv6, but to restart
listening on IPv4. Specifying network configuration using
/etc/network/interfaces does not cause this behaviour,
@Jonathan: Yes, I agree that this is clearly related to the
NetworkManager. That said I'm not convinced that is an actual bug in
Network Manager. For example; compare to sshd, which doesn't have any
trouble with Network Manager and its ipv6 behavior.
Anyway, I'm changing the Status to Confirmed.
@Andreas: Before editing /etc/apache2/sites-avaible/default the apache
was working normally (but I didn't check it after restart). I'm using
NetworkManager. I will now test the Allow from all-option.
As Martin said, http://127.0.0.1 is working.
** Attachment added: hosts
With Allow from all-option, http://[::1]/ , http://127.0.0.1/ and
http://localhost/ are all working. So this is a problem with Allow from
localhost or a specified ip address.
--
Accessing http://localhost gives a 403 Forbidden when using apache allow
localhost directive
I observe exactly the same behaviour as Andreas did on his desktop
install, right down to everything being fine when I use
/etc/network/interfaces instead of NetworkManager.
--
Accessing http://localhost gives a 403 Forbidden when using apache allow
localhost directive
@papukaija: Just for confirmation; are your problems depending on Allow
from localhost or do they also occur using Allow from all. How does
your /etc/hosts look like? Using the NetworkManager?
--
Accessing http://localhost gives a 403 Forbidden when using apache allow
localhost directive
** Summary changed:
- Accessing http://localhost gives without reason a 403 Forbidden error page
+ Accessing http://localhost gives a 403 Forbidden when using apache allow
localhost directive
--
Accessing http://localhost gives a 403 Forbidden when using apache allow
localhost directive
14 matches
Mail list logo
