-
Notifications
You must be signed in to change notification settings - Fork 10.3k
DefaultHttpResponse.StartAsync without feature #7778
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
Comments
Yeah I'd be fine with that change. |
Going to put this in preview3 for now (it's a 1 line fix). @muratg are we still fine to merge into preview3 or does it require approval? |
Why do we need it in preview3? What doesn't work that would affect a customer trying preview3? |
If it's not a critical need or preview 3 then I wouldn't bother and just go with |
We decided to keep the flush behavior, but we should still check IsStarted too. |
If there is no
IHttpResponseStartFeature
thenStartAsync
will callBody.FlushAsync
every time. Should it only callBody.FlushAsync
ifHasStarted
is false?https://github.com/aspnet/AspNetCore/blob/25f1f593783de4819a1e8e30dc09af7388cc68b3/src/Http/Http/src/Internal/DefaultHttpResponse.cs#L147-L155
The text was updated successfully, but these errors were encountered: