-
Notifications
You must be signed in to change notification settings - Fork 10.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change KestrelServerOptions.AllowSynchronousIO default to false #4774
Comments
@Tratcher could you file a bug on HttpSysServer to track this for 3.0.0? |
We need to do this again in 3.0 https://github.com/dotnet/corefx/issues/32665 |
I just fixed response compression so this is unblocked. |
So System.IO.StreamReader.EndOfStream calls sync Stream.Read...
|
Do we need a StreamReader.EndOfStreamAsync()? Or can we just avoid using this API and recommend other's do the same like with the other sync Stream(Reader) APIs? |
It looks easy enough to just keep reading and check for null. |
cc @stephentoub FYI |
@halter73 @davidfowl why didn't Kestrel block sync response Flush()? It can cause all of the same issues, no? I tried blocking it but found that StreamWriter.Dispose always calls Flush. |
StreamWriter.Dispose() was the reason. aspnet/KestrelHttpServer#1919 (comment) |
All of the diagnostics pages do sync writes.... |
Required after this: #6397 |
KestrelServerOptions.AllowSynchronousIO is going to default to true for 2.0.0. Hopefully we can change this to false in our next major release.
aspnet/Announcements#252 (comment)
@muratg @Tratcher We'll probably want to file a similar issue for HttpSysServer.
The text was updated successfully, but these errors were encountered: