# What are the plans for HTTP/2?

**URL:** <https://discourse.haproxy.org/t/what-are-the-plans-for-http-2/38>\
**Category:** Help!\
**Created:** [December 15, 2015, 10:54am UTC](https://discourse.haproxy.org/t/what-are-the-plans-for-http-2/38 "2015-12-15T10:54:57Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![sam](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.haproxy.org/sam/32/83_2.png) [@sam](https://discourse.haproxy.org/u/sam)\
**Post date:** [December 15, 2015, 10:54am UTC](https://discourse.haproxy.org/t/what-are-the-plans-for-http-2/38/1 "2015-12-15T10:54:58Z")

</div>

Are there any plans to support HTTP/2 natively in HAProxy (either natively in the frontend or allowing for a HTTP/2 backend) ?

As it stands the only practical method of deploying HTTP/2 would be fronting HAProxy with NGINX or losing out on a bunch of features and doing TCP balancing.

---

<div class="post-metadata">

**Author:** ![ahayworth](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.haproxy.org/ahayworth/32/11_2.png) [@ahayworth](https://discourse.haproxy.org/u/ahayworth)\
**Post date:** [December 15, 2015, 3:11pm UTC](https://discourse.haproxy.org/t/what-are-the-plans-for-http-2/38/2 "2015-12-15T15:11:55Z")

</div>

Hi Sam -

There are plans in the works - there have been a few tidbits thrown out on the mailing list from time to time:

From Baptiste:

> HTTP/2 will be support in 1.7, if not in 1.6 🙂  
> It’s a long journey, you know 🙂

From Willy:

> Thus my first goal with HTTP/2 in haproxy really is to make it a  
> solid H2-\>H1 gateway in order to provide a seamless migration to H2  
> to everyone, just like haproxy was massively used to provide IPv6  
> connectivity for the last IPv6 day.

> I’ll still focus on H2 on the backend but more as a longterm goal, to  
> help making architectural choices when needed, but I don’t see this as  
> a benefit for now. It will probably be one when servers start to exploit  
> server push, which could be a reason for having H2 on the server side.  
> But that’s not urgent in my opinion.

and

> but was a consequence of the applet  
> rework done months ago to prepare for HTTP/2

Hope that helps!

- Andrew

---

<div class="post-metadata">

**Author:** ![hofmanndavid](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.haproxy.org/hofmanndavid/32/108_2.png) [@hofmanndavid](https://discourse.haproxy.org/u/hofmanndavid)\
**Post date:** [August 9, 2016, 3:53am UTC](https://discourse.haproxy.org/t/what-are-the-plans-for-http-2/38/3 "2016-08-09T03:53:56Z")

</div>

Any updates on this ? 😃 I will have to fallback to caddy server if I can’t have http2 here ☹  
Will this be ready/Is this ready on development version 1.7 already?

Thanks!

---

<div class="post-metadata">

**Author:** ![ivan15](https://avatars.discourse-cdn.com/v4/letter/i/6a8cbe/32.png) [@ivan15](https://discourse.haproxy.org/u/ivan15)\
**Post date:** [August 25, 2016, 1:21pm UTC](https://discourse.haproxy.org/t/what-are-the-plans-for-http-2/38/4 "2016-08-25T13:21:09Z")

</div>

+1 here. Looking forward to HTTP/2 support

---

<div class="post-metadata">

**Author:** ![ivan15](https://avatars.discourse-cdn.com/v4/letter/i/6a8cbe/32.png) [@ivan15](https://discourse.haproxy.org/u/ivan15)\
**Post date:** [September 5, 2016, 2:48pm UTC](https://discourse.haproxy.org/t/what-are-the-plans-for-http-2/38/5 "2016-09-05T14:48:25Z")

</div>

This silence is quite scary 🙂

---

<div class="post-metadata">

**Author:** ![ask](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.haproxy.org/ask/32/131_2.png) [@ask](https://discourse.haproxy.org/u/ask)\
**Post date:** [November 3, 2016, 6:12am UTC](https://discourse.haproxy.org/t/what-are-the-plans-for-http-2/38/6 "2016-11-03T06:12:27Z")

</div>

Apache Traffic Server is a very capable HTTP proxy (cache) with good HTTP/2 support. You can put that in front of haproxy, too.