Cache

Use cache when Fluxheim sits in front of an origin and repeated responses should be served faster.

Proxy cache example

[cache]
enabled = true
default_ttl_secs = 300
max_object_bytes = "32MiB"
status_header = "X-Cache-Status"

[cache.memory]
enabled = true
max_size_bytes = "256MiB"

[cache.disk]
enabled = true
path = "/var/cache/fluxheim/site"
max_size_bytes = "10GiB"

Cache backends

Backend locale localeUsalo quando
memoryYou need the fastest cache and can keep objects in RAM.
diskYou need cache capacity that survives process restarts.
tieredVuoi memory per oggetti caldi e disk per capacità maggiore.
storage-binTi aspetti churn alto e vuoi allocazione disk bounded.
encrypted diskYou need cache-at-rest protection for disk objects.

Route cache policy

[[vhosts.routes]]
name = "assets"
path_prefix = "/assets/"
action = "proxy"

[vhosts.routes.proxy]
upstreams = ["127.0.0.1:3000"]

[vhosts.routes.cache]
enabled = true
status_ttls = { "200" = 3600, "404" = 60 }
content_types = ["text/css", "application/javascript", "image/*"]
extensions = ["css", "js", "png", "webp", "svg"]
include_query = false
stale_while_revalidate_secs = 30
stale_if_error_secs = 120

Advanced cache controls

ControlloloScopo
lockCollapse concurrent misses so one request fills the cache.
range.sliceCache fixed byte slices for large files and resumable downloads.
peer_fillPermetti a un edge di riempire da un altro edge prima di usare origin.
origin_protectionLimita i fill origin concorrenti durante pressione alta.
cache_purgerPulisci entry disk stale in batch bounded.

Use cache carefully

  • Do not cache private user pages unless the route is explicitly safe.
  • Keep cache keys bounded and predictable.
  • Usa purge o TTL brevi quando il contenuto cambia spesso.
  • Bypass su cookie, authorization, header preview e query string non sicure.
Italiano