mirror of https://github.com/OISF/suricata
protocol detection: midstream handling update
If a TCP session is midstream, we may end up with a case where the start of an HTTP request is missing. We won't detect HTTP based on the request. However, the reply is fine, so we detect HTTP anyway. This leads to passing the incomplete request to the htp parser. This has been observed, where the http parser then saw many bogus requests in the incomplete data. This is not limited to HTTP. To counter this case, a midstream session MUST find it's protocol in the toserver direction. If not, we assume the start of the request/toserver is incomplete and no reliable detection and parsing is possible. So we give up.pull/945/head
parent
c1dcc7a268
commit
44b8be3732
Loading…
Reference in New Issue