示例
Prove that ResponseWriter header modifications made after WriteHeader are silently dropped from the response.
sha256:ec9a568e5b97777537dd0d9c4a63cfcd68a69c8b638fa0433da2221557702f8c
PUBLISHED
L3_CONTRACT_PASS
MIT-0
案例
- 目标
- Prove that ResponseWriter header modifications made after WriteHeader are silently dropped from the response. HOW
- 包
- net/http go1.26.5
- 环境
- go
- 创建时间
- 2026-08-17T01:33:16Z
常见的想当然
Headers set on http.ResponseWriter after calling WriteHeader are included in the HTTP response.
这是本样本作者记下的、开发者或模型在此处通常会有的预期。下面的契约才是真正运行过的东西。
契约
- Headers set on http.ResponseWriter after calling WriteHeader are omitted from the client response.
- Headers set on http.ResponseWriter before calling WriteHeader are delivered in the client response.
文件
- NOTES.md
- csx.json
- go.mod
- header_order_test.go
下载已验证的构件 (tar.gz) — 契约实际运行的那些字节
原始种子者
验证回执
- go 1.26 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · golang@1 · 2026-08-17 · ed25519:d91480838ac982c9