I could not get it to work that way either, so here is what I did that
My rainbow is no longer the root application I put a redirect
in the root folder so that all hits do a redirect to a virtual directory like
mike.domain.com default.asp sends all default :80
traffic to mike.domain.com/myportal
Now I have no .net application at the root level so I am make
all my applications run in virtual directories. so my ssl will work with them
because the domain is correct.
I don't recall if I call my applications from within rainbow any
more though. I do open new browser window.
Hope this is helps you some
Director of Computer Information Services
27210 College Road
Centralia, IL 62801
>>> firstname.lastname@example.org 5/20/2005 17:38:12 >>>
Has anyone gotten a virtual directory application to work under
Here's the scenario:
Rainbow is set up as a Web Site in IIS with it's own IP address.
I have multiple Portals running
I have another web application that I would like my users of the Rainbow
Portal to use by accessing it from their domain name. For example:
A main concern with this is SSL certificates. I know that I could just
redirect to another url, but I want to use the same cert for both
I've already tried just defining a Virtual Directory under the Rainbow web
site in IIS, but when I try to get to the Virtual Directory it either hangs or
gives me a "Rewrite.net.dll not found" error.
I'm looking further into this, but any pointers by someone who's gone down
this path would be helpful.