You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to use the WS listener with socket.io on the client side (where the WS and HTTP servers are under different domains).
I get a message saying thet Access-Control-Allow-Origin header is not set.
How can it be set on the srver side?
The text was updated successfully, but these errors were encountered:
hvta
changed the title
How to bypass CORP?
How to bypass CORS?
Apr 11, 2018
However, as far as I remember, socket.io is more than just a websocket. In the other hand, this component is pure raw websocket protocol, no fallback to other transports.
I'd like to use the WS listener with socket.io on the client side (where the WS and HTTP servers are under different domains).
I get a message saying thet
Access-Control-Allow-Origin
header is not set.How can it be set on the srver side?
The text was updated successfully, but these errors were encountered: