upstream/suricata
1
0
Fork 0
mirror of https://github.com/OISF/suricata.git synced 2026-05-28 04:32:12 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

docs: clarify HTTP/2 frame transaction behaviour and restore stream ID 0 explanation

Browse source 
Improved the HTTP/2 documentation by adding a clarification note distinguishing HTTP/2 protocol frames from Suricata’s internal frame concept.

Restored the original explanation for frames with stream ID 0, as this behaviour is correct: connection‑level frames (stream ID 0) result in a transaction being created for each frame, while other frames are grouped into transactions based on their stream identifier.

No functional changes; documentation only.
This commit is contained in:
Sujala Vasanthasena Nelavai 2026-05-24 21:22:30 +01:00 committed by GitHub
parent 0d95293f99
commit 09342edaa9
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 4 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
doc/userguide/rules/http2-keywords.rst
View file

@ -11,8 +11,10 @@ HTTP2 Keywords
internal *frame* concept used in the rule language.
HTTP/2 frames are grouped into transactions based on their stream
identifier. Frames with a stream ID of 0 are connection‑level frames
and are not part of a transaction.
identifier.
Frames with a stream ID of 0, whose effects are global for the
connection, result in a transaction being created for each frame.