We are experiencing a weird problem with Phoenix Websockets.
We are exposing an authenticated channel. The authentication is made getting the
token from the token parameter given during the connection, and then if the token is valid the connection is established.
The problem is that the token is passed as query param in the url of the connection (for example …/socket/websocket?token=…).
For us this is a problem because in some cases we have very long token (2500 chars) which generates a url which have a length greater than the one accepted by our load balancer.
So my question is: is there an alternative way to pass a token along a websocket connection (maybe through a header on into the request body)?