Bug#511594: default ports.conf should not contain NameVirtualHost directive

2009-01-16 Thread Stefan Fritsch
tags 511594 wontfix thanks On Monday 12 January 2009, Marvin Renich wrote: The NameVirtualHost directive is specifically tied to the VirtualHost directive and should be in the site-specific file (e.g. sites-available/default) not the default ports.conf. Currently, if you create your own site

Bug#511594: default ports.conf should not contain NameVirtualHost directive

2009-01-12 Thread Marvin Renich
Package: apache2.2-common Version: 2.2.9-10+lenny1 Severity: normal The NameVirtualHost directive is specifically tied to the VirtualHost directive and should be in the site-specific file (e.g. sites-available/default) not the default ports.conf. Currently, if you create your own site file that