Skip to content
This repository has been archived by the owner. It is now read-only.

WebSockets error #1338

Closed
dennusb opened this issue May 27, 2015 · 1 comment
Closed

WebSockets error #1338

dennusb opened this issue May 27, 2015 · 1 comment

Comments

@dennusb
Copy link

@dennusb dennusb commented May 27, 2015

Hi,

We are trying the new 1.1.0-beta2 version, and it is using websockets to gather throughput information. Because we want to load balance things in our cluster we have a Squid 3 in front, and now it's dropping the websocket connections. So the througput thing is not working anymore.. we did you guys switch to websockets? Because this is going to cause a lot of trouble with load balancers i think!

@edmundoa
Copy link
Member

@edmundoa edmundoa commented May 27, 2015

Hi,

We added an option to disable websockets in here: #1322, please take a look at the upcoming 1.1-beta-3.

@edmundoa edmundoa closed this May 27, 2015
kroepke added a commit that referenced this issue May 29, 2015
this changes the default behavior to use xhr-polling (or even more basic polling techniques), while still allowing to use the websockets.enabled sytem property to turn on support for more permissive environments

the default behavior should now properly use plain xhr requests (or xdr on IE 9), and fall back to jsonp or even iframe polling.

fixes #1344, fixes #1353, refs #1338 #1322
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.