Introduction
We’ve introduced the SNI Override feature to address limitations in our existing DNS and Host Header override options, which do not provide control over the SNI (Server Name Indication) field in the initial TLS handshake. With this enhancement, Catchpoint clients—especially when running non-browser (JS API) and web HTTPS tests that use DNS Override—can now specify a custom SNI value in the TLS "Client Hello" packet. This enables comprehensive monitoring for servers that depend on SNI-based routing and certificate selection.
Solution
To overcome these failures, you will need to include an Sni-Override custom header in the request section for non-transaction tests, or use the setHeader command to set a Sni-Override header for an API script.
For example:
API Script:
setHeader(dns-override:abc.xyz.com, 12.12.15.25);
setHeader("Sni-Override", "abc.xyz.com");
open("https://abc.xyz.com/something");
Request Section:
