[Bug 268868] Re: [Intrepid Alpha 5 through Live release] NameVirtualHost entry in ports.conf causes "NameVirtualHost *:80 has no VirtualHosts" warning and breaks virtualhosts

2009-10-07 Thread Chuck Short
This bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more a

[Bug 268868] Re: [Intrepid Alpha 5 through Live release] NameVirtualHost entry in ports.conf causes "NameVirtualHost *:80 has no VirtualHosts" warning and breaks virtualhosts

2008-11-25 Thread Glassbox
Yep, figures that you can sync 'em up either way, with the ports or without. It just seems kinda buggy in that it breaks what was previously working to allow the -potential- for ssl virtual hosts. Seems like at least a simple change to documentation in the new ports.conf file along the lines of th

[Bug 268868] Re: [Intrepid Alpha 5 through Live release] NameVirtualHost entry in ports.conf causes "NameVirtualHost *:80 has no VirtualHosts" warning and breaks virtualhosts

2008-11-24 Thread Ryan Niebur
Hi Glassbox, The correct fix is to change all of your "" to "". Please see /usr/share/doc/apache2/NEWS.Debian.gz for more information. Thanks, Ryan -- [Intrepid Alpha 5 through Live release] NameVirtualHost entry in ports.conf causes "NameVirtualHost *:80 has no VirtualHosts" warning and break