sneak f438c10c0c Label request metrics by route, not by path (closes #254) ...

The metrics middleware gave the handler label each request's path, so
every new path added series that were never removed, and /metrics
listed encrypted URL tokens. The label is now the pattern of the chi
route the request matches, or "unmatched" for one that matches none.
The metrics library takes the label before calling the handler, so the
middleware asks the router with chi's Find which route matches.

The existing TestMetricsRecordsServedRequest now fails: it serves a
request outside any router and expects handler="/test", the path.
Changing it needs the owner's approval.

Model: opus-5-5

2026-10-15 01:45:21 +00:00

..

client_ip_internal_test.go

Resolve real client IP behind trusted proxies (closes #94)

2026-09-22 10:25:41 +02:00

metrics_internal_test.go

Test that metrics label requests by route, not path

2026-10-15 01:39:22 +00:00

middleware_internal_test.go

Remove unsafe-inline from the Content-Security-Policy (closes #125)

2026-10-04 18:58:40 +02:00

middleware.go

Label request metrics by route, not by path (closes #254)

2026-10-15 01:45:21 +00:00

request_id_internal_test.go

Return and pass on request IDs, and give /v1/e/ ETag, 304 and HEAD (closes #84)

2026-10-04 12:41:54 +02:00