<?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: Caching Static Assets Made Simple with Nginx, Varnish, S3</title>
	<atom:link href="http://elwoodicious.com/2008/09/18/caching-static-assets-made-simple-with-nginx-varnish-s3/feed/" rel="self" type="application/rss+xml" />
	<link>http://elwoodicious.com/2008/09/18/caching-static-assets-made-simple-with-nginx-varnish-s3/</link>
	<description>Those who can make you believe absurdities can make you commit atrocities. —Voltaire</description>
	<lastBuildDate>Wed, 30 Nov 2011 11:58:23 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: stefancaunter</title>
		<link>http://elwoodicious.com/2008/09/18/caching-static-assets-made-simple-with-nginx-varnish-s3/comment-page-1/#comment-9352</link>
		<dc:creator>stefancaunter</dc:creator>
		<pubDate>Thu, 24 Sep 2009 02:35:07 +0000</pubDate>
		<guid isPermaLink="false">http://elwoodicious.com/?p=1074#comment-9352</guid>
		<description>nginx is less capable of negotiating specifics with the origin server. varnish is the best in class for header rewriting to control the client&#039;s behaviour too. nginx won&#039;t have any problem with lots of small images, it&#039;s designed to work with that - if that is the only issue I would use nginx and be done; it&#039;s the best reverse proxy and it&#039;s the best http server, no question. varnish is not an http server at all, but if you need to specify expiry, max-age and other headers, and want to control this for sites and directories and want to be able to use file extension, regular expressions and normalizing algorithms for site names, you need varnish.</description>
		<content:encoded><![CDATA[<p>nginx is less capable of negotiating specifics with the origin server. varnish is the best in class for header rewriting to control the client&#8217;s behaviour too. nginx won&#8217;t have any problem with lots of small images, it&#8217;s designed to work with that &#8211; if that is the only issue I would use nginx and be done; it&#8217;s the best reverse proxy and it&#8217;s the best http server, no question. varnish is not an http server at all, but if you need to specify expiry, max-age and other headers, and want to control this for sites and directories and want to be able to use file extension, regular expressions and normalizing algorithms for site names, you need varnish.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: james</title>
		<link>http://elwoodicious.com/2008/09/18/caching-static-assets-made-simple-with-nginx-varnish-s3/comment-page-1/#comment-9343</link>
		<dc:creator>james</dc:creator>
		<pubDate>Sat, 19 Sep 2009 22:16:21 +0000</pubDate>
		<guid isPermaLink="false">http://elwoodicious.com/?p=1074#comment-9343</guid>
		<description>We switched back to Apache to use passenger (haven&#039;t felt the urge to switch back to nginx because that would just make me dizzy) but I am sure that caching will be coming back up on my radar and I&#039;ll make sure to take a look at how nginx handles it.  :-D</description>
		<content:encoded><![CDATA[<p>We switched back to Apache to use passenger (haven&#8217;t felt the urge to switch back to nginx because that would just make me dizzy) but I am sure that caching will be coming back up on my radar and I&#8217;ll make sure to take a look at how nginx handles it.  <img src='http://elwoodicious.com/wp-includes/images/smilies/icon_biggrin.gif' alt=':-D' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Josh</title>
		<link>http://elwoodicious.com/2008/09/18/caching-static-assets-made-simple-with-nginx-varnish-s3/comment-page-1/#comment-9342</link>
		<dc:creator>Josh</dc:creator>
		<pubDate>Sat, 19 Sep 2009 21:46:41 +0000</pubDate>
		<guid isPermaLink="false">http://elwoodicious.com/?p=1074#comment-9342</guid>
		<description>Current nginx versions have caching functions built-in, so is varnish even necessary with the latest nginx versions?
Could you eventually post an example for a current version? :-)</description>
		<content:encoded><![CDATA[<p>Current nginx versions have caching functions built-in, so is varnish even necessary with the latest nginx versions?<br />
Could you eventually post an example for a current version? <img src='http://elwoodicious.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anton</title>
		<link>http://elwoodicious.com/2008/09/18/caching-static-assets-made-simple-with-nginx-varnish-s3/comment-page-1/#comment-9172</link>
		<dc:creator>Anton</dc:creator>
		<pubDate>Tue, 28 Jul 2009 09:56:31 +0000</pubDate>
		<guid isPermaLink="false">http://elwoodicious.com/?p=1074#comment-9172</guid>
		<description>Thanks a lot!

I was experiencing problems with bucket.s3.amazonaws.com approach too.

I think the problem is in varnish, because when using only nginx to cache content there is no problem. You can check it out here:

http://kpoxit.blogspot.com/2008/12/how-to-save-60-month-with-20-lines-of.html

Nginx relies on a filesystem for caching. And this is a huge trouble when dealing with lots of small images (avatars, etc). This is why I am trying varnish now.</description>
		<content:encoded><![CDATA[<p>Thanks a lot!</p>
<p>I was experiencing problems with bucket.s3.amazonaws.com approach too.</p>
<p>I think the problem is in varnish, because when using only nginx to cache content there is no problem. You can check it out here:</p>
<p><a href="http://kpoxit.blogspot.com/2008/12/how-to-save-60-month-with-20-lines-of.html" rel="nofollow">http://kpoxit.blogspot.com/2008/12/how-to-save-60-month-with-20-lines-of.html</a></p>
<p>Nginx relies on a filesystem for caching. And this is a huge trouble when dealing with lots of small images (avatars, etc). This is why I am trying varnish now.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: grantmichaels</title>
		<link>http://elwoodicious.com/2008/09/18/caching-static-assets-made-simple-with-nginx-varnish-s3/comment-page-1/#comment-8921</link>
		<dc:creator>grantmichaels</dc:creator>
		<pubDate>Fri, 17 Apr 2009 13:21:50 +0000</pubDate>
		<guid isPermaLink="false">http://elwoodicious.com/?p=1074#comment-8921</guid>
		<description>i&#039;m about to build something that needs this very kind of tooling, and since this is the second time i&#039;ve gleamed something useful from your site - one could not possible forget the header photo - i thought i&#039;d leave a note and say thanks ...</description>
		<content:encoded><![CDATA[<p>i&#8217;m about to build something that needs this very kind of tooling, and since this is the second time i&#8217;ve gleamed something useful from your site &#8211; one could not possible forget the header photo &#8211; i thought i&#8217;d leave a note and say thanks &#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Zerga Lyman</title>
		<link>http://elwoodicious.com/2008/09/18/caching-static-assets-made-simple-with-nginx-varnish-s3/comment-page-1/#comment-2875</link>
		<dc:creator>Zerga Lyman</dc:creator>
		<pubDate>Sun, 09 Nov 2008 20:08:26 +0000</pubDate>
		<guid isPermaLink="false">http://elwoodicious.com/?p=1074#comment-2875</guid>
		<description>Good job! Thank you!</description>
		<content:encoded><![CDATA[<p>Good job! Thank you!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

