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

Serviço backend	Use quando
`memory`	You need the fastest cache and can keep objects in RAM.
`disk`	You need cache capacity that survives process restarts.
`tiered`	Quer memória para objetos quentes e disco para maior capacidade.
`storage-bin`	Espera muito churn e quer alocação de disco limitada.
`encrypted disk`	You 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

Controlo operacionalo operacional	Finalidade
`lock`	Collapse concurrent misses so one request fills the cache.
`range.slice`	Cache fixed byte slices for large files and resumable downloads.
`peer_fill`	Permitir que um edge preencha a partir de outro edge antes de usar origin.
`origin_protection`	Limitar fills concorrentes de origin sob pressão alta.
`cache_purger`	Limpar entradas stale em disco em lotes limitados.

Use cache carefully

Do not cache private user pages unless the route is explicitly safe.
Keep cache keys bounded and predictable.
Use purge ou TTLs curtos quando o conteúdo muda frequentemente.
Bypass em cookies, authorization, preview headers e query strings inseguras.