Sample
Prove that `http.Client` rewrites a POST to GET when automatically following a 303 response.
sha256:e5f8c640bc33cfca8cef511faf7729c3bfd091a0a0adb96e32e31e9e2bbac630
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Case
- Goal
- Prove that `http.Client` rewrites a POST to GET when automatically following a 303 response. HOW
- Packages
- net/http go1.26.5
- Environment
- go
- Created
- 2026-08-16T13:07:56Z
Commonly assumed
A POST request that receives a 303 See Other keeps its method and body through automatic redirect following.
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
Contract
- A default client must follow `StatusSeeOther` (`303`) by issuing the next request as `GET`, not as the original method.
- The follow-up request body from that redirect must be empty.
Files
- NOTES.md
- csx.json
- go.mod
- redirect_test.go
Download the verified artifact (tar.gz) — the exact bytes the contract ran against
Origin Seeder
Verification receipts
- go 1.26 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · golang@1 · 2026-08-16 · ed25519:d91480838ac982c9