I’m not 100% sure if I understand the second case, but I think you are saying it’s the same as the first case, but in various sub folders?

If so, then try removing the starting regex anchor ^ from the beginning of your existing rules. Let me know if this makes sense or if I mis-understood. Posting an example with some specific URLs might also be easier.

ruleid=”101″ direction=”in” from=”^/content\.aspx?content=(\w+)$” to=”/content.aspx?content=$1″

ruleid=”102″ direction=”in” from=”^/(\w+)\.aspx$” to=”/content.aspx?content=$1″

ruleid=”206″ direction=”out” from=”^/content\.aspx\?content=(.*)” to=”/$1.aspx”

END

Rocks!

I have 2 in/out cases I need to set up. The objective is to mask dynamic template pages and also to map legacy pages that are now dynamic to their original static urls.

First case is handled, in which the ‘page’ is in the root folder. The rules are like this, where the page id is either an int or a string:

IN 102 works for string, ie. home.aspx -> pageid=home
OUT 206 works for numeric & string, ie. pageid=93 -> 93.aspx & pageid=home -> home.aspx

Second case I have to add arbitrary folder paths to the the 1st case. Any suggestions?

When I search for ‘transformer.net’ your site doesn’t come up. I go to the iis.net link, which links to your site. Is it your search tags? One of the resources to get listed is sitemap.org. Google sponsored this standard, you can use it to get them to index your site – the way you want them to.

Cheers!

I’m using IIS 6.0 with w2003 R2 SP2

I would of liked to try this module.

Thanks anyway

Based on your post, I would guess they should look something like the following:

<add ruleid="in-1" direction="in" from="^/(.*)\.htm$" to="/dir1/file.dll/$1" />
<add ruleid="out-1" direction="out" from="^/dir1/file\.dll/(.*)" to="/$1.htm" />

This, of course, is just a guess based on the limited amount of information you provided. You’ll notice above that I added the “.htm” file extension to the re-written URLs. This is because without the “dir1/file.dll” portion of the URL, there is nothing left to uniquely identify the requests that need to be routed to the DLL vs any other request (like one for a .gif image). Assuming there are no .htm files on your server, this rule will properly route all .htm requests to the DLL.

If you are running on IIS6, you might be out of luck with the outbound URL re-writing. HttpModules on IIS6 only seem to have access to the response stream for managed handlers (aka .NET) and not other handlers. In either case, I hope this helps.

I have a situation where a sw application company sold us a web based app that has a home page URL of http://www.company.com/dir1/file.dll/home. (sheesh…)

They won’t modify the configuration because they consider it “customization” and will charge extra do it.

I need to be able to rewrite browser requests and responses to “hide”
the /dir1/file.dll/ part of the URL, so the new home page would be http://www.company.com/home and all browser responses would not contain the /dir1/file.dll/ part of the URL.

I already do this for external(internet) browser users with a reverse proxy server but the proxy is bypassed for internal (intranet) users.

1. Will this work for this application?
2. Will it work wil SSL?
3. Do you have a rule to share that I could use for testing?

Thanks