Skip to content

feat!: make CORS opt-in via --cors-allow-all#7

Merged
SeverinAlexB merged 3 commits intomainfrom
feat/no-cors-arg
Mar 10, 2026
Merged

feat!: make CORS opt-in via --cors-allow-all#7
SeverinAlexB merged 3 commits intomainfrom
feat/no-cors-arg

Conversation

@SeverinAlexB
Copy link
Collaborator

@SeverinAlexB SeverinAlexB commented Mar 10, 2026

Summary

  • CORS headers are no longer added by default (breaking change)
  • New --cors-allow-all flag enables permissive CORS (Access-Control-Allow-Origin: *)
  • Production deployments behind reverse proxies (nginx, caddy) no longer need to worry about conflicting CORS headers

Migration

If you rely on the relay's built-in CORS headers, add --cors-allow-all to your startup command.

SeverinAlexB and others added 3 commits March 10, 2026 11:16
Allows disabling relay-level CORS when running behind a reverse proxy
(nginx, caddy) that manages CORS independently.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
BREAKING: CORS headers are no longer added by default. Use
--cors-allow-all to enable permissive CORS (Access-Control-Allow-Origin: *).
This better suits production deployments behind reverse proxies that
manage CORS independently.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@SeverinAlexB SeverinAlexB changed the title feat: add --no-cors flag to disable CORS headers feat!: make CORS opt-in via --cors-allow-all Mar 10, 2026
@SpontaneousOverthrow SpontaneousOverthrow self-requested a review March 10, 2026 10:39
@SeverinAlexB SeverinAlexB merged commit 37926a7 into main Mar 10, 2026
3 checks passed
@SeverinAlexB SeverinAlexB deleted the feat/no-cors-arg branch March 10, 2026 10:40
@SeverinAlexB SeverinAlexB mentioned this pull request Mar 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants