"multiplexing" seems to be a good use case for upstream proxying. We don't have control how fast end users adopting HTTP/2, so we may still have tons of HTTP/1.x requests coming in, but we can certainly upgrade upstream servers that we control to support HTTP/2. If nginx upstream proxy module can also support HTTP/2, we will be able to take advantage of "multiplexing" the connection between nginx and upstream.
Thanks! Frank On Mon, Dec 14, 2015 at 8:17 AM, Maxim Dounin <[email protected]> wrote: > Hello! > > On Fri, Dec 11, 2015 at 10:03:15PM +0000, Nicholas Capo wrote: > > > Is HTTP/2 proxy support planned for the near future? > > Short answer: > > No, there are no plans. > > Long answer: > > There is almost no sense to implement it, as the main HTTP/2 > benefit is that it allows multiplexing many requests within a > single connection, thus [almost] removing the limit on number of > simalteneous requests - and there is no such limit when talking to > your own backends. Moreover, things may even become worse when > using HTTP/2 to backends, due to single TCP connection being used > instead of multiple ones. > > On the other hand, implementing HTTP/2 protocol and request > multiplexing within a single connection in the upstream module > will require major changes to the upstream module. > > Due to the above, there are no plans to implement HTTP/2 support > in the upstream module, at least in the foreseeable future. If > you still think that talking to backends via HTTP/2 is something > needed - feel free to provide patches. > > -- > Maxim Dounin > http://nginx.org/ > > _______________________________________________ > nginx mailing list > [email protected] > http://mailman.nginx.org/mailman/listinfo/nginx >
_______________________________________________ nginx mailing list [email protected] http://mailman.nginx.org/mailman/listinfo/nginx
