January 30, 2013 11:13AM
Hey,

thx for the fast answer :-)

> The connection to varnish comes from the address 127.0.0.1. That's
> what it logs here.

> The connection to varnish comes from the address 192.168.0.1. That's
> what it logs here.

But why? The only difference is the proxy_pass statement:

proxy_pass http://127.0.0.1:80;
vs.
proxy_pass http://192.168.0.1:80;

No other changes were done, and no changes in varnish config.

> varnish could see the "true" remote_addr in the X-Real-IP: http header
> that you send, if it looked there.
>
> If you want varnish to log the contents of that header, or to log that
> instead of what it sees as the connecting ip address, you'll be better
> off to ask in a place where people know varnish.

Hm, would be interesting which param varnish checks. It can't be $remote_addr, so it has to be the address nginx proxies to (127.0.01 or 192.168.0.1). Very strange. So it seems to be a varnish problem? :-/


revirii
Subject Author Posted

proxy_pass to backend (varnish): delivered ip?

revirii January 30, 2013 10:33AM

Re: proxy_pass to backend (varnish): delivered ip?

Francis Daly January 30, 2013 10:54AM

Re: proxy_pass to backend (varnish): delivered ip?

revirii January 30, 2013 11:13AM

Re: proxy_pass to backend (varnish): delivered ip?

Francis Daly January 30, 2013 11:22AM

Re: proxy_pass to backend (varnish): delivered ip?

revirii January 31, 2013 02:13AM

Re: proxy_pass to backend (varnish): delivered ip?

Francis Daly January 31, 2013 06:48AM

Re: proxy_pass to backend (varnish): delivered ip?

Axel January 30, 2013 11:24AM

Re: proxy_pass to backend (varnish): delivered ip?

revirii January 31, 2013 01:40AM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 158
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready