[Epic] Caching, ETags & data-versioning #17
Labels
No labels
area: api
area: auth
area: build
area: cache
area: ci
area: compare
area: model
area: provenance
area: rite
backport
blocked
breaking
confirmed
dependencies
duplicate
epic
invalid
needs-info
needs-triage
php
priority: high
priority: low
priority: medium
regression
type: chore
type: correction
type: docs
type: enhancement
type: feature
type: fix
type: perf
type: refactor
type: security
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Directorium/Api#17
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Implement the Cloudflare-fronted cache contract: cache-everything semantics, long immutable TTLs, ETags, and a service-wide data-version stamp that gates invalidation. Done when responses are immutable per key and a version bump is the only way to invalidate.
Epic — child issues are tracked as sub-issues.
Epic complete — strong ETags + immutable
Cache-Control+ conditional-GET 304s (CacheHeaders), the service-wideX-Data-Versionheader on every response, and the Cloudflare origin/edge contract (docs/deploy/cloudflare.md). Live edge rules + purge token remain maintainer infra. #136.