On Fri, Mar 01, 2013 at 06:10:32PM -0500, Chris Yang wrote:
Hi Baptiste,
Thanks for your suggestion. I have read that article (a few times
actually), and except for a few timeout settings I lack comparing to the
config in the article, everything else (that matters for websocket) seems
to be
Hi Willy,
Thanks for your comments.
It's unusual to see the client write both keep-alive and Upgrade in the
connection header. Thus, I suspect that something between the client and
the server (eg: a proxy on the client side or the application server
itself)
has added it. If it's a proxy on
Hi Chris,
I'm quickly jumping into this thread because I'm seeing something strange :
On Wed, Feb 27, 2013 at 10:35:16AM -0500, Chris Yang wrote:
Hello again,
Regarding the second problem (failure to establishing websocket connections
in supported browsers), I can confirm that it happens on
Hello again,
Regarding the second problem (failure to establishing websocket connections
in supported browsers), I can confirm that it happens on both Chrome and
Firefox. And below is what I see for the '101 Switching Protocols' request
in Firefox when it happened:
Request URL:
Hi Chris,
Please read the article below:
http://blog.exceliance.fr/2012/11/07/websockets-load-balancing-with-haproxy/
You may find answers ;)
cheers
On Wed, Feb 27, 2013 at 4:35 PM, Chris Yang bhp...@gmail.com wrote:
Hello again,
Regarding the second problem (failure to establishing
Hello,
I upgraded to dev17 from dev15. I am running Tornado servers behind HAProxy
with SockJS support. Comparing to before the upgrade, I've noticed two
problematic behaviors:
1. When a client is using IE with xhr-streaming protocol to connect to
servers, such connections are closed (seeing
6 matches
Mail list logo
