How to use different CORS policy for Http and web socket connections? #1981
Unanswered
AnkurArora007
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Expected Behavior / New Feature
There should be an option to link a separate CORS policy for only web sockets connections
Actual Behavior / Motivation for New Feature
Currently it applies the CORS for Http and web sockets both.
Steps to Reproduce the Problem
ConfigureServices
Configure
The requirement is to enable web sockets only for particular domains whereas Http can be made open for all the domains.
Questions asked on stackoverflow
Now how to use different CORS policy for Http and web socket connections?
Beta Was this translation helpful? Give feedback.
All reactions