-
Notifications
You must be signed in to change notification settings - Fork 10.4k
Keep Kestrel's connection PipeReader in a consistent state #16725
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pending tests, this looks good.
src/Servers/Kestrel/Core/src/Internal/Http/Http1ContentLengthMessageBody.cs
Outdated
Show resolved
Hide resolved
Needs @Pilchie approval to get it in, and we need to get it in today for preview3 (without QB approval). |
- When the request body PipeReader.ReadAsync throws, the connection-level pipe should be advanced, so subsequent attempts to read from the connection-level pipe don't fail unnecessarily
20ac3e0
to
1c5707e
Compare
This comment was made automatically. If there is a problem contact [email protected]. I've triaged the above build. I've created/commented on the following issue(s) |
@jkotalik this is ready. |
1c5707e
to
618a66e
Compare
618a66e
to
4e5acc7
Compare
pipe should be advanced, so subsequent attempts to read from the
connection-level pipe don't fail unnecessarily
Addresses #14727