Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Connect Pending in Chrome #266

alexdresko opened this Issue Mar 22, 2012 · 10 comments


None yet
5 participants

I thought I was doing something stupid in my little signalr playground, but I just discovered that the Signalr.Hosting.AspNet.Samples project (I just got latest) doesn't even do what it's supposed to do in Chrome. If I open the Network tab in Chrome's dev tools, the /Connect call (line 525 in signalr.js) always shows as "Pending" in the "Time" column... sometimes, eventually, it will finish, but the resultant stream from the server is incredibly flaky. I've seen this happen on every Chrome installation I've tried it on. The same samples work great in IE and FireFox.

Please let me know if there's any information I can provide you to help diagnose this issue.


davidfowl commented Mar 22, 2012

That's by design. What isn't working? Yes please provide more details. Also use the nuget package, what's on github is in development.

This zip contains a repro: https://skydrive.live.com/redir.aspx?cid=17c1edb06aff1380&resid=17C1EDB06AFF1380!1973&parid=17C1EDB06AFF1380!1972&authkey=!AB2mcmQf9sbrWic

Launch the site in both IE9 and the latest Chrome. Chrome seems to show "connected" almost immediately, while IE takes a couple of seconds. Still, once they're both connected, press "Test" on either browser. IE immediately begins the counting process (0 - 99). Chrome will eventually start, but stops as soon as IE reaches 99, regardless of what number Chrome makes it to (usually around 70 on my machine).

The subject of this thread might not accurately describe the real problem. I just noticed the /connect call in IE seems to end quicker, and clearly the results come back faster and more reliable in IE.

Please let me know if there's anything else you need. I'll go as far as connecting you to my machine so you can see it happen here.


davidfowl commented Mar 24, 2012

Just downloaded your project, opened the main page in both IE and chrome, saw connected in both, then clicked test and watch both go count up to 99 twice. So I can't repro your issue. Maybe there's something you did slightly differently that you forgot to mention or that I forgot to do?

What is the actual bug you're trying to describe, it's still not clear to me.

@davidfowl davidfowl closed this Mar 30, 2012

For future ref this issue turned out to be AVG blocking the responses. It also made the chrome client very slow. 2/3 second responses to simple connects.

Thanks a million, red. For anyone else dealing with this, these instructions show how to exclude your signalr site from AVG Web Protection..


Alternatively, select Tools --> Advanced Settings --> Online Shield --> Web Protection, then uncheck "Enable Web Protection". Will continue looking further to see if I can fix the issue in my web page...

Note that my machine is running AVG 10.0.1424 with DB 2113/4904.

Alex, thanks for finding this! Just spend the last day and a half wrestling with it. Updated AVG settings was the trick!

I wasted huge amounts of time on this too - cant really go telling all your users to put these exceptions in. Large coporates probably would not allow it anyway.


davidfowl commented Apr 24, 2013

Use ssl or longpolling. Nothing you can do about that as protocols just don't work when the response is buffered.

Will give it a go – Thanks for your feedback ☺

From: David Fowler [mailto:notifications@github.com]
Sent: 24 April 2013 19:02
To: SignalR/SignalR
Cc: Graeme Gets
Subject: Re: [SignalR] Connect Pending in Chrome (#266)

Use ssl or longpolling. Nothing you can do about that as protocols just don't work when the response is buffered.

Reply to this email directly or view it on GitHubhttps://github.com/SignalR/SignalR/issues/266#issuecomment-16953444.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment