|
From: Barry <we...@i1...> - 2006-03-27 21:26:34
|
I wonder if you cold have multiple https listening ports on inside addresses (192.168.x.x for example), and then proxy/NAT to those *at the firewall* to those ports, based on the domain name or the request somehow? Best, Barry Kris Deugau wrote: > Ravi Gehlot wrote: >> When you say “not effectively” you mean it wouldn’t work? > > In short, no. > >> If I could type on my browser http://www.thataddress.com/ and have it >> proxied to http://www.thataddress.com:8080/ > > That would work fine for HTTP (please note, NOT HTTP*S*!) because the > browser has a chance to send the domain/site address it's looking for > before it sets up the SSL layer. But then with standard HTTP you > don't need to bother with multiple ports because that mechanism is > available in the first place. > |