node.js HAProxy + WebSocket 断线
声明：本页面是StackOverFlow热门问题的中英对照翻译，遵循CC BY-SA 4.0协议，如果您需要使用它，必须同样遵循CC BY-SA许可，注明原文地址和作者信息，同时你必须将它归于原作者（不是我）：StackOverFlow
原文地址: http://stackoverflow.com/questions/4360221/
Warning: these are provided under cc-by-sa 4.0 license. You are free to use/share it, But you must attribute it to the original authors (not me):
StackOverFlow
HAProxy + WebSocket Disconnection
提问by Ross
I am using HAProxy to send requests, on a subdomain, to a node.js app.
我正在使用 HAProxy 在子域上向 node.js 应用程序发送请求。
I am unable to get WebSockets to work. So far I have only been able to get the client to establish a WebSocket connection but then there is a disconnection which follows very soon after.
我无法让 WebSockets 工作。到目前为止，我只能让客户端建立一个 WebSocket 连接，但是很快就出现了断开连接。
I am on ubuntu. I have been using various versions of socket.ioand node-websocket-server. The client is either the latest versions of Safari or Chrome. HAProxy version is 1.4.8
我在 ubuntu 上。我一直在使用的各种版本socket.io和node-websocket-server。客户端是最新版本的 Safari 或 Chrome。HAProxy 版本为 1.4.8
Here is my HAProxy.cfg
这是我的 HAProxy.cfg
global
maxconn 4096
pidfile /var/run/haproxy.pid
daemon
defaults
mode http
maxconn 2000
option http-server-close
option http-pretend-keepalive
contimeout 5000
clitimeout 50000
srvtimeout 50000
frontend HTTP_PROXY
bind *:80
timeout client 86400000
#default server
default_backend NGINX_SERVERS
#node server
acl host_node_sockettest hdr_beg(host) -i mysubdomain.mydomain
use_backend NODE_SOCKETTEST_SERVERS if host_node_sockettest
backend NGINX_SERVERS
server THIS_NGINX_SERVER 127.0.0.1:8081
backend NODE_SOCKETTEST_SERVERS
timeout queue 5000
timeout server 86400000
server THIS_NODE_SERVER localhost:8180 maxconn 200 check
I've trawled the web and mailing list but can not get any of the suggested solutions to work.
我已经浏览了网络和邮件列表，但无法获得任何建议的解决方案。
(p.s. this could be for serverfault, but there are other HAProxy question on S.O, so I have chosen to post here)
（ps 这可能是因为服务器故障，但 SO 上还有其他 HAProxy 问题，所以我选择在这里发帖）
回答by Shripad Krishna
Upgrade to latest version of socket.io (0.6.8 -> npm install [email protected], which is patched to work with HAProxy)
and download the latest version of HAProxy.
升级到最新版本的 socket.io（0.6.8 -> npm install [email protected]，已打补丁以与 HAProxy 一起使用）并下载最新版本的 HAProxy。
Here is an example config file:
这是一个示例配置文件：
global
maxconn 4096 # Total Max Connections. This is dependent on ulimit
nbproc 2
defaults
mode http
frontend all 0.0.0.0:80
timeout client 5000
default_backend www_backend
acl is_websocket hdr(Upgrade) -i WebSocket
acl is_websocket hdr_beg(Host) -i ws
use_backend socket_backend if is_websocket
backend www_backend
balance roundrobin
option forwardfor # This sets X-Forwarded-For
timeout server 5000
timeout connect 4000
server server1 localhost:8081 weight 1 maxconn 1024 check
server server2 localhost:8082 weight 1 maxconn 1024 check
server server3 localhost:8083 weight 1 maxconn 1024 check
backend socket_backend
balance roundrobin
option forwardfor # This sets X-Forwarded-For
timeout queue 5000
timeout server 5000
timeout connect 5000
server server1 localhost:8081 weight 1 maxconn 1024 check
server server2 localhost:8082 weight 1 maxconn 1024 check
server server3 localhost:8083 weight 1 maxconn 1024 check
回答by kanaka
It's likely that your client is using WebSockets version 76. In which case you can't use "mode http" because the WebSockets handshake violates HTTP. There seems to be ambivalence in the committee about whether the WebSockets handshake should be compatible with HTTP or not. Anyways, the problem with the v76 handshake is that raw data is sent with the handshake (the checksum chunk).
您的客户端很可能使用的是 WebSockets 版本 76。在这种情况下，您不能使用“模式 http”，因为 WebSockets 握手违反了 HTTP。对于 WebSockets 握手是否应该与 HTTP 兼容，委员会似乎存在矛盾。无论如何，v76 握手的问题在于原始数据是与握手（校验和块）一起发送的。
The relevant HAProxy discussion: http://www.mail-archive.com/[email protected]/msg03046.html
相关HAProxy讨论：http: //www.mail-archive.com/[email protected]/msg03046.html
From the discussion it sounds like there might be a way to default to TCP mode and fall back to HTTP for non-WebSockets connections.
从讨论来看，似乎有一种方法可以将非 WebSockets 连接默认为 TCP 模式并回退到 HTTP。
回答by Ilya
We are using a Netty implementation https://github.com/ibdknox/socket.io-nettyand here is the HAProxy file that worked for us. The trick to get it not to fall back to XHR-Polling but use Websockets is putting HAProxy into TCP mode. HAProxy config:
我们正在使用 Netty 实现https://github.com/ibdknox/socket.io-netty，这里是对我们有用的 HAProxy 文件。让它不回退到 XHR 轮询而是使用 Websockets 的技巧是将 HAProxy 置于 TCP 模式。HAProxy 配置：
global
daemon
maxconn 32000
defaults
mode http
timeout connect 5000ms
timeout client 50000ms
timeout server 50000ms
listen http-in
bind *:80
server server1 1.1.1.1:8000 check
server server2 1.1.1.1:8000 check
listen socketio-in
mode tcp
bind *:8080
balance source
timeout queue 5000
timeout server 86400000
timeout connect 86400000
server server1 1.1.1.1:8080 check
server server2 1.1.1.1:8080 check
Where 1.1.1.1 is your IPs
其中 1.1.1.1 是您的 IP
回答by Robin Duckett
Try using Socket.io instead of node-websockets-server, it's an abstraction layer with fallbacks to many different methods of instant communication between browser and server.
尝试使用 Socket.io 而不是 node-websockets-server，它是一个抽象层，可以回退浏览器和服务器之间的许多不同的即时通信方法。
Whilst it's true WebSockets violate HTTP 1.0, they do not violate HTTP 1.1, so you should be able to proxy them with any server capable of proxying HTTP 1.1
虽然 WebSockets 确实违反了 HTTP 1.0，但它们并没有违反 HTTP 1.1，因此您应该能够使用任何能够代理 HTTP 1.1 的服务器来代理它们
