Thanks for the article, really informative. One question. You had the following statement in the article:
"For example, when the user types www.internal.net/web10 into the browser, the request arrives at the Incoming Web Request listener and is passed by the Web Proxy service to the Web Publishing Rules. The Web Publishing Rule says to redirect the request to http://10.0.0.10/web10 on the internal network (actually, the rule says to pass the request to http://10.0.0.10, but the ISA Server always preserves the path when it performs the redirect)."
Is it possible to have ISA Server not preserve the path?
For example: If I create a web publishing rule as follows
Published destination: external.mysite.com
Redirected internal web server: internal
It will work fine
If I create a web publishing rule as follows
Published destination: external.mysite.com/web1
Redirected internal web server: internal
It will search for a web1 directory on the "internal" web site and it is not possible to redirect the requests to any other path on "internal"
Thanks for the compliments on part one. I hope you like part 2, which will be up tomorrow.
You are at the crux of the problem. ISA Server will not redirect to the root, and you can't configure ISA Server to redirect to a particular path. You can only configure it to redirect to a server name or IP address; the path is always preserved. That's the reason for the primary and redirect Destination Sets and Publishing Rules.
Thanks Tom. One other idea we were tossing around is that you could redirect to a unique web site (host header or ip based) on one server and have the root of the web site configured to match the desired redirected path for that request. It would require a unique web site for every unique path, not ideal, but potentially doable.
The unique Web site would work just fine. In the article I use a redirect to the same site, but you can certainly redirect to the root of any Web site you wish.
Please correct me if I'm wrong. If I want to use SSL and use this approach to redirect, I would need multiple SSL certs as well as multiple addresses to tie them too, correct?
RE: Publishing Multiple Web Roots with a Path Statement... - 7.Oct.2003 12:39:00 AM
Guest
quote:Originally posted by tshinder: Each site needs a certificate,
Really annoying that.... It would be nice to be able to build a simple 'reduced-TCO' case around publishing multiple secure sites using only 1 SSL certificate.
I guess the only way around it would be to change the structure of the web applications.
Fingers-crossed that the functionality from Proxy 2 makes it back into Stingray!
RE: Publishing Multiple Web Roots with a Path Statement... - 13.Jul.2004 5:16:00 PM
Guest
Thanks for the white paper, very informative. Just curious if you have any idea how difficult it would be to build an addon to ISA that would do path redirections. Thanks Richard
Hi I am not an expert in ISA. This site helped me a lot to get to know more about ISA, especially Tom's articles, thanks a lot.
In the end of your first part's, you mentioned that "The next step is to create the Web Publishing Rule for the redirect." But the second part didnt mention anything regarding this!?