Different SessionId between %CSP.Page and %CSP.Websocket
We are having a problem where sometimes a websocket connection started from a CSP page does not share the same SessionId as the CSP page itself. We are also using ECP and can see that both sessions are often even on different application servers.
Is there any way to force a websocket request to go to the same server using the same CSP session as the page it's being called from? We have already tried with passing the CSPCHD GET parameter containing the value of %session.CSPSessionCookie but that does not seem to have any effect.