Skip to content
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

Websockets gives 501 error in 'some' networks in NGINX but works via Tomcat #1687

Closed
karansingh1000 opened this issue Aug 4, 2014 · 2 comments

Comments

@karansingh1000
Copy link

Hi Jeanfrancois,

I wanted to request help please.
Protocol: Websockets with fallback as long-polling
Tomcat: 8
NGINX: 1.6.0
Java: 1.7.0_45
OS: Ubuntu

My application works via websockets in most of the networks. But in some of networks when i directly access via NGINX i get:
WebSocket connection to 'ws://11.22.25.15/test/message?X-Atmosphere-tracking-id=0&X-Atmosphere-Framework=2.2.0-javascript&X-Atmosphere-Transport=websocket&X-Atmosphere-TrackMessageSize=true&X-Cache-Date=0&Content-Type=application/json&X-atmo-protocol=true' failed: Error during WebSocket handshake: Unexpected response code: 501

Then it fallsback to Long Polling in NGINX.
But in the same network it works via Tomcat on websockets.
Thus websockets work in tomcat and 'not' via NGINX.
(The same application 'will' run via NGINX on websockets in other networks)

Really Appreciate your help.

Thanks,
Jaskaran

@jfarcand
Copy link
Member

jfarcand commented Aug 4, 2014

Please use the mailing lisr for question : https://groups.google.com/group/atmosphere-framework?pli=1 or buy some support

@karansingh1000
Copy link
Author

This was a issue in the Microsoft Proxy ISA. It does not work on port 80 for websockets.
Suggestion is 443 port fallback with ws protocol.

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

No branches or pull requests

2 participants