Https Redirection
am 02.09.2007 10:26:00 von wilson
I have an ssl.x.com website which is configured with a valid SSL certificate
and a public ip address running on IIS 6.0. Now I need to have a new website
called sales.x.com and needs to be redirected to ssl.x.com, so external user
just need to type https:\\sales.x.com. May I know how can this be achieved?
Do I simply go to the new sales.x.com website Home Directory tab and select
the "Redirection to a URL" radio button? How about DNS setting, is there a
need to change anything?
Re: Https Redirection
am 02.09.2007 10:47:39 von David Wang
On Sep 2, 1:26 am, Wilson wrote:
> I have an ssl.x.com website which is configured with a valid SSL certificate
> and a public ip address running on IIS 6.0. Now I need to have a new website
> called sales.x.com and needs to be redirected to ssl.x.com, so external user
> just need to type https:\\sales.x.com. May I know how can this be achieved?
> Do I simply go to the new sales.x.com website Home Directory tab and select
> the "Redirection to a URL" radio button? How about DNS setting, is there a
> need to change anything?
You will need to provide more information about what exactly you want
to achieve. There are *many* types of redirection, and there are many
logical possibilities to do what you want. You will have to be more
precise.
http://blogs.msdn.com/david.wang/archive/2005/08/01/HOWTO_Co mmon_URL_Redirection_Techniques_for_IIS_Summary.aspx
What you are configuring in IIS6 is one of the simpler redirections,
client-side redirection.
It will make external users see https://ssl.x.com in their Browser's
URL/Location bar (and not https://sales.x.com -- what they typed in).
If that is ok, then what you are doing is fine.
If you want people to see https://sales.x.com, then you want a
different sort of redirection, and you have to do more things for it
to behave correctly.
1. You have to get the server that hosts ssl.x.com to also answer to
sales.x.com. There are many ways to do this, depending on what you can/
want to change
2. You *must* change the SSL certificate of ssl.x.com to also include
sales.x.com, or else users will see security warnings from their
browsers complaining about getting a certificate for ssl.x.com instead
of the expected sales.x.com.
//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//