The issue arises when an upstream TLS cluster is used with `auto sni` enabled and a request contains a `host`/`:authority` header longer than 255 characters, causing an abnormal termination of the Envoy process. This occurs because Envoy does not handle errors gracefully when setting SNI for outbound TLS connections, expecting the operation to always succeed. The SNI length is limited to 255 characters per standard.