On Tue, Sep 18, 2012 at 3:02 PM, Igor Galić <i.ga...@brainsware.org> wrote: > > Yeh. We'll need to back-port the fix to not ALWAYS assume SNI for > all SSL connections, since not quite all browsers support that yet > > @James, can you please do the proposal, kthnxby > >> -jf
This is already in the CHANGES/PATCHES ACCEPTED TO BACKPORT FROM TRUNK list in v3.2.x, and what we're already using (sorry for referring to wrong commit earlier): *) Fix SNI certificate fallback path Trunk: 9c3bebd88eecf6aee1ce346b67460b8e1787752d Jira: https://issues.apache.jira/browse/TS-1471 +1: jpeach, igalic, zwoop But when applying 8586b8ec6d6e934233fc195a4f35944cea1d85a4 on top of it it looks like non-SNI browsers broke again... -jf
