* I have managed to get it all set up and RT running OK with named virtual
host over http. However, I am having problems with getting them to work over
https. When I set a virtual host name, it always serves the first listed
domain. See settings below. https:firstone serves the correct folder, but
Each SSL site pretty much needs to be on it's own IP address, the
reasoning is the cert negotiation isn't name based header as apache
would. The only other way would be to have them on different ports but
then you'd have to specify the port when going to the site.
testwreq wreq wrote:
*
I
Actually, I should have mentioned before that our rt installation is on a
different IP.
On Fri, Aug 21, 2009 at 11:09 AM, Curtis Bruneau curt...@vianet.ca wrote:
Each SSL site pretty much needs to be on it's own IP address, the reasoning
is the cert negotiation isn't name based header as
Try naming the virtual hosts. *:443 means any domain that resolves to that
machine will get the first one, since it matches.
Curtis may also be right (never tried two https sites on the same box), but
try having the first one be VirtualHost firstone:443 and the second one
VirtualHost rt:443 and
I tried VirtualHost firstone:443 and the second one Virtual Host rt:443
but still https://rt.hostname.com goes to https;//firstone
While restarting apache, the warning message now was:
[Fri Aug 21 11:20:23 2009] [warn] VirtualHost firstname:443 overlaps with
VirtualHost rt.hostname.com:443, the
On Fri, Aug 21, 2009 at 11:09, Curtis Bruneaucurt...@vianet.ca wrote:
Each SSL site pretty much needs to be on it's own IP address, the
reasoning is the cert negotiation isn't name based header as apache
would. The only other way would be to have them on different ports but
then you'd have to
