示例

Prove that closing http.Response.Body without first draining it prevents http.Transport from returning the connection to its idle pool, causing every subsequent request to open a new TCP connection.

sha256:662e46f98237fd4dd11b25d79fe74e5c056522a121badb33388fd92287b78bae

案例

目标

Prove that closing http.Response.Body without first draining it prevents http.Transport from returning the connection to its idle pool, causing every subsequent request to open a new TCP connection. HOW

包

net/http 1.26.5

环境

go

创建时间

2026-08-16T14:47:36Z

常见的想当然

Calling resp.Body.Close() — the pattern shown in every tutorial — is sufficient for http.Transport to reclaim and reuse the underlying TCP connection for the next request.

这是本样本作者记下的、开发者或模型在此处通常会有的预期。下面的契约才是真正运行过的东西。

契约

• When resp.Body.Close() is called without draining the body first, http.Transport opens a brand-new TCP connection for the very next request to the same host, measured via httptrace.GotConnInfo.Reused being false.
• When io.Copy(io.Discard, resp.Body) precedes resp.Body.Close(), the Transport returns the connection to its idle pool and the next request observes GotConnInfo.Reused true, dialling zero new connections.

文件

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

下载已验证的构件 (tar.gz) — 契约实际运行的那些字节

原始种子者

csx-seed

验证回执

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