[ryantownsend]

This is excellent news - SNI very widely supported in browsers now, so there is little excuse to avoid it.

Would be great to see SPDY/HTTP2 support so the overhead of serving many small assets (i.e. typical website use) would be reduced.

[mrweasel]

Sadly support for SNI isn't supported widely enough that you can actually use it, unless you control the clients.

You really need Internet Explorer to support SNI on Windows XP before you can use it. We would lose maybe $50- 100.000 in turnover per month by relying on SNI support, rather than just having multiple IP for each domain.

[mike-cardwell]

If a browser doesn't support SNI, it doesn't prevent them from accessing the site. It just means the wrong cert is returned, so they get a cert warning. Depending on the type of your site and type of users, this may or may not be a problem.

[josteink]

Windows XP is completely and utterly deprecated as of next month. For any future deployment and new development it should not even be on your consideration-matrix.

It's dead, Jim.

Let's just let it die already, instead of sowing cushions under XP-users arms. If their internets starts breaking, they might actually be motivated to upgrade.

[mrweasel]

>If their internets starts breaking, they might actually be motivated to upgrade.

More likely: My customers take their business elsewhere.

[goldenkey]

That thinking doesn't work when Warbucks Scrooge McXP has a million dollar account with your agency.

[Dylan16807]

Hey, don't blame XP. XP works fine. Just needs a browser that hasn't been abandoned.