Forum Discussion
Health Monitor unable to connect to OpenShift Router
In our environment we use custom HTTPS monitors where we specify the Host: header. This allows the OpenShift router to reach the application.
GET /favicon.ico HTTP/1.1\r\nHost: my-tls-passtrough-service.com\r\nConnection: Close\r\n\r\n
- Genna_ReingoldMar 17, 2025
Nimbostratus
Hi bramwittendorp
Thanks. Yes we have done it too, but it doesn't work. Not that I have expected it to work - when route in OpenShift is configured as TLS passthrough the routing host information is taken from TLS Client Hello Message not from HTTP Host Header- bramwittendorpMar 17, 2025
Altostratus
I see, and in the ServerSSL profile you did also specify the Server Name to be used for Client Hello?
- Genna_ReingoldMar 17, 2025
Nimbostratus
Yes. Correct
And that what allowed the connection through.
So the requests are routed correctly through the VS using ServerSSL profile with host name in it. But Health checks configured with the same ServerSSL profile are failing
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com