I think I'm completely wrong on this, my fault for doing this completely from memory without verifying that it actually works.
The problem is more of Apache's completely unexpected behavior: it listens on whatever port you tell it. You have only a virtual host on *:1080? Listen 80, it comes up and listens on 80, does not serve your site. You have multiple virtual hosts on one port, and multiple others on other ports? You can't have multiple Listen directives on the same port, Apache won't start. The same information is in two places and it doesn't have to make sense. I should have actually checked before I filed this invalid report; the actual issue I want to report is something completely different and upstream. On Fri, Jan 25, 2013 at 4:22 PM, Bug Watch Updater < [email protected]> wrote: > ** Changed in: apache2 (Debian) > Status: Unknown => New > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1105411 > > Title: > apache2 default conf file contains Listen directive > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1105411/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1105411 Title: apache2 default conf file contains Listen directive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1105411/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
