- Original Message -
From: Krist van Besien
To: users@httpd.apache.org
Sent: Wed Dec 16 07:17:43 2009
Subject: Re: [us...@httpd] Enabling SSL on a virtual host
On Tue, Dec 15, 2009 at 5:37 PM, Jonathan Mast
wrote:
> I'm thinking that the host name actually is require
- Original Message -
From: Krist van Besien
To: users@httpd.apache.org
Sent: Wed Dec 16 07:17:43 2009
Subject: Re: [us...@httpd] Enabling SSL on a virtual host
On Tue, Dec 15, 2009 at 5:37 PM, Jonathan Mast
wrote:
> I'm thinking that the host name actually is require
On Tue, Dec 15, 2009 at 5:37 PM, Jonathan Mast
wrote:
> I'm thinking that the host name actually is required in the VirtualHost
No it is not required.
A hostname in a VirtualHost directive is internally converted to an IP
address and only needed if this VirtualHost needs to be bound to a
particu
I'm thinking that the host name actually is required in the VirtualHost
declaration.
But the 2 separate VirtualHost entries worked, thanks
On Tue, Dec 15, 2009 at 10:53 AM, Eric Covener wrote:
> On Tue, Dec 15, 2009 at 10:48 AM, Jonathan Mast
> wrote:
> > So my question is, how do I configure
On Tue, Dec 15, 2009 at 10:48 AM, Jonathan Mast
wrote:
> So my question is, how do I configure the VirtualHost to allow HTTP traffic
> (port 80) and HTTPS traffic (443)?
You need two virtualhosts, one with SSL and one without. If you want
everything other than SSL to be common, use Include to sou
I have a single webserver (1 IP) to which many DNS entries point to. Up
till now I've haven't needed SSL and the following config pattern has worked
fine for me:
ServerName foo.mysite.com
...
ServerName bar.mysite.com
...
However, when I added SSL to to foo.mysite.com, the config had to be