HTTP-caching lader browsere og CDN'er genbruge et response i stedet for at hente det igen, styret af Cache-Control-headeren. Det vindende mønster for web-apps: hash dine asset-filnavne, og cache dem for evigt; hold HTML uncacheable.
To-lags-strategien
http
# Hashed, versioned assets — content never changes for a given URL
Cache-Control: public, max-age=31536000, immutable
# e.g. /static/app.9f2c1a.js (the hash changes when content changes)
# HTML — must always be fresh so it can point at new asset hashes
Cache-Control: no-cache
