Ronnie Overby

Server side (nuget package): > Client side (bower package): > "signalr": "^2.2.0" I'll try your suggested config on Monday. Thanks.

So looking at that ticket you referenced it doesn't seem there is going to be a fix unless I make it myself?

Last time I checked this library has total feature parity with the 2 reader/writer classes found in .NET's BCL. The 7-bit methods are used for communicating string lengths and are...

That's news to me; I doubt they were public at the time, since the entire implementation is a copy-paste-edit. Submit a PR and I'll merge and deploy it.

Apparently these are new in .NET 5: 

Changing the existing methods to value tasks would introduce breaking changes. I'm open to ideas, though.

> looks like `Stream` class won't support them I'm not quite sure what you mean. > However, the new classes in [`System.IO.Pilelines`](https://docs.microsoft.com/en-us/dotnet/api/system.io.pipelines?view=dotnet-plat-ext-3.1) could get a corresponding `AsyncBinaryReader` and `AsyncBinaryWriter`. Interesting.

This seems doable.

Same thing for me. My cors headers are not in the 404 response.

I will post repro.