On Tue, Feb 9, 2016 at 3:42 PM, Yann Ylavic <[email protected]> wrote: > On Mon, Feb 8, 2016 at 6:07 PM, Stefan Eissing > <[email protected]> wrote: >> >> One thing: the ssl_hostname that is used for SNI by the generic proxy utils >> seems to get lost when the socket needs to reset and is then not available >> on the next connect. That should affect mod_proxy_http as far as I can tell. >> Maybe someone with more experience in that module wants to take a look. > > This is intended (for http/1 at least), why is it an issue? > When mod_proxy closes the backend connection, it indeed clears any > associated SNI.
OK, I see now, hopefully fixed in r1729826 (backport to 2.4.x candidate...). I also removed mod_proxy_http2 workaround code in r1729830, please let me know if it still does not work. Regards, Yann.
