HTTP/2 on the Upstream

Valentin V. Bartenev vbart at nginx.com
Wed Apr 12 19:57:16 UTC 2017


On Wednesday 12 April 2017 11:40:16 Igal @ Lucee.org wrote:
> According to https://www.nginx.com/blog/http2-module-nginx/#QandA nginx 
> only supports HTTP/2 on the client side, but it is possible to configure 
> proxy_pass to use HTTP/2.
> 
> There is a huge benefit in supporting HTTP/2 on the Upstream, as that 
> will allow the Upstream servers to perform HTTP/2 Push 
> (https://en.wikipedia.org/wiki/HTTP/2_Server_Push).
[..]

That's not related.

Server Push doesn't require HTTP/2 from the Upstream side.  Moreover,
upstream usually don't have access to the static resources that are
served directly from nginx.

> 
> While nginx can not know which resources should be pushed on a dynamic 
> page, as dynamic pages can not be simply cached across different users, 
> the Upstream servers can know which resources should be pushed.
> 
> I really think that nginx should reconsider its position on this matter.
> 
> In the meantime, where can I find documentation on how to configure 
> proxy_pass to use HTTP/2?
> 

There's no such documentation since HTTP/2 isn't supported by the proxy
module.

  wbr, Valentin V. Bartenev



More information about the nginx mailing list