<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments for Nginx, IMO</title>
	<atom:link href="http://cwells.net/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://cwells.net</link>
	<description>Of course it&#039;s just my opinion. I&#039;m here to make it yours.</description>
	<lastBuildDate>Mon, 04 Mar 2013 09:50:06 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>Comment on Why doesn&#8217;t Nginx support .htaccess files? by adityamenon</title>
		<link>http://cwells.net/2012/03/27/why-doesnt-nginx-support-htaccess-files/#comment-147</link>
		<dc:creator><![CDATA[adityamenon]]></dc:creator>
		<pubDate>Mon, 04 Mar 2013 09:50:06 +0000</pubDate>
		<guid isPermaLink="false">http://cwells.net/?p=71#comment-147</guid>
		<description><![CDATA[Thanks, that&#039;s a good overview and those are good points. An osCommerce site I was working on was a victim of a .htaccess attack a long time ago, so I can relate. I also picked up a nugget from here: better disable .htaccess completely in can&#039;t-help-but-Apache setups, and do the configuration from Apache&#039;s config file like gcbenison mentioned.]]></description>
		<content:encoded><![CDATA[<p>Thanks, that&#8217;s a good overview and those are good points. An osCommerce site I was working on was a victim of a .htaccess attack a long time ago, so I can relate. I also picked up a nugget from here: better disable .htaccess completely in can&#8217;t-help-but-Apache setups, and do the configuration from Apache&#8217;s config file like gcbenison mentioned.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on What features are missing in Nginx? by Alex</title>
		<link>http://cwells.net/2012/03/27/what-features-are-missing-in-nginx/#comment-31</link>
		<dc:creator><![CDATA[Alex]]></dc:creator>
		<pubDate>Sat, 08 Sep 2012 00:29:33 +0000</pubDate>
		<guid isPermaLink="false">http://cwells.net/?p=112#comment-31</guid>
		<description><![CDATA[Ideally, make configuration like

location *.jpg {
   ...
}

merge with configuration like

location /some/path {
...
}

for url like /some/path/some/file.jpg]]></description>
		<content:encoded><![CDATA[<p>Ideally, make configuration like</p>
<p>location *.jpg {<br />
   &#8230;<br />
}</p>
<p>merge with configuration like</p>
<p>location /some/path {<br />
&#8230;<br />
}</p>
<p>for url like /some/path/some/file.jpg</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on What features are missing in Nginx? by Alex</title>
		<link>http://cwells.net/2012/03/27/what-features-are-missing-in-nginx/#comment-30</link>
		<dc:creator><![CDATA[Alex]]></dc:creator>
		<pubDate>Fri, 07 Sep 2012 20:24:48 +0000</pubDate>
		<guid isPermaLink="false">http://cwells.net/?p=112#comment-30</guid>
		<description><![CDATA[Make Location directives inherit configurations as in:

location /user {
    # Configuration shared by anything that&#039;s &quot;below&quot; /user, unless
    # overriden by more specific location section
}

location /user/cgi {
    # Configuration that makes it different from what was already configured by &quot;location /user&quot; section.
    # Currently &quot;location /usr/cgi&quot; does not inherit what was configured by &quot;location /user&quot;.
    # And &quot;include&quot; directive is far from what is considered convinient.
}]]></description>
		<content:encoded><![CDATA[<p>Make Location directives inherit configurations as in:</p>
<p>location /user {<br />
    # Configuration shared by anything that&#8217;s &#8220;below&#8221; /user, unless<br />
    # overriden by more specific location section<br />
}</p>
<p>location /user/cgi {<br />
    # Configuration that makes it different from what was already configured by &#8220;location /user&#8221; section.<br />
    # Currently &#8220;location /usr/cgi&#8221; does not inherit what was configured by &#8220;location /user&#8221;.<br />
    # And &#8220;include&#8221; directive is far from what is considered convinient.<br />
}</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on What features are missing in Nginx? by wellsc</title>
		<link>http://cwells.net/2012/03/27/what-features-are-missing-in-nginx/#comment-25</link>
		<dc:creator><![CDATA[wellsc]]></dc:creator>
		<pubDate>Tue, 24 Jul 2012 17:12:35 +0000</pubDate>
		<guid isPermaLink="false">http://cwells.net/?p=112#comment-25</guid>
		<description><![CDATA[DSO&#039;s are slated for Nginx 2.0, which should be out next year.]]></description>
		<content:encoded><![CDATA[<p>DSO&#8217;s are slated for Nginx 2.0, which should be out next year.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Apache 2.4 &#8211; fast or fastest? by snabb</title>
		<link>http://cwells.net/2012/03/26/apache-2-4/#comment-24</link>
		<dc:creator><![CDATA[snabb]]></dc:creator>
		<pubDate>Tue, 24 Jul 2012 11:15:19 +0000</pubDate>
		<guid isPermaLink="false">http://cwells.net/?p=9#comment-24</guid>
		<description><![CDATA[You have very valid points here. After years of headaches from trying to tune Apache installations for optimal performance and to tolerating high request floods i looked at nginx. I have never needed to look back. Apache feels completely obsolete now.]]></description>
		<content:encoded><![CDATA[<p>You have very valid points here. After years of headaches from trying to tune Apache installations for optimal performance and to tolerating high request floods i looked at nginx. I have never needed to look back. Apache feels completely obsolete now.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on What features are missing in Nginx? by snabb</title>
		<link>http://cwells.net/2012/03/27/what-features-are-missing-in-nginx/#comment-23</link>
		<dc:creator><![CDATA[snabb]]></dc:creator>
		<pubDate>Tue, 24 Jul 2012 10:50:57 +0000</pubDate>
		<guid isPermaLink="false">http://cwells.net/?p=112#comment-23</guid>
		<description><![CDATA[It would be great if nginx had dynamic modules. Then OS distributions could package it the same way as for example the uwsgi Debian/Ubuntu package: the user can install exactly the modules that are needed and leave out extra clutter. Also users could compile additional un-packaged modules independently of the main package maintainer.

Currently the package maintainers need to pre-select a list of likely needed modules and build a couple of alternatives, such as nginx-light and nginx-full in Debian/Ubuntu. This is far from optimal.]]></description>
		<content:encoded><![CDATA[<p>It would be great if nginx had dynamic modules. Then OS distributions could package it the same way as for example the uwsgi Debian/Ubuntu package: the user can install exactly the modules that are needed and leave out extra clutter. Also users could compile additional un-packaged modules independently of the main package maintainer.</p>
<p>Currently the package maintainers need to pre-select a list of likely needed modules and build a couple of alternatives, such as nginx-light and nginx-full in Debian/Ubuntu. This is far from optimal.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why doesn&#8217;t Nginx support .htaccess files? by gcbenison</title>
		<link>http://cwells.net/2012/03/27/why-doesnt-nginx-support-htaccess-files/#comment-18</link>
		<dc:creator><![CDATA[gcbenison]]></dc:creator>
		<pubDate>Wed, 25 Apr 2012 16:00:15 +0000</pubDate>
		<guid isPermaLink="false">http://cwells.net/?p=71#comment-18</guid>
		<description><![CDATA[It&#039;s worth noting that the Apache developers themselves point out that there&#039;s nothing you can do in .htaccess that you can&#039;t do from Apache&#039;s configuration file; .htaccess is mainly about letting users without permission to edit the configuration files do a bit of configuration.  So users may be accustomed to doing things in .htaccess and not realize that there is another way.]]></description>
		<content:encoded><![CDATA[<p>It&#8217;s worth noting that the Apache developers themselves point out that there&#8217;s nothing you can do in .htaccess that you can&#8217;t do from Apache&#8217;s configuration file; .htaccess is mainly about letting users without permission to edit the configuration files do a bit of configuration.  So users may be accustomed to doing things in .htaccess and not realize that there is another way.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
