http: check that custom logging does not collide

for content range header for instance

diff --git a/tests/http2-range/suricata.yaml b/tests/http2-range/suricata.yaml
new file mode 100644 (file)
index 0000000..76791fe
--- /dev/null
+++ b/tests/http2-range/suricata.yaml
@@ -0,0 +1,25 @@
+%YAML 1.1
+---
+
+outputs:
+  - eve-log:
+      enabled: yes
+      types:
+        - files
+        - stats
+        - http:
+           custom: [Content-Range]
+  - file-store:
+      version: 2
+      enabled: yes
+      force-filestore: yes
+      stream-depth: 0
+
+app-layer:
+  protocols:
+    http:
+      enabled: yes
+      libhtp:
+        default-config:
+          personality: IDS
+          response-body-limit: 100kb

diff --git a/tests/http2-range/test.yaml b/tests/http2-range/test.yaml
index a3b204d970dbaa8389609426412b45fb75f5aa0e..058e97eeba9d4d5db1bdcd7d625bdff183303322 100644 (file)
--- a/tests/http2-range/test.yaml
+++ b/tests/http2-range/test.yaml
@@ -15,6 +15,12 @@ checks:
       match:
         event_type: fileinfo
         fileinfo.size: 69
+  - filter:
+      count: 1
+      match:
+        event_type: http
+        http.response_headers[0].name: "Content-Range"
+        http.response_headers[0].value: "bytes 10-20/69"
   - filter:
       count: 0
       match: