Forum Discussion

kgaigl's avatar
kgaigl
Icon for Cirrocumulus rankCirrocumulus
Jan 20, 2021

HTTPS Monitor: JSON File behind login page

Hello, we've already a https monitor that reads the contents of a json file, it looks like this: send string: GET /intern/api/v1/health/portal-status HTTP/1.1\r\nHost: host.company.com\r\n\r\n r...
application delivery
JSON
LTM
monitor
jaikumar_f5's avatar
jaikumar_f5
Icon for MVP rankMVP
Jan 20, 2021

Can you open the webserver & check the htaccess file to know what type of authentication is configured. If its a simple BASIC authorization, you can check the https monitor behavior via openssl itself.

Also you can still turn on the monitor logging & see what happens for every monitor interval. Check the monitor log file in /var/log/monitors/.

Also I have read in an article that double CR/LF could cause issues on authentication headers.

So in your send string, do not give the closing double CR/LF & see how it behaves.

Refer this article - https://support.f5.com/csp/article/K54561004 - Quoted the point.

Unlike other HTTP monitor send strings, an NTLM or Basic Authentication monitor should not include a closing double CR/LF sequence. When NTLM/NTLMv2 is enabled by adding a Username and Password to the monitor configuration, the BIG-IP system appends the Authorization header and a double CR/LF sequence after the last character in the Send string.

Please keep us posted.