On 6/24/2015 1:23 PM, Willy Tarreau wrote: > 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.
Awesome. It sounds like your plans line up perfectly with what I had envisioned. I think that TLS is a separate discussion. I assume that because the final spec makes it optional, haproxy will not enforce it on the back end, in the http/2 client code. I'm curious what you think about it being optional on the front end. I heard that Mozilla and Google have both stated that they will require TLS for http/2. I wonder whether Firefox and Chrome will be forced by industry pressure to make it optional. Thanks, Shawn
