The challenge with using the DNN redirector is since it is an ASP.NET HTTP Module it can only redirect requests that IIS has mapped to ASP.NET. This requires that the request either end in a file extension mapped it ASP.NET (aspx, ashx, etc.) or it requires that IIS be configured to map ALL requests to ASP.NET.

If you want to do redirects that mimic a folder heriarchy, like http:/www.sitename.com/news (with no file extension), my understanding is, you either have to

1. Use an ISAPI filter

2. Use Custom error pages (as described in this thread)

3. Map all requests to ASP.NET and use the DNN UrlRewrite Http Module or equivelent.

ISAPI filters require a level of complexity and risk I'd like to avoid. Mapping all requests to ASP.NET may cause perofrmance issues so I've tried to avoid it. Presently, we leverage UrlRewrite for short cut urls, but this requres that the request end in a mapped file extension - http://www.wildvoice.com/people/wildvoice.aspx. It is kind of ugly that it requres the extension, so Custom error pages seems like a good compromise approach. http://support.microsoft.com/kb/814869/ seems like a good place to find out more info.

Oh, right.  I should have looked closer at the original post. You do need an extension mapped to ASP.net before the internal DNN rewrite will work.

If you want to do it just based on folders, then I would recommend http://www.isapirewrite.com/, it's an ISAPI filter that does it all.