Filed Oct 25, 05:09 IST; not yet triaged. Downstream report: cloudflared #1777 (05:03 IST). With go1.27.3 and x/net v0.61.0, an http2.Server{MaxConcurrentStreams: math.MaxUint32} passed to ServeConn advertises 250 in its initial SETTINGS frame. Values of 0, 250 and MaxInt32 behave as before, but MaxInt32+1 and MaxUint32 both fall back to 250. Building with -tags=http2legacy preserves 4294967295. The cause, which we confirmed in source: x/net's Go 1.27 wrapper converts the field with int(...) in HTTP2Config(), and net/http's internal setConfigDefaults replaces any value outside 1..MaxInt32 with the default of 250. No error or log is emitted, and the public field is still a uint32 with no documented upper bound. cloudflared 2026.10.3 sets MaxUint32 for its HTTP/2 tunnel server, so each tunnel connection is capped at 250 streams. The reporter had to ship a custom http2legacy build to production.
math.MaxInt32, or build with http2legacy, and add a test that reads the SETTINGS frame.