cancel
Showing results for 
Search instead for 
Did you mean: 
Create Post
Level 11

HTTP(s) Component monitor results

Hello, 

I have trouble running HTTP(s) component monitor, I can't find the logic

My results : 

"initial_value must be str or None, not bytes" (status down) when testing http://www.google.fr on port 80
whereas testing on the server : 
[user@server ~]$ curl http://www.google.fr:80 --head
HTTP/1.1 200 OK

"initial_value must be str or None, not bytes" (status down) when testing https://www.google.fr on port 443
whereas testing on the server : 
[user@server ~]$ curl https://www.google.fr:443 --head
HTTP/1.1 200 OK

****

Exactly the same with http://www.youtube.com & https://www.youtube.com

****

"status OK" when testing http://www.lequipe.fr on port 80
whereas testing on the server : 
[user@server ~]$ curl http://www.lequipe.fr:80 --head
HTTP/1.1 301 Redirection https.

"initial_value must be str or None, not bytes" (status down) when testing https://www.lequipe.fr on port 443
whereas testing on the server : 
[user@server ~]$ curl https://www.lequipe.fr:443 --head
HTTP/1.1 200 OK


****

"status OK" when testing http://www.free.fr on port 80
whereas testing on the server : 
[user@server ~]$ curl http://www.free.fr:80 --head
HTTP/1.1 301 Moved Permanently

"initial_value must be str or None, not bytes" (status down) when testing https://www.free.fr on port 443
whereas testing on the server : 
[user@server ~]$ curl https://www.free.fr:443 --head
HTTP/1.1 302 Moved Temporarily

****

"status OK" (????????) when testing http://www.lequipe.fr on port 443 (irrelevant, just for the test)
whereas testing on the server : 
[user@server ~]$ curl http://www.lequipe.fr:443 --head
curl: (52) Empty reply from server

What is the magical behind this component ?

Labels (3)
0 Kudos
2 Replies
Level 7

We had a similar issue. Found that the HTTP monitor has issue if you are using agent as the preferred polling method on the monitor. After changing to Agentless for that particular application monitor it would work. 

0 Kudos

I opened a ticket to support, it was a bug in the agent ; it has been corrected in 2020.2

0 Kudos