We have a legacy ASP.NET website in which complex redirect rules are coded in Global.asax. Actually this logic processes requests with several optional or variable parts like
{http|https}://[www.]ourdomain.com/[Home/]Products/old-product-name/page.aspx
and redirects them to
https://ourdomain.com/new-product-name/
Theoretically this logic can be rewritten with a set of rules for the IIS URL rewrite module. I am considering this approach for two reasons. First, this should simplify the redirect logic as it will be written as a set of declarative rules. Second, we need to add more and more redirect rules, and it will be simpler to do this in the format of the URL Rewrite rules.
The question: does it make sense to rewrite our redirect logic with the URL Rewrite module? Can it lead to performance degrade and the like? Or maybe, the best way to do what we need is to use Global.asax together with the URL Rewrite rules, coding complex rules in Global.asax and using URL Rewrite for simple redirects?