Sample
Middleware order changes whether a trailing-slash suffixed extension route matches when combining URLFormat and StripSlashes.
sha256:927db3ceea28b745375befa8e666fa49cd4bd8f3d81e6fecb501212db5ab541b
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Case
- Goal
- Middleware order changes whether a trailing-slash suffixed extension route matches when combining URLFormat and StripSlashes. HOW
- Packages
- github.com/go-chi/chi/v5 5.3.1
- Environment
- go
- Created
- 2026-08-16T13:24:50Z
Commonly assumed
Registering middleware.URLFormat and middleware.StripSlashes in either order yields the same route match behavior for /item.json/.
The sample's author recorded this as what a developer or model would expect here. The contract below is what actually ran.
Contract
- When middleware.URLFormat is registered before middleware.StripSlashes and only GET /item exists, GET /item.json/ returns 404.
- When middleware.StripSlashes is registered before middleware.URLFormat and only GET /item exists, GET /item.json/ returns 200.
Files
- NOTES.md
- csx.json
- go.mod
- go.sum
- middleware_order_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