On Wed, 2020-05-20 at 15:52 -0400, C c wrote: > It seems that DefaultTlsSetupHandler is final and I can't extend it. > One way is for me to change the source so that I can extend it. > > Is there another suggested way I can adjust that class for SNI ? > >
The class literally has two lines of code. What is the point of extending it? Oleg > > On Wed, May 20, 2020 at 7:05 AM Oleg Kalnichevski <[email protected]> > wrote: > > > On Tue, 2020-05-19 at 21:25 -0400, C c wrote: > > > I looked at emails and docs and can't find a trail on getting > > > started > > > w/ > > > SNI. > > > > > > In netty, I can set up SNI to look up what domain is being > > > requested > > > so I > > > can use a cert to the non-async server so I can serve multiple > > > domains with > > > 'Let's Encrypt'. > > > > > > How do I do SNI in HTTP core v5 non-async server? > > > > > > Vic > > > > Hi Vic > > > > SNI extension APIs are available in Java as of version 11 only. > > HttpCore is currently Java 1.7 compatible and therefore does not > > provide any SNI specific functionality. You will likely need to > > implement a custom TLS setup handler instead of > > `DefaultTlsSetupHandler` in order to customize TLS context > > negotiation. > > > > Hope this helps > > > > Oleg > > > > > > ----------------------------------------------------------------- > > ---- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: > > [email protected] > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
