I'm in the process of migrating our main Sitefinity site from IIS6 to IIS7.5, so I started looking at various new things in IIS7+ that I can take advantage of: Integrated Pipeline Mode, URL Rewrite Module, etc. When it comes to URL rewriting, I know Sitefinity has the built in way to provide "other URLs" to any given page in the sitemap. This works great for when I want my /group1/group2/page.aspx
to also be available as, for example, /something/differentName.aspx
. I also noticed that if I want to make a short, EXTENSIONLESS URL to a page, I still have to add the additional URL with the extension into Sitefintiy. For example, if I have:
...and I want it available also as:
... this means that I have to go to Sitefinity, Page properties, add an additional URL of "~/myShortUrl.aspx
". This is a little counter-intuitive to me, but it works (I can type in www.mysite.com/myShortUrl
in the browser and I get the right result). If I'm going wrong about setting that up, please let me know.
Now... If my old, pre-sitefinity site had addresses such as /folder/folder/page.html
, and I'd like them to redirect to the new pages, how would I do that with Sitefinity redirect mechanism? I can't seem to be able to simply add an additional URL of "~/folder/folder/index.html
" and redirect to /group1/group2/page.aspx
So one question is: how would I do that with Sitefinity? Second question is, even if I could do that with Sitefinity, should I perhaps be using the IIS URL Rewrite Module
instead. It seems to be made exactly for this sort of purpose, and although Sitefinity might be able to cover most of those needs, I wonder if I should switch to that. It would also help keep all redirect mappings and short URLs in one place (root web.config).
Has anybody gone through this thought process already and made a decision as to what's best long-term? Thanks.