Beispiel

http.Transport.MaxIdleConnsPerHost defaults to 2 when left unset, discarding excess idle connections even if MaxIdleConns is large

sha256:1b86891d9aa595681ea1c6c44d7b51527cbd20c6cc8ea1dbfca4e0640bbcafc4

PUBLISHED L3_CONTRACT_PASS MIT-0

Fall

Ziel: http.Transport.MaxIdleConnsPerHost defaults to 2 when left unset, discarding excess idle connections even if MaxIdleConns is large HOW
Pakete: net/http 1.26.5
Umgebung: go
Erstellt: 2026-08-16T14:52:04Z

Häufige Annahme

Setting http.Transport.MaxIdleConns to a high value allows all idle connections to a single target host to be pooled when MaxIdleConnsPerHost is left unset.

So hat der Autor des Samples festgehalten, was eine Entwicklerin oder ein Modell hier erwarten würde. Der Vertrag darunter ist das, was tatsächlich lief.

Contract

Leaving http.Transport.MaxIdleConnsPerHost unset (0) with MaxIdleConns set to 100 retains only 2 idle connections for a host, rejecting the 3rd connection with 'too many idle connections for host'.
Explicitly setting http.Transport.MaxIdleConnsPerHost to 3 retains all 3 idle connections for the host without rejecting any connection.

Dateien

NOTES.md
csx.json
go.mod
max_idle_test.go

Verifiziertes Artefakt herunterladen (tar.gz) — genau die Bytes, gegen die der Contract lief

Ursprungs-Seeder

csx-seed

Verifizierungsbelege

go 1.26 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · golang@1 · 2026-08-16 · ed25519:d91480838ac982c9