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
When I updated socket.io to v3, I started running a v2 and a v3 server in parallel on separate paths: /socket.io and /socket.io3. (I would have liked to just filter by the EIO parameter, but had issues with that approach.) Now that v3.1.0 is out and the v3 server can handle v2 connections, I'd like to remove the v2 server and send all its remaining requests to v3.
Is it possible for the v3 server to capture from more than one path? Or can I somehow redirect the requests from one to the other? I tested using express to send a 301 but ran into issues, and this might not be very efficient anyway. What's the best way to do this?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
When I updated socket.io to v3, I started running a v2 and a v3 server in parallel on separate paths:
/socket.ioand/socket.io3. (I would have liked to just filter by theEIOparameter, but had issues with that approach.) Now that v3.1.0 is out and the v3 server can handle v2 connections, I'd like to remove the v2 server and send all its remaining requests to v3.Is it possible for the v3 server to capture from more than one path? Or can I somehow redirect the requests from one to the other? I tested using express to send a 301 but ran into issues, and this might not be very efficient anyway. What's the best way to do this?
Beta Was this translation helpful? Give feedback.
All reactions