4 ms·
Probably incorrect - the HTTP/2 push specification is a way for a server to send files the client along with the original request - it makes no mandates about w
by sudhirj 10y ago
Probably incorrect - the HTTP/2 push specification is a way for a server to send files the client along with the original request - it makes no mandates about where the files must be sourced from. It doesn't even say the data needs to be static. Cloudflare already supports push - you set a special header, and the CF proxy will GET the URLs you specify and bundle them along with the original request. No technical Cloudfront or any other CDN can't do this as well.
- jbergstroem 10y agoThe point here is to re-use the already open http2 connection; so I'd argue that you should strive for same-domain transport.
- artursapek 10y agoThat's what I meant - if the HTML page (which knows which assets it will require) is not being served from the same machine as the assets will be, you cannot take advantage of HTTP/2 push.
- jbergstroem 10y agoWell, you can still utilize it. For instance, if you serve `/static.css` from your CDN; you would (should) also add `Link` headers to all same-domain assets tied to it.
- sudhirj 10y agoI think same-domain is enforced - because it's sending data down the same connection (a different domain would need a different connection). The point is that it doesn't matter where the proxy server gets the data from, if the proxy is handline HTTP/2 termination.