<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hello,<br>
<br>
On 4/12/2017 12:59 PM, Maxim Dounin wrote:<br>
<blockquote type="cite">
<pre wrap="">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.
</pre>
</blockquote>
<br>
On 4/12/2017 2:13 PM, Igal @ Lucee.org wrote:<br>
<blockquote
cite="mid:7c70d560-3b3f-5e6a-1475-852de3ea25f8@lucee.org"
type="cite">
<p>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?</p>
</blockquote>
<br>
Upon studying HTTP/2 Push further I have learned that the way to do
so is with the "Link" header, e.g.<br>
<br>
<tt>Link: </res/css/style.css>; rel=preload; as=style,
</res/min/script.js>; rel=preload; as=script</tt><br>
<br>
Chrome developer tools confirms that these assets are being pushed,
so it's all good.<br>
<br>
You can ignore my previous email if you read this one in time.<br>
<br>
Thank you,<br>
<br>
<div class="moz-signature">
<p>Igal Sapir
<br>
Lucee Core Developer
<br>
<a href="http://lucee.org/">Lucee.org</a></p>
</div>
<br>
<br>
</body>
</html>