Comments on: HOWTO: log the user’s IP, not the proxy’s, in Lighttpd access log

By: fak3r

fak3r — Thu, 31 Jul 2008 14:44:56 +0000

@jt
I don’t know of a way to do that, currently I’m running nginx w/o varnish so I haven’t had that issue. I want to re-implement varnish in the mix soon, possibly with nginx acting as a proxy in front of it so it only sends dynamic requests back to varnish, while handling static requests by itself (nginx is said to be faster at serving static that varnish, which makes sense since varnish stores files via disk.

By: jt

jt — Wed, 02 Apr 2008 03:30:50 +0000

This works fine but I’m getting the port # appended to the IP address. I’m setting the X-Forward-For in Varnish like this:

# Capture the client IP address
remove req.http.X-Forwarded-For;
set req.http.X-Forwarded-For = client.ip;

And the accesslog.format in lighttpd as shown above. What I get in the lighttpd log is:

IPAddress:Port, IPAddress like this:

208.96.54.73:51575, 208.96.54.73 - - [01/Apr/2008:23:27:41 -0400] “GET /robots.txt HTTP/1.1″ 404 345 “-” “Mozilla/5.0 (compatible; discobot/1.0; +http://discoveryengine.com/discobot.html)”

AWStats treats IP’s with the port #’s as separate hosts obviously and I want to remove the port # from the ip address. Any way to configure Varnish to just send the client IP and not the port? I’d rather not have to parse & fix the log files if possible.

By: Anon

Anon — Wed, 09 Jan 2008 18:04:21 +0000

You can also do this with mod_extforward:
http://trac.lighttpd.net/trac/wiki/Docs/ModExtForward

With some caveats … modifying the conf file seems more straightforward.