Web-browsing application being identified instead of SSL on port 443.
We just noticed that in our traffic logs there is traffic with the web-browsing application identified with a destination port of 443. The rule it is hitting on is only a port based rule with 80 and 443 as dest ports. My question is why would the traffic match the signature of web-browsing since the standard port in the App is 80? Is it because...




