Repository navigation
fix: resolve real client IP behind Cloudflare and log rejected requests - #16
Merged
Merged
Conversation
Behind Cloudflare, the rightmost public address in X-Forwarded-For is a Cloudflare edge, so the 24h auto-ban hit the edge IP and blocked every visitor routed through it. clientIP now skips private addresses, Cloudflare's published ranges and operator-configured proxies (TRUSTED_PROXY_IPS) when walking the chain from the right. - strip the port from RemoteAddr when no forwarded header is present - move LoggingMiddleware outside the rate limiter so 403/429 are logged - add TRUSTED_PROXY_IPS to config and docker-compose Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
Fayupable
commented
Oct 13, 2026
Fayupable
left a comment
Owner
Author
There was a problem hiding this comment.
cf ipleri banlanmicak
Backend Coverage ReportStatus: PASS Measured on: domain, application/service, adapter/chesscom |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Behind Cloudflare, the rightmost public address in X-Forwarded-For is a Cloudflare edge, so the 24h auto-ban hit the edge IP and blocked every visitor routed through it. clientIP now skips private addresses, Cloudflare's published ranges and operator-configured proxies (TRUSTED_PROXY_IPS) when walking the chain from the right.