4 ms·
> costing a fortune. The problem is not the SSL certificate, the problem is the IP address. That will no longer be a problem as soon as IPv6 takes hold in a fe
by x5n1 11y ago
> costing a fortune.
The problem is not the SSL certificate, the problem is the IP address. That will no longer be a problem as soon as IPv6 takes hold in a few years, I give it about 3. They currently have to deploy the SSL certificate to over 30 different IPs hence it costing the immense amount. The certificate can be had for $10.
- toomuchtodo 11y agoWhy would anyone use non-SNI SSL/TLS anymore? Are there really that many Windows XP clients out there?
- eropple 11y agoOne of my clients still sees a surprising amount of Android 2.x traffic. Other than that, yeah, I can't see a reason.
- mike-cardwell 11y agoExactly. I default to SNI being acceptable now, unless somebody has convincing evidence that for their particular use case they can't use it.
- eli 11y agoI dunno where the line it, but Windows XP is in the ballpark of 2% of our traffic, depending on the site and how you measure it. The bummer is that HTTPS breaks kinda badly if you use an SNI cert and the OS/browser doesn't support it.
- Dylan16807 11y ago2% is IE on XP, or XP in general? I wish people would be more clear when they bring up XP. The OS is not the problem.
- ademarre 11y ago> 2% is IE on XP, or XP in general? The latter sounds more likely to me. The sites I run get about 2.5% XP, but most of that population uses Chrome or Firefox. IE on XP accounts for only 0.3% overall.
- rodgerd 11y agoAt this point my experience is that most people still on XP are using IE - it mostly appears to be institutions that are still(!) using a primitive corporate build.
- stenius 11y agopython 2.7 doesn't support SNI which is used by a lot of consumers of APIs
- hnmsc12 11y agoPython 2.7.9 supports SNI: https://www.python.org/downloads/release/python-279/ https://www.python.org/downloads/release/python-279/