3 ms·
Browser caching. This is one that I've found developers et al often overlook. It's also the level of caching that can cause the most headaches. But it's the che
by jjoe 10y ago
Browser caching. This is one that I've found developers et al often overlook. It's also the level of caching that can cause the most headaches. But it's the cheapest to implement and cheapest to run so it's definitely worth getting browser caching right first.
Yes this one's tricky. Especially when you update page layout and assets often.
- laumars 10y agoYou can get around frequent changes by having a cache busting version number. eg <script src="http://example.com/css/all.css?v=1"> then your next update will be <script src="http://example.com/css/all.css?v=2"> The obvious issue is you then cannot cache the base HTML file. But that's something you'd never want to cache for long periods anyway.