internal/http3: do not treat 1xx status as the final response status TestServer1xxExpect100ContinueRace is flaky for HTTP/3 in std. This is because duplicate status 100 can cause the HTTP/3 transport to accidentally treat 100 as the final response status. Make sure that 1xx headers are always treated as informational status rather than the final status. For golang/go#70914 For golang/go#81119 Change-Id: Id834c403ae565ed00aa03ac89f69b7286a6a6964 Reviewed-on: https://go-review.googlesource.com/c/net/+/822544 Reviewed-by: Damien Neil <dneil@google.com> LUCI-TryBot-Result: golang-scoped@luci-project-accounts.iam.gserviceaccount.com <golang-scoped@luci-project-accounts.iam.gserviceaccount.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.