On Tuesday 03 August 2010, 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.
Makes sense. If one of the restriction turns out to be too painful in practice, we can always allow that case again.
