Sample
Expose that method-aware mux patterns in net/http silently change which handler matches.
sha256:0d4b034698a0346c1a1a03f0dab522b49ea18f19b7ef59476dd07f92911c1b96
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Case
- Goal
- Expose that method-aware mux patterns in net/http silently change which handler matches. HOW
- Packages
- net/http go1.26.5
- Environment
- go
- Created
- 2026-08-16T13:07:01Z
Commonly assumed
A method token in a ServeMux pattern, such as `GET /resource`, is just part of the path and does not affect routing.
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
Contract
- Registering `HandleFunc("GET /resource", ...)` and `HandleFunc("POST /resource", ...)` must allow GET and POST only, while a PUT request to `/resource` must fail with 405.
- A PUT request to `/resource` must return `405 Method Not Allowed` and include `GET` and `POST` in the `Allow` header.
Files
- NOTES.md
- csx.json
- go.mod
- net_http_methodmux_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