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, and works as expected (apache2 uses IPv4 consistently).
Therefore, this is really a Network Manager bug, not an apache2 bug -- should we change it to be against network-manager?
This also implies that doing "allow from ::1" as well as "allow from localhost" is a only workaround, not really addressing the issue itself.
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, and works as expected (apache2 uses IPv4 consistently).
Therefore, this is really a Network Manager bug, not an apache2 bug -- should we change it to be against network-manager?
This also implies that doing "allow from ::1" as well as "allow from localhost" is a only workaround, not really addressing the issue itself.