Hi all, Usually it's not possible to use name-based virtual hosts for SSL connections since the well known chicken-egg problem (at least if I understood the FAQ correctly). My question would be if there is some way of "emulating" this if one has a server which uses virtualization to run different hosts (or a server running SSL-aware hosts no different ports). Imagine this server having two external non-RFC1918 IPs and a large number of internal RFC1918 IPs, however no access to change the DNS for differently named-hosts for the outside world. Is there a tricky way to use rewriting, ProxyPass or whatever to get into a situation where one can use "true" SSL sessions with different host certificates, e.g. https://www.server/ https://webmail.server/ https://wiki.server/ [...] Any pointers are welcomes as this must have been discussed before but I failed to find anything really hitting the nail on the head (except maybe this one which is still have to try out http://www.g-loaded.eu/2007/08/10/ssl-enabled-name-based-apache-virtual-hosts-with-mod_gnutls/ ) Cheers Carsten --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|