Skip to content
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

Replace X-Forwarded-For/Via by Forwarded Standard #567

Open
kekkc opened this issue Aug 26, 2023 · 1 comment
Open

Replace X-Forwarded-For/Via by Forwarded Standard #567

kekkc opened this issue Aug 26, 2023 · 1 comment

Comments

@kekkc
Copy link

kekkc commented Aug 26, 2023

Hi,

new Cloudflare checkings fail if X-Forwarded-For/Via is spoofed. In addition sites discontinue to load with it, e.g. https://www.daz3d.com/forums/discussion/235556/mud-shaders . Problem: currently X-Forwarded-For/Via are both send with the same IP, although X-Forwarded-For should describe the client, while Via should describe the proxy.

However, the new standard header is forwarded and it's suggested to replace X-Forwarded-For/Via with Forwarded:
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Forwarded

X-Forwarded-For: 192.0.2.172
Forwarded: for=192.0.2.172

X-Forwarded-For: 192.0.2.43, "[2001:db8:cafe::17]"
Forwarded: for=192.0.2.43, for="[2001:db8:cafe::17]"

Would be awesome if this could be included in Chameleon.

EDIT: more & more standard application use forwarded instead of x-forwarded-*, e.g. HAProxy haproxy/haproxy#575

@sereneblue
Copy link
Owner

Thank @kekkc! I wasn't aware that there's a new standard for this. This is something I can add in a future update.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants