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 puse puseLieto, kad
memoryYou need the fastest cache and can keep objects in RAM.
diskYou need cache capacity that survives process restarts.
tieredVēlies memory karstiem objektiem un disk lielākai ietilpībai.
storage-binSagaidi augstu churn un vēlies ierobežotu disk allocation.
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

KontroleMērķis
lockCollapse concurrent misses so one request fills the cache.
range.sliceCache fixed byte slices for large files and resumable downloads.
peer_fillĻauj vienam edge aizpildīt no cita edge pirms origin izmantošanas.
origin_protectionIerobežo vienlaicīgus origin fill augsta spiediena laikā.
cache_purgerTīri stale disk entries ierobežotās partijās.

Use cache carefully

  • Do not cache private user pages unless the route is explicitly safe.
  • Keep cache keys bounded and predictable.
  • Izmanto purge vai īsus TTL, ja saturs bieži mainās.
  • Bypass uz cookie, authorization, preview headeriem un nedrošām query string.
Latviešu