[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#396782: apache2.2-common: Upgrade adds "default" virtual host; breaks existing config

Package: apache2.2-common
Version: 2.2.3-2
Severity: normal

I had a working apache2 configuration, with many virtual hosts.
After this recent upgrade, parts of my web sites stopped working.
I eventually discovered that the upgrade had added a new
virtual host to
That virtual host begins with
	NameVirtualHost *
	<VirtualHost *>
Alas, my existing configuration already had
	NameVirtualHost *:80
	NameVirtualHost *:443
and many existing virtual hosts of these forms:
	<VirtualHost *:80>
	<VirtualHost *:443>

This turned out to introduce a conflict, and some of my existing virtual hosts
stopped working.

Surely the error is that a new "000-default" virtual host should not be
inserted into an existing working apache configuration.  Just that by itself
(introducing an unexpected and unneeded new virtual web site) would be
annoying, but in this case it had the additional effect of disabling part of
my existing configuration.

	-- Don

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-686-smp
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C)

Versions of packages apache2.2-common depends on:
ii  apache2-utils                 2.2.3-2    utility programs for webservers
ii  libmagic1                     4.17-4     File type determination library us
ii  lsb-base                      3.1-15     Linux Standard Base 3.1 init scrip
ii  mime-support                  3.37-1     MIME files 'mime.types' & 'mailcap
ii  net-tools                     1.60-17    The NET-3 networking toolkit

apache2.2-common recommends no packages.

-- no debconf information

Reply to: