fix: apply CORS restrictions #4168
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Restrict CORS to allow only localhost and 127.0.0.1 for development purposes.
CORS is not strictly required for our use case, as the REST API, WebSocket, and Static File Server are all hosted on the same host and port. However, to support development workflows—such as working on themes—we allow access to the Client REST API from
localhostor127.0.0.1.This change restricts access from third-party websites, ensuring that only local development environments can make cross-origin requests. Note that this does not affect the
External Client Menufeature, as long as the host URL is accessed directly.