3 ms·
If TLS could negotiate certificates instead of supporting one and only one, the backbone of any sane "virtual host" system, then https: wouldn't be a big deal.
by astrodust 14y ago
If TLS could negotiate certificates instead of supporting one and only one, the backbone of any sane "virtual host" system, then https: wouldn't be a big deal. It'd be the default.
Now you need a separate IP (expensive) or port (annoying) for each virtual host configured with a different SSL cert. This has to stop, but it will not be easy to fix.
- rwg 14y agoRFC 3546, which includes TLS Server Name Indication, has existed since June 2003. The problem preventing deployment is the lack of client support, especially Internet Explorer on Windows XP and Android 2.x [1]. -- 1. http://en.wikipedia.org/wiki/Server_Name_Indication#No_support http://en.wikipedia.org/wiki/Server_Name_Indication#No_suppo...
- deleted 14y ago[deleted]