Endel Dreyer

Let's keep this issue open, maybe this will pop in the future...

@vitalyrotari @serjek apparently this has been finally fixed on the react-native side! https://github.com/facebook/react-native/commit/86db62b7a8b28ac82dd0a0627a8b6c351875f682

Hi @tottaka, this has been introduced recently on the WebSocket implementation embedded with Colyseus: https://github.com/colyseus/colyseus-unity3d/pull/158/files Would be nice to move that implementation to this repo as well

Hi @Harris-lans, could you provide a project in which I can reproduce this? Thanks!

Hi @dylanh724, I haven't tested, but you're probably right. This library uses `System.Net.WebSockets.ClientWebSocket` ([docs](https://docs.microsoft.com/en-us/dotnet/api/system.net.websockets.clientwebsocket?view=netcore-3.1)) Here's what they say in their docs: > Some of the classes and class elements in...

Hi @veboys, the browser does not allow sending custom HTTP headers through WebSocket requests. I think what you could do is sending the data you need through query string instead...

Hi @AmineZouitine, if you're referring to HTTP basic-auth you need to provide an `Authorization` header with the credentials encoded in base64 format. See more at https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Authorization **EDIT:** keep in mind...

Hi @tfgstudios, this change on the library has been introduced since this PR https://github.com/endel/NativeWebSocket/pull/11, IIRC this new threading mechanism was due to extra unnecessary delays happening on the previous implementation...

Nice, thanks for sharing @Iblis! I'm curious how to use your lib, do you mind including a usage example in your project? Cheers

Hi @salinhard, could it be a certificate issue? Can you confirm on this SSL reports if yours is valid? https://www.ssllabs.com/ssltest/ A recurring SSL configuration issue I see (and do myself...