- Path rules with their own TTL, disk budget per cache
- Honour or ignore backend cache headers
- Purge from the panel, X-Cache-Status on every response
- Hit and miss statistics
- Serves its own domains or takes over the target's domains on the same server
- Reaches targets on other servers through the restricted :8099 entrypoint
What it is for
Static-heavy sites, image-serving APIs, anything where the same response is computed again and again. Put a cache in front, pick which paths to cache and for how long, and the origin only sees misses.
Placement
A cache serves its own domains and, on the target’s server, can take over the target’s domains too. From another server it reaches the target through the target’s :8099 entrypoint restricted to the cache’s IP, so the origin is never published. In front of a load balancer the balancer gains an internal X-Dockxo-Via router for its caches.
Controls
- Path rules: cache
/images/*for a week,/api/*for 30 seconds, skip/admin/*. - Disk budget: the cache evicts by itself when the budget is reached.
- Headers: honour the backend’s
Cache-Controlor ignore it and apply your own TTL. - Purge: everything or a path prefix, from the panel or the API.
- Statistics: hit ratio and bytes served from cache; every response carries
X-Cache-Status.