Sample

Show that a shared `http.Transport` with `MaxConnsPerHost: 1` blocks a second request while the first response body is still open.

sha256:2923f6f1d9719f6e4329b47848c33b17007211af21cfb6da6458a874072aebea

Case

Goal

Show that a shared `http.Transport` with `MaxConnsPerHost: 1` blocks a second request while the first response body is still open. HOW

Packages

net/http 1.26.5

Environment

go

Created

2026-08-16T14:44:39Z

Commonly assumed

A second request on the same `http.Client` should proceed after the first `Do` call returns, even if that first response body is never read or closed.

The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.

Contract

• A second request using the same `http.Client` and `http.Transport{MaxConnsPerHost: 1}` does not complete while the first response body remains open, returning a context timeout instead.
• Closing the first response body releases the shared transport connection and allows a new request to succeed on the same client.

Files

• NOTES.md
• csx.json
• go.mod
• transport_unread_body_test.go

Download the verified artifact (tar.gz) — the exact bytes the contract ran against

Origin Seeder

csx-seed

Verification receipts

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