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

Bug#663530: apache2.2-common: ports.conf also specifies NameVirtualHost *:80



Hi,

On 21.07.2013 17:32, Edward Welbourne wrote:
> Even though I
> actually have a NameVirtualHost in my enabled sites-available file,
> matching exactly the same file's VirtualHost parameter, my configuration
> was broken by a NameVirtualHost *:80 elsewhere, that I knew nothing
> about.
> ...
> Given that the <VirtualHost> directive lives in a user-configurable file
> and *must* exactly match the NameVirtualHost directive, it strikes me
> that the old way, having the later also in the user-configurable file,
> was a better approach than the present, where the user must - in fact -
> edit a file that's not in sub-directory in which user-configuration
> normally takes place.  If there's genuinely a compelling reason to put
> the NameVirtualHost somewhere other than *right next to* the
> <VirtualHost> directive (as I'm fairly sure it used to be), where it'll
> be obvious that they need to stay in sync, please add a comment to
> default, immediately before the <VirtualHost> directive, saying "be sure
> to keep ports.conf's NameVirtualHost in sync; the host:port must match
> exactly".


First, let me point out that also ports.conf is a user-configurable
file. You can safely edit and adapt it to your needs. That what it is
meant for.

Having NameVirtualHost in 000-default though is dangerous, at is a
directive being _shared_ across virtual hosts. It is used by all sites,
including but not limited to the default site. Assuming you deactivate
the default site, this causes undefined and broken behavior if you have
other name based virtual hosts.

This is a major problem lots of Debian users stumbled upon over the
years. Thus, we're more than glad and very happy NameVirtualHost is no
more in 000-default.conf and we are definitely not going back that road.


That being said please note, that NameVirtualHost itself is deprecated
and not used anymore in Apache2 2.4. There is no chance to fix this in
Debian Stable anyway due to our freezing policy, and the next Debian
release will have Apache2 2.4 only, not using NameVirtualHost at all
anymore.

-- 
with kind regards,
Arno Töll
IRC: daemonkeeper on Freenode/OFTC
GnuPG Key-ID: 0x9D80F36D

Attachment: signature.asc
Description: OpenPGP digital signature


Reply to: