Our great sponsors
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
The best thing to do is just use the browser's own cache but because of the cache partitioning mentioned in the article, host 3rd party libs on your own site instead of using traditional shared CDN URLs. By hosting yourself you can make sure each resource is at a version specific URL can you can crank the cache durations way up for all your CSS and JS files so you don't even need to do cache validation often. You can even have a cache seeding page the loads every resource if you want. For HTML files make sure that your HTTP servers support last modified or etags so that If-None-Match or If-Modified-Since can be used.
Use a CDN accelerator like Cloudflare to improve load time since server side caching and client to server distance can impact performance.
Caching is solved fairly well by browsers, its usually server misconfiguration or lack of that is the problem.
I think http://www.squid-cache.org/ has options to ignore some of the browsers cache headers and return cached content anyway. But HTTPS caching requires that you let the traffic be intercepted and install custom CA certs so the proxy can be a MITM caching proxy.
Related posts
- Squid: Optimising Web Delivery
- squid proxy cache server without systemd built and ready to serve
- Netflix Canada Just Got Rid of Its Cheapest Ad-Free Plan Without Even a Heads Up
- How to get my IP traffic data to an AWS lambda using Darkstat?
- Help with “manually” making an offline dependency for a project