-
Notifications
You must be signed in to change notification settings - Fork 78
websockets timeout with signalr #58
Comments
Actually it does not work for SignalR version I have in repository too ... it throws: ---> (Inner Exception #0) System.NotImplementedException: Metoda nebo operace není implementována. Could you try to add this into App.config: <system.diagnostics>
</system.diagnostics> Then look into global.log for exceptions ... Also what version of SignalR you using? I also tried simple websocket echo sample and it works without problem... So I suspect something in SignalR ... |
I forgot about this bug SignalR/SignalR#2720 - and it is still open ... So last signalr which worked ok is 1.x version. |
Server side (nuget package): Client side (bower package):
I'll try your suggested config on Monday. Thanks. |
So looking at that ticket you referenced it doesn't seem there is going to be a fix unless I make it myself? |
Looks like it ... I think they will support only .Net core in future, and even SignalR will not be finished for 1.0 version. Now I expect that I will also port Nowin to .Net core after it will at least a little bit stabilize. |
For the exception: As a dirty work-around I have added my own OwinWebSocketContext to then environment (see: https://github.com/SignalR/SignalR/blob/master/src/Microsoft.AspNet.SignalR.Core/Owin/OwinWebSocketHandler.cs#L66) |
Nice, thanks for sharing! |
When switching my app from Microsoft.Owin.Host.HttpListener to Nowin my signalr hub connections via websockets timeout and then succeed when switching to SSE.
Any idea why this is happening?
Everything else seems to work great with the switch to Nowin.
Here's the js client log showing the timeout:
The text was updated successfully, but these errors were encountered: