From: Philippe Antoine Date: Wed, 30 Nov 2022 15:38:52 +0000 (+0100) Subject: http: check that custom logging does not collide X-Git-Tag: suricata-6.0.13~23 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=64f0400b87e754f430c24ac1ba725b3d4c30f980;p=thirdparty%2Fsuricata-verify.git 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 index 000000000..76791fe54 --- /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 a3b204d97..058e97eeb 100644 --- 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: