Honour ETag and data-version on responses #27

New issue

Open

opened 2026-07-01 01:05:17 +00:00 by manlycucumber · 0 comments

manlycucumber commented

2026-07-01 01:05:17 +00:00

(Migrated from github.com)

Problem

The Api is cache-first and stamps responses with ETags and a data-version. The client must send conditional requests and respect the data-version so corrections propagate without serving stale content forever.

Acceptance criteria

The client stores and replays ETags via If-None-Match and treats 304 as a cache hit.
The stored data-version is compared on each fetch; a bump invalidates affected cached entries.
Conditional requests do not re-download unchanged payloads.
A data-version change is observable in a test that asserts cache invalidation.

Notes

Data-version + ETag are the contract for correctness-after-correction.

## Problem The Api is cache-first and stamps responses with ETags and a data-version. The client must send conditional requests and respect the data-version so corrections propagate without serving stale content forever. ## Acceptance criteria - [ ] The client stores and replays ETags via If-None-Match and treats 304 as a cache hit. - [ ] The stored data-version is compared on each fetch; a bump invalidates affected cached entries. - [ ] Conditional requests do not re-download unchanged payloads. - [ ] A data-version change is observable in a test that asserts cache invalidation. ## Notes Data-version + ETag are the contract for correctness-after-correction.

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/Ordo#27

No description provided.

Rows
Columns