You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Matthias Behrens <ma...@gulp.de> on 2006/04/18 16:36:13 UTC

HTTP_X_FORWARDED_FOR in mod_proxy

hi

is there a way to overwrite the HTTP_X_FORWARDED_FOR instead of adding to
it?

the problem is that the content of this headerline is sometimes totally
chaotic so its very difficult to parse.
other possible solutions would be:

- to clear the HTTP_X_FORWARDED_FOR before processing the request. (dont
know how to do) or

- using a different header / env.variable to protokoll the original
ipaddress (dont know how to do it eather)

thx
matthias
www.gulp.de



Re: HTTP_X_FORWARDED_FOR in mod_proxy

Posted by Joshua Slive <jo...@slive.ca>.
On 4/20/06, Matthias Behrens <ma...@gulp.de> wrote:
> thx
>
> doesnt seem to work on 2.0
>
> its a 2.2 feature isnt it?
>

The "early" option, which may be necessary here, is a 2.2 feature.

Joshua.

AW: HTTP_X_FORWARDED_FOR in mod_proxy

Posted by Matthias Behrens <ma...@gulp.de>.
thx

doesnt seem to work on 2.0

its a 2.2 feature isnt it?

-----Ursprüngliche Nachricht-----
Von: jslive@gmail.com [mailto:jslive@gmail.com]Im Auftrag von Joshua
Slive
Gesendet: Mittwoch, 19. April 2006 18:48
An: dev@httpd.apache.org
Betreff: Re: HTTP_X_FORWARDED_FOR in mod_proxy


On 4/18/06, Matthias Behrens <ma...@gulp.de> wrote:
> hi
>
> is there a way to overwrite the HTTP_X_FORWARDED_FOR instead of adding to
> it?
>
> the problem is that the content of this headerline is sometimes totally
> chaotic so its very difficult to parse.
> other possible solutions would be:
>
> - to clear the HTTP_X_FORWARDED_FOR before processing the request. (dont
> know how to do) or
>
> - using a different header / env.variable to protokoll the original
> ipaddress (dont know how to do it eather)

The RequestHeader directive, with or without the "early" option, may
be able to clear the old X-Forwarded-For header.  Otherwise, you'll
need to edit the mod_proxy_http source to change the name of the
header.

Joshua.


Re: HTTP_X_FORWARDED_FOR in mod_proxy

Posted by Joshua Slive <jo...@slive.ca>.
On 4/18/06, Matthias Behrens <ma...@gulp.de> wrote:
> hi
>
> is there a way to overwrite the HTTP_X_FORWARDED_FOR instead of adding to
> it?
>
> the problem is that the content of this headerline is sometimes totally
> chaotic so its very difficult to parse.
> other possible solutions would be:
>
> - to clear the HTTP_X_FORWARDED_FOR before processing the request. (dont
> know how to do) or
>
> - using a different header / env.variable to protokoll the original
> ipaddress (dont know how to do it eather)

The RequestHeader directive, with or without the "early" option, may
be able to clear the old X-Forwarded-For header.  Otherwise, you'll
need to edit the mod_proxy_http source to change the name of the
header.

Joshua.

HTTP_X_FORWARDED_FOR in mod_proxy

Posted by Matthias Behrens <ma...@gulp.de>.
anyone?


-----Ursprüngliche Nachricht-----
Von: Matthias Behrens [mailto:matthias.behrens@gulp.de]
Gesendet: Dienstag, 18. April 2006 16:36
An: dev@httpd.apache.org
Betreff: HTTP_X_FORWARDED_FOR in mod_proxy


hi

is there a way to overwrite the HTTP_X_FORWARDED_FOR instead of adding to
it?

the problem is that the content of this headerline is sometimes totally
chaotic so its very difficult to parse.
other possible solutions would be:

- to clear the HTTP_X_FORWARDED_FOR before processing the request. (dont
know how to do) or

- using a different header / env.variable to protokoll the original
ipaddress (dont know how to do it eather)

thx
matthias
www.gulp.de