4 ms·
More specifically: IE on XP. No, SNI is fully broken on all platforms. I tried it for a while, save yourself the headache. It fails intermittently on all brow
by moe 15y ago
More specifically: IE on XP.
No, SNI is fully broken on all platforms. I tried it for a while, save yourself the headache.
It fails intermittently on all browsers (including latest Firefox and chrome) under various conditions. These failures usually manifest as "Certificate does not match"-warnings for the user.
I have not fully understood all scenarios, but a few seem to be:
Keep-alive connection to vhost A, then browser tries connection to vhost B. Loadbalancer doing funny things. Intermediate proxies doing funny things.
General implementation bugs (I've seen the cert-warning even on a freshly booted chrome for no obvious reason).
And let's not get started on mobile browers... (hint: the built-in browser may actually seem fine but the http-library in your app still fails intermittently, older androids [widely deployed] have no SNI support at all)
Do yourself a favor and either switch to a wildcard cert or stick with separate IPs.
- dspillett 15y agoI've not implemented SNI myself yet as a chunk of our clients fall in the "stoneage" category, running XP+IE8 or in at least one case XP+IE6. I'll take your warnings as things to thoroughly test if I ever need to try implement it. You are right in noting that mobile platforms apparently don't support it well at all. Really IPv6 is the answer, but for out clients at least that is even more "future magic" then running a decent browser...