Everything is working smoothly on my localhost but when I Deployed my app on azure (HTTP) it doesn't work. I have tried different scenarios :
a ) persistent connections, b) adding this code :
<httpRuntime targetFramework="4.5.2" maxRequestLength="1048576" executionTimeout="1800" requestValidationMode="2.0"/>
Note: I have enabled the websockets in my azure app service so that isn't the problem. I am using a react-redux app as a frontend and a Asp.net MVC5 as a backend. On Azure I am not using a Virtual machine . Only an App Service
In localhost , the signalR uses websockets but for some reason it fails in azure then it results to longpolling , based from the log:
The Client Called the server method , and the server called the client method as well , but after that the connection is lost. The SignalR will automatically try to reconnect but still it will result to a timeout, any thoughts about this?
Q1 : Why Is the websocket failing on azure? Q2 : in long polling : Why is it going on timeout ? Q3 : in Long polling : why can't it reconnect ?
Any help would be greatly appreciated. Thank you :)