Ionics ISAPI Rewriting Filter 1.2.14

IIRF is a small, cheap, easy to use, URL rewriting ISAPI filter


BSEditor: IIRF is a small, cheap, easy to use, URL rewriting ISAPI filter that combines a good price (free!) with good features. It is reasonably fast, and reasonably powerful. You can get the source code to inspect it or modify it yourself if you desire. If you use IIS, you can download IIRF and get started right now. Or, Visit the IIRF Forums to ask a question.
Why Rewrite URLs?

Server-side rewriting of URLs means a URL like http://foo/bar/bam can be translated, on the server, into http://foo/baz/bam.jsp or http://foo/something/dispatch.cgi?q=bam or http://bam/hello/foo.aspx or... anything! The browser is none the wiser.

Rewriting URLs on the server-side goes way back. It has a bunch of advantages:

* you can use pretty URLs ("Search-engine friendly", "Search Engine Safe" (SES), or "Search-Engine Optimized" (SEO) URLs), with web application platform infrastructure that uses or generates ugly URLs. Some web or portal servers are notorious for generating ugly URLs, but you dont need to expose them to the world.
* URLs can stay pretty, even if you change the server-side system (eg, dispatch.fcgi instead of .cgi, or .aspx instead of .jsp).
* you can migrate or modify sites, without stranding old links.

Its really convenient with Cold Fusion, PHP, Ruby, Joomla, ASP.NET, JSP or any number of other server-side technologies these days.
Why was IIRF created?

Apache has mod_rewrite, which allows URL rewriting. But IIS doesnt 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 wont work cleanly.