Open NovusTheory opened 6 years ago
This also seems to fix the issue its a modified websocket based on the original websocket class so all you have to do it replace clientwebsocket with this class and it works. https://github.com/PingmanTools/System.Net.WebSockets.Client.Managed
Thank you for that @xXBuilderBXx. I will look into this!
As per how ClientWebSocket works in .NETFramework (Microsoft's problem) the WebSocket fails to connect properly or at least will throw an exception saying the "Connection" header is invalid because Lavalink is sending
Upgrade,Keep-Alive
and Microsoft programmed it to only allow a connection header equal toUpgrade
.Workaround / Likely only fix => Create custom WebSocket class. EDIT: WebSocket4Net usage works too