On Wednesday 18 March 2015 04:32:55 Mark Mielke wrote:
> 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.

"Server push" doesn't require HTTP/2 for upstream connection.

Upstreams don't request content, instead they return it, so there's nothing
to prioritize from the upstream point of view.


> 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?

HTTP/1.1 actually can perform better than HTTP/2.

HTTP/1.1 has less overhead by default (since it doesn't introduce another
framing layer and another flow control over TCP), and it also uses more
connections, which means more TCP window, more socket buffers and less
impact from packet loss.

There's almost no reason for HTTP/2 to perform better unless you're doing
many handshakes over high latency network or sending hundreds of kilobytes
of headers.

wbr, Valentin V. Bartenev

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx