Varnish, between Zeus and Apache
traian.bratucu at eea.europa.eu
Wed Mar 2 09:09:58 CET 2011
My guess is that Zeus may also set other headers that identify it to the apache module, and somehow get stripped by Varnish. You should check that out.
Otherwise another solution may be placing Varnish in front of Zeus, if that does not affect your cluster setup.
From: varnish-misc-bounces at varnish-cache.org [mailto:varnish-misc-bounces at varnish-cache.org] On Behalf Of Dan Gherman
Sent: Tuesday, March 01, 2011 5:55 PM
To: varnish-misc at varnish-cache.org
Subject: Varnish, between Zeus and Apache
I am confronting with this situation: I manage a Zeus load-balancer cluster who has Apache as a webserver on the nodes in the backend. When Zeus load-balances a connection to an Apache server or Apache-based application, the connection appears to originate from the Zeus machine.Zeus provide an Apache module to work around this. Zeus automatically inserts a special 'X-Cluster-Client-Ip' header into each request, which identifies the true source address of the request. Zeus' Apache module inspects this header and corrects Apache's calculation of the source address. This change is transparent to Apache, and any applications running on or behind Apache.
Now the issue is when I have Varnish between Zeus and Apache. Varnish will always "see" the connections coming from the Zeus load-balancer. Is there a way to have a workaround, like that Apache module, so I can then send to Apache the true source address of the request? My error.log is flooded with the usual messages " Ignoring X-Cluster-Client-Ip 'client_ip' from non-Load Balancer machine 'node_ip'
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the varnish-misc