Infinite reconnection if after onopen event triggerred onclose event

[dmytrous]

If after onopen event, server close connection (onclose event), websocket going to infinite recconection. It causes because recconnection counter cleared after onopen event.

[weglov]

Sounds like the correct logic of the reconnect function, in case if after onopen event the client received the onclose then retry the connection until the successful event onopen.

Maybe you should disable the reconnect option in the options?

[dmytrous]

Sounds right, but if i have option 'reconnectionAttempts' equal to 5, websocket must recconnect 5 times and die, it works if no connection with server, but if connection is fine we have infinite recconnection.

In my case, socket is opening connection, something going wrong on server side or something else, i dont know what happens here but connection is closing. After that, socket is connecting to server again because connection is ok, but something wrong again and our connection is closing. And i have infinite recconection.

[KristapsK-globitex]

I have the same issue. I ended up doing it all manually.

[manyvasa]

@dmytrous Have you solved your problem?

[dmytrous]

@dmytrous Have you solved your problem?

Nope

[jeancaffou]

Try #111

[NikolajDL]

In my case, I do some authentication when handling the connection open event server-side and if the authentication fails, the connection is closed. Since the socket successfully connects (but isn't authorized) it doesn't count as an attempt apparently. Is it possible to change the behavior, such that if the connection closes within X (configurable) seconds of being opened, it counts as a failed connection attempt?