search

dotnet / aspnetcore

ASP.NET Core is a cross-platform .NET framework for building modern cloud-based web applications on Windows, Mac, or Linux.
https://asp.net
MIT License
35.44k stars 10.03k forks source link

HTTP/3: Connection error if control stream closes #32159

Open JamesNK opened 3 years ago

JamesNK commented 3 years ago

https://quicwg.org/base-drafts/draft-ietf-quic-http.html#section-6.2.1-2

ghost commented 3 years ago

Thanks for contacting us. We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. Because it's not immediately obvious that this is a bug in our framework, we would like to keep this around to collect more feedback, which can later help us determine the impact of it. We will re-evaluate this issue, during our next planning meeting(s). If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

ghost commented 3 years ago

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

JamesNK commented 3 years ago

API required on runtime https://github.com/dotnet/runtime/issues/51848

This is low priority. An error when attempting to write to a write-only stream is sufficient for now. Can reevaluate in the future if it is a problem.

adityamandaleeka commented 3 years ago

Let's sync with runtime on whether we can get that API in during 7.

adityamandaleeka commented 3 years ago

Let's see if the recently added "wait for state change" feature in SNQuic works for this.

ghost commented 2 years ago

Thanks for contacting us.

We're moving this issue to the .NET 7 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s). If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

JamesNK commented 2 years ago

QuicStream.WaitForWriteCompletionAsync() might be useful here for checking if the peer closed the outbound write stream.

ghost commented 2 years ago

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

adityamandaleeka commented 2 years ago

We don't think this will affect real users much (only broken clients would run into this). Moving to backlog for now.