-
Notifications
You must be signed in to change notification settings - Fork 5
Open
Labels
bugSomething isn't workingSomething isn't working
Description
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 to Upgrade
.
Workaround / Likely only fix => Create custom WebSocket class. EDIT: WebSocket4Net usage works too
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working