We noticed that when a request is made to a domain with a trailing dot, the SNI server name is not included in the ClientHello message.

Upon investigation, it seems the peerHost needs to be valid for the SNI server name to be generated in the SSL engine. However, the host passed in the pipeline configurator includes the trailing dot, making it invalid.

I came across #4875 that allows trailing dots, that may be related.

Code Ref:

https://github.com/netty/netty/blame/4.1/handler/src/main/java/io/netty/handler/ssl/ReferenceCountedOpenSslEngine.java#L345