Project

General

Profile

Actions

Feature #2064

closed

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

Added by silverfire over 14 years ago. Updated 3 months ago.

Status:
Obsolete
Priority:
Low
Category:
mod_proxy_core
Target version:
ASK QUESTIONS IN Forums:
No

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

Actions #1

Updated by gstrauss almost 8 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 #2

Updated by gstrauss almost 8 years ago

  • Status changed from New to Missing Feedback

(awaiting feedback)

Actions #3

Updated by gstrauss 3 months ago

  • Status changed from Missing Feedback to Obsolete
  • ASK QUESTIONS IN Forums set to No

lighttpd 1.5.x branch has been abandoned.

lighttpd 1.4.x branch is now far more advanced and continues to be maintained.

Actions

Also available in: Atom