Good day everyone. We've implemented Varnish in front of Cherokee. We did this to speed things up additionally via the caching provided by Varnish.
Having issues with the IP information when we put Varnish in front. If we run Varnish and bypass Cherokee going directly to our web server the IP information is fine. Similarly, if we eliminate Varnish and run Cherokee going directly to our web server the IP information is fine/correct. When running both Vanish and Cherokee, we see many requests end up with 127.0.0.1 as their remote IP (Cherokee and Varnish are on same machine so Varnish speaks to Cherokee on 127.0.0.1:81). Oddly, not all end up with the originating IP as 127.0.0.1. So remote IP info actually appears correctly. In Cherokee we have toggled Preserve Host Headers on and off and hard restarted Cherokee. Either way we notice no change in the REMOTE IP information. Both ways we seen many remote clients being reported as remote IP of 127.0.0.1 The Remote IP information we are gathering in our application server and I've checked our code and find no issues with it. Our code checks for X-Forwarded-For and logs it when available. Anyone seen the same problem before? I am fairly sure we experienced the same problem when testing SQUID out in similar capacity priort to Varnish. My guess here is that Cherokee is taking the CGI.REMOTE_ADDR or equivalent on requests and not utilizing the X-Forwarded-For when such is already set and available. Thanks! _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
