envoyproxy / envoyproxy/gateway

Support for Forwarded header RFC7239

Offen
#2,288 2 Kommentare 4 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
kind/enhancement stale
Vorherrschende Sprache
Go
Sterne
3k
Forks
864
Ø Merge
2 T. 2 Std.
Gemergte PRs (30 T.)
140

Beschreibung

*Description*:
Having support for the Forwarded header would be really useful. The issue with relying on X-Forwarded-For is that those can be forged easily. The `Forwarded` header supports adding a secret key so that downstream sources can validate that the header actually coming from your proxy.

If there was a way to restrict the existing X-Forwarded-* headers so they only applied to certain IP ranges that would be great. If we could have a built-in option to dynamically load IP ranges from CloudFlare upon start (with a refresh once a week) that would be a really fantastic solution.

[optional *Relevant Links*:]
https://datatracker.ietf.org/doc/html/rfc7239
https://developers.cloudflare.com/support/troubleshooting/restoring-visitor-ips/restoring-original-visitor-ips/
https://www.cloudflare.com/ips/

Beitragsleitfaden

Für dieses Repository ist kein Beitragsleitfaden indexiert

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.