-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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
net/http/httptrace: Successive HTTP requests call trace function only once when using DefaultTransport #43953
Comments
from https://golang.org/pkg/net/http/httptrace/#ClientTrace , emphasis mine:
There are other hooks for determining if a connection is resused I believe this is working as intended |
Are you certain the connection isn't being reused? See https://pkg.go.dev/net/http#DefaultTransport |
@seankhliao It's not only |
adding
I get
|
Thanks. I think the docs weren't clear enough for me. But I still don't see why this initialization would behave differently
than this one:
Otherwise your previous comment does indeed clear my confusion. |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
What did you expect to see?
Infinite logs
What did you see instead?
I get only one line of log
I don't understand why the DefaultTransport behaves differently.
The text was updated successfully, but these errors were encountered: