Websocket 502 bad gateway sometimes - Githubissues

jshuaf / Aquaforces

The land of the free

0 stars 0 forks source link

Websocket 502 bad gateway sometimes #126

Open ssneilss opened 8 years ago

ssneilss commented 8 years ago

Process

Open aquaforces.com/host/
Refresh a couple of times
Syndrome
Sometimes it's connected while sometimes it gets 502 bad gateway
Solution

This might happen 'cause the time consumed for client and server to connect exceeds websocket's close timeout, maybe we can solve the problem by:

(1) Writing reconnection attempt codes
(2) Using socket.io with its build-in reconnection features

ssneilss commented 8 years ago

----- update -----

tried (1) but failed. seems like if ws://.../host/ connects earlier than http://.../host/ it will be fine