Author	SHA1	Message	Date
lif	ab6a5a6b6d	fix(api): reject requests with NUL bytes in URL (#869) ... ## Summary - Added `NulByteValidationMiddleware` to validate incoming requests - Returns 400 Bad Request when NUL bytes (%00) detected in URL path or query - Prevents PostgreSQL encoding errors from being exposed as 500 errors ## Before ``` GET /v0.1/servers?cursor=%00 → 500 Internal Server Error → "invalid byte sequence for encoding UTF8: 0x00" ``` ## After ``` GET /v0.1/servers?cursor=%00 → 400 Bad Request → "Invalid request: query parameters contain null bytes" ``` Fixes #862 Signed-off-by: majiayu000 <1835304752@qq.com> Co-authored-by: Radoslav Dimitrov <radoslav@stacklok.com>	2026-01-03 19:14:44 +02:00
adam jones	6bb62d160e	fix: add HTTP middleware to redirect trailing slash URLs to canonical form (#420) ... Resolves #419 where URLs with trailing slashes like `/v0/servers/` would return empty responses instead of proper data. **Changes**: - Added TrailingSlashMiddleware that redirects trailing slash URLs with 301 status - Preserves root path ('/') without redirecting - Uses HTTP 301 Moved Permanently to indicate canonical form - Added comprehensive test coverage for the middleware This follows REST API best practices and is consistent with how major Go web frameworks handle trailing slash normalization. Generated with [Claude Code](https://claude.ai/code) --------- Co-authored-by: claude[bot] <209825114+claude[bot]@users.noreply.github.com> Co-authored-by: adam jones <domdomegg@users.noreply.github.com>	2025-09-10 13:14:59 -07:00