Skip to content

Conversation

@agrawroh
Copy link
Member

@agrawroh agrawroh commented Dec 4, 2025

Description

This PR adds a new ip_address_header which could be used to provide the client IP address instead of computing it using XFF hops. It's valuable in cases where we trust the first layer to correctly determine the client IP and then provide that as a header.


Commit Message: geoip: allow extracting the client IP address from a custom request header
Additional Description: Adds a new ip_address_header which could be used to provide the client IP address instead of computing it using XFF hops.
Risk Level: Low
Testing: Added Unit + Integration Tests
Docs Changes: Added
Release Notes: Added

@repokitteh-read-only
Copy link

As a reminder, PRs marked as draft will not be automatically assigned reviewers,
or be handled by maintainer-oncall triage.

Please mark your PR as ready when you want it to be reviewed!

🐱

Caused by: #42416 was opened by agrawroh.

see: more, trace.

@repokitteh-read-only
Copy link

CC @envoyproxy/api-shepherds: Your approval is needed for changes made to (api/envoy/|docs/root/api-docs/).
envoyproxy/api-shepherds assignee is @wbpcode
CC @envoyproxy/api-watchers: FYI only for changes made to (api/envoy/|docs/root/api-docs/).

🐱

Caused by: #42416 was opened by agrawroh.

see: more, trace.

…eader

Signed-off-by: Rohit Agrawal <rohit.agrawal@databricks.com>
@agrawroh agrawroh marked this pull request as ready for review December 4, 2025 18:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants