URL aliasing and redirection options?

[Erin Paseka]

Where can I find a writeup of the aliasing and redirection options when a site moves from frontier to the CMS?

Say I've had have site http://www.unl.edu/zzz/ on frontier for ages, I rebuild it in the CMS, and I'm ready for the CMS site to go live. It looks like I have 2 options for my new site's URL: something like http://zzz.unl.edu/ or something like http://unlcms.unl.edu/long-text-string/ ... -here/zzz/ .

1. Can the CMS site instead go live at the same old http://www.unl.edu/zzz/ URL?

2. Or if the site goes live as http://zzz.unl.edu/ , can the old http://www.unl.edu/zzz/ URL redirect to the new site and continue to do so beyond July 1?

Basically my concern is that we need the old http://www.unl.edu/zzz/ URL to continue to get visitors to our content one way or another, not just until July 1, primarily due to other sites linking to us and us having a small stockpile of promotional items printed with our frontier URL.

[saltybeagle]

1. Can the CMS site instead go live at the same old http://www.unl.edu/zzz/ URL?

Yep! This is supported through what we call a proxy pass reverse proxy.

2. Or if the site goes live as http://zzz.unl.edu/ , can the old http://www.unl.edu/zzz/ URL redirect to the new site and continue to do so beyond July 1?

Yes. This is possible too. Al Stark should be able to set up any necessary redirects or proxies when you're ready to go live.