New issue

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

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Be able to turn off websocket usage #1322

Closed
kroepke opened this Issue May 22, 2015 · 0 comments

Comments

Projects
None yet
1 participant
@kroepke
Contributor

kroepke commented May 22, 2015

In case a reverse proxy is used for the web interface, and it cannot be configured to support websockets and sockjs does not detect that websocket support is missing, add the option to turn off server side support for websockets.

The implementation will then fall back to xhr methods or worse iframe polling for older IEs.

Due to implementation details this has to be done with a system property:
-Dwebsockets.enabled=false

@kroepke kroepke self-assigned this May 22, 2015

@kroepke kroepke added this to the 1.1.0 milestone May 22, 2015

@kroepke kroepke closed this in 70c4e95 May 22, 2015

kroepke added a commit that referenced this issue May 29, 2015

some setups have problems with websockets and even xhr_streaming
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 join this conversation on GitHub. Already have an account? Sign in to comment