<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>fak3r &#187; lighttpd</title>
	<atom:link href="http://fak3r.com/tag/lighttpd/feed/" rel="self" type="application/rss+xml" />
	<link>http://fak3r.com</link>
	<description>look out honey, &#039;cause I&#039;m using technology</description>
	<lastBuildDate>Sat, 11 Feb 2012 05:25:38 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>HOWTO: log the user&#039;s IP, not the proxy&#039;s, in nginx access log</title>
		<link>http://fak3r.com/2008/12/18/howto-log-the-user%e2%80%99s-ip-not-the-proxy%e2%80%99s-in-nginx-access-log/</link>
		<comments>http://fak3r.com/2008/12/18/howto-log-the-user%e2%80%99s-ip-not-the-proxy%e2%80%99s-in-nginx-access-log/#comments</comments>
		<pubDate>Thu, 18 Dec 2008 18:55:27 +0000</pubDate>
		<dc:creator>phil</dc:creator>
				<category><![CDATA[geek]]></category>
		<category><![CDATA[howto]]></category>
		<category><![CDATA[debian]]></category>
		<category><![CDATA[lighttpd]]></category>
		<category><![CDATA[nginx]]></category>
		<category><![CDATA[varnish]]></category>

		<guid isPermaLink="false">http://www.fak3r.com/?p=1280</guid>
		<description><![CDATA[

So 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 year, I just got lazy on running Varnish) fronted again by Varnish.  I had the same [...]]]></description>
		<wfw:commentRss>http://fak3r.com/2008/12/18/howto-log-the-user%e2%80%99s-ip-not-the-proxy%e2%80%99s-in-nginx-access-log/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>HOWTO: Configure nginx for Debian / Ubuntu</title>
		<link>http://fak3r.com/2008/05/05/howto-configure-nginx-for-debian-ubuntu/</link>
		<comments>http://fak3r.com/2008/05/05/howto-configure-nginx-for-debian-ubuntu/#comments</comments>
		<pubDate>Mon, 05 May 2008 18:20:19 +0000</pubDate>
		<dc:creator>phil</dc:creator>
				<category><![CDATA[geek]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[apache]]></category>
		<category><![CDATA[lighttpd]]></category>
		<category><![CDATA[nginx]]></category>
		<category><![CDATA[unix]]></category>
		<category><![CDATA[webserver]]></category>

		<guid isPermaLink="false">http://www.fak3r.com/?p=779</guid>
		<description><![CDATA[

UPDATE: I&#8217;m reworking my config blending in the security ideas found on camomel.org they&#8217;re really thought things through on this, this should make for a very secure environment.
I&#8217;m always trying new software, and with the webserver I&#8217;ve moved from Apache 1.3 to 2.0 to 2.2, and then later I moved everything over to Lighttpd, which [...]]]></description>
		<wfw:commentRss>http://fak3r.com/2008/05/05/howto-configure-nginx-for-debian-ubuntu/feed/</wfw:commentRss>
		<slash:comments>12</slash:comments>
		</item>
		<item>
		<title>HOWTO: determine optimal fastcgi settings for Lighttpd</title>
		<link>http://fak3r.com/2008/02/28/howto-determine-optimal-fastcgi-settings-for-lighttpd/</link>
		<comments>http://fak3r.com/2008/02/28/howto-determine-optimal-fastcgi-settings-for-lighttpd/#comments</comments>
		<pubDate>Thu, 28 Feb 2008 17:50:58 +0000</pubDate>
		<dc:creator>phil</dc:creator>
				<category><![CDATA[geek]]></category>
		<category><![CDATA[howto]]></category>
		<category><![CDATA[fast-cgi]]></category>
		<category><![CDATA[lighttpd]]></category>
		<category><![CDATA[lighty]]></category>
		<category><![CDATA[max_procs]]></category>
		<category><![CDATA[optimize fastcgi]]></category>
		<category><![CDATA[php]]></category>
		<category><![CDATA[php5]]></category>
		<category><![CDATA[php_fcgi_children]]></category>
		<category><![CDATA[webserver]]></category>

		<guid isPermaLink="false">http://www.fak3r.com/2008/02/28/howto-determing-optimal-fastcgi-settings-for-lighttpd/</guid>
		<description><![CDATA[

Anyone building a server with a LAMP stack today has tons of options, mine have evolved to using Varnish -&#62; Lighttpd -&#62; Xcache -&#62; PHP5 -&#62; MySQL.  Once I had Lighttpd (aka Lighty) installed and running PHP pages I looked to optimize the configuration and push it as hard as possible for more speed. [...]]]></description>
		<wfw:commentRss>http://fak3r.com/2008/02/28/howto-determine-optimal-fastcgi-settings-for-lighttpd/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>HOWTO: use monit to keep Lighttpd and Varnish running</title>
		<link>http://fak3r.com/2008/02/19/howto-use-monit-to-keep-lighttpd-and-varnish-running/</link>
		<comments>http://fak3r.com/2008/02/19/howto-use-monit-to-keep-lighttpd-and-varnish-running/#comments</comments>
		<pubDate>Tue, 19 Feb 2008 19:51:00 +0000</pubDate>
		<dc:creator>phil</dc:creator>
				<category><![CDATA[geek]]></category>
		<category><![CDATA[howto]]></category>
		<category><![CDATA[debian]]></category>
		<category><![CDATA[lighttpd]]></category>
		<category><![CDATA[varnish]]></category>

		<guid isPermaLink="false">http://www.fak3r.com/2008/02/19/howto-use-monit-to-keep-lighttpd-and-varnish-running/</guid>
		<description><![CDATA[Thanks to a post from Steve over at debian-administration.org, I finally got around to setting up monit, the little monitoring app we use at work to keep things sane.  I was getting around to installing it at home, but it became more urgent when Varnish went down last week; without it running there&#8217;s nothing to [...]]]></description>
		<wfw:commentRss>http://fak3r.com/2008/02/19/howto-use-monit-to-keep-lighttpd-and-varnish-running/feed/</wfw:commentRss>
		<slash:comments>10</slash:comments>
		</item>
		<item>
		<title>HOWTO: log the user&#039;s IP, not the proxy&#039;s, in Lighttpd access log</title>
		<link>http://fak3r.com/2008/01/09/howto-log-the-users-ip-not-the-proxys-in-lighttpd-access-log/</link>
		<comments>http://fak3r.com/2008/01/09/howto-log-the-users-ip-not-the-proxys-in-lighttpd-access-log/#comments</comments>
		<pubDate>Wed, 09 Jan 2008 16:17:41 +0000</pubDate>
		<dc:creator>phil</dc:creator>
				<category><![CDATA[geek]]></category>
		<category><![CDATA[howto]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[access log]]></category>
		<category><![CDATA[http accelerator]]></category>
		<category><![CDATA[IP]]></category>
		<category><![CDATA[lighttpd]]></category>
		<category><![CDATA[lighty]]></category>
		<category><![CDATA[referring]]></category>
		<category><![CDATA[reverse proxy]]></category>
		<category><![CDATA[squid]]></category>
		<category><![CDATA[varnish]]></category>
		<category><![CDATA[x-forwarded-for]]></category>

		<guid isPermaLink="false">http://fak3r.com/2008/01/09/howto-log-users-ip-not-the-proxys-in-lighttpd-access-log/</guid>
		<description><![CDATA[When you run a webserver behind a reverse proxy or HTTP accelerator like Squid or Varnish, the webserver access logs will display the IP of the proxy (generally 127.0.0.1) instead of the end user&#8217;s IP.  This not only breaks any kind of tracking or reporting you want to run against your webserver logs, but it [...]]]></description>
		<wfw:commentRss>http://fak3r.com/2008/01/09/howto-log-the-users-ip-not-the-proxys-in-lighttpd-access-log/feed/</wfw:commentRss>
		<slash:comments>11</slash:comments>
		</item>
	</channel>
</rss>

