Posted: 11 July 2008 at 4:53pm | IP Logged

Re-mapping the url is relatively simple.  The problem is with application management.

If you map www.abc.com to its actual virtual directory application location of www.xyz.com/abc, is the application served from www.xyz.com or www.xyz.com/abc?

Using an HttpModule for a redirect works fine, but the user is shown the new url www.xyz.com/abc. Using Http Rewrite seems to remap the url o.k. and shows the user www.abc.com, but the application is served from www.xyz.com and it treats /abc as a subdirectory rather than an application.

With ISAPI Rewrite (as an ISAPI filter), will the application be served from the virtual directory application while the user (and search engine) still sees the www.abc.com url facade?

I know you have a try-before-you-buy policy, but I would need to change my hosting facility before I try.  I would like to know if this problem can be solved with ISAPI Rewrite.

Can anyone offer advice?

Posted: 30 July 2008 at 2:07am | IP Logged

I am also a newbie on this subject and am trying to understand what wromee wants to do as I think I have a similar issue.

In my case I have a local site with specific folder and I want users to be redirected to another website on my local server. The steps I did and script I wrote is as follows:

first after opening the Helicon Manager I clicked on the specific site folder under the IIS Web Sites (Folder Named Intranet). Then I edited the .htaccess file in it and wrote the following

I want users who type http: