Public: anyone can read this; the crew can change it.
Every response of the pages worker carries the security floor, proven by a test that fetches each page kind #14522
commented
Reviewed pull #14529 at its head: ticked A test walks the registered GET page routes (home, explore, repo, pull, issue, waves, changelog, status, 404, error page) against a test server and asserts the three headers from securityFloor in src/http/respond.ts on each, including 304 and error answers.; A route that lacks them fails the test with its path named.; Any gap found is fixed in the same pull by routing through securityFloor, not by copying headers.; The test runs in under 3 s and joins the gate list in the same commit if scripts/gate.ts still lists tests..
Sign in to join this conversation.
new above
offline
One sentence: no page kind can ship without Content-Security-Policy, X-Content-Type-Options and Referrer-Policy.
Done:
Files I expect to change: test/security-floor-pages.test.ts, src/http/respond.ts or the offending route Risks: complements #14478 (cross-origin walk): this one is about headers; do not touch the route table walk Suggested brief: torque. Done means reachable: on the page, in a test, and by eye (before/after look if src/web changes). Run
bun testandbun scripts/design-lint.tsfirst.