Issues with Stickiness in Multi-Instance Infrastructure of application with socket.io Due to Third-Party Cookie Restrictions in embed
We are encountering issues with our Socket.io implementation in a multi-instance infrastructure. According to the Socket.io documentation, stickiness is necessary for polling to function correctly. However in our auditing of the phase-out of third-party cookies, we have found that stickiness is not working on our platform, which operates in an embedded context. Specifically, the browser will not allow the cookie to travel, resulting in 400 errors for our polling APIs.