Why was IIRF created?
Apache has modrewrite, which allows URL rewriting. But IIS, prior to v7, doesn’t have anything similar as a built-in, or as a “standard” free add-on. ASP.NET has a URL mapping mechanism, but it works only for filetypes that are handled by ASP.NET: aspx, ascx, asmx, and so on. For static files or non-ASP.NET files, (xml, gif, jpg, css), the ASP.NET mapping won’t work cleanly. IIS, like the Apache HTTP server, has an extension mechanism: it is called the ISAPI filter. There are commercial ISAPI filters that endow IIS with the ability to re-write URLs. But you have to pay. There are free ones, but they generally don’t offer regular expression matching, or automatic configuration reloading, or other powerful features. IIRF is a small, cheap, easy to use, URL rewriting ISAPI filter that combines a good price (free!) with good features. What does IIRF Look like? How do I use it? IIRF is a single DLL. You install it as an ISAPI Filter on your web server. You configure it with a text-based INI
