You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: