-
Notifications
You must be signed in to change notification settings - Fork 363
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow setting of trusted CIDR blocks for X-Forwarded-For #4489
Comments
A knob for configuring CIDR can be added to the
Given that the IP lists are updated only once a year, I believe it’s reasonable to just manually update the CTP whenever Cloudflare makes changes. cc @envoyproxy/gateway-maintainers |
+1 to a generic |
@arkodg I would like to contribute to this, please assign if help wanted. Thanks! |
This issue has been automatically marked as stale because it has not had activity in the last 30 days. |
Can we keep this open until the code is actually released (1.3.0?) with documentation? |
Description:
Last week Envoy just released support for trusted CIDR blocks when processing X-Forwarded-For headers.
It would be really useful to have a default configuration mode called "cloudflare" which would automatically load the IP ranges from these two dynamically updated lists:
Cloudflare IPv4 CIDR blocks: https://www.cloudflare.com/ips-v4/
Cloudflare IPv6 CIDR blocks: https://www.cloudflare.com/ips-v6/
[optional Relevant Links:]
envoyproxy/envoy#31831
https://github.com/envoyproxy/envoy/releases/tag/v1.32.0
The text was updated successfully, but these errors were encountered: