Google dumps SPDY in favour of HTTP/2, any plans for nginx?
mark.mielke at gmail.com
Wed Mar 18 08:32:55 UTC 2015
I think the ability to "push" content, and prioritize requests are examples
of capabilities that might require intelligence upstream, and therefore a
requirement to proxy HTTP/2 upstream. However, I expect much of this is
still theoretical at this point, and until there are actually upstream
servers that are providing effective capabilities here, HTTP/1.1 will
perform just as good as HTTP/2? I also expect that some of these benefits
could only be achieved if the upstream server knows it is talking to a
specific client, in which case it would make more sense to use an HAProxy
approach, where one client connection is mapped to one upstream
On Tue, Mar 17, 2015 at 6:37 PM, Rainer Duffner <rainer at ultra-secure.de>
> > Am 17.03.2015 um 23:32 schrieb Valentin V. Bartenev <vbart at nginx.com>:
> > On Tuesday 17 March 2015 09:49:04 alexandru.eftimie wrote:
> >> Will there be support for http/2 for upstream connections? I can't seem
> >> find anything about this online ( either SPDY or HTTP/2 for upstream
> >> connections )
> > The problems that SPDY (and HTTP/2) is trying to solve usually do not
> > exist in upstream connections, or can be solved more effectively using
> > other methods already presented in nginx (e.g. keepalive cache).
> > Could you provide any real use case for HTTP/2 in this scenario?
> My guess would be if your upstream is actually a „real“ internet-server
> (that happens to do http/2).
> Somebody trying to build the next „CloudFlare/Akamai/WhateverCDN“?
> Is a world possible/imaginable that only does http/2?
> nginx mailing list
> nginx at nginx.org
Mark Mielke <mark.mielke at gmail.com>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the nginx