external monitor GTM
We are using an external monitor on our F5 GTM (version 12.1.2) for sending curl statements to an openshift platform (https call constructed with DNS name & uri). Up till now this seemed to be working. But now for some applications hosted on this openshift platform , we are seeing strange behavior , when testing in CLI with curl statement like "curl -skv https://<application-name>/probe/liveness" --> 2 out of 3 requests are coming back with "HTTP /1.1 200 ok" which is the expected answer --> 1 out of 3 requests is coming back with 'HTTP /1.0 503 " We also have some LTM units in same network & when doing the same request from LTM , we always get the "HTTP /1.1 200 ok" . So the behavior seems only to be present on GTM , not LTM units. When diving into SSL answers which are failing we mainly notice : * server is presenting different certificates (failing call is using different certificate than the ones that are working) * failing calls we see answer coming back in http /1.0 and giving a 503 response (rather than answering in 1.1 My main problem is that we are only seeing this kind of behavior on GTM . We never have this behavior on LTM units & even tested from other stations .bit here we are always getting the correct answer .461Views0likes2Comments