How would you approach setting up 301 redirects within Kentico CMS (v5.0)?
I want to provide a client with an easy way (ideally through the CMS Desk interface) to set up 301 redirects in a website that has recently be re-implemented on Kentico. For example, I would want to redirect “old-page.cfm” to “new-page.aspx”, and ensure that the HTTP response to the original request is 301.
I have an approach that looks like it works, but maybe there is a better way. I configured extensions-less URLs (per Kentico’s documentation) and added a new document alias to the “new-page” document, specifying the “old-page” as the URL path and adding “.cfm” to the URL extensions list. Using Fiddler (HTTP Debugging Proxy) tool, it looks like what I want to have happen is happening: the request for “old-page.cfm” is returning a 301, redirecting to the “new-page” document, and returning a 200 response.
Does anyone know if this is a good approach for setting up 301 redirects in Kentico? Is there a better way? Are there any known drawbacks to using extension-less URLs in Kentico?
I think this is a good approach and I’m not aware of any other way to accomplish 301 redirects without doing what your doing. I’ve used Extension-less URLs in Kentico for awhile now and they work well.