Serve static assets with an efficient cache policy

[barredterra]

Is your feature request related to a problem? Please describe.

Google PageSpeed Insight complains that static files served by frappe don't have a caching policy. For example, I'm serving a slideshow on a frappe-based website. The images will be loaded again and again, every time I visit the site.

Describe the solution you'd like

Serve static assets with an efficient cache policy.

Probably we can add some lines here to attach a cache policy to images served.

bench/bench/config/templates/nginx.conf

Lines 77 to 89 in 777b204

	location / {
	rewrite ^(.+)/$ $1 permanent;
	rewrite ^(.+)/index\.html$ $1 permanent;
	rewrite ^(.+)\.html$ $1 permanent;
	location ~ ^/files/.*.(htm|html|svg|xml) {
	add_header Content-disposition "attachment";
	try_files /{{ site_name }}/public/$uri @webserver;
	}
	try_files /{{ site_name }}/public/$uri @webserver;
	}

[ankush]

For example, I'm serving a slideshow on a frappe-based website. The images will be loaded again and again, every time I visit the site.

I don't think this is true as even without cache-control headers browsers will still cache things heuristically. 👀 Open the network tab and check. They'd most likely be loaded from disk. Please confirm if that's not happening ( much worse scenario)

[barredterra]

@ankush I can confirm that Chrome automatically caches files for the short term (i.e., hitting reload does not download the files again). But I expect this cache is short term and will not survive a browser restart, etc. This issue is in regard to long term caching (say, a couple of months or until the content changes).

[ankush]

1.5 mil request with response, 0.5mil more with 304 on FC. EVERYDAY! 🤣