- edited description
Monit showing wrong protocol
I have set up a check on a host using HTTPS
check host "xxx server" with address app.xxx.xxx
if failed port 443 protocol https
and request "/admin/login/"
for 3 cycles
then alert
But the interface is showing HTTP:
In this case the page does not work, it shows Connection failed
but also HTTP:
Comments (9)
-
reporter -
reporter - edited description
-
reporter - changed title to Monit checking host on HTTP instead of HTTPS
-
reporter - edited description
-
reporter - edited description
- changed title to Monit showing wrong protocol
-
- changed status to closed
HTTP is the protocol. It is using HTTPS when checking, which you can see from the text about using TLS which is HTTPS
-
reporter Ah. Then calling it
protocol https
in the configuration might not be a good idea -
Good point. Most, me included, tend to think of https as its own protocol thing and not as http over a secure channel which it really is (SSL or nowadays TLS). Previously, in the config we called it type TCP/IP using TLS with protocol http which was a mouthful and https was introduced as a shorter alias. The text in the view is composed of fragments and use the old way. It’s a hassle to change, but to avoid confusion we should probably add an 's' at the end, like https, smtps, imaps etc.
-
reporter Well, so you have two pieces of information: the protocol (HTTP) and if it uses TLS/SSL or not. You can pack both pieces of information in the same word:
- HTTP for plain HTTP
- HTTPS for HTTP + secure
Everybody will understand. On top of that, you can add more info in the details (“using SSL” or “using TLS”)
It’s important to have consistency in the application. If you are using the word
protocol
to say ifhttps
orhttp
, then if the user sees the word protocol he expects that it will mean the same
- Log in to comment