[PATCH] Add an option in mod_proxy_core to control X-Forwarded-For
Attached is a patch to mod_proxy_core.c made against r2533 snapshot.
Adds 'proxy-core.transparent' (enable/disable) to control whether lighttpd sends the X-Forwarded-For header to the backend instead of always sending it.
#default behavior (identical to original) -- X-Forwarded-For headers sent to backend proxy-core.transparent = "enable" #X-Forwarded-For not sent to backend proxy-core.transparent = "disable"
Updated by gstrauss about 3 years ago
Would you help us to understand the use case where it is important to omit this information?
X-Forwarded-For has its uses and so does the Forwarded HTTP extension (https://tools.ietf.org/html/rfc7239), not yet implemented in lighttpd, but which would need to be similarly restricted if X-Forwarded-For and X-Forwarded-Host and ... were restricted as you have requested above.
Also available in: Atom