Fix Bug: .NetFramework 4.8 ClientWebSocket Cann't Connect To .Net8 WsSession #278
Comments
lwf163
changed the title
chronoxor
added a commit
that referenced
this issue
Dec 23, 2023
chronoxor
added a commit
that referenced
this issue
Dec 23, 2023
|
Thanks for reporting! Fixed in 8.0.6.0 - please check on your side |
chronoxor
added a commit
that referenced
this issue
Dec 23, 2023
chronoxor
added a commit
that referenced
this issue
Dec 23, 2023
lukebakken
pushed a commit
to lukebakken/NetCoreServer
that referenced
this issue
Feb 8, 2024
lukebakken
pushed a commit
to lukebakken/NetCoreServer
that referenced
this issue
Feb 8, 2024
lukebakken
pushed a commit
to lukebakken/NetCoreServer
that referenced
this issue
Feb 8, 2024
lukebakken
pushed a commit
to lukebakken/NetCoreServer
that referenced
this issue
Feb 8, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I fix a bug is
161 Line, In WebSocket.cs File:
if ((string.Compare(value, "Upgrade", StringComparison.OrdinalIgnoreCase) != 0) && (string.Compare(value, "keep-alive, Upgrade", StringComparison.OrdinalIgnoreCase) != 0) && (string.Compare(value, "upgrade,keep-alive", StringComparison.OrdinalIgnoreCase) != 0))
because request header is "Connection=Upgrade,Keep-alive"
The text was updated successfully, but these errors were encountered: