search

leporo / tornado-redis

Asynchronous Redis client that works within Tornado IO loop.
666 stars 162 forks source link

Websocket demo is not working on a public interface #66

Closed davidblaisonneau-orange closed 10 years ago

davidblaisonneau-orange commented 10 years ago

When the client is not on the server, we need to replace the websocket url by the public ip of the server, but when the websocket refuse to open.

On firebug: I got a 400 Bad Request.

With an other app using tornado-redis (https://github.com/Orange-OpenSource/Real-Time-Nodes-Statistics) I got this output: AttributeError: 'NoneType' object has no attribute 'write_message'

Thanks

leporo commented 10 years ago

Could you please provide more information on this issue? What's your production server configuration: I'm not interested in hardware, just OS and what proxy servers do you use, if any?

Could you please also try the SockJS demo?

Thank you

On Wed, Jun 25, 2014 at 6:30 PM, David Blaisonneau <notifications@github.com

wrote:

When the client is not on the server, we need to replace the websocket url by the public ip of the server, but when the websocket refuse to open.

On firebug: I got a 400 Bad Request.

With an other app using tornado-redis ( https://github.com/Orange-OpenSource/Real-Time-Nodes-Statistics) I got this output: AttributeError: 'NoneType' object has no attribute 'write_message'

Thanks

— Reply to this email directly or view it on GitHub https://github.com/leporo/tornado-redis/issues/66.

davidblaisonneau-orange commented 10 years ago

I work on it this morning and find the issue. My company force the usage of a proxy even for local network, so it works for getting the page, but for WS it fallback to pure HTTP and fails. When I force a direct path with foxyproxy it works. Sorry for this ticket, now I will try to find how to catch the usage of pure http beside WS.

Thanks for your answer, it guides me to check the basis :)

PS: I am on Firefox 29 with a Mint 17(Ubuntu 14.04).