Support passing CookieJar to WebSocket through Params

[assembly-adrianlai]

The ws library is not passing the Cookie jar to the Websocket connection.

The server we have is using the cookie in the request to pull out the necessary variables to establish the websocket

The underlying Go library seems to support it but it is ignored and dropped when establishing the WS.

It would be create to support it.

[na--]

Thanks for reporting this! Looking at the current websocket connection code, I can't find any mention of cookies 😞 We need to fix this, though at this point I'm not sure if it wouldn't be a medium-sized breaking change rather than a bugfix, if we just started automatically using the global VU cookie jar 🤦‍♂️ So maybe we should just add the option to specify one manually?

In either case, until we fix this, it seems like the only workaround for this issue is to manually specify the Cookie header value in the WS params' headers option...

[assembly-adrianlai]

Thanks for that, with that workaround, it requires changes to the code on the websocket listener to take the cookies from the header as opposed to the Cookie Jar depending on how the server code was
built which is not ideal but workable for now.

Hope this makes it into a bugfix version soon!

[mstoykov]

fixed by #2193