HTTP/2 Server Push and Browser Cache


I’m using Cloudflare with its cache everything rule. I read some documents about HTTP/2 Server Push.

A blog owner said that:

However, there is a very headache problem in server push. If the browser has already cached the resource files which are to be pushed, pushing is just a waste of bandwidth.

Another one said:

Since server push will send the assets to the client as distinct HTTP objects (each with its own Cache-Control headers), they can be cached by the browser just like anything else.

My question is that, HTTP/2 Push and browser cache both are working well? Or If I activate HTTP/2 Push feature for some assets, browser cache won’t work for these assets?

This topic was automatically closed after 14 days. New replies are no longer allowed.