Sounds at first like an admirable concept, but unfortunately would be incredibly problematic. What about the case where you're virtual-hosting many sites on on

Sounds at first like an admirable concept, but unfortunately would be incredibly problematic. What about the case where you're virtual-hosting many sites on one IP address? Since the SSL handshake occurs prior to any HTTP data being sent, and the browser will reject a server-certificate whose hostname does not match, you're normally restricted to one HTTPS domain per IP address. I gather there are TLS extensions to suppport SSL vhosts, but I don't know how widespread they are. There are also methods of including more than one hostname per certificate, but I'm assuming that when you purchase a SSL cert from a registrar, you're going to be restricted to one host.