HTTP: fix classification (#1692)

If we have a valid HTTP sessions, we should ignore
`flow->guessed_protocol_id` field (i.e. classification "by-port")
altogheter.

The attached trace was classified as "SIP/HTTP" only because the *client*
port was 5060...
As a general rule, having a classification such as "XXXX/HTTP" is
*extremely* suspicious.
This commit is contained in:
Ivan Nardi
2022-07-30 22:57:20 +02:00
committed by GitHub
parent 8b6a00f84b
commit 2a596c79e6
4 changed files with 30 additions and 5 deletions
Binary file not shown.