-
Notifications
You must be signed in to change notification settings - Fork 18k
x/net/http2: add DialTLSContext to Transport #52114
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
It seems like we clearly need DialTLSContext given that it's already in http.Transport. |
Based on the discussion above, this proposal seems like a likely accept. |
No change in consensus, so accepted. 🎉 |
FYI #50392 is a duplicate (rather, was written first, but the PR and this issue were written after without linking to it) |
Change https://go.dev/cl/377114 mentions this issue: |
Fixes golang/go#52114 Change-Id: Ibc0ba6b401bb39ea89f88796d55fbf781596140e GitHub-Last-Rev: 488673bebeca2cc9d79328cc348ac1014096b697 GitHub-Pull-Request: golang/net#123 Reviewed-on: https://go-review.googlesource.com/c/net/+/377114 Reviewed-by: Ian Lance Taylor <iant@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Damien Neil <dneil@google.com> Run-TryBot: Ian Lance Taylor <iant@google.com>
net.Transport contains DialContext, but http2.Transport only contains DialTLS, so a similar DialTLSContext has been added to make http.Transport support context.
What's changed:
https://github.com/golang/net/blob/8e4df14915a2b0bef8fb1a2d5f67f1bcedc6ab31/http2/transport.go#L66-L88
This proposal only adds a new API, so there is no breaking change.
ref:
golang/net#123
https://go-review.googlesource.com/c/net/+/377114
The text was updated successfully, but these errors were encountered: