Guides
Caching and ETags
Use response cache headers without hiding recovery states.
Cache-Control
Successful public reads use public, short-lived shared caching when API_CACHE_SECONDS is greater than zero. Health is no-store. Partial overview responses are also no-store so database recovery is visible promptly.
Cache-Control: public, max-age=0, s-maxage=30, stale-while-revalidate=120Conditional requests
Every JSON response includes an ETag derived from its response body. Send If-None-Match on a later GET or HEAD request; an unchanged successful response returns 304.
curl -i -H 'If-None-Match: "cached-etag"' https://fluxuscentral.sbs/api/v1/status