x/net/http2: When using an http2.Transport with http.Client, TLS-related httptrace callbacks are not invoked

[hawkinsw]

First, thank you so much for the awesome httptrace functionality! It's a lifesaver. Second, I have a patch that fixes the issue here -- I am submitting an Issue first because

Excluding very trivial changes, all contributions should be connected to an existing issue.

and I want to make sure that I am following best practices. And now, on with the report:

What version of Go are you using (go version)?

$ go version
go version devel go1.19-e72cd2de38 Sun Mar 27 02:50:33 2022 -0400 linux/amd64

Note: Same behavior seen with the "Release" versions of 1.18.

Does this issue reproduce with the latest release?

Yes (see above)

What operating system and processor architecture are you using (go env)?

go env Output

$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/hawkinsw/.cache/go-build"
GOENV="/home/hawkinsw/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/hawkinsw/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/hawkinsw/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/home/hawkinsw/code/gosrc/goroot"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/home/hawkinsw/code/gosrc/goroot/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="devel go1.19-e72cd2de38 Sun Mar 27 02:50:33 2022 -0400"
GCCGO="gccgo"
GOAMD64="v1"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/hawkinsw/code/goresponsiveness/go.mod"
GOWORK=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build3289694319=/tmp/go-build -gno-record-gcc-switches"

What did you do?

A fully buildable and executable program (with flags for eliciting expected and unexpected behavior) is available at

https://github.com/hawkinsw/bugs/tree/main/httptrace

$ go build ./repro.go

To get expected behavior,
$ ./repro

To get unexpected behavior,
$ ./repro -bug

All code (and rationale behind it) in the MRE is commented. I look forward to submitting my (simple) patch and contributing!

I hope that all this information is helpful!
Will

[cherrymui]

cc @neild

[hawkinsw]

Thanks for updating the cc @cherrymui -- I am busy with ${DAY_JOB} for a few days and coming off an illness, but I have a patch ready and just need to get it properly formatted, etc. Thank you for your patience!

[gopherbot]

Change https://go.dev/cl/403114 mentions this issue: crypto/tls,net/http: consolidate TLS event logging

[gopherbot]

Change https://go.dev/cl/403077 mentions this issue: net/http, crypto/tls: centralize mgmt of TLS trace events

[hawkinsw]

Hello @cherrymui and @neild -- I have a patch submitted that will address this issue: https://go-review.googlesource.com/c/go/+/403077

I'd love to get your feedback on how to make the patch acceptable. I'd love to be able to help the community! Thank you for everything!