Skip to content

DEV: Support 'cors origins' site setting for message-bus #33066

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jun 4, 2025
Merged

Conversation

davidtaylorhq
Copy link
Member

Discourse message-bus traffic is not considered a 'public api' for general consumption. However, it does make sense to have consistency with the CORS behavior of the rest of the app, so that people can use it at their own risk.

Discourse message-bus traffic is not considered a 'public api' for general consumption. However, it does make sense to have consistency with the CORS behavior of the rest of the app, so that people can use it at their own risk.
@SamSaffron
Copy link
Member

I think the way we wire stuff up this is multisite safe, but probably worth double checking. Approving preemptively.

@davidtaylorhq
Copy link
Member Author

Yup this change is inside a RailsMultisite::ConnectionManagement.with_hostname block, which is already doing site-specific stuff

@davidtaylorhq davidtaylorhq merged commit 1281152 into main Jun 4, 2025
16 checks passed
@davidtaylorhq davidtaylorhq deleted the mb-cors branch June 4, 2025 13:22
martin-brennan pushed a commit that referenced this pull request Jun 10, 2025
Discourse message-bus traffic is not considered a 'public api' for
general consumption. However, it does make sense to have consistency
with the CORS behavior of the rest of the app, so that people can use it
at their own risk.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants