How can I migrate from my old site to a new DNN site and maintain redirections to our old pages.

I'm hoping that the HTTP Module can acomadate this task however I do not understand how it works,

Basically I want anyone attempting to access a list of old page names.

such as www.oursite.com/myoldnewspage.aspx to be presented with the new page. www.dotnetnukesite.com/default.aspx?tabid=123123518279

You're probably talking about the UrlRewrite HTTPModule. It does not have this capability built in. It's a longshot, but it may also be possible by creating new rules in the siteurls.config file which is the config for the module.

Since this is provider based you could use that one as a model and build your own.

It might be easier and better to just put http transfers with "page moved" in at your old site.
This will help you maintain any search engine rankings you may have had on the old Urls.
Alert you site users of the move, etc.

You could also look into a 3rd party component.. ISAPII rewrite.. I use it for several different applications.. Plan on using it when I migrate to DNN to keep all the urls that I have in google working..

http://www.isapirewrite.com/

Will loading in 150 possible redirects to the URL Rewrite module impact performance significantly?We get alot of traffic and I want to re-build the site so that it is almost transparent to the end-user that we have switched. Therefore not saying anything and quietly redirecting our most popular bookmarked links is something that I would like to do.

I concur, Shad... not everything has to be a function of DNN. Since you have control over your hardware, an ISAPII solution would be most efficient/effective.

Great Thanks, I will concur as well. :)

I posted this in the core forum before, apologies for not posting here. We are investigating alternate methods of making more human friendly URLs.

For example, if you wanted a page to be called www.dotnetnuke.com/Modules.aspx, you could add an entry to SiteUrls.config

<RewriterRule>
<LookFor>.*Modules.aspx</LookFor>
<SendTo>~/default.aspx?tabid=1</SendTo>
</RewriterRule>

Make sure its the first in the list.

Thanks,

That is what I wanted to hear.

There are a lot of hosts out there that also have this filter installed on their hosting servers. Ask around, your provider may already have it installed.

As for performance, I had Google slam my amazon.com shopping site that uses the rewrite engine and it didn't even flinch.. perl on the other hand.... I wouldn't worry about performance...

I posted this in the core forum before, apologies for not posting here. We are investigating alternate methods of making more human friendly URLs.

For example, if you wanted a page to be called www.dotnetnuke.com/Modules.aspx, you could add an entry to SiteUrls.config

<RewriterRule>
<LookFor>.*Modules.aspx</LookFor>
<SendTo>~/default.aspx?tabid=1</SendTo>
</RewriterRule>

Make sure its the first in the list.

I tried this but it came up with a 404 error.
Would it matter if the url was an .asp page?

I'm not opposed to the url re-write, but I think the dnn method is more portable.

Why not rewrite the '404/page not found' this way there will be no performance loss to any correct urls. Just write some sort of filter/redirect into the page not found for known urls.

When you get the 404, what is the url in the browser? Does that page actually exist?

I'll have to try it, but I don't think you can use an external site/page in the SendTo field of the SiteUrls.config.

The HTTP handler lets those requests continue to be processed by DNN without doing a redirect as far as I know.

Actually, if you leave it for IIS to handle the 404 there is a performance hit. Better to catch it before the error.

Our Old site has a page under /state_cup/default.asp

so under DNN in the SiteURL.config file I added (with the proper syntax and spelling of course.)

<LookFor>/state_cup/default.asp</LookFor>
<SendTo>/default.aspx?TabID=67</SendTo>


And when I browse to http://dnn.mysite.com/state_cup/default.asp I get the 404 page does not exist error.

How does the URL module Intercept the request? If it is not looking for an ASP.net page how can an ASP.net handler redirect it? My question is should it work, and if so then I will keep at it. If not then I'll go to another component.

That should work because you are sending to a dnn tab in the app.
The HTTP Module works on application_begin request it's not looking for a specific page.

The LookFor is a Regexp so try adding a backslash in front of that last period.

<LookFor>/state_cup/default\.asp</LookFor>
<SendTo>/default.aspx?TabID=67</SendTo>