You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I've noticed that the recommended way of using multiple socket.io server nodes that do http long-polling and therefore maintaining a sticky session is to be done via cookies - according to https://socket.io/docs/v4/using-multiple-nodes/.
However, this crate does not seem to support that as reqwest's cookie store needs to be enabled as a feature and through a client builder.
Would you consider adding that functionality? I'll happily prepare a PR.
The text was updated successfully, but these errors were encountered:
This might not be that easy as I initially thought due to the fact that there are two transports created - one for handshake and one afterwards with the SID which wouldn't share cookies.
Hi,
I've noticed that the recommended way of using multiple socket.io server nodes that do http long-polling and therefore maintaining a sticky session is to be done via cookies - according to https://socket.io/docs/v4/using-multiple-nodes/.
However, this crate does not seem to support that as reqwest's cookie store needs to be enabled as a feature and through a client builder.
Would you consider adding that functionality? I'll happily prepare a PR.
The text was updated successfully, but these errors were encountered: