I have the same issues on windows XP clients (IE8). I don't have any issues at all with Win 7/IE9 and win2012/IE10.
cheers On Wed, Jan 16, 2013 at 3:43 PM, Jonathan Matthews <[email protected]> wrote: > On 16 January 2013 13:48, Alexandru Florescu <[email protected]> wrote: >> >> Hi, >> following the instructions here >> http://blog.exceliance.fr/2012/09/10/how-to-get-ssl-with-haproxy-getting-rid-of-stunnel-stud-nginx-or-pound/ >> I managed to set up a SSL enabled version of HAproxy and things generally >> work fine. >> >> Anyway, in haproxy.cfg I configured a list of SSL certs >> bind 0.0.0.0:443 ssl crt /etc/haproxy/certificates/cert1.pem crt >> /etc/haproxy/certificates/cert2.pem crt /etc/haproxy/certificates/cert3.pem >> >> Generally they work but some browsers (e.g. IE8/9) complain about the cert >> for domain1.com being served to domain2.com >> >> Is there a way to specifically declare what certificate should be served to >> what domain so I won't get these kind of warnings anymore? > > These client-side warnings are inevitable given your setup, and are a > byproduct of how HTTPS works. You may find this post useful in > understanding why: http://webmasters.stackexchange.com/a/13992 > The multiple answers to this post go into more detail if you're that > way inclined: > http://serverfault.com/questions/109800/multiple-ssl-domains-on-the-same-ip-address-and-same-port > > Until SNI is more widely adopted, you need a distinct IP address for > each cert you wish to use. > > Regards, > Jonathan > -- > Jonathan Matthews // Oxford, London, UK > http://www.jpluscplusm.com/contact.html >
