Bug 50436 - VirtualHost could behave like people expect it to
VirtualHost could behave like people expect it to
Status: NEW
Product: Apache httpd-2
Classification: Unclassified
Component: Core
2.5-HEAD
All All
: P2 enhancement (vote)
: ---
Assigned To: Apache HTTPD Bugs Mailing List
:
Depends on:
Blocks:
  Show dependency tree
 
Reported: 2010-12-08 16:43 UTC by Vincent Deffontaines
Modified: 2010-12-08 16:43 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
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>

<VirtualHost www.bar.com>
  # no servername
  ...
</VirtualHost>

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,

Vincent