Joseph S wrote:
Krist van Besien wrote:That documentation is old and needs to be updated. Since apache 2.2.12 you can have ssl name virtual hosts if you have a recent openssl library that supports RFC 4366. Like I said this is working for all my other *.a domains, just today it stopped working for this one.On Tue, Oct 27, 2009 at 7:41 PM, Joseph S <jks@xxxxxxxxxxxxxxx> wrote:Now here's the kicker: When I click through the warning in Firefox my logsshow that I am going to the second virtual host, the one with thethat *.a certificate, even though I'm using the *.* certificate. So how is it apache is sending me to the correct virtual host but serving up the wrongcertificate?At the moment that the SSL handshake takes place apache does not yet know which Virtual Host you want to be served by, so it used the certificate of the first host. Read this: http://httpd.apache.org/docs/2.2/ssl/ssl_faq.html#vhosts2---------------------------------------------------------------------The official User-To-User support forum of the Apache HTTP Server Project.See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
--------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx