Last post Jan 10, 2019 08:34 PM by jzero
Jan 10, 2019 09:23 AM|Clucasm|LINK
I'm running a website that receives data using a SignalR connection.
The website and SignalR are running on different servers, both under port 80. When I try to establish a SignalR connection I can see (using Wireshark) that initially it will try (and fail) to connect using Websockets. After 5 seconds, it will fall back
to server sent events, again unable to connect. After a further 5 seconds, a connection will be established using long polling. Therefore there is a 10-second delay to establish the SignalR connection which is far too long.
If I move SignalR to another port, e.g. 9999, then the connection works fine using Websockets. However, the website needs to run on all networks, and alternative ports may be blocked by the customer's firewall. Therefore I would like to be able to use
Please can you advise why I am unable to run SignalR on port 80.
Jan 10, 2019 08:34 PM|jzero|LINK
@Clucasm, you not alone, I have same kind of delay, in my case 5~10 secs.
I did not found a clear explanation, but concluded it is due to "Transport Selection Process"
Maybe someone with more knowledge can help us to understand, not only about delay, but why Long-Pooling is used when there are all requirements for WebSockets