[privoxy-devel] [ ijbswa-Feature Requests-2105617 ] {+add-header{X-Forwarded-For: Client-IP}}

[SourceForge.net <no...@so...>]

Feature Requests item #2105617, was opened at 2008-09-11 12:46
Message generated for change (Comment added) made by nobody
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=361118&aid=2105617&group_id=11118

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Configuration
Group: version 3.0
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Fabian Keil (fabiankeil)
Summary: {+add-header{X-Forwarded-For: Client-IP}}

Initial Comment:
Dear,

I'm setting up Privoxy version 3.0.8 like a URL-Filtering in intercept proxy mode. But the feature needed is to provide real client ip address to server.

Could you please give me sample for doing this?

Should it done by CLIENT-HEADER-TAGGER & {+add-header{X-Forwarded-For: XXX}}. But I don't know how is arguement attern.

I already tried version 3.0.6 it's OK in providing server the real client ip address but it's not support intercept proxy mode.

Thank you in advance.

Cheers,
Sanan K.

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2008-09-15 05:15

Message:
Dear fabiankeil,

I already done as your sugesstion. But changing transform field "Accept: "
instead of "Connection: " client header.

Thanks a lot,
Sanan K. 

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2008-09-13 14:06

Message:
fabiankeil,

Thank so much for your prompt response. I will try.

Cheers,
Sanan K.

----------------------------------------------------------------------

Comment By: Fabian Keil (fabiankeil)
Date: 2008-09-12 16:16

Message:
There currently is no clean way to add a
X-Forwarded-For header, so it looks like
we need a add-x-forwarded-for-header action.

As a workaround you could add the following
client-header filter to one of your filter
files:

CLIENT-HEADER-FILTER: x-forwarded-for-workaround Replaces any Connection
header with an "X-Forwarded-For:" header.
s@^Connection:.*$@X-Forwarded-For: $origin@iD
(The description should be one line, SF may split it in two.)

And add the following section to one of your action
files:

{+client-header-filter{x-forwarded-for-workaround}\
 +add-header{Connection: close}\
}
/


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=361118&aid=2105617&group_id=11118