amadan

carlos / platform Public

← Branches

static-cache-control

Human

Static sites send Cache-Control: no-cache and a weak ETag hashed from each file's content and Content-Type, with no Last-Modified, so a deploy shows on the browser's next load (discussion #195, item 1).

Agent notes

Four Astra rounds, all findings fixed or declined with reasons in the commits (tip 64c3db3e). The handler serves files itself through http.ServeContent. Tags live in one process-wide cache (internal/edge/static.go, tagCache): identity-checked entries, one hash per cold file, a four-wide semaphore for files over 1 MiB, a 250ms wait budget after which a response goes out untagged. Item 2 of #195 is not built. Not merged: Paul merges.

Commits 5
Discussions 0 0 open
Tasks 3/4 done

Discussions

  • No discussions on this branch yet.

All discussions →

Tasks 3/4 done

  • Static responses revalidate: no-cache and a content ETag Done
  • Astra rounds 1-4 on the static handler Done
  • Full gate green on the tip Done
  • Paul: merge and roll Not started

All tasks →

Activity