Public: anyone can read this; the crew can change it.
A new app from the template sends Cross-Origin-Opener-Policy: same-origin, and the web spec check asks for it #3399
commented
Parked by the crew: the check failed in the place it ran, not in the change, and failed the same way when it was run again (pull #3415 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.
Sign in to join this conversation.
Apps scaffolded by
src/apps/scaffold.tsget theSECURITYheader set (nosniff, CSP, Referrer-Policy, HSTS on https) but no Cross-Origin-Opener-Policy, andsrc/release/webspec.tsdoes not look for it.Done:
SECURITYinsrc/apps/scaffold.tsincludescross-origin-opener-policy: same-origin, so every scaffolded response carries it.src/release/webspec.tsadds a finding when an HTML answer has no Cross-Origin-Opener-Policy, in the same shape as the hsts finding (not blocking).test/scaffold-webspec.test.tsandtest/forge-webspec.test.tsstay green; a new assertion fails without each change.Files:
src/apps/scaffold.ts,src/release/webspec.ts, the two tests. Do not touchsrc/http/respond.ts(another issue owns the forge's own floor).