<?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>Glen Lumanau &#187; nginx</title>
	<atom:link href="http://lumanau.web.id/tag/nginx/feed" rel="self" type="application/rss+xml" />
	<link>http://lumanau.web.id</link>
	<description>About Glen Lumanau</description>
	<lastBuildDate>Fri, 23 Jul 2010 10:08:00 +0000</lastBuildDate>
	<language></language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>A message “ ‘sys_errlist’ is deprecated; use ‘strerror’ or ‘strerror_r’ instead ”</title>
		<link>http://lumanau.web.id/2010/06/08/a-message-%e2%80%9c-%e2%80%98sys_errlist%e2%80%99-is-deprecated-use-%e2%80%98strerror%e2%80%99-or-%e2%80%98strerror_r%e2%80%99-instead-%e2%80%9d.html</link>
		<comments>http://lumanau.web.id/2010/06/08/a-message-%e2%80%9c-%e2%80%98sys_errlist%e2%80%99-is-deprecated-use-%e2%80%98strerror%e2%80%99-or-%e2%80%98strerror_r%e2%80%99-instead-%e2%80%9d.html#comments</comments>
		<pubDate>Tue, 08 Jun 2010 15:33:18 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Unix]]></category>
		<category><![CDATA[deprecated]]></category>
		<category><![CDATA[nginx]]></category>
		<category><![CDATA[sys_errlist]]></category>

		<guid isPermaLink="false">http://lumanau.web.id/?p=269</guid>
		<description><![CDATA[While building nginx version 0.7.66, 0.8.35 or higher on Linux the following warning messages are issued: warning: `sys_errlist' is deprecated; use `strerror' or `strerror_r' instead warning: `sys_nerr' is deprecated; use `strerror' or `strerror_r' instead This is normal: nginx has to use the deprecated sys_errlist[] and sys_nerr in signal handlers because strerror() and strerror_r() functions are [...]]]></description>
			<content:encoded><![CDATA[<p>While building nginx version 0.7.66, 0.8.35 or higher on Linux the following warning messages are issued:</p>
<blockquote>
<pre>warning: `sys_errlist' is deprecated;
    use `strerror' or `strerror_r' instead
warning: `sys_nerr' is deprecated;
    use `strerror' or `strerror_r' instead
</pre>
</blockquote>
<p>This is normal: nginx has to use the deprecated sys_errlist[] and  sys_nerr in signal handlers because strerror() and strerror_r() functions are not Async-Signal-Safe.</p>
<p>Source : <a href="http://nginx.org/en/docs/sys_errlist.html" target="_blank">Nginx</a></p>
]]></content:encoded>
			<wfw:commentRss>http://lumanau.web.id/2010/06/08/a-message-%e2%80%9c-%e2%80%98sys_errlist%e2%80%99-is-deprecated-use-%e2%80%98strerror%e2%80%99-or-%e2%80%98strerror_r%e2%80%99-instead-%e2%80%9d.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Nginx.net is using an Old Version?</title>
		<link>http://lumanau.web.id/2009/02/06/nginxnet-version.html</link>
		<comments>http://lumanau.web.id/2009/02/06/nginxnet-version.html#comments</comments>
		<pubDate>Fri, 06 Feb 2009 08:25:47 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Unix]]></category>
		<category><![CDATA[nginx]]></category>
		<category><![CDATA[version]]></category>

		<guid isPermaLink="false">http://www.lumanau.web.id/?p=173</guid>
		<description><![CDATA[By now I&#8217;m writing this post, nginx latest stable version is nginx-0.6.35 I tried to see which version is nginx.net using right now.. HTTP/1.1 200 OK Server: nginx/0.6.31 Date: Fri, 06 Feb 2009 08:21:44 GMT Content-Type: text/html Content-Length: 5675 Last-Modified: Mon, 02 Feb 2009 11:03:48 GMT Connection: keep-alive Accept-Ranges: bytes I think there&#8217;s no such [...]]]></description>
			<content:encoded><![CDATA[<p>By now I&#8217;m writing this post, <a href="http://nginx.net">nginx</a> latest stable version is nginx-0.6.35</p>
<p>I tried to see which version is nginx.net using right now..</p>
<blockquote><p><span id="more-173"></span>HTTP/1.1 200 OK<br />
Server: <strong>nginx/0.6.31</strong><br />
Date: Fri, 06 Feb 2009 08:21:44 GMT<br />
Content-Type: text/html<br />
Content-Length: 5675<br />
Last-Modified: Mon, 02 Feb 2009 11:03:48 GMT<br />
Connection: keep-alive<br />
Accept-Ranges: bytes</p></blockquote>
<p>I think there&#8217;s no such a security upgrade since 0.6.31 to 0.6.35.. But if you want to make sure, please see the <a href="http://nginx.net/CHANGES-0.6">changelog</a></p>
]]></content:encoded>
			<wfw:commentRss>http://lumanau.web.id/2009/02/06/nginxnet-version.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Nginx rewrite rules for vBulletin + vbSEO</title>
		<link>http://lumanau.web.id/2009/01/16/nginx-rewrite-rules-for-vbulletin-vbseo.html</link>
		<comments>http://lumanau.web.id/2009/01/16/nginx-rewrite-rules-for-vbulletin-vbseo.html#comments</comments>
		<pubDate>Fri, 16 Jan 2009 04:56:00 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Unix]]></category>
		<category><![CDATA[forum]]></category>
		<category><![CDATA[how to]]></category>
		<category><![CDATA[nginx]]></category>
		<category><![CDATA[rewrite]]></category>
		<category><![CDATA[vbseo]]></category>
		<category><![CDATA[vbulletin]]></category>

		<guid isPermaLink="false">http://www.lumanau.web.id/?p=142</guid>
		<description><![CDATA[I searched on google and I think never heard about it. I actually have implement nginx + vbseo on the forum that I maintained. You can see them here and here How to create a nginx rewrite rule that is working for vBulletin and vbSEO plugins? This&#8217;s the nginx configuration that&#8217;s working for vBulletin and [...]]]></description>
			<content:encoded><![CDATA[<p>I searched on google and I think never heard about it.</p>
<p>I actually have implement nginx + vbseo on the forum that I maintained. You can see them <a href="http://forum.seleb.tv">here</a> and <a href="http://forum.kompas.com">here</a></p>
<p>How to create a nginx rewrite rule that is working for vBulletin and vbSEO plugins?</p>
<p><span id="more-142"></span>This&#8217;s the nginx configuration that&#8217;s working for vBulletin and vbSEO</p>
<blockquote><p>location / {<br />
rewrite ^/((urllist|sitemap_).*\.(xml|txt)(\.gz)?)$ /vbseo_sitemap/vbseo_getsitemap.php?sitemap=$1 last;</p>
<p>if ($request_filename ~ &#8220;\.php$&#8221; ) {<br />
rewrite ^(.*)$ /vbseo.php last;<br />
}</p>
<p>if (!-e $request_filename) {<br />
rewrite ^/(.*)$ /vbseo.php last;<br />
}</p>
<p>}</p></blockquote>
<p>Any comments please welcome <img src='http://lumanau.web.id/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
			<wfw:commentRss>http://lumanau.web.id/2009/01/16/nginx-rewrite-rules-for-vbulletin-vbseo.html/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Nginx Rewrite rules for WordPress MU with Wp Super Cache plugin enabled</title>
		<link>http://lumanau.web.id/2008/11/27/nginx-rewrite-rules-for-wordpressmu-with-wp-super-cache-plugin-enabled.html</link>
		<comments>http://lumanau.web.id/2008/11/27/nginx-rewrite-rules-for-wordpressmu-with-wp-super-cache-plugin-enabled.html#comments</comments>
		<pubDate>Thu, 27 Nov 2008 05:32:39 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Unix]]></category>
		<category><![CDATA[cache]]></category>
		<category><![CDATA[nginx]]></category>
		<category><![CDATA[rewrite]]></category>
		<category><![CDATA[wordpress mu]]></category>
		<category><![CDATA[wordpressmu]]></category>

		<guid isPermaLink="false">http://www.lumanau.web.id/?p=116</guid>
		<description><![CDATA[I&#8217;ve spending my time to search how wordpressMU on nginx can support WP Super Cache plugin By default they only giving us the rewrite rules for Apache Default nginx rewrite rules without WP Super Cache plugin rewrite ^.*/files/(.*) /wp-content/blogs.php?file=$1; if (!-e $request_filename) { rewrite ^.+?(/wp-.*) $1 last; rewrite ^.+?(/.*\.php)$ $1 last; rewrite ^ /index.php last; [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve spending my time to search how wordpressMU on nginx can support <a href="http://wordpress.org/extend/plugins/wp-super-cache/">WP Super Cache plugin</a></p>
<p>By default they only giving us the rewrite rules for <a href="http://www.apache.org">Apache</a></p>
<p>Default nginx rewrite rules without WP Super Cache plugin</p>
<blockquote><p>rewrite ^.*/files/(.*) /wp-content/blogs.php?file=$1;<br />
if (!-e $request_filename) {<br />
rewrite ^.+?(/wp-.*) $1 last;<br />
rewrite ^.+?(/.*\.php)$ $1 last;<br />
rewrite ^ /index.php last;<br />
}</p></blockquote>
<p>WP Super Cache plugin will not able to run with that rewrite rules. So now the question is, How can we make nginx rewrite rule to work with WP Super Cache plugin ?</p>
<p><span id="more-116"></span></p>
<p>Here&#8217;s my nginx config that&#8217;s running very well <img src='http://lumanau.web.id/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<blockquote><p>if (-f $request_filename) {<br />
break;<br />
}</p>
<p>if (-d $request_filename) {<br />
break;<br />
}</p>
<p>rewrite ^.*/files/(.*) /wp-content/blogs.php?file=$1;</p>
<p>if (!-e $request_filename) {<br />
rewrite ^.+/?(/wp-.*) $1 last;<br />
rewrite ^.+/?(/.*\.php)$ $1 last;<br />
rewrite ^(.+)$ /index.php?q=$1 last;<br />
}</p>
<p>set $supercache_file &#8221;;<br />
set $supercache_uri $request_uri;</p>
<p>if ($request_method = POST) {<br />
set $supercache_uri &#8221;;<br />
}</p>
<p>if ($query_string) {<br />
set $supercache_uri &#8221;;<br />
}</p>
<p>if ($http_cookie ~* &#8220;comment_author_|wordpress|wp-postpass_&#8221; ) {<br />
set $supercache_uri &#8221;;<br />
}</p>
<p>if ($supercache_uri ~ ^(.+)$) {<br />
set $supercache_file /wp-content/cache/supercache/$http_host/$1index.html;<br />
}</p>
<p>if (-f $document_root$supercache_file) {<br />
rewrite ^(.*)$ $supercache_file break;<br />
}</p></blockquote>
<p>Congratulations that you have successfully make your nginx to work with WP Super Cache plugin</p>
]]></content:encoded>
			<wfw:commentRss>http://lumanau.web.id/2008/11/27/nginx-rewrite-rules-for-wordpressmu-with-wp-super-cache-plugin-enabled.html/feed</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Install/Recompile nginx upstream hash module on Debian/Ubuntu</title>
		<link>http://lumanau.web.id/2008/11/27/install-recompile-nginx-upstream-hash-module-on-debianubuntu.html</link>
		<comments>http://lumanau.web.id/2008/11/27/install-recompile-nginx-upstream-hash-module-on-debianubuntu.html#comments</comments>
		<pubDate>Thu, 27 Nov 2008 05:06:46 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Unix]]></category>
		<category><![CDATA[install]]></category>
		<category><![CDATA[module]]></category>
		<category><![CDATA[nginx]]></category>
		<category><![CDATA[recompile]]></category>
		<category><![CDATA[upstream hash]]></category>

		<guid isPermaLink="false">http://www.lumanau.web.id/?p=114</guid>
		<description><![CDATA[I have described how to recompile/install nginx to support upstream hash module on Debian/Ubuntu before. But I don&#8217;t know why it&#8217;s not appear on search engine. You can read more about how to install/recompile nginx to support upstream hash module]]></description>
			<content:encoded><![CDATA[<p>I have described how to recompile/install nginx to support upstream hash module on Debian/Ubuntu before.</p>
<p>But I don&#8217;t know why it&#8217;s not appear on search engine.</p>
<p><span id="more-114"></span></p>
<p>You can read more about <a href="http://www.lumanau.web.id/2008/10/18/building-nginx-package-with-upstream-hash-module-on-debianubuntu.html">how to install/recompile nginx</a> to support <a href="http://wiki.codemongers.com/NginxHttpUpstreamRequestHashModule">upstream hash module</a></p>
]]></content:encoded>
			<wfw:commentRss>http://lumanau.web.id/2008/11/27/install-recompile-nginx-upstream-hash-module-on-debianubuntu.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Building nginx package with upstream hash module on Debian/Ubuntu</title>
		<link>http://lumanau.web.id/2008/10/18/building-nginx-package-with-upstream-hash-module-on-debianubuntu.html</link>
		<comments>http://lumanau.web.id/2008/10/18/building-nginx-package-with-upstream-hash-module-on-debianubuntu.html#comments</comments>
		<pubDate>Sat, 18 Oct 2008 06:22:14 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Unix]]></category>
		<category><![CDATA[debian]]></category>
		<category><![CDATA[nginx]]></category>
		<category><![CDATA[recompile]]></category>
		<category><![CDATA[ubuntu]]></category>
		<category><![CDATA[upstream hash]]></category>

		<guid isPermaLink="false">http://www.lumanau.web.id/?p=101</guid>
		<description><![CDATA[This’s how to recompile nginx with upstream hash module We need to recompile nginx to support upstream hash module. Because debian based nginx, doesn’t have this module loaded. And we need to download the module from here First of all, we need to install the software that’s needed to recompile a .deb packages apt-get install [...]]]></description>
			<content:encoded><![CDATA[<div class="post-content">
<p>This’s how to recompile nginx with <a href="http://wiki.codemongers.com/NginxHttpUpstreamRequestHashModule">upstream hash module</a></p>
<p>We need to recompile nginx to support upstream hash module. Because debian based nginx, doesn’t have this module loaded. And we need to download the module from <a href="http://www.lumanau.web.id/sources/nginx_upstream_hash-0.3.tar.gz">here</a></p>
<p>First of all, we need to install the software that’s needed to recompile a .deb packages</p>
<blockquote><p><em>apt-get install build-essential debhelper fakeroot</em></p></blockquote>
<p>Then go to /usr/local/src directory</p>
<blockquote><p><em>cd /usr/local/src</em></p></blockquote>
<p>Now we need to download the source package of nginx</p>
<blockquote><p><em>apt-get source nginx</em></p>
<p><em>apt-get build-dep nginx</em></p></blockquote>
<p>Before we go to the next step, we need to patch nginx with the patch given</p>
<blockquote><p><em>cd /usr/local/src/nginx-0.6.32/</em></p>
<p><em>patch -p0 &lt; /path/to/upstream/hash/directory/nginx.patch</em></p></blockquote>
<p>Then we go to nginx directory</p>
<blockquote><p><em>cd /usr/local/src/nginx-0.6.32/debian</em></p></blockquote>
<p>Edit rules to add upstream hash module</p>
<blockquote><p><em>vim rules</em></p></blockquote>
<p>Add <em>&#8211;add-module=/path/to/upstream/hash/directory</em></p>
<p>Go back to nginx directory</p>
<blockquote><p><em>cd ..</em></p></blockquote>
<p>Now it’s time for us to compile nginx and take a glass of coffee while waiting</p>
<blockquote><p><em>dpkg-buildpackage -rfakeroot</em></p></blockquote>
<p>If you found error like</p>
<blockquote><p><em>(WARNING: Failed to sign .dsc and .changes file)</em></p></blockquote>
<p>That means normal. Just ignore the error msg</p>
<p>Now go back to /usr/src directory</p>
<blockquote><p><em>cd /usr/src</em></p></blockquote>
<p>You should see a file called <strong><em>nginx_0.6.32-3_i386.deb</em></strong></p>
<p>Then install our new compiled nginx package</p>
<blockquote><p><em>dpkg -i </em><em>nginx_0.6.32-3_i386.deb</em></p></blockquote>
<p>Then lastly we add “fair” module on our nginx.conf</p>
<p>Example</p>
<blockquote><p><em>upstream backend {<br />
server server1;<br />
server server2;<br />
hash $http_cookie_username;<br />
}</em></p></blockquote>
<p>Congratulations that you have install nginx with fair proxy module on your debian <img class="wp-smiley" src="../wp-includes/images/smilies/icon_smile.gif" alt=":)" /></p>
<p>If you don&#8217;t want to do that installation, you can <a href="http://www.lumanau.web.id/debian/nginx_0.6.32-3_i386.deb">download directly</a> precompiled debian nginx package that&#8217;s already patched for upstream hash module</div>
]]></content:encoded>
			<wfw:commentRss>http://lumanau.web.id/2008/10/18/building-nginx-package-with-upstream-hash-module-on-debianubuntu.html/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Building a nginx package with fair proxy module on Debian/Ubuntu</title>
		<link>http://lumanau.web.id/2008/10/17/building-a-nginx-package-with-fair-proxy-module-on-debianubuntu.html</link>
		<comments>http://lumanau.web.id/2008/10/17/building-a-nginx-package-with-fair-proxy-module-on-debianubuntu.html#comments</comments>
		<pubDate>Fri, 17 Oct 2008 09:09:07 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Unix]]></category>
		<category><![CDATA[fair proxy module]]></category>
		<category><![CDATA[nginx]]></category>

		<guid isPermaLink="false">http://www.lumanau.web.id/?p=59</guid>
		<description><![CDATA[This&#8217;s how to recompile nginx with fair proxy module We need to recompile nginx to support fair proxy module. Because debian based nginx, doesn&#8217;t have this module loaded. And we need to download the module from here First of all, we need to install the software that&#8217;s needed to recompile a .deb packages apt-get install [...]]]></description>
			<content:encoded><![CDATA[<p>This&#8217;s how to recompile nginx with fair proxy module</p>
<p>We need to recompile nginx to support fair proxy module. Because debian based nginx, doesn&#8217;t have this module loaded. And we need to download the module from <a href="http://github.com/gnosek/nginx-upstream-fair/tree/master">here</a></p>
<p>First of all, we need to install the software that&#8217;s needed to recompile a .deb packages</p>
<blockquote><p><em>apt-get install build-essential debhelper fakeroot</em></p></blockquote>
<p><span id="more-59"></span></p>
<p>Then go to /usr/src directory</p>
<blockquote><p><em>cd /usr/src</em></p></blockquote>
<p>Now we need to download the source package of nginx</p>
<blockquote><p><em>apt-get source nginx</em></p>
<p><em>apt-get build-dep nginx</em></p></blockquote>
<p>$ mkdir /path/to/ngx_http_upstream_fair_module<br />
$ cd /path/to/ngx_http_upstream_fair_module<br />
$ curl -o ngx_http_upstream_fair_module.c  http://github.com/gnosek/nginx-upstream-fair/tree/master%2Fngx_http_upstream_fair_module.c?raw=true<br />
$ curl -o config  http://github.com/gnosek/nginx-upstream-fair/tree/master%2Fconfig?raw=true</p>
<p>Then we go to nginx directory</p>
<blockquote><p><em>cd /usr/src/nginx-0.6.32/debian</em></p></blockquote>
<p>Edit rules to add fair proxy module</p>
<blockquote><p><em>vim rules</em></p></blockquote>
<p>Add <em>&#8211;add-module=/path/to/ngx_http_upstream_fair_module</em></p>
<p>Go back to nginx directory</p>
<blockquote><p><em>cd ..</em></p></blockquote>
<p>Now it&#8217;s time for us to compile nginx and take a glass of coffee while waiting</p>
<blockquote><p><em>dpkg-buildpackage -rfakeroot</em></p></blockquote>
<p>If you found error like</p>
<blockquote><p><em>(WARNING: Failed to sign .dsc and .changes file)</em></p></blockquote>
<p>That means normal. Just ignore the error msg</p>
<p>Now go back to /usr/src directory</p>
<blockquote><p><em>cd /usr/src</em></p></blockquote>
<p>You should see a file called <strong><em>nginx_0.6.32-3_i386.deb</em></strong></p>
<p>Then install our new compiled nginx package</p>
<blockquote><p><em>dpkg -i </em><em>nginx_0.6.32-3_i386.deb</em></p></blockquote>
<p>Then lastly we add &#8220;fair&#8221; module on our nginx.conf</p>
<p>Example</p>
<blockquote><p><em>upstream backend {<br />
server server1;<br />
server server2;<br />
fair;<br />
}</em></p></blockquote>
<p>Congratulations that you have install nginx with fair proxy module on your debian <img src='http://lumanau.web.id/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
			<wfw:commentRss>http://lumanau.web.id/2008/10/17/building-a-nginx-package-with-fair-proxy-module-on-debianubuntu.html/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
