-
-
Notifications
You must be signed in to change notification settings - Fork 799
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
nginx websocket proxy #44
Comments
Does the connection work from your browser directly? Would be good to establish that it works without the proxy in the way; might be a browser-specific bug as well. That said, the current |
I found the culprit. It looks like specifying the ws:// url for the code for that in autobahn is at : https://github.com/crossbario/autobahn-python/blob/a771b54bc93f4d0cc273162dc737f2c528a92fdd/autobahn/websocket/protocol.py#L2508 by removing the url at https://github.com/andrewgodwin/channels/blob/master/channels/interfaces/websocket_asyncio.py#L23 my errors goes away and it looks like everything is working now. |
Fantastic, thanks for investigating - will remove that now. |
Fixes #44 also for twisted backend
Hi,
I'm currently playing with django channels and it looks really great. I have tried several other websocket stuff in the last weeks, like crossbar (http://crossbar.io) and something I have build with tornado.
I have added following snippet to my nginx configuration:
which works fine with other websocket servers, but it looks like it won't work with runwsserver.
(I tried asyncio and twisted).
The error I see in the browser is:
WebSocket connection to 'ws://localhost/ws/asd' failed: Error during WebSocket handshake: Unexpected response code: 400
I can see that the websocket server is reached since it prints some debug lines:
but thats not really helpful ;)
I'll try to dig into the code at the weekend, but maybe someone can help me before that ;)
Thanks,
Bastian
The text was updated successfully, but these errors were encountered: