In Apache2 template site use <Virtualhost *:80> rather than <Virtualhost *>

Bug #137526 reported by AlainKnaff
28
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apache2 (Ubuntu)
Invalid
Wishlist
Ralph Janke

Bug Description

Binary package hint: apache-common

The default site in /etc/apache2/sites-available/default sets the default virtual virtual host as follows:

NameVirtualHost *
<VirtualHost *>
  ...
</VirtualHost>

This is all fine and dandy as long as there is no SSL site.

However, if there is, this will result in the following error:

VirtualHost *:443 -- mixing * ports and non-* ports with a NameVirtualHost address is not supported, proceeding with undefined results

Also specifying the port (80) for the default site (as well as any non-SSL sites) makes this problem go away.

NameVirtualHost *:80
<VirtualHost *:80>
  ...
</VirtualHost>

Ralph Janke (txwikinger)
Changed in apache2:
importance: Undecided → Wishlist
Revision history for this message
Ralph Janke (txwikinger) wrote :

Thank you for your suggestion. However, the changes you are requesting aren't really a bug and require more discussion, which should be done on an appropriate mailing list or forum. http://www.ubuntu.com/support/community/mailinglists might be a good start for determining which mailing list to use.

It seems this suggestion has two sides. On one hand, if the changes will be made, it is easier to add the ssl option. On the other hand, if the changes are made, and someone adds another port to which apache is listening, or changes the port, the default site does not capture those.

Thanks

Changed in apache2:
assignee: nobody → txwikinger
status: New → Incomplete
Revision history for this message
Chuck Stearns (chuckstearns) wrote :

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

Revision history for this message
Ralph Janke (txwikinger) wrote :

Thank you for your suggestion. However, the changes you are requesting aren't really a bug and require more discussion, which should be done on an appropriate mailing list or forum. http://www.ubuntu.com/support/community/mailinglists might be a good start for determining which mailing list to use.

Changed in apache2:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.