Nikky
10/14/2019, 7:14 PMUrl
, i do not quite understand whats going on..
anyways next weird issue
on javascript it seems like additional headers are not supported on websockets, but i=on jvm it works
according to https://stackoverflow.com/a/4361358/9006779 thats a limitation of the websocket api
is there ways beultin ktor serverside to deal with this on Sessions? or should i manually pass the sessionId via some other way and retreive the Session object manually during the call ?
its weird that this works on the jvm though, same code being called too