# HTTP/2

**URL:** <https://community.gatling.io/t/http-2/2025>\
**Category:** Gatling (Open-Source)\
**Created:** [February 18, 2015, 11:51am UTC](https://community.gatling.io/t/http-2/2025 "2015-02-18T11:51:59Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![empty\_account](https://avatars.discourse-cdn.com/v4/letter/e/74df32/32.png) [@empty\_account](https://community.gatling.io/u/empty_account)\
**Post date:** [February 18, 2015, 11:51am UTC](https://community.gatling.io/t/http-2/2025/1 "2015-02-18T11:51:59Z")

</div>

Hi,

Is Gatling likely to support HTTP/2 in the near future?

Adrian

---

<div class="post-metadata">

**Author:** ![slandelle](https://dub1.discourse-cdn.com/flex013/user_avatar/community.gatling.io/slandelle/32/4_2.png) [@slandelle](https://community.gatling.io/u/slandelle)\
**Post date:** [February 18, 2015, 12:07pm UTC](https://community.gatling.io/t/http-2/2025/2 "2015-02-18T12:07:15Z")

</div>

Not in the near future, but it will, of course.

Yes, the spec was announced as done today by the IESG, but there’s still a long way to go before it becomes a widely used technology with stable implementations that can be used for production…

Regarding HTTP/2 support in Gatling, things will work this way:

Waiting for stable HTTP/2 support in Netty =\> Implement HTTP/2 support in AsyncHttpClient =\> Implement HTTP/2 support in Gatling

Quite some work 🙂

Does your company already have some plans for HTTP/2? Are you already playing by implementations of the drafts?