Project

General

Profile

Actions
Copy link

Feature #2064

closed

[PATCH] Add an option in mod_proxy_core to control X-Forwarded-For

Added by silverfire over 13 years ago. Updated almost 7 years ago.

Status:
Missing Feedback
Priority:
Low
Category:
mod_proxy_core
Target version:
1.5.0
ASK QUESTIONS IN Forums:

Description

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"

Files

lighttpd-1.5.x-mod_proxy_core_nontransparent.patch (2.97 KB) lighttpd-1.5.x-mod_proxy_core_nontransparent.patch silverfire, 2009-09-07 00:25
Actions
Copy link
 #1

Updated by gstrauss almost 7 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.

Actions
Copy link
 #2

Updated by gstrauss almost 7 years ago

  • Status changed from New to Missing Feedback

(awaiting feedback)

Actions
Copy link

Also available in: Atom