Better HTTP/1 connection reuse in Go 1.27

Every new HTTPS connection costs several round trips before content moves: a TCP handshake to reach the server, then a TLS handshake to set up encryption. Go 1.27's HTTP client reuses idle HTTP/1 connections more aggressively, skipping most of that setup when programs make many requests. In the Go team's benchmark, 100 requests dropped from about 710 milliseconds to about 150.

Summary written with AI by HowTechMoves, based on reporting by go.dev.