3 weeks ago
I have one DTC record with pool that is monitored via simple tcp_https health monitor. Pool members are in fact Pulse Secure VPN gateways with enabled health checking URI (https://docs.pulsesecure.net/WebHelp/PCS/9.1R4/AG/Content/PCS/PCS_AdminGuide/Health_Checking_a_Serve...)
GET returns HTTP code 200 with simple HTML page with additional information which I would like to evaluate via health monitor. Response is smaller then 1k Bytes.
Once feature is enabled on Pulse Secure response looks more or less like this:
"HTTP/1.1 200 Connection Established
Content-Type: text/html; charset=utf-8
with simple HTML page:
Health check details:
I am intested in line MAX-LICENSED-USERS-REACHED=[NO/YES] based on that line once number of users will hit license limit I can stop forwarding new users towards that gateway in pool.
First I have created new health monitor to at least catch http code 200 and this works perfect.
Use HTTPS: checked
HTTP Request: get /dana-na/healthcheck/healthcheck.cgi?status=all http/1.1 host: <IP>
Response Code Check: A valid response code "equals" 200
Test HTTP Health Monitor - IPv4 Test Result: Success - The health criteria ware met.
Then I have tried to extend this new http monitor with aditional evaulaton of response:
Search for the string in response content section
Search in: body
Regular Expression: MAX-LICENSED-USERS-REACHED=NO
The content is valid if the regular expression is: "found"
Unfortunatelly I was failing with test status: "An error occured while connecting to the DTC server" all the time...
So I started to experiment with different settings and I have found that I am able to evaluate response content only when option "Search in" is set for "Headers". Of course I will not find in headers my precious MAX-LICENSED-USERS-REACHED=NO but at least I could verify if this feature works at all. So as an example I had no issues with looking for SAMEORIGIN string when search in is set to "Headers". Unfortunatelly whenever I try to search various strings or even reg exp. ".*" in "body" or even "both the heather and body" I am getting same error message "An error occured while connecting to the DTC server".
It is strange as I should at least get same results while looking for SAMEORIGIN string for Search in set to "Headers" and "Both the headers and body" but it is not the case.
HTTP monitor configuration page informs about limit of search in first 5 kB but again Pulse Secure response is much much smaller then that.
I am running code 8.2.7. I have valid support but once NOC tried to open a case with our "support provider" the only response we got was - go to code 8.3.8, 8.4.8 or 8.5.2. The problem is I do not even know if in those versions my problem was solved... Does anyone had similar problem or at least can confirm it this functionallity was fixed in newer NIOS releases?
a week ago
I will probably answer to my own question...
The response content check for the DTC HTTPS health monitor did not work as expected.