I configured a HTTPS-HEAD Keepalive in a GSS that fails even if the server responds correctly. The problem could be that the server responds with a not trusted certificate. Does anyone know what the GSS's behaviour is in this particulal case?
That is an interesting question. The GSS does not check the certificate chain or domain, thus, to directly answer your question, no, it doesn't care about trust. I have never tested if the clock is checked against the date range on the certificate, but I would imagine it doesn't check that either.
At this point, if you had a linux box, issue a wget or curl request against the server and see what it sends back for the the page your GSS is probing (GSS only accepts a 200ok.)
Assure Application Performance on Hyperconverged InfrastructureWednesday November 20th at 11 am ET
Increased adoption of hyperconverged infrastructure has been driven by the need for IT teams to simplify IT operations and increase agility. Organizations a...
To participate in this event, please use the button to ask your questions
This topic is a chance to discuss more about the migration options from existing network designs to Cisco Application Centr...
Worried about the next Azure Stack firmware update? Learn how Cisco UCS makes the complex simple with every update.
In order to get the latest features, defect fixes and to protect from security threats it is the responsibility of the Microsoft Azu...
Cisco Workload Optimization Manager (CWOM)
Continuously Assure Application Performance at Any Scale
Webinar: Wednesday, October 23rd at 11am ET
Today’s applications utilize traditional virtualization platforms as well as newer DevOps meth...