3 ms·
It's not just IE/XP which is the problem, library support for SNI is still pretty poor, which is an issue if you're running REST services.
by pwaring 14y ago
It's not just IE/XP which is the problem, library support for SNI is still pretty poor, which is an issue if you're running REST services.
- jgrahamc 14y agoSNI is backwards compatible with sites that are not using it, so this is really an asymmetric problem. If you are writing your REST service with a library that doesn't support SNI then you just fall back to the old one SSL certificate per IP:port. When a browser comes in presenting the SNI option it just gets ignored and life goes on.
- pwaring 14y agoI think you've got the point I was trying to make the wrong way round. If I set up half a dozen REST services with SSL on a single IP, clients which don't support SNI will experience problems. Last time I checked, libwww in Perl, urllib in Python (until 3.2) and the WebClient library in C# all didn't support SNI.