Last post Jun 26, 2013 03:38 AM by cwt237
May 29, 2013 02:43 AM|cwt237|LINK
Anyone else experiencing that jabbr.net/signalr does not work?
I can log in and get the lobby page, but the page is blank (not showing the rooms, e.g. signalR).
I have tried with IE10, IE9 (simulated), Chrome (24.0.1312.52 m), FF (18.0) and none of them work. In FF I had to add a trusted site rule, since it was complaining about the site not being trusted.
Based on Chrome debugger tool, it seems that it tries to setup a web socket connection, but fails, then tries SSE, but cancels this and then it takes almost 2 minutes to get the response for the LP request:
Then I see a few long polling requests (very slow around 2 minutes), with the same response.
It could be a company policy that is blocking, but it used to work (last week or the week before that - maybe around SignalR 1.1.1 release)
Any ideas or similar experiences?
May 29, 2013 02:53 PM|cwt237|LINK
It works fine from my home computer (totally different network setup) - so I guess there is no problem ...
I am still puzzled why it does not work in the office when it used too, but I guess I will have to dig into why that is.
May 30, 2013 02:35 AM|cwt237|LINK
Just for info (if anyone has same problem):
It seems to be a problem with proxy authentication.
Fiddler shows that I get several: HTTP/1.1 407 Proxy Authentication Required
So this is of course an internal policy kicking in.
May 30, 2013 08:38 AM|davidfowl|LINK
This is the signalr forum. Report jabbr issues on the jabbr issue list https://github.com/JabbR/JabbR
Jun 26, 2013 03:38 AM|cwt237|LINK
For others with same issue, please see:
Forcing the connection to longPolling worked for me.