mirror of https://github.com/OISF/suricata
detect: use direction-based tx for app-layer logging
When we only have stream matches. Ticket: 6846 This solves the case where another transaction was created by parsing data in the other direction, before running the detection. Like 1. get data in direction 1 2. acked data: parse it, but do not run detection in dir 1 3. other data in direction 2 4. other data acked : parse it and create new tx, then run detection for direction 1 with data from first packetpull/10921/head
parent
f6635ea960
commit
7274ad58aa
Loading…
Reference in New Issue