Welcome to ISAserver.org

Solution for automatic HTTP to HTTPS redirection

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [ISA Server 2000 General] >> Web Publishing >> Solution for automatic HTTP to HTTPS redirection

Page: [1]

Message

<< Older Topic Newer Topic >>

Solution for automatic HTTP to HTTPS redirection - 1.Nov.2004 3:47:00 PM

Guest

I was tasked with setting up an ISA 2000 server to do secure OWA 2000 publishing for a client. The client would only accept a solution where external users could type "webmail.clientdomain.com" into IE and be redirected to https://webmail.clientdomain.com/exchange. ISA, and internal webmail users, would make a cleartext connection to Exchange. The client had an internal AD domain called clientdomain.com and an internal DNS entry for webmail.clientdomain.com pointing to Exchange.

The SSL to HTTP bridging and OWA publishing parts are fairly well documented here and elsewhere, but I didn't like the ideas for using error pages or ASP scripts and I couldn't get anywhere with link translation. Here's how I got it to work.

1. Set up external DNS to point webmail.clientdomain.com to the external IP of the ISA server.
2. Changed the ISA HTTP listener to run on port 81.
3. Created a protocol rule called "HTTP for OWA" using TCP 80.
4. Created a server publishing rule called "OWA Redirect" that redirected TCP 80 on the ISA external IP to the ISA internal IP.
5. Created a packet filter to permit HTTP traffic inbound to the ISA server.
6. Enabled IIS on the ISA box on port 80 on the internal IP.
7. Set the default web site on IIS to hard redirect to https://webmail.clientdomain.com.
8. Added the / path to the OWA destination set.
9. Set the default web site on the Exchange server to redirect to /exchange.

This lets:

- Internal users go to "webmail.clientdomain.com" and get redirected to http://webmail.clientdomain.com/exchange.
- External users go to "webmail.clientdomain.com" and get redirected to https://webmail.clientdomain.com, which is then redirected to https://webmail.clientdomain.com/exchange by the Exchange server.

It's a bit hackish and I'm sure there are better ways to do this, but it worked for me.

Post #: 1