Cache-control that works
Most caching problems are not in the cache — they are in the headers your application sends. Get those right and everything downstream behaves.
The headers that matter
Cache-Control is the main lever: max-age for how long, public or private for who may store it, no-store for things that must never be cached. ETag and Last-Modified let a client revalidate cheaply instead of refetching. Everything from the browser to a CDN obeys these; set them deliberately.
Fingerprint static assets, revalidate HTML
Give static files a content hash in the name and cache them hard — a year, immutable — because a changed file gets a new name. Keep HTML on a short or revalidated cache so a deploy is visible immediately. This one split removes most "why am I seeing the old version" tickets.
Where the cache lives
A Varnish layer or your reverse proxy can cache on the server side using these same headers, taking load off the application entirely. The rule is the same: the origin's headers are the source of truth, so fix them there rather than papering over it downstream.
Still stuck? Mail support@novogara.com — an engineer answers, at any hour. Back to the knowledge base