Menu

#689 HTTPS (TLS) connection fails due to missing SNI

v1.0 (example)
open
nobody
None
2
2015-12-02
2015-12-02
Tom Arn
No

soapUI version: 5.2.1
JRE: 1.8.0_66-b17
Platform: Windows 8.1 Enterprise

Our webservice closes the https connection from soapUI during the TLS handshake because soapUI does not set the SNI server name (SNI: server name indication, rfc 6066), although this should be the standard since JRE 7

Please provide a fix, because this problem prevents us from using soapUI as more and more webservices require the SNI extension.

Thanks
Tom

Discussion


Log in to post a comment.