On Mon, 2003-03-17 at 16:40, Andre M. V. wrote: > What you can do is companies domains will > be redirected to your domain like below. > > https://www.yourowndomain.com/company1 > https://www.yourowndomain.com/company2 > https://www.yourowndomain.com/company3 > > I know it's kludgy...
Yes it is, and I don't think clients would be happy with that setup. :P > You mean reverse proxy supporting SSL? > that will work, have done it too... but > what exactly are you going to do? I dunno about proxy, but I guess it's something similar to the IPTABLES NAT, since it seems to behave in the same way. The setup: server is inside a firewall with 1 internal ip. 1 external IP points to this internal ip. Server hosts many sites/domains, and WILL have more than 1 SSL-enabled site/domain. (1 SSL cert per domain, of course). Name-based vhosting is currently enabled with no problems whatsoever. It's the addition of SSL that poses a problem. I did some further reading, and as far as I can tell, the issue about the IP addresses resides on the client (browser). That, if a browser has already mapped the IP address with a particular SSL certificate, it won't allow any other certificate with the same IP address. Thanks! -- Joon Guillen ================================ So computers are tools of the Devil? thought Newt. He had no problem believing it. Computers had to be the tools of _somebody_, and all he knew for certain is that it definitely wasn't him. from "Good Omens", Neil Gaiman & Terry Pratchett _ Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph To leave: send "unsubscribe" in the body to [EMAIL PROTECTED] Fully Searchable Archives With Friendly Web Interface at http://marc.free.net.ph To subscribe to the Linux Newbies' List: send "subscribe" in the body to [EMAIL PROTECTED]
