SNI bug re-added in latest MU?

[LinqLOL]

Hi (Igor especially),

Is it possible that a SSL SNI bug had re-added in the lastest MU updates? The problem in a nutshell. A website with an SSL website on a dedicated IP address was threated as an SNI (shared SSL website) and is served with the default ssl certificate.
With new sites added I see the same behaviour again as it was when I submitted the bug (ticket #1732555)

Steps to reproduce:
* Create website
* Assign dedicated IP address to it
* Add an SSL certificate under the specific website
* Test website at https://ssltools.websecurity.symantec.com/checker. The SAN shows the default certificate for websites instead

 

[IgorG]

We do not touch anything in the latest microupdates related to SNI. This issues has been fixed in MU#17.
If you faced this issue with installed MU#21 - please send me in PM login credentials on your server and step-by-step instruction for reproducing this issue.