Maxim,
On 4/13/2017 8:07 AM, Maxim Dounin wrote:
Note: there is no HTTP/2 push support in nginx as of now. If you
indeed see the resources being pushed with the "Link" header,
likely you are using cloudflare and this is something Cloudflare
does for you.
Thank you for clarifying. That did
e this. This doesn't need
> > HTTP/2 between nginx and upstream servers.
>
> On 4/12/2017 2:13 PM, Igal @ Lucee.org wrote:
> >
> > If my Upstream (Tomcat, for example) generates a dynamic page for the
> > client, then it can keep track of all of the images on that
Hello,
On 4/12/2017 12:59 PM, Maxim Dounin wrote:
It's just a matter of providing upstream servers
with a way to push resources, e.g., via something like the
X-Accel-Push header or something like this. This doesn't need
HTTP/2 between nginx and upstream servers.
On 4/12/2017 2:13 PM, Igal
> Please watch the clip at https://youtu.be/QpLtBftqM04?t=34m51s until
> about 36m12s where Simone Bordet, a Jetty developer, claims that
> HA Proxy is a better proxy solution than nginx because it talks
> HTTP/2 to the Upstream.
This statement is misleading.
As of now, haproxy does
Thank you, Maxim and Valentin, for your prompt replies. I will reply
here to both so that we can maintain a single thread for this issue:
On 4/12/2017 12:57 PM, Valentin V. Bartenev wrote:
Server Push doesn't require HTTP/2 from the Upstream side. Moreover,
upstream usually don't have
t 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).
>
> While nginx can not know which resources should be pushed on a dynamic
> page, as dynamic pages can not be simply
pporting 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 reso
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
