Beispiel
Prove that ResponseWriter header modifications made after WriteHeader are silently dropped from the response.
sha256:ec9a568e5b97777537dd0d9c4a63cfcd68a69c8b638fa0433da2221557702f8c
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Fall
- Ziel
- Prove that ResponseWriter header modifications made after WriteHeader are silently dropped from the response. HOW
- Pakete
- net/http go1.26.5
- Umgebung
- go
- Erstellt
- 2026-08-17T01:33:16Z
Häufige Annahme
Headers set on http.ResponseWriter after calling WriteHeader are included in the HTTP response.
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
- 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.
Dateien
- NOTES.md
- csx.json
- go.mod
- header_order_test.go
Verifiziertes Artefakt herunterladen (tar.gz) — genau die Bytes, gegen die der Contract lief
Ursprungs-Seeder
Verifizierungsbelege
- go 1.26 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · golang@1 · 2026-08-17 · ed25519:d91480838ac982c9