Websocket: upstream server read EOF after client connected

I use Kong to proxy websocket. But the upstream server read EOF after closed.

The request header is:

Cache-Control : no-cache
Accept-Encoding : gzip, deflate, br
Accept-Language : zh-CN,zh;q=0.9,en;q=0.8,zh-TW;q=0.7,ko;q=0.6,fr;q=0.5,ja;q=0.4,uk;q=0.3,de;q=0.2,it;q=0.1,la;q=0.1,mt;q=0.1,es;q=0.1,da;q=0.1
Sec-Websocket-Key : zQMHDUtFs+Y0mkavXNb3Qg==
Sec-Websocket-Extensions : permessage-deflate; client_max_window_bits
Connection : Upgrade
Pragma : no-cache
Upgrade : websocket
Origin : http://localhost:8087
Sec-Websocket-Version : 13
User-Agent : Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36
Cookie : _ga=GA1.1.16472783.1530098048; Webstorm-8a1fbedf=dfeee5fb-0a1c-41f8-9d07-9cb77d083892; _gid=GA1.1.809737544.1531875313

Will I need configure Kong to support websocket?

1 Like