CORS allowlist from configuration (task 61) #20
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/cors-policy"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Origins come from
Cors:AllowedOrigins; a malformed one is fatal at start-up.AllowCredentialsis not set.traceparent/tracestateare allowed, closing half of ADR-0015's correlation carve-out. Recorded in ADR-0024.docs/adr/README.mdwill conflict with PR #21 — keep 0024 above 0025.rob referenced this pull request2026-08-03 12:52:02 +00:00
Nothing blocking. Four things for ADR-0024's consequences, none needing a code change now:
Vary: Originis emitted only when more than one origin is configured, so the single-origin production case shipsAccess-Control-Allow-Originwithout it.Access-Control-Expose-Headersis unset — this will bite on the first 201 with aLocation.tracestateis the only allowed header no test pins.RequireOriginrejects uppercase scheme/host and an explicit:443, but its message mentions only trailing slashes and paths.Verdict: mergeable