A
Andy
I have a web server with 2 domain names, one IP and a single SSL cert.
Domain name one has the SSL cert, but domain name two doesn't.
domain name one is the actual domain name of the server, domain name two is
more of an alias to one site on the server. Therefore, a url on domain name
one and another url on domain name two actually point to the same site.
so http://www.domainnameone.com/some/long/site points to the same place as
http://www.domainnametwo.com
The site on domain name two requires secure transactions of passwords and
user names (via form authentication and LDAP). However, this is the only
secure transaction required. Everything else doesn't need to be secure.
Howeer, is it possible to some how piggyback on the SSL cert of the first
domain name, pass the transaction securely, yet not have the web browser of
the users complain that the domain name doesn't match?
Domain name one has the SSL cert, but domain name two doesn't.
domain name one is the actual domain name of the server, domain name two is
more of an alias to one site on the server. Therefore, a url on domain name
one and another url on domain name two actually point to the same site.
so http://www.domainnameone.com/some/long/site points to the same place as
http://www.domainnametwo.com
The site on domain name two requires secure transactions of passwords and
user names (via form authentication and LDAP). However, this is the only
secure transaction required. Everything else doesn't need to be secure.
Howeer, is it possible to some how piggyback on the SSL cert of the first
domain name, pass the transaction securely, yet not have the web browser of
the users complain that the domain name doesn't match?