Geek Answers Handbook

SignalR performs long polling instead of websocket in case of cross domain

When I connect to signalR located in one virtual directory, I receive data through a websocket transport. But in the case of a cross domain, a long poll becomes used as a transport.

Browser compatibility is not a problem as I try in the Chrome browser.

What can I do to use websocket as a transport in case of cross domain.

I tried all possible solutions available on the network, including those available on the wiki signature.

https://github.com/SignalR/SignalR/wiki/SignalR-JS-Client-Hubs

+4
source share
1 answer

Thanks to David for answering my question in the comments:

Since only IIS8 supports websockets and neither SSE nor ForeverFrame work with cross domain, so you are stuck in a lengthy survey -

+5
source

More articles:


All Articles