It should be possible, using the extension described in
Section 3.1 of RFC
4366 to have different host keys for different virtual
hosts. I tried this
with the latest Cherokee release. It was promising that one
obviously can use
SSLCertificateFile and friends inside of a virtual host
definition, i.e.
inside of a ``Server example.com { ... }'' construct.
Unfortunately,
however, in all variations I tried, always the host key of
the default host
was used. This means that Cherokee served files from the
DocumentRoot defined
for the proper virtual host, but not with the host key given
inside of the
virtual host definition.
Is such a feature implemented at all? Can it be expected to
be implemented
some day? It would be VERY convenient not having to use
multiple IP addresses
for different HTTPS sites.
Regards, Lasse
_______________________________________________
Cherokee mailing list
Cherokee cherokee-project.com
http://cherokee-project.com/cgi-bin/mailman/listinf
o/cherokee
|
