Update helmet Content Security Policy to allow websocket connections to sources other than the location where the frontend is hosted#513
Merged
Belchy06 merged 2 commits intoEpicGamesExt:masterfrom Feb 26, 2025
Conversation
…to source other than the location where the frontend is hosted
lukehb
approved these changes
Feb 26, 2025
Contributor
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation and see the Github Action logs for details |
mcottontensor
added a commit
that referenced
this pull request
Feb 28, 2025
[UE5.5] Update helmet Content Security Policy to allow websocket connections to sources other than the location where the frontend is hosted (#513)
This file contains hidden or 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.
Relevant components:
Problem statement:
Due to web content security policies, websocket connections to locations other than the same location that the page is hosted from are disallowed. This means that if you were to use a frontend hosted in location X, and a signalling server in location Y, and connect to the frontend with
http://LocationX?ss=LocationY, you won't be able to establish a connection.Solution
Update the default content security policy used by helmet to allow websocket connections from different locations