I have a site due to go live imminently, but I need to arrange redirects from the old site URLs to the new ones. The old site was a mixture of plain HTML pages and 'classic ASP' pages ('.asp').
I have a spreadsheet of old URLs mapped to new URLs and am looking to set these up as redirects now. I've tried redirecting on a previous site, using the Umbraco URLRewriting.config file, but had major issues with it not working for '.htm' files (I had to do some updates in IIS to pass .htm files through the .NET processor, which then created major problems with the functioning of Umbraco itself). As a result, I'd prefer to use ISAPI rewrite, which is installed on the server. Question is, if I use ISAPI Rewrite will it have any side-effects on the website, or can I just run it confidently without risk of anything going wrong?
I use ISAPI_Rewrite on several client sites, (with Umbraco), had no problems with it! As long as the rules in your .htaccess file don't conflict with UrlRewriting, all should be fine!
Is there a reason why you don't use the built-in config file for rewrite rules?
/config/UrlRewriting.config
<urlrewritingnet xmlns="http://www.urlrewriting.net/schemas/config/2006/07"> <rewrites> <!-- Urlrewriting.Net is a cool tool, what can make your urls look nice. The rewriting is controlled with regular expressions. To get more help look at http://www.urlrewriting.net/.
This sample is usefull for a productpage, where the product comes from a dynamic datasource, e.g. a database. The querystring "productid" can be loaded from the template, into a macro, that then loads the product!
Any bugs or problems with the rewriter, contact Anders/Duckie --> </rewrites> </urlrewritingnet>
ISAPI rewrite and Umbraco
Hi,
I have a site due to go live imminently, but I need to arrange redirects from the old site URLs to the new ones. The old site was a mixture of plain HTML pages and 'classic ASP' pages ('.asp').
I have a spreadsheet of old URLs mapped to new URLs and am looking to set these up as redirects now. I've tried redirecting on a previous site, using the Umbraco URLRewriting.config file, but had major issues with it not working for '.htm' files (I had to do some updates in IIS to pass .htm files through the .NET processor, which then created major problems with the functioning of Umbraco itself). As a result, I'd prefer to use ISAPI rewrite, which is installed on the server. Question is, if I use ISAPI Rewrite will it have any side-effects on the website, or can I just run it confidently without risk of anything going wrong?
Thanks all.
Hi Dan,
I use ISAPI_Rewrite on several client sites, (with Umbraco), had no problems with it! As long as the rules in your .htaccess file don't conflict with UrlRewriting, all should be fine!
Cheers, Lee.
Cheers Lee - did it and it worked a charm.
For reference, if anyone's interested, the syntax for this kind of thing in the .htaccess file is like this:
ISAPI_Rewrite is fine, but has a free and commercial version.
If you are on a budget, you may try Ionics Isapi Rewrite Filter, which is OpenSource.
You can find it on Codeplex: http://iirf.codeplex.com/Wikipage
Is there a reason why you don't use the built-in config file for rewrite rules?
/config/UrlRewriting.config
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.