Damien Arrachequesne ff2b8aba48 fix: do not reset the ping timer after upgrade ...

There was two issues with this behavior:

- v3 clients (with allowEIO3: true) were also receiving a "ping" after
a successful upgrade, which is incorrect (in v3, it's the client that
sends the "ping", and the server answers with a "pong")

- the ping timer is not reset after upgrade on the client-side, so an
upgrade which took longer than the `pingTimeout` duration could lead to
a "ping timeout" error on the client-side

I think the latter issue is present since the initial implementation.

Related: https://github.com/socketio/socket.io-client-swift/pull/1309#issuecomment-768475704

2021-02-02 10:48:02 +01:00

..

parser-v3

feat: add support for v3.x clients

2021-01-14 01:44:52 +01:00

transports

feat: add support for v3.x clients

2021-01-14 01:44:52 +01:00

engine.io.js

fix: correctly pass the options when using the Server constructor (#610)

2020-12-30 10:04:47 +01:00

server.js

feat: add support for v3.x clients

2021-01-14 01:44:52 +01:00

socket.js

fix: do not reset the ping timer after upgrade

2021-02-02 10:48:02 +01:00

transport.js

feat: add support for v3.x clients

2021-01-14 01:44:52 +01:00