RE: HTTP to HTTPS and HTTPS to HTTPS
- From: "Steve Moffat" <steve@xxxxxxxxxx>
- To: "ISA Mailing List" <isalist@xxxxxxxxxxxxx>
- Date: Wed, 23 Feb 2005 18:16:19 -0400
1. The host headers are for ISA's benefit and DNS's benefit, nothing to
do with having them working.
2. No idea, but I wouldn't think so.
-----Original Message-----
From: Andrew English [mailto:andrew@xxxxxxxxxxxxxxxxxxxxxx]
Sent: Wednesday, February 23, 2005 5:57 PM
To: ISA Mailing List
Subject: [isalist] RE: HTTP to HTTPS and HTTPS to HTTPS
http://www.ISAserver.org
Honestly Steve you shouldn't have to use host headers under Windows 2003
Server. I have 4 websites on my web server which work with nothing but
IP's.
My question about redirection, is there anyway to fool ISA into
redirecting port 80 HTTP traffic to another server on the same name and
letting RPC do its own thing when the right moment comes along?
Andrew
-----Original Message-----
From: Steve Moffat [mailto:steve@xxxxxxxxxx]
Sent: Wednesday, February 23, 2005 4:37 PM
To: [ISAserver.org Discussion List]
Subject: [isalist] RE: HTTP to HTTPS and HTTPS to HTTPS
http://www.ISAserver.org
Wooooohhh.at last you grasp the concept....
Add another IP address on the exchange or IIS webserver, use that ip
for the new site...give it a host headername....create the dns entry for
it.....create a publishing rule for it....hey presto it works.
<snip>
The haggis is unusual in that it is neither consistently nocturnal nor diurnal,
but instead is active at dawn and dusk (crepuscular), with occasional forays
forth during the day and night.
Other related posts:
