-
All replies
-
Helpful answers
-
Dec 1, 2015 1:39 AM in response to situkakby Camelot,It sounds like you have the apache caching proxy enabled - this used to be called the Performance Cache, but it may be different now. The proxy sits in front of Apache, intercepting incoming requests and only passing cache misses to Apache. Since Apache sees the connection from the proxy, which is running on the same box, the IP address it sees is the IP address of the server.
There are a couple of ways of getting around it, and it's been a while since I've played with it, but the simplest may be to disable the proxy. It doesn't serve a huge purpose for most people. If you do want/need the cache then you need to adjust the logging to include the X-Forwarded-For headers instead of the client IP.
-
Dec 1, 2015 2:49 PM in response to Camelotby situkak,Hi Camelot,
Now I understand the cause, the proxy cache.
I'll try the X-Forwarded-For logging.
Thanks
Tac (OSX 10.11 + Server5.0.15)