httpRedirect and IIRF order of execution

Topics: User Forum
Nov 9, 2012 at 4:33 PM

I have installed IIRF at the global level so it applies to all sites on IIS7. I have a website which uses httpRedirect in the site web.config to redirect URL's for specific non-existent content to pages that do exist. For pages that do not exist at all and have no specific redirect I want IIRF to redirect to a third party site that may hold an old version of the content (effectively a catch all rule). The IIRF rule has some RewriteCond logic which isn't supported by httpRedirect.

The problem is that IIRF rules appears to execute before IIS' httpRedirects. Is there any way to change the execution order?

Thanks in advance,