Re: Re: Enabling SSL on VirtualHosts Revisited

[Jonathan Mast <jhmast.developer@xxxxxxxxx>]

OK, so I added NameVirtualHost foo.mysite.com:80 and NameVirtualHost foo.mysite.com:443 above their respective sections and it seems to work despite not being recommended as per the docs, but this was the only way to do it because all my domains: mysite.com, othersite.com, etc point to a single IP.

Any idea on why using hostnames in NameVirtualHost directives is not recommended?  Is this something that could come back and bite me?

Thanks for the help!

On Fri, Dec 18, 2009 at 10:34 AM, Philip Wigg <phil@xxxxxxxxxxxxxxxx> wrote:

Possibly the information you need is here:-

http://httpd.apache.org/docs/2.2/vhosts/name-based.html

When adding a name-based Virtual Host the...

"Main host goes away

If you are adding virtual hosts to an existing web server, you must
also create a <VirtualHost> block for the existing host. The
ServerName and DocumentRoot included in this virtual host should be
the same as the global ServerName and DocumentRoot. List this virtual
host first in the configuration file so that it will act as the
default host."

Cheers,
Phil.

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
  "   from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx