Denis Zykov

Because this is a fairly common "issue" for which we cannot do anything on development side. My suggestion is to catch the `Mono.Cecil.AssemblyResolutionException` by wrapping its message in something like...

@microsoft-github-policy-service agree

Hi @zydjohnHotmail ! Yes, I recently completely redesigned the package. Now, instead of the globally accessible and static type `TypeConvert`, there is an interface `ITypeConversionProvider` that can be injected into...

Ok, then you could use static class approach: ```csharp // this is compatible with old package's signature public static class TypeConvert { public static TypeConversionProvider Default = new TypeConversionProvider(); public...

I think it is related to self-signed certificate. Here is another issue from original project https://github.com/vtortola/WebSocketListener/issues/104. As for message. It is happens when connection _hello_ part is not valid HTTP...

It's seems two different connections, one is ended with "Not GET request", and second one is connected fine. Browser could hide failed attempt from you because it's 'ok' to re-send...

I have added 0b92673d83e7391e6c5d90cdb2604a92126122e6 better error messages when handshake error is occurring. But I can't find reason why it is happens. Let leave it open. Maybe one day some one...

Are you using last version? Because there is no error "Not GET request" in last version and some error has been fixed.

Are you using WebSocketDeflateExtension?

One more question. Do you CloseAsync() and then Dispose() connected clients? Even faulted during transmission?