http and https monitors

To explain simply:

http means "HTTP: No Data Encryption Implemented":

HTTP can be intercepted (because flow between client and server is in clear: no ssl/tls encryption) and potentially altered, making both the information and the information receiver (that’s you) vulnerable.

https means "HTTPS: Encrypted Connections":

HTTPS is not the opposite of HTTP, but its younger cousin. The two are essentially the same, in that both of them refer to the same “hypertext transfer protocol” that enables requested web data to be presented on your screen. But, HTTPS is still slightly different, more advanced, and much more secure (encrypting data transmission, and protecting the exchanges from tamperin).

So

• You have to set HTTP monitor when your backend (Application) don't use tls/ssl (to know that the port has no dependence with the protocol. you can put an http profile on port 8443 very well if the server is configured like this).

   

• You have to set https monitor when your backend use tls/ssl on the backend side (ask it to application owner).

   

In general HTTP user port 80 and https user port 443 (standard). Additional point as i told you, the used port does not matter you can have ssl/tls flow in port 8080... it's depending of application owner... So to answer to your question you can use this monitor, it does not matter the port, it is necessary that you configures the monitor https when it is a port which uses the encryptions (SSL / TLS) and the HTTP when it is the flow in clear (thus no encryption)

Hope it's clear for your.