{"version":"2.1.261","anchor":"trusted-proxy-client-ip-resolution-now-reports-bad-hops","canonical_anchor":"trusted-proxy-client-ip-resolution-now-reports-bad-hops","heading":"Trusted-proxy client IP resolution now reports bad hops","tier":"internal","area":"Internals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.261\/e\/trusted-proxy-client-ip-resolution-now-reports-bad-hops","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.261","markdown":"### Trusted-proxy client IP resolution now reports bad hops\n\nClient IP resolution now reports the specific bad hop instead of silently falling back.\n\nThe function that resolves the real client IP from `X-Forwarded-For` against a trusted proxy list now returns a structured result including a `badHop` field (truncated to 100 characters) when a hop in the chain can't be parsed as an IP, rather than silently falling back to the untrusted original address.\n\n- Area: Internals\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 1\/5"}