We seem to have run into a problem with our SSL scheme.
We have multiple web sites (www.site1.com, www.site2.com, www.site3.com) and
need to run SSL pages on each site (for credit card purposes).
The problem is you can't set up multiple sites in IIS with the same SSL
port, it seems.
What we did was create a port for each site (https://www.site1.com:4433,
https://www.site2.com:4434, https://www.site3.com:4435 ) and this seemed to
work.
We just found out that if you have an ISA Proxy server, you will get a 502
error.
We are having connection issuse using secure connection if we hit a site
with an ISA Proxy server. Not sure if other proxies would have this problem.
I had a friend at Microsoft try to access our secure pages and he got a 502
error. I had another friend try it and he got the same error. Both had an
ISA Proxy server. When my other friend went around the Proxy server, it
worked fine.
I got the following from googling:
***************************************************************************************************************************
"Error 502 returned by a HTTP proxy (Proxy Error (The specified Secure
Sockets Layer (SSL) port is not allowed. ISA Server is not configured to
allow SSL requests from this port. Most Web browsers use port 443 for SSL
requests.))."
This is caused by the default behavior of Microsoft ISA server, which only
allows requests to ports 443 and 563 using its HTTP Connect method. (Primary
use of HTTP Connect is to allow SSL connections to HTTPS servers).
The Microsoft Knowledge Base article Q283284 addresses this issue.
To access FTP sites through ISA server's HTTP proxy, access to all ports
must be allowed. FTP's control connection port is 21 by default, but data
connections can use virtually any port, because it is assigned by the FTP
server. (Although allowing port 21 and ports >1024 should be enough, there
might be exceptions.)
To allow connections to all ports through the HTTP proxy, following VB
script must be run on the ISA server:
set isa=CreateObject("FPC.Root")
set arraypolicy=isa.Arrays.GetContainingArray.ArrayPolicy
set tprange=arraypolicy.WebProxy.TunnelPortRanges
set tmp=tprange.AddRange("FTP", 1, 65535)
tprange.Save
***************************************************************************************************************************
We are also using SiteUpTime.com to test our pages, periodically. Everything
was fine until Sunday. Since then it can't see the pages. I assume something
changed on their end but can't be sure until we hear back from them.
The problem is we need to solve the issue if this is going a problem with
some of our clients or potential clients.
The only other way we can see to solve this problem would be to put a
different server in for each web site. This would be pretty expensive and
would like to get around that if possible.
I don't think we can ask our potential clients to change their Proxy Servers
to allow our pages in.
Any other ways around this?
Thanks,
Tom