Ejemplo
Path-modifying middleware in chi like StripSlashes and RedirectSlashes must be registered at router-level via r.Use() before routes, because per-route r.With() executes only after radix tree matching and silently returns 404 on trailing slashes while post-route r.Use() panics loudly.
sha256:fcbcbadcffd8004b6fe3539b9a9137361e9b41cbe68ebbceaf6c9737b2888f7d
PUBLISHED
L3_CONTRACT_PASS
MIT-0
Caso
- Objetivo
- Path-modifying middleware in chi like StripSlashes and RedirectSlashes must be registered at router-level via r.Use() before routes, because per-route r.With() executes only after radix tree matching and silently returns 404 on trailing slashes while post-route r.Use() panics loudly. HOW
- Paquetes
- github.com/go-chi/chi/v5 v5.3.1
- Entorno
- go
- Creado
- 2026-08-17T01:26:03Z
Lo que suele suponerse
applying path-modifying middleware like StripSlashes per-route with r.With() strips trailing slashes for that specific route and serves a 200 OK response
El autor de la muestra anotó aquí lo que un desarrollador o un modelo esperaría. El contrato de abajo es lo que realmente se ejecutó.
Contrato
- assert per-route With(StripSlashes) fails with 404 on trailing slash requests because tree matching precedes route middleware
- assert router-level Use(StripSlashes) strips trailing slashes and serves 200 before tree matching
- assert per-route With(RedirectSlashes) fails with 404 while router-level Use(RedirectSlashes) returns 301
- assert calling Use after route registration panics with frozen middleware chain error
Archivos
- NOTES.md
- csx.json
- go.mod
- go.sum
- router_test.go
Descargar el artefacto verificado (tar.gz): los bytes exactos con los que se ejecutó el contrato
Seeder de origen
Recibos de verificación
- go 1.26 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · golang@1 · 2026-08-17 · ed25519:d91480838ac982c9