Re%3A%20add%20req.http.x-forwarded-for%20header&In-Reply-To=%3C2465AAEEC8B8A242B26ED5F44BCA805F2609D265EB%40SM-CALA-VXMB04A.swna.wdpr.disney.com%3E

[Andreas Götzfried]

Hi Raul,

thanks for your answer! I checked vcl_recv but couldn't find anything
relevant. And i don't think this is the problem, because:

I.
nginx.https -> varnish
x-forwarded-for is logged in /var/log/varnish/varnish.log

II.
only varnish.http
x-forwarded-for isn't logged in /var/log/varnish/varnish.log

So this has to be a quite strange return statement that clears the
x-forwarded-for when the http request is received by varnish
externally, but leaves the header untouched when it's sent via nginx
(and this traffic is http as well).

I'll re-check the code again, but... :-/


Andreas