Hi,Thanks for that. Unfortunately, even after the changes, entering domain2.com on a browser still goes directly to domain1.com.No, I don't have any intention to do SSL on domain2.com. Is this causing a problem?D.Le 1 octobre 2013 à 17:29, Nick Tkach a écrit :Well, question is, are you trying to have domain2.com *also* do that same http->https ( http://domain2.com to https://domain2.com )? If so, do you have separate certificates for each (domain1 and domain2)?
On Tue, Oct 1, 2013 at 10:36 AM, Pete Houston <ph1@xxxxxxxxxxxxxxxx> wrote:
On Tue, Oct 01, 2013 at 04:25:05PM +0100, John McIntyre wrote:No, you are almost there. The problem is that for some reason you have
> Am I doomed to failiure, or is what I'm trying to do, actually possible?
an asterisk in your VirtualHost declaration for domain2. Change that the
the actual IP address (or hostname since you're using that for the
others) and you should be fine.
I'd also swap out the asterisk the NameVirtualHost directive too.
HTH,
Pete
--
Openstrike - improving business through open source
http://www.openstrike.co.uk/ or call 01722 770036 / 07092 020107