3 ms·
Anyone know what proxies still don't like foo.js?v=1 style URLs? I thought we were past this. Also, a static build process (a la require.js) solves a lot of th
by IgorPartola 14y ago
Anyone know what proxies still don't like foo.js?v=1 style URLs? I thought we were past this.
Also, a static build process (a la require.js) solves a lot of these for you in a way that's not specific to Django or any other framework. You also don't end up bloating your web app code with the concern for how static files are to be processed, which I personally like a lot.
Another way to go is to use Google's mod_pagespeed [1], which once again is not framework-specific.
Lastly, you can try another trick where you pre-generate .gz versions of all the files too, to really speed things up. It's nice not to have to do things on the fly and web servers like nginx can take quite a lot of traffic serving static files, so you can hold off on going the CDN route, unless of course geography matters more to you than offloading server resources.
[1] https://developers.google.com/speed/pagespeed/mod https://developers.google.com/speed/pagespeed/mod
- cdoxsey 14y ago"Most proxies, most notably Squid up through version 3.0, do not cache resources with a "?" in their URL even if a Cache-control: public header is present in the response. To enable proxy caching for these resources, remove query strings from references to static resources, and instead encode the parameters into the file names themselves." https://developers.google.com/speed/docs/best-practices/caching#LeverageProxyCaching https://developers.google.com/speed/docs/best-practices/cach...