Hi,

I have next problems with old (non dnn website) conversion:

www.tennisplanet.com  is currently in use and build in classic asp. However, now we have running www.tennisplanet2007.com. It seems to run stable, so we want to start using the actual url: www.tennisplanet.com. Since SSL is used, I will install new certificate, but I have the idea that by leaving the portal alias www.tennisplanet2007.com the SSL will not work. It will work, but in SSL mode not. Is there a way to configure DNN so that www.tennisplanet2007.com becomes automatically www.tennisplanet.com ? A kind of HTTP filter doing this conversion would be great?

Second issue is about classic asp. Links are like,www.tennisplanet.com/index.asp  . How can I configure DNN or IIS to keep all those links working if I have www.tennisplanet.com/default.aspx ?

Any help appreciated.

S.I.

The file siteurls.config is what you are looking for.  It is also managed on the Host Settings page under "Friendly URL Settings".

This file uses regex to manipulate page requests... so you can do just about anything with it that you want if you can get a proper regex string.  I imagine you are looking for something similar to:

    <RewriterRule>
      <LookFor>(.*)tennisplanet2007.com(.*)</LookFor>
      <SendTo>$1tennisplanet$2</SendTo>
    </RewriterRule>

This should successfully convert any link from the one domain to another (BOTH aliases need to be valid in your list).  So...

http://www.tennisplanet2007.com/fr/tabid/890/Cc/SS/St/0/Chaussures/Default.aspx would become:
http://www.tennisplanet.com/fr/tabid/890/Cc/SS/St/0/Chaussures/Default.aspx (will take care of https also)

If you run this as a test, you will notice that you do not appear logged in when the switch occurs... this is because of cookies.  But this should not be a problem in production as you will never login under tennisplanet2007 again.

Cheers

Scott Willhite, Co-Founder DNN

There is nothing special being done here to attend to SEO implications.  It is a straight translation from one url to the other peformed by the http handler.  Since the handler is not smart enough to understand the nature of the translation, it does not do anything like send back a 302.  It might be an interesting modification to the handler, however, to add this as an option for each translation configured.

Scott Willhite, Co-Founder DNN