-
Notifications
You must be signed in to change notification settings - Fork 84
ResponseCompression async APIs write synchronously #247
Comments
I think we should open an issue in https://github.com/dotnet/corefx for DeflateStream. @Tratcher Did you verify that DeflateStream.FlushAsync() was being called by ResponseCompression prior to DeflateStream.Dispose()? |
We should check tomorrow see if that fixes this issue on .NET Core. It's not unreasonable for DeflateStream.Dispose() to call InnerStream.Write() if there's still unflushed output. |
No, I had tried it, it was still calling Flush. |
Bringing back to triage |
This is still missing in 2.1.0-rc1-final. Will this be done in RC2? |
No this isn't getting fixed for 2.1. We need to get some work done on the underlying compression streams to enable it. The worst cases I saw when I checked last were Flush and Dispose. |
cc @davidfowl Something you may want to call out in your amazing new 'diagnosability' doc :) |
We will react to https://github.com/dotnet/corefx/issues/32665 |
This is now unblocked by dotnet/corefx#33415, pending picking up a new build. |
This is relevant because the servers are planning to disable sync IO: aspnet/HttpSysServer#366
net461
netcoreapp2.0
The text was updated successfully, but these errors were encountered: