x-forwarded-for problems since 2.1

[Poul-Henning Kamp]

In message <2903443B3710364B814B820238DDEF2CA761B637 at TIL-EXCH-01.netmatch.local
>, =?iso-8859-1?Q?Angelo_H=F6ngens?= writes:
>
>In my vcl_recv I have:
>
>remove req.http.X-Forwarded-For;
>set    req.http.X-Forwarded-For = req.http.rlnclientipaddr;
>
>Since I upgraded to 2.1 yesterday, the header is no longer sent to backends
>.. Any ideas?

In 2.1 we have moved X-F-F processing to the default VCL, you need
to make sure you do not hit that code if you want to do you own
X-F-F processing.

Poul-Henning

PS: I wonder if we should change the default.vcl to not touch an
existing X-F-F header by default ?  Input from the list ?

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk at FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.