Tornado does not handle node-http-proxy websockes on linux #765

Closed
srossross opened this Issue Apr 27, 2013 · 4 comments

Projects

None yet

2 participants

@srossross

If I start a server python wsserver.py and then run python wsclient.py --host localhost --port 8888 the tornado server and client behave as expected.

However, if I start up a proxy server as well: node node_modules/http-proxy/bin/node-http-proxy --port 8889 --host localhost --target localhost:8888 then python wsclient.py --host localhost --port 8889 does connect, but no messages get passed.

This works fine on Max osx however fails on ubuntu and centos.

see this stackoverflow question for details

@bdarnell
Member

Why do you suspect that this is a tornado problem instead of a node-http-proxy problem? (or for that matter a websocket-client problem?)

@srossross

It very possible that this is a node-http-proxy problem. I have provided a simple example that demonstrates the problem. I've tested this with chrome and safari browsers with the same issue. I have also verified that the proxy works with a nodejs web-socket server.

I would be grateful for any debugging tips you can provide. how can I test where the issue is coming from?

@bdarnell
Member

tcpdump and wireshark are the best way to see what's really going on.

@srossross

Thanks, this does seem to be an issue with nodejs > 0.6.x

@srossross srossross closed this Apr 28, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment