<?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>Scott Yang's Playground &#187; nginx</title>
	<atom:link href="http://scott.yang.id.au/tag/nginx/feed/" rel="self" type="application/rss+xml" />
	<link>http://scott.yang.id.au</link>
	<description>Faith, Technology and Randomness in Life, According to Scott</description>
	<lastBuildDate>Thu, 09 Feb 2012 09:01:12 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Securing PHP-FastCGI on Nginx</title>
		<link>http://scott.yang.id.au/2011/04/securing-php-fastcgi-on-nginx/</link>
		<comments>http://scott.yang.id.au/2011/04/securing-php-fastcgi-on-nginx/#comments</comments>
		<pubDate>Fri, 08 Apr 2011 08:00:41 +0000</pubDate>
		<dc:creator>scotty</dc:creator>
				<category><![CDATA[Technology]]></category>
		<category><![CDATA[nginx]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[Security]]></category>

		<guid isPermaLink="false">http://scott.yang.id.au/?p=2042</guid>
		<description><![CDATA[Via Hacker News. Setting up PHP-FastCGI and nginx? Don’t trust the tutorials: check your configuration! I have in fact written quite a few tutorials and published automated scripts that are vulnerable. Seems the easiest way to prevent this issue is by adding a try_files statement (or a if (-f $request_filename) if Nginx -V &#60; 0.7.27) [...]]]></description>
			<content:encoded><![CDATA[<p>Via <a href="http://news.ycombinator.com/item?id=2421894">Hacker News</a>. <a href="https://nealpoole.com/blog/2011/04/setting-up-php-fastcgi-and-nginx-dont-trust-the-tutorials-check-your-configuration/">Setting up PHP-FastCGI and nginx? Don’t trust the tutorials: check your configuration!</a> I have in fact written quite a few tutorials and published automated scripts that are vulnerable. Seems the easiest way to prevent this issue is by adding a <code>try_files</code> statement (or a <code>if (-f $request_filename)</code> if Nginx -V &lt; 0.7.27) into <code>location ~ \.php</code> block. For example</p>
<pre class="code">
location ~ \.php$ { # For nginx -V &gt;= 0.7.27
  try_files $uri =404;
  fastcgi_pass localhost:8080;
  ...
}
location ~ \.php$ { # For nginx -V &lt; 0.7.27, i.e. Debian 5
  if (-f $request_filename) {
    fastcgi_pass localhost:8080;
  }
  ...
}
</pre>
]]></content:encoded>
			<wfw:commentRss>http://scott.yang.id.au/2011/04/securing-php-fastcgi-on-nginx/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>WordPress.com From LiteSpeed to Nginx</title>
		<link>http://scott.yang.id.au/2008/04/wordpresscom-from-litespeed-to-nginx/</link>
		<comments>http://scott.yang.id.au/2008/04/wordpresscom-from-litespeed-to-nginx/#comments</comments>
		<pubDate>Wed, 16 Apr 2008 00:43:58 +0000</pubDate>
		<dc:creator>scotty</dc:creator>
				<category><![CDATA[Technology]]></category>
		<category><![CDATA[litespeed]]></category>
		<category><![CDATA[nginx]]></category>
		<category><![CDATA[Open Source]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://scott.yang.id.au/2008/04/wordpresscom-from-litespeed-to-nginx/</guid>
		<description><![CDATA[shyam: Goodbye Litespeed, hello Nginx, says WordPress.com. Apparently the reason to ditch LiteSpeed for Nginx is, according to Matt M (but no quotes), that WordPress wants to run open source for their full stack. LiteSpeed is a nice (but expensive) async-IO based web server that provides full Apache compatibility (which is not that useful if [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://fatalerror.wordpress.com/2008/04/14/goodbye-litespeed-hello-nginx-wordpresscom/">shyam: Goodbye Litespeed, hello Nginx, says WordPress.com</a>. Apparently the reason to ditch <a href="http://litespeedtech.com/">LiteSpeed</a> for <a href="http://nginx.net/">Nginx</a> is, according to Matt M (but no quotes), that WordPress wants to run open source for their full stack. LiteSpeed is a nice (but expensive) async-IO based web server that provides full Apache compatibility (which is not that useful if you just want to serve a single app). Another blow to the proprietary software?</p>
]]></content:encoded>
			<wfw:commentRss>http://scott.yang.id.au/2008/04/wordpresscom-from-litespeed-to-nginx/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

