> No, this does not answer my question. In my scenario the SSL-certificate is > the same for all vhosts concerned. So Apache could use that certificate to > establish the SSL connection, and then parse the Host:-header to determine, > which group of other (non-SSL) settings to apply to the request. But Apache > does not do that -- not in 2.2.22. > > Is this an omission, that can and should be fixed, or am I missing something > else? Thanks!
Got a pointer to your configuration?
