HTTP/2 on the Upstream

[Igal @ Lucee.org]

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 @ 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 page and 
> then push them.  How can the Upstream "tell" nginx what to Push?
>

Upon studying HTTP/2 Push further I have learned that the way to do so 
is with the "Link" header, e.g.

Link: </res/css/style.css>; rel=preload; as=style, </res/min/script.js>; 
rel=preload; as=script

Chrome developer tools confirms that these assets are being pushed, so 
it's all good.

You can ignore my previous email if you read this one in time.

Thank you,

Igal Sapir
Lucee Core Developer
Lucee.org <http://lucee.org/>



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20170412/3c53d28a/attachment.html>