How is server push implemented in current nginx?
Can nginx itself automatically parse HTML/CSS and send required resources?
Is there a mechanism for the proxied application to specify additional resources? (for JavaScript use)
Can nginx itself automatically parse HTML/CSS and send required resources?
Is there a mechanism for the proxied application to specify additional resources? (for JavaScript use)
HTTP/2's 'Server Push' feature is not supported in this patch and will not be supported in the first production-ready release of the HTTP/2 implementation. This feature might appear in a future NGINX release. [1]
I believe that it's going to take a while to find good heuristics that work in most of the cases. Until then only big companies like Google will have the financial incentive to develop their own custom version that's tailored to their specific use-case.
Once you've got code running on the client then there's significantly less need for server push, as you can initiate requests in a bunch of ways, XHRs or <img> tags etc.
Server push's big win is in getting necessary resources down to the client on the initial page load without waiting for numerous round. As such, you'll see the biggest gains on high latency connections, e.g. mobile.