Forum Discussion

Netmart's avatar
Netmart
Icon for Nimbostratus rankNimbostratus
Nov 07, 2024

HTTPS Monitor Health - Receive String 200 OK Not Working

Hello, Though we receive in https response header "HTTP/1.1 200 OK", the same string used as receive in Health Monitor does not work. F5 seems to ignore any character after HTTP/1.1. In sum: Not W...
monitors
Netmart's avatar
Netmart
Icon for Nimbostratus rankNimbostratus

Thank you Akonu.

I am aware of this document and tried the following without any progress:

Receive String: HTTP/1.1 200 OK
 
 
Not Working:
HTTP/1.1 200 OK
HTTP/1.1\s200
HTTP/1\.(0|1)
HTTP/1\.(0|1) (200)
HTTP/1\.(0|1)\s200
HTTP/1.1 200 OK
HTTP/1.1\s200\sOK
200
 
Only Working:
==> HTTP/1.1 
==> OK||200
==> <bank>
 
And I verified via curl/openssl the HTTPS Response header: HTTP/1.1 200 OK:
---
HTTP/1.1 200 OK
Date: Wed, 06 Nov 2024 23:52:28 GMT
Content-Type: application/json; charset=UTF-8
Content-Length: 153
Connection: close
X-Krakend: Version 2.2.0
X-Krakend-Completed: false
X-Processing-Time: 0.000029
X-Request-Id: e187dac8-20f7-43fd-b99a-6e4671b7f8e6
Expires: Wed, 06 Nov 2024 22:52:28 GMT
Cache-Control: no-cache
X-Frame-Options: DENY
Strict-Transport-Security: max-age=31536000; includeSubdomains; preload
X-XSS-Protection: 1; mode=block
Client-Verify: NONE
X-Content-Type-Options: nosniff
X-Permitted-Cross-Domain-Policies: none
Feature-Policy: geolocation 'none'; camera 'none'; speaker 'none'; microphone 'none';
Referrer-Policy: strict-origin-when-cross-origin
Expect-CT: enforce, max-age=72000
Content-Security-Policy: default-src 'self' blob:;base-uri 'self'; form-action 'self'; frame-ancestors 'self'; script-src 'self'; style-src 'self' 'unsafe-inline'; font-src 'self' data:; object-src 'none'; img-src 'self' data:;
Cache-Control: no-store
 
{"status":"starting","services":[{"name":"nae-kmip","status":"started"}],"messages":["all services ok, waiting 1m0s for services to continue to be ok"]}
closed

 

 
Thanks
akonu's avatar
akonu
Icon for Moderator rankModerator
Nov 07, 2024

Netmart 

From your update, you said the 200 does not work. if that is the case, your server could be responding to the health probes with a different status code other than 200. Can I ask that you verify the output of the monitor using the guide below.( please use the same string as the monitor send string)

K81239024: Testing HTTP/HTTPS Monitor Send String using openssl s_client and netcat (nc)

https://my.f5.com/manage/s/article/K81239024

Hope this helps.