We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It's not easy to find good documentation on allowing web sockets. https://outlandish.com/blog/configure-content-security-policy-with-websockets-and-express/ claims you need the domain, but connect-src 'self' ws: wss: seems to be working for me.
connect-src 'self' ws: wss:
The text was updated successfully, but these errors were encountered:
Well there is certainly somewhat of doc findable: https://stackoverflow.com/questions/32986074/content-security-policy-meta-tag-for-allowing-web-socket#41389590
However, I agree it may be a good idea to add a proper doc here.
Sorry, something went wrong.
Though it's kinda already mentioned: https://content-security-policy.com/connect-src/
No branches or pull requests
It's not easy to find good documentation on allowing web sockets. https://outlandish.com/blog/configure-content-security-policy-with-websockets-and-express/ claims you need the domain, but
connect-src 'self' ws: wss:
seems to be working for me.The text was updated successfully, but these errors were encountered: