In article <[EMAIL PROTECTED]> you wrote: > On 17-Sep-98 Ralf S. Engelschall wrote: >> On Thu, Sep 17, 1998, [EMAIL PROTECTED] wrote: >> >>> Anyone have a example of httpd.conf with two virtual host and two >>> certificates? >>> >>> I put the correct directives in httpd.conf, but https try use first >>> certificate >>> in httpd.conf! >>> If I change order, he look the first, no from virtual host... >> >> Perhaps your second virtual host is a named-based one? Then it grabs the one > Yes.... ^^^^ >> from the IP-based one. Please give us more details about your actual config >> to let us help you better. > Look: >[...] > https://www.yyy.com.br call xxx certificate. > If I change (swap yyy -> xxx), he call yyy certificate... Ok, looks exactly that the name-based VHost is your problem. Because SSL cannot be used with those. The effect is that the first non-name-based VHost (the one treated as IP-based this way) matches when the connection is established and the second one has no chance, of course. You have to make _BOTH_ www.xxx.com.br and www.yyy.com.br IP-based. Without IP-based vhosts you have no chance with SSL. Because Apache/mod_ssl _CANNOT_ determine the name-based VHost under connection time (where the SSL handshake is done). Here only IP-based VHosts can be correctly dispatched. Ralf S. Engelschall [EMAIL PROTECTED] www.engelschall.com ______________________________________________________________________ Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/ Official Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
