quic: retire read-closed streams on FIN Previously, after closing the receive side of a stream locally, we ignored incoming STREAM frames and waited for a RESET_STREAM in reply to our STOP_SENDING. Per RFC 9000 Section 3.5, however, a peer that has already sent FIN (Data Sent) may wait for its packets to be acknowledged rather than sending RESET_STREAM, reaching Data Recvd without ever resetting. Because we still acknowledged those packets while dropping the STREAM frames, the receive side never retired, leaking stream state, holding its MAX_STREAMS slot indefinitely, and never returning connection-level MAX_DATA credit for those bytes. For golang/go#70914 Change-Id: I3ccf83cf9c645c50f52beb091250a87f6a6a6964 Reviewed-on: https://go-review.googlesource.com/c/net/+/864420 LUCI-TryBot-Result: golang-scoped@luci-project-accounts.iam.gserviceaccount.com <golang-scoped@luci-project-accounts.iam.gserviceaccount.com> Reviewed-by: Damien Neil <dneil@google.com> Reviewed-by: Nicholas Husin <husin@google.com>
This repository holds supplementary Go networking packages.
This repository uses Gerrit for code changes. To learn how to submit changes to this repository, see https://go.dev/doc/contribute.
The git repository is https://go.googlesource.com/net.
The main issue tracker for the net repository is located at https://go.dev/issues. Prefix your issue with “x/net:” in the subject line, so it is easy to find.