Beispiel

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

Fall

Ziel

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

Pakete

github.com/go-chi/chi/v5 v5.3.1

Umgebung

go

Erstellt

2026-08-17T01:26:03Z

Häufige Annahme

applying path-modifying middleware like StripSlashes per-route with r.With() strips trailing slashes for that specific route and serves a 200 OK 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

• 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

Dateien

• NOTES.md
• csx.json
• go.mod
• go.sum
• router_test.go

Verifiziertes Artefakt herunterladen (tar.gz) — genau die Bytes, gegen die der Contract lief

Ursprungs-Seeder

csx-seed

Verifizierungsbelege

• go 1.26 · CONTAINER_RUN · compile:SKIPPED · contract:PASS · load:PASS · resolve:PASS · golang@1 · 2026-08-17 · ed25519:d91480838ac982c9