# \#http2

**URL:** https://community.emergingthreats.net/tag/http2/8.md

[Latest](https://community.emergingthreats.net/latest.md) · [Categories](https://community.emergingthreats.net/categories.md) · [Tags](https://community.emergingthreats.net/tags.md)

---

## [HTTP/2 in Suricata 6](https://community.emergingthreats.net/t/http-2-in-suricata-6/257)

<div class="topic-metadata">

**Author:** [@bmurphy](https://community.emergingthreats.net/u/bmurphy)\
**Replies:** 0\
**Last updated:** [January 10, 2023, 4:56pm UTC](https://community.emergingthreats.net/t/http-2-in-suricata-6/257 "2023-01-10T16:56:57Z")

</div>

While recently working on a malware sample which had some HTTP2 traffic in it. I was surprised that Suricata did not log or alert on any of the traffic for HTTP2, despite having written a rule for the traffic. Turns out…