httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Trawick <>
Subject Re: Failing startup for vhost configuration problems
Date Wed, 04 Aug 2010 12:22:01 GMT
On Tue, Aug 3, 2010 at 8:05 AM, Dan Poirier <> wrote:
> I'd like to propose that in 2.3/2.4, we fail startup for any of the
> virtual host misconfigurations for which behavior is undefined but right
> now we only issue a warning.
> E.g. no VirtualHosts matching a NameVirtualHost, overlapping
> VirtualHosts, use of _default_ in NameVirtualHost, mixing * and non-*
> ports in name-based virtual hosts.
> The rationale is that these configurations are unsupported, the behavior
> is undefined, and presumably they are the result of errors, so better to
> make sure the admin corrects the error than to continue and probably not
> behave as the admin expects.
> A new major version seems like a good time for a change like this.
> Thoughts?

+1 concept (I'm lacking a sense of the frequency distribution of such
config errors and related problem symptoms out in the real world)

View raw message