08 Oct 2007
01 Mar 2012
Link to this post
I'm trying to implement some URL rewriting rules in order to handle some customized URLS for our site. The pattern is pretty simple: http://www.site.com/12345 redirects to http://www.site.com/details/itemdetail?ID=12345. The redirect itself works great, but it seems to get in the way of all of the other paths that Sitefinity already handles. For example, with that rule in place, if I go to http://www.site.com/buy, the same rule intercepts, tries to redirect, and I get a server error. Since the rest of the page tree isn't technically a directory or a file, the IsFile and IsDirectory conditions fail to kick in to tell it to skip. The only thing I can think of is to hard code all of the first-level paths in the site in the match, but that seems to be a total pain and way too much work for a straightforward setup.
Is there any way to program it to tell the site to handle Sitefinity's rewriting rules first, and if those fail, then process the other rules? Or is there another configuration that will work in order to accomplish this goal?