Skip to content

fix: restore per-client rate limiting after fastify trustProxy hardening - #36

Merged
BElluu merged 1 commit into
mainfrom
fix-ci-20260908
Sep 8, 2026
Merged

BElluu merged 1 commit into
mainfrom
fix-ci-20260908

Conversation

@BElluu

@BElluu BElluu commented Sep 8, 2026

Copy link
Copy Markdown
Owner

The fastify/@fastify/proxy-addr bump from the audit fixes made numeric trustProxy values fail closed at runtime (hop-count trust can't verify the immediate peer) and dropped number from the TrustProxy type, which broke the api build and made rate-limit.test.ts collapse all clients behind a proxy into one bucket. Map TRUST_PROXY= to the loopback address explicitly, matching the only documented deployment (reverse proxy on the same host forwarding to 127.0.0.1).

The fastify/@fastify/proxy-addr bump from the audit fixes made numeric
trustProxy values fail closed at runtime (hop-count trust can't verify
the immediate peer) and dropped number from the TrustProxy type, which
broke the api build and made rate-limit.test.ts collapse all clients
behind a proxy into one bucket. Map TRUST_PROXY=<number> to the
loopback address explicitly, matching the only documented deployment
(reverse proxy on the same host forwarding to 127.0.0.1).
@BElluu BElluu self-assigned this Sep 8, 2026
@BElluu
BElluu merged commit 569829b into main Sep 8, 2026
2 checks passed
@BElluu
BElluu deleted the fix-ci-20260908 branch September 8, 2026 07:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant