<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: HOWTO: log the user&#039;s IP, not the proxy&#039;s, in Lighttpd access log</title>
	<atom:link href="http://fak3r.com/2008/01/09/howto-log-the-users-ip-not-the-proxys-in-lighttpd-access-log/feed/" rel="self" type="application/rss+xml" />
	<link>http://fak3r.com/2008/01/09/howto-log-the-users-ip-not-the-proxys-in-lighttpd-access-log/</link>
	<description>look out honey, &#039;cause I&#039;m using technology</description>
	<lastBuildDate>Sat, 11 Feb 2012 04:52:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Remote Lighttpd Logging and Cloudflare/Reverse Proxy &#171; A No Nonsense Blog</title>
		<link>http://fak3r.com/2008/01/09/howto-log-the-users-ip-not-the-proxys-in-lighttpd-access-log/#comment-2626</link>
		<dc:creator>Remote Lighttpd Logging and Cloudflare/Reverse Proxy &#171; A No Nonsense Blog</dc:creator>
		<pubDate>Thu, 01 Sep 2011 22:50:12 +0000</pubDate>
		<guid isPermaLink="false">http://fak3r.com/2008/01/09/howto-log-users-ip-not-the-proxys-in-lighttpd-access-log/#comment-2626</guid>
		<description>[...] google, I found this accesslog.format = &#8220;%{X-Forwarded-For}i %l %u %t &#8221;%r&#8221; %&gt;s %b [...]</description>
		<content:encoded><![CDATA[<p>[...] google, I found this accesslog.format = &#8220;%{X-Forwarded-For}i %l %u %t &#8221;%r&#8221; %&gt;s %b [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bummer</title>
		<link>http://fak3r.com/2008/01/09/howto-log-the-users-ip-not-the-proxys-in-lighttpd-access-log/#comment-947</link>
		<dc:creator>Bummer</dc:creator>
		<pubDate>Sun, 07 Jun 2009 04:41:43 +0000</pubDate>
		<guid isPermaLink="false">http://fak3r.com/2008/01/09/howto-log-users-ip-not-the-proxys-in-lighttpd-access-log/#comment-947</guid>
		<description>Thanks! This is exactly what I was looking for...</description>
		<content:encoded><![CDATA[<p>Thanks! This is exactly what I was looking for&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bummer</title>
		<link>http://fak3r.com/2008/01/09/howto-log-the-users-ip-not-the-proxys-in-lighttpd-access-log/#comment-946</link>
		<dc:creator>Bummer</dc:creator>
		<pubDate>Sat, 06 Jun 2009 23:41:43 +0000</pubDate>
		<guid isPermaLink="false">http://fak3r.com/2008/01/09/howto-log-users-ip-not-the-proxys-in-lighttpd-access-log/#comment-946</guid>
		<description>Thanks! This is exactly what I was looking for...</description>
		<content:encoded><![CDATA[<p>Thanks! This is exactly what I was looking for&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bummer</title>
		<link>http://fak3r.com/2008/01/09/howto-log-the-users-ip-not-the-proxys-in-lighttpd-access-log/#comment-1639</link>
		<dc:creator>Bummer</dc:creator>
		<pubDate>Sat, 06 Jun 2009 23:41:00 +0000</pubDate>
		<guid isPermaLink="false">http://fak3r.com/2008/01/09/howto-log-users-ip-not-the-proxys-in-lighttpd-access-log/#comment-1639</guid>
		<description>Thanks! This is exactly what I was looking for...</description>
		<content:encoded><![CDATA[<p>Thanks! This is exactly what I was looking for&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: fak3r &#187; HOWTO: log the user&#8217;s IP, not the proxy&#8217;s, in nginx access log</title>
		<link>http://fak3r.com/2008/01/09/howto-log-the-users-ip-not-the-proxys-in-lighttpd-access-log/#comment-945</link>
		<dc:creator>fak3r &#187; HOWTO: log the user&#8217;s IP, not the proxy&#8217;s, in nginx access log</dc:creator>
		<pubDate>Mon, 19 Jan 2009 06:38:04 +0000</pubDate>
		<guid isPermaLink="false">http://fak3r.com/2008/01/09/howto-log-users-ip-not-the-proxys-in-lighttpd-access-log/#comment-945</guid>
		<description>[...] back in January I had a post about HOWTO: log the user&#8217;s IP, not the proxy&#8217;s, in Lighttpd access log, but today I switched that system to run nginx (actually nginx has been running since early this [...]</description>
		<content:encoded><![CDATA[<p>[...] back in January I had a post about HOWTO: log the user&#8217;s IP, not the proxy&#8217;s, in Lighttpd access log, but today I switched that system to run nginx (actually nginx has been running since early this [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: fak3r</title>
		<link>http://fak3r.com/2008/01/09/howto-log-the-users-ip-not-the-proxys-in-lighttpd-access-log/#comment-944</link>
		<dc:creator>fak3r</dc:creator>
		<pubDate>Thu, 31 Jul 2008 14:44:56 +0000</pubDate>
		<guid isPermaLink="false">http://fak3r.com/2008/01/09/howto-log-users-ip-not-the-proxys-in-lighttpd-access-log/#comment-944</guid>
		<description>@jt
I don&#039;t know of a way to do that, currently I&#039;m running nginx w/o varnish so I haven&#039;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.</description>
		<content:encoded><![CDATA[<p>@jt<br />
I don&#8217;t know of a way to do that, currently I&#8217;m running nginx w/o varnish so I haven&#8217;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.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: fak3r</title>
		<link>http://fak3r.com/2008/01/09/howto-log-the-users-ip-not-the-proxys-in-lighttpd-access-log/#comment-950</link>
		<dc:creator>fak3r</dc:creator>
		<pubDate>Thu, 31 Jul 2008 14:44:00 +0000</pubDate>
		<guid isPermaLink="false">http://fak3r.com/2008/01/09/howto-log-users-ip-not-the-proxys-in-lighttpd-access-log/#comment-950</guid>
		<description>@jt
I don&#039;t know of a way to do that, currently I&#039;m running nginx w/o varnish so I haven&#039;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.</description>
		<content:encoded><![CDATA[<p>@jt<br />
I don&#8217;t know of a way to do that, currently I&#8217;m running nginx w/o varnish so I haven&#8217;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.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jt</title>
		<link>http://fak3r.com/2008/01/09/howto-log-the-users-ip-not-the-proxys-in-lighttpd-access-log/#comment-943</link>
		<dc:creator>jt</dc:creator>
		<pubDate>Wed, 02 Apr 2008 03:30:50 +0000</pubDate>
		<guid isPermaLink="false">http://fak3r.com/2008/01/09/howto-log-users-ip-not-the-proxys-in-lighttpd-access-log/#comment-943</guid>
		<description>This works fine but I&#039;m getting the port # appended to the IP address. I&#039;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] &quot;GET /robots.txt HTTP/1.1&quot; 404 345 &quot;-&quot; &quot;Mozilla/5.0 (compatible; discobot/1.0; +http://discoveryengine.com/discobot.html)&quot;


AWStats treats IP&#039;s with the port #&#039;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&#039;d rather not have to parse &amp; fix the log files if possible.</description>
		<content:encoded><![CDATA[<p>This works fine but I&#8217;m getting the port # appended to the IP address. I&#8217;m setting the X-Forward-For in Varnish like this:</p>
<p>        # Capture the client IP address<br />
        remove req.http.X-Forwarded-For;<br />
        set req.http.X-Forwarded-For = client.ip;</p>
<p>And the accesslog.format in lighttpd as shown above. What I get in the lighttpd log is:</p>
<p>IPAddress:Port, IPAddress   like this:</p>
<p>208.96.54.73:51575, 208.96.54.73 &#8211; - [01/Apr/2008:23:27:41 -0400] &#8220;GET /robots.txt HTTP/1.1&#8243; 404 345 &#8220;-&#8221; &#8220;Mozilla/5.0 (compatible; discobot/1.0; +<a href="http://discoveryengine.com/discobot.html" rel="nofollow">http://discoveryengine.com/discobot.html</a>)&#8221;</p>
<p>AWStats treats IP&#8217;s with the port #&#8217;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&#8217;d rather not have to parse &amp; fix the log files if possible.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jt</title>
		<link>http://fak3r.com/2008/01/09/howto-log-the-users-ip-not-the-proxys-in-lighttpd-access-log/#comment-949</link>
		<dc:creator>jt</dc:creator>
		<pubDate>Wed, 02 Apr 2008 03:30:00 +0000</pubDate>
		<guid isPermaLink="false">http://fak3r.com/2008/01/09/howto-log-users-ip-not-the-proxys-in-lighttpd-access-log/#comment-949</guid>
		<description>This works fine but I&#039;m getting the port # appended to the IP address. I&#039;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] &quot;GET /robots.txt HTTP/1.1&quot; 404 345 &quot;-&quot; &quot;Mozilla/5.0 (compatible; discobot/1.0; +http://discoveryengine.com/discobot.html)&quot;


AWStats treats IP&#039;s with the port #&#039;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&#039;d rather not have to parse &amp; fix the log files if possible.</description>
		<content:encoded><![CDATA[<p>This works fine but I&#8217;m getting the port # appended to the IP address. I&#8217;m setting the X-Forward-For in Varnish like this:</p>
<p>        # Capture the client IP address<br />
        remove req.http.X-Forwarded-For;<br />
        set req.http.X-Forwarded-For = client.ip;</p>
<p>And the accesslog.format in lighttpd as shown above. What I get in the lighttpd log is:</p>
<p>IPAddress:Port, IPAddress   like this:</p>
<p>208.96.54.73:51575, 208.96.54.73 &#8211; - [01/Apr/2008:23:27:41 -0400] &#8220;GET /robots.txt HTTP/1.1&#8243; 404 345 &#8220;-&#8221; &#8220;Mozilla/5.0 (compatible; discobot/1.0; +<a href="http://discoveryengine.com/discobot.html" rel="nofollow">http://discoveryengine.com/discobot.html</a>)&#8221;</p>
<p>AWStats treats IP&#8217;s with the port #&#8217;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&#8217;d rather not have to parse &amp; fix the log files if possible.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anon</title>
		<link>http://fak3r.com/2008/01/09/howto-log-the-users-ip-not-the-proxys-in-lighttpd-access-log/#comment-942</link>
		<dc:creator>Anon</dc:creator>
		<pubDate>Wed, 09 Jan 2008 18:04:21 +0000</pubDate>
		<guid isPermaLink="false">http://fak3r.com/2008/01/09/howto-log-users-ip-not-the-proxys-in-lighttpd-access-log/#comment-942</guid>
		<description>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.</description>
		<content:encoded><![CDATA[<p>You can also do this with mod_extforward:<br />
<a href="http://trac.lighttpd.net/trac/wiki/Docs/ModExtForward" rel="nofollow">http://trac.lighttpd.net/trac/wiki/Docs/ModExtForward</a></p>
<p>With some caveats &#8230; modifying the conf file seems more straightforward.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

