You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some TLS servers require SNI, but the Golang HTTP client doesn't include it in the ClientHello when connecting to an IP address.
Use Case(s)
We ran into this use case while trying to health check external services using consul-esm. Things work fine if we register them using hostnames as addresses, but if we use IP addresses the SNI is not set and handshakes fail.
In #3936 there was a suggestion to add a new TLSServerName field to the check definition: #3936 (comment). I believe the same TLSServerName field could be used here to optionally set TLSClientConfig.ServerName, and the change would be backwards compatible. If that sounds reasonable, I'd be happy to provide a PR addressing this.
The text was updated successfully, but these errors were encountered:
Some TLS servers require SNI, but the Golang HTTP client doesn't
include it in the ClientHello when connecting to an IP address. This
change adds a new TLSServerName field to health check definitions to
optionally set it. This fixeshashicorp#9473.
Feature Description
Some TLS servers require SNI, but the Golang HTTP client doesn't include it in the ClientHello when connecting to an IP address.
Use Case(s)
We ran into this use case while trying to health check external services using consul-esm. Things work fine if we register them using hostnames as addresses, but if we use IP addresses the SNI is not set and handshakes fail.
In #3936 there was a suggestion to add a new
TLSServerName
field to the check definition: #3936 (comment). I believe the sameTLSServerName
field could be used here to optionally setTLSClientConfig.ServerName
, and the change would be backwards compatible. If that sounds reasonable, I'd be happy to provide a PR addressing this.The text was updated successfully, but these errors were encountered: