← Back to Martin Tile Server roadmap
Emit HTTP Cache-Control and Expires headers alongside the existing ETag so that CDNs, reverse proxies, and browsers can cache tiles for a configurable lifetime instead of revalidating every request.
Tiles are among the most cacheable resources a map serves, yet without freshness headers every client is forced back to origin. Adding configurable max-age (ideally per source) would dramatically cut load for deployments that sit behind a CDN.
Open questions to resolve before committing:
- Global default vs. per-source
max-ageconfiguration - How this interacts with Hot Reloading and cache invalidation when the underlying data changes (#1707)
- Sensible defaults for dynamic PostGIS sources vs. immutable PMTiles/MBTiles archives