More of a change in behavior than a bug, but important to be documented
Related to
Bug https://redmine.openinfosecfoundation.org/issues/7199
--- /dev/null
+# Test
+
+Showcase change of behavior from Suricata-7.0.5 to Suricata-7.0.6.
+Before, a non-stream rule that matched traffic associated with an app-layer
+transaction would result in app-layer metadata being logged with the alert, if
+metadata was enabled. Starting with 7.0.6, this will only be achieved if the
+rule is an app-layer/stream one.
+
+### Pcap
+
+Packet capture resulting of a curl to suricata.io.
+
+### Ticket
+
+https://redmine.openinfosecfoundation.org/issues/7199
--- /dev/null
+%YAML 1.1
+---
+
+outputs:
+ - eve-log:
+ enabled: yes
+ filetype: regular
+ filename: eve.json
+ types:
+ - alert:
+ enabled: true
+ tagged-packets: true
+ metadata: true
+ http-body: true
+ - http:
+ extended: true
+ tagged-packets: true
+ - tls:
+ extended: true
+
+detect:
+ guess-applayer-tx: yes
\ No newline at end of file
--- /dev/null
+reject ip any any -> any any (msg: "Reject by AntreaNetworkPolicy:default/ingress-allow-http-request-to-api-v2"; flow: to_server, established; sid: 1;)
+pass http any any -> any any (msg: "Allow http by AntreaNetworkPolicy:default/ingress-allow-http-request-to-api-v2"; http.uri; content:"/api/v2/"; startswith; http.method; content:"GET"; http.host; content:"foo.bar.com"; startswith; endswith; sid: 2;)
+alert http any any -> any any (msg: "Alert by AntreaNetworkPolicy:default/ingress-allow-http-request-to-api-v2"; http.uri; content:!"/api/v2/"; sid: 3;)
--- /dev/null
+requires:
+ features:
+ - LIBNET1.1
+
+args:
+- -k none
+- --set stream.midstream=true
+- --simulate-ips
+
+checks:
+ - filter:
+ count: 4
+ match:
+ event_type: alert
+ alert.signature_id: 1
+ - filter:
+ min-version: 8
+ count: 1
+ match:
+ event_type: alert
+ alert.signature_id: 1
+ has-key: http
+ - filter:
+ count: 0
+ match:
+ event_type: alert
+ alert.signature_id: 2
+ - filter:
+ count: 1
+ match:
+ event_type: alert
+ alert.signature_id: 3
+ has-key: http