I am new to ISA (Linux/Unix background). Will be brief and to the point. I need to
configure the ISA box to do SSL to HTTP bridging. Basically, we have a backend database
that also runs a webserver on it on port 80. I built a Linux caching box which talks to the
webserver (also port 80). I need ISA (sits on the DMZ, one NIC in it) to take an SSL
request and bridge it to HTTP 80 to the Linux box, which, in turn, will talk to the
webserver on the database. For some reason, ISA box is not doing that.
I am not sure what is going on, but I have been on isaserver.org, newsgroups, etc – here
what i have done – built win2k server (all service packs…), installed isa, requested a SSL
certificate from Verisign, installed it,imported it into ISA – it says it is ok. Firewall
on ISA is disabled for now, all traffic is allowed (HTTP, HTTPS, HTTPS Server in
particular), web publishing rules point to the Linux caching box (I even bypassed Linux and
went straight to the webserver – same result), http requests are being redirected as http,
ssl is redirected as http, certificate is configured, destinations are set – when I type in
the browser http(s)://ipaddress.of.isa.box(i can’t do a dns name yet for production reasons)
from a client machine – it returns http 502 proxy error saying that The Uniform Resource
Locator (URL) does not use a recognized protocol. I hooked up the sniffer and put everything
into a hub – all I see is client making a request and isa returning the error. Isa is not
talking to anybody else. I can connect to ISA on port 80, 443 just fine. I must be missing
something very basic. ISA is just sitting there doing nothing with the request. Can anyone
decipher my convoluted scenario and push me in the right direction? What am I missing?