Bug 50436

Summary: VirtualHost could behave like people expect it to
Product: Apache httpd-2 Reporter: Vincent Deffontaines <gryzor>
Component: CoreAssignee: Apache HTTPD Bugs Mailing List <bugs>
Status: NEW ---    
Severity: enhancement    
Priority: P2    
Version: 2.5-HEAD   
Target Milestone: ---   
Hardware: All   
OS: All   

Description Vincent Deffontaines 2010-12-08 16:43:33 UTC
From my support experience on #httpd, people do not understand quite well how name based virtualhosting works.

Most people who haven't read the doc carefully just configure their virtualhosts as follows :

<VirtualHost www.foo.com>
  # no servername

<VirtualHost www.bar.com>
  # no servername

The enhancement I would like to suggest : just let apache works when a config is set like above. Ie : if VirtualHost is given fqdn as argument(s), and no ServerName is explicitely set, why not just accept VirtualHost argument(s) as ServerName (and ServerAliases) ?

I can tell that people not reading much (or not reading at all) the documentation will finally have vhosts working at first attempt.

Of course, does not mean that the sane way to go (use IPs or * for VirtualHost, set a ServerName) should not remain supported...

My 2 cents,