Configure Cloudflare cache-everything rules and origin headers #20

New issue

Closed

opened 2026-07-01 00:58:02 +00:00 by manlycucumber · 1 comment

manlycucumber commented

2026-07-01 00:58:02 +00:00

(Migrated from github.com)

Problem

The edge must be configured to cache every cacheable response with long immutable TTLs while respecting origin headers and the data-version key. Misconfiguration here breaks the cost model.

Acceptance criteria

Edge cache rules cache all GET responses under /v1 per the documented key.
Origin cache-control and ETag headers are honored end to end.
Admin/auth and error responses are excluded from cache-everything.
The configuration is documented and version-controlled.

Notes

Keep edge config in the repo so it is reviewable and reproducible.

## Problem The edge must be configured to cache every cacheable response with long immutable TTLs while respecting origin headers and the data-version key. Misconfiguration here breaks the cost model. ## Acceptance criteria - [ ] Edge cache rules cache all GET responses under `/v1` per the documented key. - [ ] Origin cache-control and ETag headers are honored end to end. - [ ] Admin/auth and error responses are excluded from cache-everything. - [ ] The configuration is documented and version-controlled. ## Notes Keep edge config in the repo so it is reviewable and reproducible.

manlycucumber commented

2026-07-03 05:57:43 +00:00

(Migrated from github.com)

Delivered in #136 (squash-merged to develop).

Delivered in #136 (squash-merged to `develop`).

manlycucumber referenced this issue from a commit

2026-08-05 19:02:25 +00:00

feat: ETags, immutable caching, and the data-version stamp (#136)

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

Directorium/Api#20

No description provided.

Rows
Columns