301 Redirect for multiple host names

You may have your site working with and without the www in front.  For SEO purposes you may also want to make sure that it is not counted as duplicate content.

For SEO, the redirect should be a "301 Moved Permanently".  Here is the code you would need.

< script runat="server">
PrivateSub Page_Init(ByVal sender As System.Object, ByVal e As System.EventArgs) HandlesMyBase.Init
      If Not Request.Url.Host.ToLower().StartsWith("www") Then
        Response.Status = "301 Moved Permanently"
        Response.AddHeader("Location", Request.Url.Scheme & "://" & "www." & Request.Url.Host & Request.Url.PathAndQuery)
        Response.End
     End If
EndSub

< /script>

I recommend putting it in the skin for the home page so it only works on the specific portal.

If you put this in the default.aspx page, then this will only work if you are not using other host names as the Portal Alias for different portals.

If you are using other portals with different host names then you could also make the code above be more specific.

Hi Shane,

There are many answers to this question so bear with me.

If you are wanting to re-direct from a .HTM extension then you would need to assign that extension to ASP.Net to get a DNN module to recognize it.  This is not the most optimal thing to do but it is possible.

If you have control of the server and you want to keep from mapping .htm files to the ASP.Net pipeline you can use an ISAPI filter.

http://www.isapirewrite.com/  is a good one for this purpose that gives you all the flexibility of the Apache mod-rewrite.

In IIS7 Microsoft has taken us closer to the Apache world and is making it possible for developers to plug-in ASP.Net HttpModules to the IIS system.  What this means is that you won't need to have control of the server to do what the ISAPI Rewrite filter does now.

Ok, back to the code above.  It is something that you can paste into an ASP.Net page (.aspx), or an ASP.Net User Control (.ascx).
The main drawback is that it will not work with .htm extensions unless the Asp.net application mapping mentioned earlier is configured in IIS.

Last, but certainly not least, my PageBlaster module will have this functionality in the near future.

Unfortunately my "near future" usually turns out to be more than 30 days.

Do you have access to change your website settings in IIS so that you can have virtual page names with an HTM extension be handled by ASP.Net? If so, then the current version of PageBlaster can handle delivering your pages without doing a 301 redirect. You can give them virtual names like myfirstpage.htm and the content delivered could be from the new DotNetNuke page automatically.

 Asp.net application mapping has the procedure, but it is for a wildcard mapping.  All you really need is to add a mapping to .htm files if you want to use that extension.

We use a module DS-trafficDirector. It is nice for multiple domainnames to the same content.

Peter

Hi - like the the look of this but I have a question...

Is there any way to redirect using the whole URL? When I use this script to redirect this:

http://mysite.com/gff/FitnessCoursesCatalogue/FitnessInstructorCourses/Level2CertificateinFitnessInstructingExerc/tabid/131/Default.asp

I want to achieve this:

http://www.mysite.com/gff/FitnessCoursesCatalogue/FitnessInstructorCourses/Level2CertificateinFitnessInstructingExerc/tabid/131/Default.asp

But what I actually get is this:

http://www.mysite.com/Default.asp?TabId=131

Thanks