Comment 2 for bug 137526

Not to be ornery, but if an individual is adding ports for Apache's
listening capabilities, then it is likely that they will check their
VirtualHost configs before applying any changes.

Alternatively, if someone who is relatively new to Apache sees the "*
and non-*" warning, it may cause more frustration than having a separate
*:80 and *:443 by default.

One more item to bear in mind is that a typical user may want to have a
more strict rule set on a secure config that a standard HTTP, either for
PCI compliance, or just personal preference. Maintaining a distinction
between *:80 and *:443 is, I think, ideal.

Just my $.02.

/cs