# HTTP/2 **URL:** \ **Category:** Development\ **Tags:** development\ **Created:** [February 6, 2015, 7:54pm UTC](https://community.zeek.org/t/http-2/3479 "2015-02-06T19:54:39Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![McMahon\_Kevin\_J](https://avatars.discourse-cdn.com/v4/letter/m/ecc23a/32.png) [@McMahon\_Kevin\_J](https://community.zeek.org/u/McMahon_Kevin_J)\ **Post date:** [February 6, 2015, 7:54pm UTC](https://community.zeek.org/t/http-2/3479/1 "2015-02-06T19:54:39Z")
Has anyone done any work on upgrading Bro to support HTTP/2? If so I'm very interested in what might have been done and/or what is being done? ---
**Author:** ![Vlad\_Grigorescu1](https://avatars.discourse-cdn.com/v4/letter/v/f9ae1b/32.png) [@Vlad\_Grigorescu1](https://community.zeek.org/u/Vlad_Grigorescu1)\ **Post date:** [February 6, 2015, 8:53pm UTC](https://community.zeek.org/t/http-2/3479/2 "2015-02-06T20:53:30Z")
I don’t believe anyone’s done any work on this. From what I can tell, most implementations (at least IE, Firefox, and Chrome) are only supporting HTTP/2.0 over TLS. If that trend continues, the only changes to Bro might just be ensuring that the SSL analyzer would work with it. –Vlad ---
**Author:** ![anthony\_kasza1](https://avatars.discourse-cdn.com/v4/letter/a/dfb087/32.png) [@anthony\_kasza1](https://community.zeek.org/u/anthony_kasza1)\ **Post date:** [February 6, 2015, 10:00pm UTC](https://community.zeek.org/t/http-2/3479/3 "2015-02-06T22:00:00Z")
I was under the impression the spec was still being drafted. -AK ---
**Author:** ![Seth\_Hall3](https://avatars.discourse-cdn.com/v4/letter/s/d6d6ee/32.png) [@Seth\_Hall3](https://community.zeek.org/u/Seth_Hall3)\ **Post date:** [February 7, 2015, 4:42am UTC](https://community.zeek.org/t/http-2/3479/4 "2015-02-07T04:42:32Z")
It’s basically done. [https://http2.github.io/](https://http2.github.io/) Implementations and real world use are starting to show up all over the place. If you’d like to dig around and find evidence of http/2 being used unencrypted, that could be a huge motivator for someone to take it on. Thanks to google, this space is even more muddied than just HTTP/2. They have a new protocol named QUIC that is yet another pain to support, and this protocol is also already in use when Chrome connects to a number of Google properties.   .Seth ---
**Author:** ![McMahon\_Kevin\_J](https://avatars.discourse-cdn.com/v4/letter/m/ecc23a/32.png) [@McMahon\_Kevin\_J](https://community.zeek.org/u/McMahon_Kevin_J)\ **Post date:** [February 10, 2015, 9:38pm UTC](https://community.zeek.org/t/http-2/3479/5 "2015-02-10T21:38:56Z")
All, Ok, thanks for the feedback. I've got some colleagues looking for samples. I may be enticed to take this on depending on what we find. Kevin ---
**Author:** ![system](https://canada1.discourse-cdn.com/flex011/uploads/zeek/original/1X/f09d732bc2cc7c7cc7e35db67cf4e1d5233ce7a7.png) [@system](https://community.zeek.org/u/system)\ **Post date:** [May 6, 2022, 3:42pm UTC](https://community.zeek.org/t/http-2/3479/6 "2022-05-06T15:42:27Z")