Repository navigation
validate haproxy caching behavior #199
Description
OHF-Device-Database/frontend#66 introduced a new astro caching provider that emits standard http caching headers instead of using astro's built-in in-memory cache, eliminating the need to issue requests within the validity window of a resource
what still needs to be evaluated before this is rolled out, is if the haproxy setup just passes these headers through, or if it attempts to do some caching on its own
Metadata
Metadata
Assignees
Type
Projects
- Status
Activity
djwmarcx commentedon Nov 9, 2026
The HAProxy template has no cache section, no cache filter, no cache-use or cache-store directive, no compression filter, and no response rule that adds, removes or rewrites headers. So no problem on that side.
Evaluating cloudflare now
djwmarcx commentedon Nov 9, 2026
Cloudflare does not cache HTML by default and ignores
Vary, so before today every page wascf-cache-status: DYNAMICregardless of what the origin sent. Two Cache Rules now exist on the zone fordevice-database-preview.openhomefoundation.org:Authorization, no?feature=) are eligible for cache, edge TTL "use Cache-Control if present, bypass if not", browser TTL "respect origin".Authorizationheader orfeature=in the query bypasses the cache, so a signed-in or feature-flagged visitor can never be served an anonymous copy.Once the release with the cache provider ships, anonymous pages should go
MISSthenHIT: