Although the answer provided by @Bruno above indeed addresses the hows and whys, it leaves the question as to how to setup up SSL/TLS enabled name based virtualhosts with a less than workable solution - deferring instead to someone binding (or purchasing from their hosting provider) additional IP addresses for their machine and depending, also altering the listen on parameters for httpd.conf
IOW, there isn't a solution in @Bruno's answer - you must use IP based virtualhosts.
@ocsarjd, on the other hand, does address how to provide support for name based virtual SSL hosts, in addition to a work around for people who are insistent upon running say, IE on XP.
and then mod_rewrite provides support for browsers unable to take advantage of SNI, and therefore, no one has to purchase and/or bind additional IP addresses to the server for Apache to listen on for connections in an IP based virtual host method.
Ironically, @Bruno's answer does cover all of the reasons how and why these negotiations take place and how the obsolete browsers are unable to negotiate the proper incorporation of name based SSL virtual hosting on an Apache server.
As it has been some time since the OP posed this question, I would recommend NOT accommodating these obsolete browsers, because this is a choice that the person at the client end has made to operate insecure software, which in my opinion, is simply someone to be ignored....
That having been said, a default SSL virtual host with information akin to a custom 404 page telling the visitor that they are operating an insecure browser client would actually be in order here for a few more years, because there will surely be people who refuse to stop using a version of IE that has received no patches since XP was EOL'd, and all (so-called) 'modern' browsers (IE/Edge, Firefox, Chrome/Chromium, Opera, Safari) will accommodate the features of name based virtual hosting over HTTPS via SNI.