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

I will try it…but some examples and information etc. particularly for the DNN stuff would be very helpful.

I’ll email back after I have tried it out a little.

Thank you, Tom

For an ASP.NET application like DotNetNuke (DNN), Transformer.NET will work seamlessly on both IIS6 & IIS7. The only prerequisite would be that you will need to make a couple of entries into your web.config file (I presume you should have the ability to do this in the shared environment).

Here are a couple quick shortcuts to get it working (full documentation / user guide is included in the Zip download):

1 - Add the following entry under the <configSections> area of your web.config:

<section name="transformerConfiguration" type="Transformer.Net.Config.Options" />

2 - Add the following section as a child node of the <configuration> element of the web.config (you should be able to add this section directly after the closing </configSections> tag):

<transformerConfiguration logToBrowser="true" logLevel="Low">

</transformerConfiguration>

NOTE: You will need to add some Rewrite Rules within this section after you get it working based on your specific re-writing objectives

3 - Add the following entry under the <httpModules> area of the web.config (under <system.web> for IIS6). Note that to avoid conflicting with other DotNetNuke HttpModules, you should make this the *first* module in the list.

<add name="Transformer.Net" type="Transformer.Net.CoreModule, Transformer.Net"/>

4 - Test the installation by making a request to one of the DNN pages. You should see some Transformer.NET log entries appended to the bottom of the page.

5 - Generate Rewrite Rules. There are a number of re-write rules you can create depending on your intention here. These rules are defined within the <transformerConfiguration> web.config section we created in step 2. I would suggest consulting the User Guide (included in the Zip download) for specifics on how to do this since it will really vary depending on your objective. If you are familiar with the general syntax used by mod_rewrite, then you should be in good shape.

Hopefully this helps out. Once the rules are working as intended, you should disable all logging by setting logToBrowser=”false” logLevel=”Off” within the root “transformerConfiguration” element. If you let me know your specific objectives (i.e. what you are hoping to accomplish with the re-write rules) I would be happy to help you come up with some specific rules if you are having problems. Feel free to post back here or send an e-mail to our tools e-mail alias.

What are the installation pre-requisites?

If this is for IIS6, and if it can be used on shared ASP.NET hosting, would you please provide specific, detailed nformation about how to use this to create DotNetNuke friendly URLs??

Many people would find this very useful, since DNN’s built-in friendly URLs has a lot of issues with spaces and special characters.

There are a couple other ones out there for DNN, but they require being able to change IIS configs on the webserver, which most people with shared hosting can’t do.

Thank you, Tom