In our projects we have a strange issue (signalr 1.0.0).
The call with serverSentEvents cancels after 3s, our .done() callback is always 3+ seconds late.
[17:35:13 GMT+0100 (W. Europe Standard Time)] SignalR: Negotiating with '/signalr-angular/signalr/negotiate'. jquery.signalR-1.0.0.js:54
[17:35:14 GMT+0100 (W. Europe Standard Time)] SignalR: Attempting to connect to SSE endpoint 'http://localhost/signalr-angular/signalr/connect?transport=serverSentEvents…TrLr7_CZJZTv410&connectionData=%5B%7B%22name%22%3A%22engine%22%7D%5D&tid=0' jquery.signalR-1.0.0.js:54
[17:35:17 GMT+0100 (W. Europe Standard Time)] SignalR: EventSource timed out trying to connect jquery.signalR-1.0.0.js:54
[17:35:17 GMT+0100 (W. Europe Standard Time)] SignalR: EventSource readyState: 0 jquery.signalR-1.0.0.js:54
[17:35:17 GMT+0100 (W. Europe Standard Time)] SignalR: EventSource calling close() jquery.signalR-1.0.0.js:54
[17:35:17 GMT+0100 (W. Europe Standard Time)] SignalR: This browser supports SSE, skipping Forever Frame. jquery.signalR-1.0.0.js:54
[17:35:17 GMT+0100 (W. Europe Standard Time)] SignalR: SignalR: Initializing long polling connection with server. jquery.signalR-1.0.0.js:54
[17:35:17 GMT+0100 (W. Europe Standard Time)] SignalR: Attempting to connect to 'http://localhost/signalr-angular/signalr/connect?transport=longPolling&conn…TrLr7_CZJZTv410&connectionData=%5B%7B%22name%22%3A%22engine%22%7D%5D&tid=0' using longPolling. jquery.signalR-1.0.0.js:54
connection ready in 3985 ms
[17:35:17 GMT+0100 (W. Europe Standard Time)] SignalR: Longpolling connected jquery.signalR-1.0.0.js:54
Any clue of what to check?
Already checked proxy (none) and antivirus (bitdefender)
Something us buffering your response or for some reason it's just taking longer than 3 seconds to connect. If you have fiddler running click the stream button or server sent events will never work (since by default fiddler buffers). If somehow you're gzipping
the response it'll also fall back to long polling.
andreabalduc...
0 Points
3 Posts
serverSentEvents connection issue
Feb 26, 2013 03:47 PM|LINK
In our projects we have a strange issue (signalr 1.0.0).
The call with serverSentEvents cancels after 3s, our .done() callback is always 3+ seconds late.
[17:35:13 GMT+0100 (W. Europe Standard Time)] SignalR: Negotiating with '/signalr-angular/signalr/negotiate'. jquery.signalR-1.0.0.js:54
[17:35:14 GMT+0100 (W. Europe Standard Time)] SignalR: Attempting to connect to SSE endpoint 'http://localhost/signalr-angular/signalr/connect?transport=serverSentEvents…TrLr7_CZJZTv410&connectionData=%5B%7B%22name%22%3A%22engine%22%7D%5D&tid=0' jquery.signalR-1.0.0.js:54
[17:35:17 GMT+0100 (W. Europe Standard Time)] SignalR: EventSource timed out trying to connect jquery.signalR-1.0.0.js:54
[17:35:17 GMT+0100 (W. Europe Standard Time)] SignalR: EventSource readyState: 0 jquery.signalR-1.0.0.js:54
[17:35:17 GMT+0100 (W. Europe Standard Time)] SignalR: EventSource calling close() jquery.signalR-1.0.0.js:54
[17:35:17 GMT+0100 (W. Europe Standard Time)] SignalR: This browser supports SSE, skipping Forever Frame. jquery.signalR-1.0.0.js:54
[17:35:17 GMT+0100 (W. Europe Standard Time)] SignalR: SignalR: Initializing long polling connection with server. jquery.signalR-1.0.0.js:54
[17:35:17 GMT+0100 (W. Europe Standard Time)] SignalR: Attempting to connect to 'http://localhost/signalr-angular/signalr/connect?transport=longPolling&conn…TrLr7_CZJZTv410&connectionData=%5B%7B%22name%22%3A%22engine%22%7D%5D&tid=0' using longPolling. jquery.signalR-1.0.0.js:54
connection ready in 3985 ms
[17:35:17 GMT+0100 (W. Europe Standard Time)] SignalR: Longpolling connected jquery.signalR-1.0.0.js:54
Any clue of what to check?
Already checked proxy (none) and antivirus (bitdefender)
davidfowl
Contributor
2676 Points
605 Posts
Microsoft
Re: serverSentEvents connection issue
Feb 26, 2013 03:56 PM|LINK
Senior SDE, ASP.NET Team, Microsoft
andreabalduc...
0 Points
3 Posts
Re: serverSentEvents connection issue
Feb 26, 2013 04:41 PM|LINK
fiddler is off (and i've tried also with the stream button on).
If I reissue the call with fiddler, removing the accept: gzip / deflate it works.
I've not enabled compression, what should I've to check?
tnx.
davidfowl
Contributor
2676 Points
605 Posts
Microsoft
Re: serverSentEvents connection issue
Feb 26, 2013 04:50 PM|LINK
What are you running on classic mode? SignalR disables the gzip module in IIS but it only works in integrated mode.
Senior SDE, ASP.NET Team, Microsoft
andreabalduc...
0 Points
3 Posts
Re: serverSentEvents connection issue
Feb 27, 2013 07:12 AM|LINK
uninstalling antivirus solved. Now I've to check what av settings (BitDefender) causes the problem with gzip header