Hi
I deployed a
new gateway with Version 9.4 CR3 that will
replace a gateway with version 9.3 CR1.
So, I installed the same stuff on the new gateway and ran my test suites against it. I got several tests with the following error:
Unable to obtain HTTP response from https://[host]:[port]/[URI]: SSL verification failed!
Therefore I tried some things and noticed that the
errors disappear when I set
io.httpsHostVerify = false
So, this is not a big surprise, since the
certificate name and the hostname are not the same.
But, on a second thought, I wondered
why this works without any problems on the gateway version 9.3 CR1?
Even when I explicitly add hostname verification on the old gateway (it is also by default true), the SSL connections are working just fine:
io.httpsHostVerify = true
Has hostname verification been fixed in any release after 9.3 CR1 or how can this behaviour be explained?
Thanks
Stephan